Thursday, August 30, 2007

 
Posted by Picasa

Installation guide for 64 bit Oracle 9i on Linux 64 BIT.

Installation guide for 64 bit Oracle 9i on Linux 64 BIT।

Follow the steps below :

The following requirements need to be met for a successful installation of Oracle RDBMS Enterprise Edition version 9।2.0.7 on Red Hat Enterprise Linux AS/ES 4.0 (RHEL4) x86-64 (AMD64/EM64T)

This list is based upon a "default-RPMs" installation of RHEL AS/ES 4 update 1। Additional RPMs may be needed if a "less-than-default-RPMs" installation of RHEL AS/ES 4 update 1 (or newer) is performed. "Defining a "default RPMs" installation of the RHEL OS", When a newer "update" level is used, the RPM release numbers (such as 2.4-9.1.87) may be slightly higher (such as 2.4-9.1.93 or 2.4-9.2.37). This is fine so long as you are still using RHEL AS/ES 4 RPMs.

Next step is to check for the following packages, it should show the upper version or the same, if the lower version is there update it with the required one।

glibc-kernheaders-2.4-9.1.87.x86_64.rpm
http://fr.rpmfind.net/linux/RPM/fedora/3/x86_64/glibc-kernheaders-2.4-9.1.87.x86_64.html
glibc-headers-2.3.4-2.9.x86_64.rpm

http://rpm.pbone.net/index.php3/stat/4/idpl/4223322/com/glibc-headers-2.3.4-2.36.x86_64.rpm.html
glibc-devel-2.3.4-2.9.x86_64.rpm

http://rpm.pbone.net/index.php3/stat/4/idpl/4223321/com/glibc-devel-2.3.4-2.36.x86_64.rpm.html
glibc-devel-2.3.4-2.9.i386.rpm
http://rpm.pbone.net/index.php3/stat/4/idpl/4221742/com/glibc-devel-2.3.4-2.36.i386.rpm.html
Should be always 2.4.19
compat-gcc-32-3.2.3-47.3.x86_64.rpm

http://rpm.pbone.net/index.php3/stat/4/idpl/1882995/com/compat-gcc-32-3.2.3-47.3.x86_64.rpm.html
compat-gcc-32-c++-3.2.3-47.3.x86_64.rpm

http://rpm.pbone.net/index.php3/stat/4/idpl/1882996/com/compat-gcc-32-c++-3.2.3-47.3.x86_64.rpm.html
libstdc++-devel-3.4.3-22.1.x86_64.rpm

http://fr.rpmfind.net/linux/rpm2html/search.php?query=libstdc%2B%2B-devel
libaio-0.3.103-3.x86_64.rpm

http://rpm2html.osmirror.nl/white-box-linux/4/en/obsolete-updates/libaio-0.3.103-3.x86_64.html


You can find these rpm files on the following link : -
http://fr.rpmfind.net/linux/RPM/ByName.html

or

You can make a search for particular rpm file on the Google search engine and find the path to the downloadable site.



To check the RPM use following linux command : -

rpm -qa grep packagename

or

rpm -qa packagename.rpm


NOTE: i386 packages might require the --force option during installation if the 64-bit version of the same package is already installed। For example, "rpm -ivh --force glibc-devel-2.3.4-2.9.i386.rpm" may be required.

Run these commands

mv /usr/bin/gcc /usr/bin/gcc.orig
mv /usr/bin/g++ /usr/bin/g++.orig
ln -s /usr/bin/x86_64-redhat-linux-gcc32 /usr/bin/gcc
ln -s /usr/bin/x86_64-redhat-linux-g++32 /usr/bin/g++

Next, the following environment settings are required for the Unix / Linux user performing the installation (eg. oracle) :

to check type :- umask, thi s will show some value to you.
0022
% : type the :- echo $LD_ASSUME_KERNEL
2.4.19

To set LD_ASSUME_KERNEL

$export LD_ASSUME_KERNEL=2.4.19

Next, as root, modify your kernel settings in /etc/sysctl।conf as follows:

kernel।hostname = yourhost.yourdomain.com #<--- full qualified hostname !! kernel।domainname = yourdomain #<--- correct domain name !! fs.file-max = 327679 kernel।shmmax = 2147483648 ( In the case of 32-BIT it can not be more than4 GB but in the case of 64 BIT you can increase as much as required. required. kernel.sem = 250 32000 100 128 net.ipv4.ip_local_port_range = 1024 65000 Next, run the command "sysctl -p" as root to activate these new settings

Next, the "hostname" command should return the fully qualified hostname as shown below:

% hostname
hostname।domainname

Next, if any Java packages are installed on the system, unset any Java environment variables (for example JAVA_HOME)

The Unix user performing the installation (eg. oracle) should not have the Oracle install related variables set by default. For example setting ORACLE_HOME, PATH, LD_LIBRARY_PATH to include Oracle binaries in .profile, .bash_profile, .login file and /etc/profile.d should be completely avoided.

- Add the following settings to /etc/security/limits.conf

oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536

Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:
session required pam_limits.so
- Add the following lines to /etc/profile:
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
Error may occur during the installation, go with this …

$ORACLE_HOME/lib/ins_oemagent.mk

error invoking target install of makefile.
ignore this error and apply the patch 3119415, in my case I have simply ignored it and not applied the package.

$ORACLE_HOME/ctx/lib/ins_ctx.mk

error invoking target install of makefile.
for resolution go to the env_ctx.mk find 'INSO_LINK' type $(LDLIBFLAG)dl. Save the file and retry the error.

The solution is to edit the file $ORACLE_HOME/ctx/lib/env_ctx.mk and go to "INSO_LINK =", add a "$(LDLIBFLAG)dl" to the line and save it.
Here is the full line with the added "$(LDLIBFLAG)dl" flag:
INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m $(LDLIBFLAG)dl $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)

Error in invoking target install of makefile /db_path/sqlplus/lib/ins_sqlplus.mk"
Open the file "$ORACLE_HOME/bin/genclntsh" in an editor and find the line:LD_SELF_CONTAINED="-z defs"
Now replace it with LD_SELF_CONTAINED=" "

Next error will be at the time of linking the RDBMS ( ins_rdbms.mk ) file. Simply ignore it and let the installation continue.

Installation guide for 32 bit Oracle 9i on Red Hat 9 ( 32 Bit )

Follow the steps below :

Check following packages on the system

binutils-2.13.90.0.18-9.i386.rpm
cpp-3.2.2-5.i386.rpm
gcc-3.2.2-5.i386.rpm
glibc-devel-2.3.2-5.i386.rpm
glibc-kernheaders-2.4-8.10.i386.rpm
compat-libstdc++


Always ensure to use the latest RPM versions!

Creating Oracle User Accounts

su - root
groupadd dba # group of users to be granted with SYSDBA system privilege
groupadd oinstall # group owner of Oracle files
useradd -c "Oracle software owner" -g oinstall -G dba oracle
passwd oracle

Creating Oracle Directories

su - root
mkdir -p /software/app/oracle/product/9.2.0
chown -R oracle.oinstall /u01 ( /u01 is the path where u r installing the oracle ex. /u01, /software, /data, etc ).
This is for changing the ownership of the directory.
mkdir /var/opt/oracle
chown oracle.dba /var/opt/oracle
chmod 755 /var/opt/oracle

As root edit the "sysctl.conf"

kernel.shmmax = 1073741824
save the file
now on the prompt type ….
export LD_ASSUME_KERNEL = 2.4.1
echo $LD_ASSUME_KERNEL ( for checking ).
you may skip setting the oracle environment variables at presenet and can set these after the
installation of oracle.

Note :

switch to the oracle user to run the installer. / su - oracle
if u r system gets hang don't worry restart it, switch to oracle user and set the LD_ASSUME_KERNEL
again.
don't surf for removing the error xlib: … DISPLAY error can't connect to oracle server.
simply switch on with su - root and mount the media and log out from the root user then log on
with the oracle. ( this exercise is done because not to disturb the display variables ).
or
another reason is you have to start setup from the user who has the rights of DBA or authentication
to install the software.
or
simply give the rights to the oracle user for root.

Setting Oracle Environments Variables

edit the following lines in /home/oracle/.bash_profile
export ORACLE_BASE=/software/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/9.2.0
export ORACLE_SID=test
export ORACLE_TERM=xterm
export DISPLAY=oracleserver:0.0
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
export LD_LIBRARY_PATH
# Set shell search paths
export PATH=$PATH:$ORACLE_HOME/bin
switch to the oracle user to run the installer. / su - oracle

Run the Installer

if u r system gets hang don't worry restart it, switch to oracle user and set the LD_ASSUME_KERNEL again.








When you execute runInstaller from the Oracle 9iR2 (9.2.0) CD, you will get the following error message: Error occurred during initialization of VM
Unable to load native library: /tmp/OraInstall2003-10-25_03-14-57PM/jre/lib/i386/libjava.so:
symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
To resolve the __libc_wait symbol issue, download the p3006854_9204 patch p3006854_9204_LINUX.zip from
http://metalink.oracle.com. See bug 3006854 for more information. To apply the patch, run su - root
# unzip p3006854_9204_LINUX.zip
Archive: p3006854_9204_LINUX.zip
creating: 3006854/
inflating: 3006854/rhel3_pre_install.sh
inflating: 3006854/README.txt
# cd 3006854
# sh rhel3_pre_install.sh
Applying patch...
Patch successfully applied
#

NOTE: If you get the following error when you run rhel3_pre_install.sh: rhel3_pre_install.sh: line 36: gcc: command not foundThen you forgot to install or link gcc, see above. This means you can't start any binaries any more: # ls
ls: error while loading shared libraries: /etc/libcwait.so: cannot open shared object file: No such file or directory
# rm /etc/ld.so.preload
rm: error while loading shared libraries: /etc/libcwait.so: cannot open shared object file: No such file or directory
#To fix that, run the echo command which is a built-in shell command: # echo "" > /etc/ld.so.preload
rm /etc/ld.so.preloadAnd start over again.

if error occur's during the installation of oracle, simply go with this …

$ORACLE_HOME/lib/ins_oemagent.mk

error invoking target install of makefile.
ignore this error and apply the patch 3119415, in my case I have simply ignored it and not applied the package.

$ORACLE_HOME/ctx/lib/ins_ctx.mk

error invoking target install of makefile.
for resolution go to the file env_ctx.mk find 'INSO_LINK' insert one more variable in the line i.e.
$(LDLIBFLAG)
The solution is to edit the file $ORACLE_HOME/ctx/lib/env_ctx.mk and go to "INSO_LINK =", add a "$(LDLIBFLAG)dl" to the line and save it.
Here is the full line with the added "$(LDLIBFLAG)dl" flag: INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m $(LDLIBFLAG)dl $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)

last error may be at the time of configuration of service agent component that is just because your
Bitmap
oracle is not having the lastest patch for this, follow these setps to reconfigure the component
…..
If there is problem in the oracle initialization look for the initSID.ora file in the $ORACLE_HOME/admin/ORACLE_SID/pfile/initSID.ora and copy / rename to $ORACLE_HOME/dbs/initSID.ora

If the Agent Configuration Assistant did not run successfully during the Oracle installer session,
for service configrat then you will need to apply Oracle patches.

Go to Metalink and download patches 2617419 and 3238244. The first patch is really just a tool used
to apply the second patch. Unzip the two patch files.

Locate the directory containing a file called "opatch" in the area where you unzipped patch 2617419.

Put this directory, and /sbin onto your path with a command like:
$ PATH=$PATH:/home/oracle/patches/2617419/OPatch:/sbin

Go to the directory where you unzipped patch 3238244.

Run the following command to shut down the Oracle database:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SHUTDOWN
SQL> EXIT

Run the following command to apply patch 3238244:
$ opatch apply

Relink the intelligent agent with the following commands:
$ cd $ORACLE_HOME/network/lib
$ make -f ins_oemagent.mk install

Restart the database:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> EXIT

Start the intelligent agent:
$ agentctl start


Startup and Shutdown of the Oracle 9i Database

sqlplus: svrmgrl is not supported any more. You can now do everything with sqlplus.
For instance, to startup the database, run the following commands: oracle$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startupThe slash connects you to the schema owned by SYS. So in this example you will be connected to the schema owned by SYS with the privilege SYSDBA. SYSDBA gives you the following privileges: - sysoper privileges WITH ADMIN OPTION - create database - recover database until$ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshutYou can also use $ORACLE_HOME/bin/dbstart to startup the database, and $ORACLE_HOME/bin/dbshut to shutdown the database. You can place $ORACLE_HOME/bin/dbstart into the /etc/rc.d/rc.local boot script to automatically bring up the database at system boot time. To get $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut working, you need to change the third field for your Oracle SID in /etc/oratab from "N" to "Y".For example, for the Oracle SID "test" I changed the line in /etc/oratab from: test:/u01/app/oracle/product/9.2.0:Nto read: test:/u01/app/oracle/product/9.2.0:Y


For more information on oracle installation please refer to : -

http://www.puschitz.com/InstallingOracle9i.shtml