Linux Linux.PPC64 AIX
Solaris.SPARC Solaris.X64 HPUX HPIA HP.TRU64 Linux.IA64 Linux.xSeries
Windows Windows.X64 Windows.IA64
The following string shows an example of the path for the oraInst.loc file:
If the contents of the oraInst.loc file is empty, Oracle Universal Installer prompts you to create a new inventory.
Central Inventory
The Central Inventory contains the information relating to all Oracle products installed on a host. It contains the following files and folders:
Inventory File
This file lists all the Oracle homes installed on the node. For each Oracle home, it also lists the Oracle home name, home index, and nodes on which the home is installed. It also mentions if the home is an Oracle Clusterware home or a removed Oracle home. It can only detect removed Oracle homes created using Oracle Universal Installer version 11.2 and later. This file is present in the following location:
The following code shows a sample inventory.xml file:
Oracle recommends that you do not remove or manually edit this file as it could affect installation and patching.
Logs Directory
The Central Inventory contains installation logs in the following location:
For example, consider an attachHome operation performed on 17th, May, 2009 at 6.45AM. The associated log file would be created as follows:
Oracle Home Inventory
Oracle home inventory or local inventory is present inside each Oracle home. It only contains information relevant to a particular Oracle home. This file is located in the following location:
It contains the following files and folders:
Components File
This file contains the details about third-party applications like Java Runtime Environment (JRE) required by different Java-based Oracle tools and components. In addition, it also contains details of all the components as well as patchsets or interim patches installed in the Oracle home. This file is located here:
For an example of the components file, see «Sample Components File».
Home Properties File
This file contains the details about the node list, the local node name, and the Oracle Clusterware flag for the Oracle home. In a shared Oracle home, the local node information is not present. This file also contains the following information:
GUID — Unique global ID for the Oracle home
ARU ID — Unique platform ID. The patching and patchset application depends on this ID.
ARU ID DESCRIPTION — Platform description
The following example shows the Oracle home property file:
Table 2–3 lists the ARU_IDs for some platforms:
Источник
Как правильно установить переменную ORACLE HOME на Ubuntu 9.x?
у меня та же проблема, что и здесь:как восстановить или изменить пароль Oracle sysdba хотя я не потерял пароль, я ввел его дважды в сценарий настройки первоначально, а затем, когда я пошел в login (localhost:8080/apex, пароль не принят.
у меня нет ничего в базе данных, я просто хочу установить и использовать Oracle-XE. Я попытался apt-get удалить его дважды и переустановить, но если я попытаюсь запустить /etc/init.d/oracle-xe настроить снова, и я получаю «Oracle Database 10g Express Edition уже настроен», несмотря на второе удаление любых папок, которые я мог найти для Oracle XE.
Я попытался запустить sqlplus «/ as sysdba», но все, что я получаю:
пробовал: export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/sqlplus и все подкаталоги этого. Же каждый раз ошибка.
на что должен быть установлен ORACLE_HOME? Единственная ссылка, которую я видел либо просто скажите general или скажите выше до номера версии, затем «/db_1». У меня нет thave db_1.
Дайте мне знать если вам нужны любые разъяснения. Я не понимаю, что я сделал не так в этом процессе.
9 ответов
обычно файл msb не найден проблемы являются результатом проблемы настройки среды, но в вашем случае я немного подозрителен к установке (я никогда не использовал метод apt-get + configure).
чтобы проверить вменяемость установки:
У меня была та же проблема. В моей домашней папке у меня есть сценарий с именем sqlplus.sh это заботится об этом для меня, содержащий:
была та же проблема,
все, что мне нужно было сделать, чтобы установить переменную Oracle shell:
вы также должны установить LANG, найдите файлы с именем ‘sp1*.msb’, и установить, например, экспорт LANG=us, если вы найдете имя файла sp1us.старший бит. Сообщение об ошибке может быть лучше 🙂
ORACLE_HOME должен находиться на верхнем уровне структуры каталогов Oracle для установки базы данных. С этого момента, Оракул знает, как найти все остальные файлы. Например, вы получаете сообщение об ошибке, потому что Oracle не может найти файлы сообщений для сообщения об ошибках (должно быть в различных каталогах mesg ниже oracle home. Вместо вышеуказанного значения, которое вы даете, я бы попробовал
однажды я также получил тот же тип ошибки.
эта ошибка возникает, поскольку домашний путь установлен неправильно. Чтобы исправить это, если вы используете Windows, выполните следующий запрос:
или если вы используете Linux, то заменить set С export для приведенной выше команды так:
Это правильный способ, чтобы очистить эту ошибку.
экспортировать пути ORACLE_HOME=/u01 привода/приложение/оракул/продукта/10.2.0/данных db_1 для sqlplus / пользователя sysdba
Источник
2 Managing Oracle Homes
This chapter contains the following sections:
Introduction to Oracle Homes
The Oracle Universal Installer supports the installation of several active Oracle homes on the same host. An Oracle home is a directory into which all Oracle software is installed. This is pointed to by an environment variable. The Oracle home consists of the following:
Directory location where the products are installed
Corresponding system path setup
Program groups associated with the products installed in the home (where applicable)
Services running from the home
Introduction to Oracle Base
The Oracle base location is the location where Oracle Database binaries are stored. During installation, you are prompted for the Oracle base path. Typically, an Oracle base path for the database is created during Oracle Grid Infrastructure installation.
To prepare for installation, Oracle recommends that you only set the ORACLE_BASE environment variable to define paths for Oracle binaries and configuration files. Oracle Universal Installer (OUI) creates other necessary paths and environment variables in accordance with the Optimal Flexible Architecture (OFA) rules for well-structured Oracle software environments.
For example, with Oracle Database 11g, Oracle recommends that you do not set an Oracle home environment variable allow OUI to create it instead. If the Oracle base path is /u01/app/oracle, then by default, OUI creates the following Oracle home path:
Ensure that the paths you select for Oracle software, such as Oracle home paths and the Oracle base path, use only ASCII characters. Because installation owner names are used by default for some paths, this ASCII character restriction applies to user names, file names, and directory names.
Installing an Oracle Product
When you install an Oracle product, an Oracle home is created.
To install the product and create the Oracle home, perform the following steps:
Run Oracle Universal Installer.
In the Specify Home Details page, enter the Oracle home settings for the installation session. See Table 2-1 for a description of the fields in this section of the screen.
Continue with your installation. See Chapter 4, «Installing Products» for detailed information.
Table 2-1 Oracle Installation Settings for Specify Home Details page
| Settings | Functions |
|---|
Enter a name for the Oracle home. This name identifies the program group associated with a particular home and the Oracle services installed on this home. The Oracle home name must be between 1 to 127 characters long, and can include only alphanumeric characters and underscores.
Enter the full path to an Oracle home, or select an Oracle home from the drop-down list of existing Oracle homes. The Oracle home location is the directory where products are installed.
Data files may or may not be installed within an Oracle home. You can use the Browse button to choose a directory to install your product.
For Windows platforms, you must provide a valid path that is not in the Windows directory. Different homes cannot share the same location.
Oracle recommends that you designate an Oracle home location that is an empty or non-existing directory. If you select a directory for the Oracle home location that is not empty or already exists, you will be warned and asked if you want to proceed.
Removing Oracle Homes
To remove or deinstall Oracle homes, you can either use the Deinstall tool included with the Shiphome, or use the Deinstall utility available as part of the Oracle home.
To use the Deinstall tool, do the following to remove the Oracle home:
cd to DeinstallTool.
To use the Deinstall utility, do the following to remove the Oracle home:
Determining the Default Oracle Home
By default, when you start Oracle Universal Installer, the software searches your system to determine the default Oracle home where Oracle software should be installed.
In all cases, the ORACLE_HOME name is taken first from the command line if it is specified, or else from the response file if specified. If not specified, the value of DEFAULT_ORACLE_HOME_NAME in oraparam.ini is examined. Typically, the following convention is used for the name:
The ORACLE_HOME path is taken first from the command line if specified, or else from the response file if specified. If not, the ORACLE_HOME environment variable is used. If neither is specified, the following conventions are used for the path:
If ORACLE_BASE has been specified in the environment:
If ORACLE_BASE has not been specified in the environment:
Multiple Oracle Homes
Oracle Universal Installer supports the installation of several active Oracle homes on the same host as long as the products support this at run-time. Multiple versions of the same product or different products can run from different Oracle homes concurrently. Products installed in one home do not conflict or interact with products installed on another home. You can update software in any home at any time, assuming all Oracle applications, services, and processes installed on the target home are shut down. Processes from other homes may still be running.
Target Home
The Oracle home currently accessed by Oracle Universal Installer for installation or deinstallation is the target home. To upgrade or remove products from the target homes, these products must be shut down or stopped.
Oracle Universal Installer Inventory
The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.
Inventory information is stored in Extensible Markup Language (XML) format. The XML format enables easier diagnosis of problems and faster loading of data. Any secure information is not stored directly in the inventory. As a result, during removal of some products, you may be prompted to enter the required credentials for validation.
Oracle recommends placing the central inventory on a local file system that is not shared by other systems, since the central inventory is a system-specific inventory of the installations on this system. It is strongly recommended that you place the central inventory on a local disk so that installations from other systems do not corrupt the inventory. You should not place the central inventory in the Oracle Base.
Structure of the Oracle Universal Installer Inventory
The Oracle Universal Installer inventory has the following hierarchical structure:
Central Inventory Pointer File
Every Oracle software installation has an associated Central Inventory where the details of all the Oracle products installed on a host are registered. The Central Inventory is located in the directory that the inventory pointer file specifies. Each Oracle software installation has its own Central Inventory pointer file that is unknown to another Oracle software installation.
For Oracle homes sharing the same Central Inventory, the Oracle Universal Installer components perform all read and write operations on the inventory. The operations on the Central Inventory are performed through a locking mechanism. This implies that when an operation such as installation, upgrade, or patching occurs on an Oracle home, these operations become blocked on other Oracle homes that share the same Central Inventory.
Table 2–2 shows the location of the default inventory pointer file for various platforms:
Table 2-2 Default Inventory Pointer File Locations
| Platform | Default Inventory Pointer Location |
|---|
Linux Linux.PPC64 AIX
Solaris.SPARC Solaris.X64 HPUX HPIA HP.TRU64 Linux.IA64 Linux.xSeries
Windows Windows.X64 Windows.IA64
The following string shows an example of the path for the oraInst.loc file:
If the contents of the oraInst.loc file is empty, Oracle Universal Installer prompts you to create a new inventory.
Central Inventory
The Central Inventory contains the information relating to all Oracle products installed on a host. It contains the following files and folders:
Inventory File
This file lists all the Oracle homes installed on the node. For each Oracle home, it also lists the Oracle home name, home index, and nodes on which the home is installed. It also mentions if the home is an Oracle Clusterware home or a removed Oracle home. It can only detect removed Oracle homes created using Oracle Universal Installer version 11.2 and later. This file is present in the following location:
The following code shows a sample inventory.xml file:
Oracle recommends that you do not remove or manually edit this file as it could affect installation and patching.
Logs Directory
The Central Inventory contains installation logs in the following location:
For example, consider an attachHome operation performed on 17th, May, 2009 at 6.45AM. The associated log file would be created as follows:
Oracle Home Inventory
Oracle home inventory or local inventory is present inside each Oracle home. It only contains information relevant to a particular Oracle home. This file is located in the following location:
It contains the following files and folders:
Components File
This file contains the details about third-party applications like Java Runtime Environment (JRE) required by different Java-based Oracle tools and components. In addition, it also contains details of all the components as well as patchsets or interim patches installed in the Oracle home. This file is located here:
For an example of the components file, see «Sample Components File».
Home Properties File
This file contains the details about the node list, the local node name, and the Oracle Clusterware flag for the Oracle home. In a shared Oracle home, the local node information is not present. This file also contains the following information:
GUID — Unique global ID for the Oracle home
ARU ID — Unique platform ID. The patching and patchset application depends on this ID.
ARU ID DESCRIPTION — Platform description
The following example shows the Oracle home property file:
Table 2–3 lists the ARU_IDs for some platforms:
Источник
|
)
