Quick notes for installing Oracle on AIX
$ /etc/lsattr -El mem0 - to check the amount of RAM
$ lsps –l - to check the swap space
$ uname –a - to determine operating system information
$ instfix - a - to check which OS patches are installed
$ instfix -ivk APAR_number - to determine if a patch is installed
$ lslpp -l [fileset_name] - to determine which OS filesets are installed
$ lslpp –l - to list all installed filesets
$ xclock - to check Xmanager is working properly on local system
Following command determines if you are using correct executables
$ /usr/bin/which make
$ /usr/bin/which ar
$ /usr/bin/which ld
$ /usr/bin/which nm
Each command should point to the /usr/ccs/bin directory. If not, add
/usr/ccs/bin to the beginning of the PATH environment variable in the current
shell. See
# mkdev -1 aio0 to configure AIO manually
# smit aio To ensure AIO is configured at each system restart,
1) Select the menu item "Change/Show Characteristics of asynchronous I/O"
2) change the field "State to be configured at system restart" from defined to available
If AIO is not started during system startup, the Oracle server fails to start and these
error messages are displayed:
Could not load program Oracle
Symbol kaio_rdwr in /usr/lib/libc.a is undefined
Symbol iosuspend in /usr/lib/libc.a is undefined
Symbol acancel in /usr/lib/libc.a is undefined
Symbol listio in /usr/lib/libc.a is undefined
Could not load library libc.a(aio.o)
Error was: Exec.format error
The Oracle server uses a new interface called aio_nwait to perform asynchronous
I/O. If this interface is not present, an error message displays that is similar to this
one:
exec(): 0500-036 Cannot load program oracleSID because of the following errors:
0509-023 Symbol aio_nwait in oracle is not defined.
0509-026 System error: Cannot run a file that does not have a valid format
To find out which version of AIX you are running:
# lslpp -l bos.rte
Pre installation
Mount Points (Storage Devices) Oracle Universal Installer requires only two mount points: one for the software, and one for the database files.
UNIX Groups for OracleRoles A UNIX group is required for the OSDBA role. This book assumes that the group is named dba.
Special UNIX Group to own the Oracle Universal Installer oraInventory
All users installing Oracle products in any ORACLE_HOME must have oinstall set as their primary UNIX group. The Installer’s inventory is shared by all ORACLE_HOMEs on a system and is group writable. Install Oracle products with oinstall set as the current group.
UNIX Accounts ggh A UNIX account that is dedicated solely to installing and upgrading Oracle products. The account must have the oinstall group as its primary group and the OSDBA group as a secondary group. This book assumes the account is called oracle.
Permissions for File Creation Set umask to 022 for the oracle account.
Setup Tasks to Perform as the root User
Oracle8i requires at least two mount points:
_ one for the software
_ at least one for the database files
Create UNIX Groups for Database Administrators
During installation, two Oracle roles are created:
_ SYSDBA
_ SYSOPER
Create a UNIX Group for the Oracle Universal Installer Inventory
Use the smit utility to create a group named oinstall. The oinstall group will own the Oracle Universal Installer’s oraInventory directory. The oracle user account that runs the installation should have the oinstall group as its primary group.
Create a UNIX Account to Own Oracle Software
The oracle account is the UNIX user account that owns the Oracle8i software after
installation. Run Oracle Universal Installer with this user account.
Properties of the oracle Account
Login Name Any name, but this document refers to it as the oracle account.
Primary GID The oinstall group.
Secondary GID The dba group.
Home Directory Choose a home directory consistent with other user home directories. The home directory of the oracle account does not have to be the same as the ORACLE_HOME directory.
Login Shell The default shell can be /usr/bin/sh, /usr/bin/csh, or /usr/bin/ksh, but the samples in this document assume the Bourne shell (/usr/bin/sh).
Setup Tasks to Perform as the oracle User
Set Permissions for File Creation
Set umask to 022 for the oracle account to ensure group and other have read and execute permissions, but not write permission, on files installed.
1. Enter the umask command to check the current setting.
2. If the umask command does not return 022, set it in the.profile or.login file of the oracle account and execute the following command:
$ umask 022
Set Environment Variables
Before starting the Oracle Universal Installer, set the DISPLAY and PATH environment variables and any of the other variables as appropriate.
To set display varibles
For the Bourne or Korn shells:
On the server where the Oracle database will be installed, enter the following:
$ DISPLAY=workstation_name:0.0
$ export DISPLAY
In the session on your workstation:
$ xhost +server_name
For the C shell:
On the server where the Oracle database will be installed, enter the following:
% setenv DISPLAY workstation_name:0.0
In the session on your workstation:
% xhost +server_name
PATH
Set the shell’s search path to include the following:
_ $ORACLE_HOME/bin, /usr/bin, /etc, /usr/ccs/bin
_ the local bin directories /usr/lbin and /usr/local/bin, if it exists
ORACLE_BASE
ORACLE_BASE specifies the directory at the top of the Oracle software and administrative file structure. The value recommended for an OFAconfiguration is software_mount_point/app/oracle. For example: u01/app/oracle. If you are not using an OFA-compliant system, you do not have to set ORACLE_BASE, but it is highly recommended that you do set it.
ORACLE_HOME
ORACLE_HOME specifies the directory containing the Oracle software for a given release. The Optimal Flexible Architecture recommended value is: $ORACLE_BASE/product/release.
For example:
/u01/app/oracle/product/8.1.7. Ensure that the value of ORACLE_HOME points to a directory that does not
already contain any Oracle software prior to Oracle8i Release 1 (8.1.5) or Release 2 (8.1.6).
Update the Environment for Current Session
With a text editor, add the settings for the environment variables listed in "Set
Environment Variables" to the.profile or.login file of the oracle account.
For the Bourne or Korn shell:
$ ../.profile
For the C shell:
% source .login
$ lsps –l - to check the swap space
$ uname –a - to determine operating system information
$ instfix - a - to check which OS patches are installed
$ instfix -ivk APAR_number - to determine if a patch is installed
$ lslpp -l [fileset_name] - to determine which OS filesets are installed
$ lslpp –l - to list all installed filesets
$ xclock - to check Xmanager is working properly on local system
Following command determines if you are using correct executables
$ /usr/bin/which make
$ /usr/bin/which ar
$ /usr/bin/which ld
$ /usr/bin/which nm
Each command should point to the /usr/ccs/bin directory. If not, add
/usr/ccs/bin to the beginning of the PATH environment variable in the current
shell. See
# mkdev -1 aio0 to configure AIO manually
# smit aio To ensure AIO is configured at each system restart,
1) Select the menu item "Change/Show Characteristics of asynchronous I/O"
2) change the field "State to be configured at system restart" from defined to available
If AIO is not started during system startup, the Oracle server fails to start and these
error messages are displayed:
Could not load program Oracle
Symbol kaio_rdwr in /usr/lib/libc.a is undefined
Symbol iosuspend in /usr/lib/libc.a is undefined
Symbol acancel in /usr/lib/libc.a is undefined
Symbol listio in /usr/lib/libc.a is undefined
Could not load library libc.a(aio.o)
Error was: Exec.format error
The Oracle server uses a new interface called aio_nwait to perform asynchronous
I/O. If this interface is not present, an error message displays that is similar to this
one:
exec(): 0500-036 Cannot load program oracleSID because of the following errors:
0509-023 Symbol aio_nwait in oracle is not defined.
0509-026 System error: Cannot run a file that does not have a valid format
To find out which version of AIX you are running:
# lslpp -l bos.rte
Pre installation
Mount Points (Storage Devices) Oracle Universal Installer requires only two mount points: one for the software, and one for the database files.
UNIX Groups for OracleRoles A UNIX group is required for the OSDBA role. This book assumes that the group is named dba.
Special UNIX Group to own the Oracle Universal Installer oraInventory
All users installing Oracle products in any ORACLE_HOME must have oinstall set as their primary UNIX group. The Installer’s inventory is shared by all ORACLE_HOMEs on a system and is group writable. Install Oracle products with oinstall set as the current group.
UNIX Accounts ggh A UNIX account that is dedicated solely to installing and upgrading Oracle products. The account must have the oinstall group as its primary group and the OSDBA group as a secondary group. This book assumes the account is called oracle.
Permissions for File Creation Set umask to 022 for the oracle account.
Setup Tasks to Perform as the root User
Oracle8i requires at least two mount points:
_ one for the software
_ at least one for the database files
Create UNIX Groups for Database Administrators
During installation, two Oracle roles are created:
_ SYSDBA
_ SYSOPER
Create a UNIX Group for the Oracle Universal Installer Inventory
Use the smit utility to create a group named oinstall. The oinstall group will own the Oracle Universal Installer’s oraInventory directory. The oracle user account that runs the installation should have the oinstall group as its primary group.
Create a UNIX Account to Own Oracle Software
The oracle account is the UNIX user account that owns the Oracle8i software after
installation. Run Oracle Universal Installer with this user account.
Properties of the oracle Account
Login Name Any name, but this document refers to it as the oracle account.
Primary GID The oinstall group.
Secondary GID The dba group.
Home Directory Choose a home directory consistent with other user home directories. The home directory of the oracle account does not have to be the same as the ORACLE_HOME directory.
Login Shell The default shell can be /usr/bin/sh, /usr/bin/csh, or /usr/bin/ksh, but the samples in this document assume the Bourne shell (/usr/bin/sh).
Setup Tasks to Perform as the oracle User
Set Permissions for File Creation
Set umask to 022 for the oracle account to ensure group and other have read and execute permissions, but not write permission, on files installed.
1. Enter the umask command to check the current setting.
2. If the umask command does not return 022, set it in the.profile or.login file of the oracle account and execute the following command:
$ umask 022
Set Environment Variables
Before starting the Oracle Universal Installer, set the DISPLAY and PATH environment variables and any of the other variables as appropriate.
To set display varibles
For the Bourne or Korn shells:
On the server where the Oracle database will be installed, enter the following:
$ DISPLAY=workstation_name:0.0
$ export DISPLAY
In the session on your workstation:
$ xhost +server_name
For the C shell:
On the server where the Oracle database will be installed, enter the following:
% setenv DISPLAY workstation_name:0.0
In the session on your workstation:
% xhost +server_name
PATH
Set the shell’s search path to include the following:
_ $ORACLE_HOME/bin, /usr/bin, /etc, /usr/ccs/bin
_ the local bin directories /usr/lbin and /usr/local/bin, if it exists
ORACLE_BASE
ORACLE_BASE specifies the directory at the top of the Oracle software and administrative file structure. The value recommended for an OFAconfiguration is software_mount_point/app/oracle. For example: u01/app/oracle. If you are not using an OFA-compliant system, you do not have to set ORACLE_BASE, but it is highly recommended that you do set it.
ORACLE_HOME
ORACLE_HOME specifies the directory containing the Oracle software for a given release. The Optimal Flexible Architecture recommended value is: $ORACLE_BASE/product/release.
For example:
/u01/app/oracle/product/8.1.7. Ensure that the value of ORACLE_HOME points to a directory that does not
already contain any Oracle software prior to Oracle8i Release 1 (8.1.5) or Release 2 (8.1.6).
Update the Environment for Current Session
With a text editor, add the settings for the environment variables listed in "Set
Environment Variables" to the.profile or.login file of the oracle account.
For the Bourne or Korn shell:
$ ../.profile
For the C shell:
% source .login
Comments
Post a Comment