Development Client

The bitness of the Development Client's installer is one factor that determines which packages it can install. If the installer is 64-bits, it can install only 64-bit packages; if it is 32-bits, it can install only 32-bit packages. The bitness of the installer dictates where its logs will reside.

64-bit installer
C:\Program Files\Oracle\inventory\logs
32-bit installer
C:\Program Files (x86)\Oracle\inventory\logs

Three files will be created in the above directory:

installActions<date_time>.log
oraInstall<date_time>.err
oraInstall<date_time>.out

where <date_time> is the date and time that the installation started.

Note:

Determining which logs belong to a particular OUI installer. Because OUI is used for multiple Oracle products (for example, OEE database client, E1 Development Client, WebLogic Server Web Client (WLSH4A), WebSphere Server Web Client (WASH4A), and others), the logs directory will contain installation files for multiple products. To determine which installer created a set of files (.log, .err, and .out), you should edit the installActions<date_time>.log. The first line of the log has this form

Using paramFile: <installer_directory>\oraparam.ini

For example:

Using paramFile: \\dep_svr\e920\OneWorld Client Install\install\oraparam.ini

Use the path of the oraparam.ini file to determine the installer. In the above example, note that the installer is on the Deployment Server and is in this directory:

OneWorld Client Install\install

This indicates that the set of .log, .err, and .out files with the given time stamp were created by the Development Client installer.

When the installation completes, the logs relevant to the current installation are copied to the directory

<Oracle_Home_dir>\cfgtoollogs

For example:

C:\E920\cfgtoollogs

Additional logs are located in subdirectories under:

<Oracle_Home_dir>\cfgtoollogs

For example:

C:\E920\cfgtoollogs\oui