/build/static/layout/Breadcrumb_cap_w.png

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 11k  |  Created: 04/19/2002

Average Rating: 0
Oracle Client has 1 inventory records, 12 Questions, 0 Blogs and 3 links. Please help add to this by sharing more!

Deployment Tips (13)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 4 / 5 (Somewhat Difficult) based on 3 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (answer file driven)
124
Command Line
SETUP.EXE -RESPONSEFILE FILENAME [-SILENT] [-NOWELCOME]

FILENAME = Identifies the specific response file
-SILENT = Runs Oracle Universal Installer in complete silent mode. The Welcome window is suppressed automatically.
-NOWELCOME = Suppresses the Welcome window that appears during installation
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
121
Note
Silent installation response files are located on the installation CD in the \RESPONSE directory:

SVRTYPICAL.RSP = Oracle8i Enterprise Edition or Oracle8i Typical installation type
SVRMINIMAL.RSP = Oracle8i Enterprise Edition or Oracle8i Minimal installation type
SVRCUSTOM.RSP = Oracle8i Enterprise Edition or Oracle8i Custom installation type
OMIOMS.RSP = Oracle Management Infrastructure Oracle Management Server installation type
OMIOID.RSP = Oracle Management Infrastructure Oracle Internet Directory installation type
OMICUSTOM.RSP = Oracle Management Infrastructure Custom installation type
CLIENTADMIN.RSP = Oracle8i Client Administrator installation
CLIENTPROGMR.RSP = Oracle8i Client Programmer installation
CLIENTAPPUSER.RSP = Oracle8i Client Application User installation
CLIENTCUSTOM.RSP = Oracle8i Client Custom installation
DBCA.RSP = Oracle Database Configuration Assistant
NET8CA.RSP = Net8 Configuration Assistant
EMCA.RSP = Oracle Enterprise Manager Configuration Assistant to create a repository. Note that you cannot perform some advanced features, such as repository upgrade, repository deletion, and repository modification from silent, non-interactive mode. These advanced features must be performed through the interactive mode of Oracle Enterprise Manager Configuration Assistant.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
118
Note
If you are installing into Windows* 2000, one workaround recommendation by Oracle for this problem is:

- Install the latest Windows* 2000 Service Pack patch: http://www.microsoft.com/windows2000/downloads/

- Create a temporary directory on your Intel Pentium® 4 processor server.
- Copy the contents of the Oracle Server CD to the temporary directory you created.
- Search the directory structure created in step 2 for the existence of the filename SYMCJIT.DLL.
- Rename each copy of the SYMCJIT.DLL to SYMCJIT.OLD.
- Run the SETUP.EXE from the \TEMP\install\win32 directory and install Oracle 8.1.x.

Source: Intel Support
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
118
Note

If you do decide to repackage the 8.x client into .msi format, pay particular attention to ODBC components. eWall gives some very valuable tips on this page. This and some threads here at AppDeploy led me to discover that my delta with Wise Package Studio did not capture a necessary addition to the [Path] environmental variable. The package compiled fine and seemed clear of major errors, but would not finishing installing during testing. It would stall near the end as it would attempt to install the ODBC components. Manually adding "C:\oracle\ora81\bin" to the end of the [Path] variable using Windows Installer Editor resolved the issue. Without this, the package does not know where to find sqora32.dll and sqoras32.dll

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note
How I Did It
1) In an accessible share, create an “Oracle8” directory and copy the contents of the Oracle Client installation CD to this location.

2) Create a new directory named Oracle8\~Package in the root of the CD copy

3) Copy the INSTALL directory from the CD copy to the \\server\share\Oracle8\~Package folder

4) In the copy of ORAPARAM.INI, located at \\server\share\Oracle8\~Package\INSTALL, edit the Source, JRE_Location, and OUI_Location values to reflect the UNC path of the network shared source files

5) Copy the appropriate RSP file from the RESPONSE directory on the CD to \\server\share\Oracle8\~Package\INSTALL (i.e.: TYPICAL815.RSP)

6) Avoid potential Java Issues:

- Rename the following file to .OLD on your file server share: \\server\share\Oracle8\STAGE\COMPONENTS\ORACLE\SWD\JRE\1.1.7\1\DATAFILES\EXPANDED\WIN32\BIN\ SYMCJIT.DLL

- Edit the ''oraparam.ini'' file: change the JRE_MEMORY_OPTIONS value to read, “JRE_MEMORY_OPTIONS=-nojit -ms16m -mx32m”

7) Use the following batch file code to create your silent installation script:

<block>
if exist c:\oracle\TempInstall goto start
md c:\Oracle
md c:\Oracle\TempInstall
:start
Xcopy .\~Package\INSTALL c:\Oracle\ /E /I /Z
C:\Oracle\TempInstall\INSTALL\Win32\setup.exe -responseFile C:\Oracle\TempInstall\INSTALL\ClientAppUser.RSP -silent –nowelcome
</block>

You can wrap this into an MSI file by placing the files in their target location and using a custom action to trigger a batch file with the above lines. Control is released to the system long before the installation is complete, so keep this in mind when using IntelliMirror to assign such a package. A KiXscript, or other script, in a sleeping loop that looks for the Oracle client shortcuts to appear worked for me.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note
The Oracle Software Packager provides the ability to define all installation properties for your computer using a graphical interface.

Oracle Software Packager Documentation
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note
The Oracle installer is a java based application and by default invokes the java runtime with the JIT (just in time compiler) enabled. When installing to a Pentium 4 machine the JIT module which resides in "symcjit.dll" does not handle the processor id correctly and crashes. To workaround this problem, disable the JIT compiler option in the Oracle installation parameter file "ORAPARAM.INI" by adding the "-nojit" option as follows:

JRE_MEMORY_OPTIONS=-nojit -mx48m

The file is located in the "install" directory on the product CD. It is recommended that you first install the latest java runtime module from Sun (see link below.)
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note
If you are installing into Windows* 2000, one workaround recommendation by Oracle for this problem is:

- Install the latest Windows* 2000 Service Pack patch: http://www.microsoft.com/windows2000/downloads/

- Create a temporary directory on your Intel Pentium® 4 processor server.
- Copy the contents of the Oracle Server CD to the temporary directory you created.
- Search the directory structure created in step 2 for the existence of the filename SYMCJIT.DLL.
- Rename each copy of the SYMCJIT.DLL to SYMCJIT.OLD.
- Run the SETUP.EXE from the \TEMP\install\win32 directory and install Oracle 8.1.x.

Source: Intel Support
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note
How I Did It
1) In an accessible share, create an “Oracle8” directory and copy the contents of the Oracle Client installation CD to this location.

2) Create a new directory named Oracle8\~Package in the root of the CD copy

3) Copy the INSTALL directory from the CD copy to the \\server\share\Oracle8\~Package folder

4) In the copy of ORAPARAM.INI, located at \\server\share\Oracle8\~Package\INSTALL, edit the Source, JRE_Location, and OUI_Location values to reflect the UNC path of the network shared source files

5) Copy the appropriate RSP file from the RESPONSE directory on the CD to \\server\share\Oracle8\~Package\INSTALL (i.e.: TYPICAL815.RSP)

6) Avoid potential Java Issues:

- Rename the following file to .OLD on your file server share: \\server\share\Oracle8\STAGE\COMPONENTS\ORACLE\SWD\JRE\1.1.7\1\DATAFILES\EXPANDED\WIN32\BIN\ SYMCJIT.DLL

- Edit the ''oraparam.ini'' file: change the JRE_MEMORY_OPTIONS value to read, “JRE_MEMORY_OPTIONS=-nojit -ms16m -mx32m”

7) Use the following batch file code to create your silent installation script:

<block>
if exist c:\oracle\TempInstall goto start
md c:\Oracle
md c:\Oracle\TempInstall
:start
Xcopy .\~Package\INSTALL c:\Oracle\ /E /I /Z
C:\Oracle\TempInstall\INSTALL\Win32\setup.exe -responseFile C:\Oracle\TempInstall\INSTALL\ClientAppUser.RSP -silent –nowelcome
</block>

You can wrap this into an MSI file by placing the files in their target location and using a custom action to trigger a batch file with the above lines. Control is released to the system long before the installation is complete, so keep this in mind when using IntelliMirror to assign such a package. A KiXscript, or other script, in a sleeping loop that looks for the Oracle client shortcuts to appear worked for me.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note
I created the network share and response file and everything is working. However, I am building an unattended install CD and only need to install the application client portion of Oracle. Well to make a long story short I don't have enough space on my unattended Windows XP CD for all the Oracle files so I used the following method to only include the files I need.

Note: For this method to work you need to make sure that the last access time on files is being modified. Many users disable this feature to improve performance. You can use "dir /t:a <file>" to see the last access time on a file.

I my case the network Oracle install was setup some time ago so the last access time on all the files is several months back. After installing the Oracle client on a remote system all the files that were accessed had their last access time modified to the current date.

Now all I needed was a method to copy all the files with a specific last access time to a different folder while maintaining the directory structure. Well after writing a rather complex batch file to do this I found that the latest version of robocopy (Version XP010) included with the Windows Server 2003 Resource Kit Tools has this feature built in.

robocopy <source> <destination> /e /MAXLAD:YYYYMMDD


Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
If you're using WPS or ISAS you can "SetupCapture" this installation and create a big MSI out of it (instead of wrapping the Oracle Universal Installer and RSP, which is another solution already mentioned). Some tips:

* Don't have Wise put your ODBC entries in for you--just have it enter the Registry values directly. (Sure, it breaks Micro$oft's rules, but so do they, and this time it works better.)

* A few DLL's should not be set to self-register, including OraOLEDB.dll, OraOLEDBus.dll & OraOLEDBpus.dll. Catch 'em the first time you do a test install and go back and fix them. (You didn't really think you could get away with it working the first time, did you?)

* Thouroughly test for necessary permissions on NT/2k/XP systems... The many Java-based tools in Oracle8i leave .log and .properties files littered across the installation directory, and all these directories will need to have permissions opened up for the non-admin user.

* Rename the symcjit.dll (from the JRE 1.1.7 directory) to something else to avoid the Pentium 4 bug altogether.

* Don't put your TNSNAMES.ORA and SQLNET.ORA in your install; do it as a separate package. You know you're going to have to update it someday, and you don't want to recompile and reinstall the Oracle MSI just for that.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
Make sure all the options you set in the .RSP file have quotes around them, even if you don't have spaces in the path names!

eg: ORACLE_HOME="C:\orant"

If you still have problems, do a manual Custom install of ONLY the "Oracle Installation Products" (ie: untick everything else). When you try your silent install again, there will now be some logs file created in C:\Program Files\Oracle\Inventory\logs called "silentInstall.log" and "installActions.log" that will tell you what is going wrong.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Note

Installing 11g Patchset 1 resulted in a "failed to execute preCopy script" error in the Install Actions log. Got around this by adding -suppressPreCopyScript to the command line when installing the patch.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Oracle Client

Version

8

Questions & Answers (12)

Questions & Answers related to Oracle Oracle Client

Blogs (0)

Blog posts related to Oracle Oracle Client

Reviews (0)

Reviews related to Oracle Oracle Client

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ