Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
Exporting environment variable LD_ASSUME_KERNEL=2.4.1 will affect performance of Oracle 10g instance on Red Hat Linux starting with version 9, i.e. version with Native Posix Threads Implementation.
Since the Oracle Universal Installer (OUI) "runInstaller" is run from the oracle account,
some environment variables must be configured for this account before OUI is started.
Execute the following commands for the Bash shell which is the default shell on
Red Hat Linux (to verify your shell run: echo $SHELL):
su - oracle
export ORACLE_BASE=/u01/app/oracle
export ORACLE_SID=test
NOTE: If ORACLE_BASE is used, then Oracle recommends that you don't set the
ORACLE_HOME environment variable but that you choose the default path suggested by the OUI.
You can set and use ORACLE_HOME after you finished running OUI.
To have these environment variables set automatically each time you login as oracle,
you can add these environment variables to the ~oracle/.bash_profile file which is
the user startup file for the Bash shell on Red Hat Linux.
To have these environment variables set each time you login as oracle,
add the configuration of the above Oracle environment variables to the
~oracle/.bash_profile file if you use bash (echo $SHELL).
RHEL AS 3,Red Hat FC 2,1 have Native Posix Threads Implemented
and Oracle 10g supports NPTL
Hence, using old threads model as is advised at oracle-base.com will affect
performance of your Oracle 10g instance.
The target of publication is to highlight the optimal sequence of steps required to bring Oracle10g (10.2.0.1) ASM-database up on CentOS4.1 , placing ASM instance and serviced databases in different Oracle Homes. Oracleasm library install is done immediately after creating "oracle" linux account and "dba" group to be ready for ASM Instance creating during the first Installer run supposed to build it. ASM instance for volumes and volume's group management is created the first by Installer along with the volume's group for database supposed to be built during the second run of Installer and to be placed into recently created volume's group
View for details:-
http://bderzhavets.blogspot.com
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help