Oracle9i Installation Guide phần 7 ppsx

Configuration Tasks to Perform as the root User Post-Installation 4-3 $ORACLE_HOME/bin/ 755 rwxr-xr-x The oracle user should have read, write and execute privileges and all users should have read and execute privileges to this directory. The oracle executable, and the following executables: $ORACLE_HOME/bin/dbsnmp $ORACLE_ HOME/bin/oradism 6751 rws-r-s x The 6 sets the setuid bit and the setgid bit so the executables run as the oracle user and OSDBA group, regardless of who executes them. All other executables 755 rwxr-xr-x The oracle user should have read, write and execute privileges and all users should have read and execute privileges to this directory. $ORACLE_HOME/lib/ 755 rwxr-xr-x The oracle user should have read, write and execute privileges and all other users should have read and execute privileges to this directory. All files under $ORACLE_HOME/lib/ 644 rw-r r The oracle user should have read, write and execute privileges and the other users should have read-only privileges to these files. $ORACLE_HOME/rdbms/log 751 rwxr-x x The oracle user and ORAINVENTORY group have restricted access to files in the directory. The other users have execute privileges. Product subdirectories such as $ORACLE_HOME/sqlplus or $ORACLE_HOME/rdbms 751 rwxr-x x The oracle user and ORAINVENTORY group have restricted access to log files.The other users have execute privileges. Files in $ORACLE_HOME/sqlplus or $ORACLE_HOME/rdbms 644 rw-r r The oracle user should have read and write privileges and the other users should have read-only privileges to these files. Table 4–1 Access Permissions on Oracle Directories and Files (Cont.) Directories/Files Permissions Comments Configuration Tasks to Perform as the root User 4-4 Installation Guide Changing Group Membership of the Apache User After installing the Oracle9i database, the APACHE account access to the oraInventory directory needs to be removed in order to ensure database security. Perform the following tasks: 1. Create a new group to which no other group or user has access. 2. Assign ownership of this group to Apache. 3. Change the APACHE account primary Group Identifier (GID) from the one that has ownership of the oraInventory directory (typically ORAINVENTORY) to the new group name. Automating Database Startup and Shutdown for HP, Linux and Solaris (Optional) Oracle Corporation recommends that you configure your system to automatically start Oracle databases when your system starts up, and to shut down Oracle databases when your system shuts down. Automatic database startup and shutdown protects against improper shutdown of the database. The dbstart and dbshut scripts are located in the $ORACLE_HOME/bin directory and can be used to automate database startup and shutdown. The dbstart and dbshut scripts reference the same entries in the oratab file, so the scripts must apply to the same set of databases. For example, you cannot have the dbstart script automatically start up databases sid1, sid2, and sid3, and the dbshut script shut down only databases sid1 and sid2. You can, however, specify that the dbshut script shut down a set of databases while the dbstart script is not used at $ORACLE_HOME/network /trace 777 rwxrwxrwx or 730 rwx-wx The oracle user and members of the ORAINVENTORY group have access to trace files when 730 is used in the production environment. 777 allows broad access to view and create trace files during development. All files under product admin directories, like $ORACLE_HOME/rdbms /admin and $ORACLE_HOME/sqlplus /admin 644 -rw-r r SQL scripts should typically be run as the SYS user. Table 4–1 Access Permissions on Oracle Directories and Files (Cont.) Directories/Files Permissions Comments Configuration Tasks to Perform as the root User Post-Installation 4-5 all. To do this, include a dbshut entry in the system shutdown file but omit the dbstart entry from the system startup files. Perform the following tasks to set up the dbstart and dbshut scripts so that they are called at system startup. This process must be completed for every new database that you want to configure for automated startup and shutdown. 1. Edit the /var/opt/oracle/oratab file for Solaris and /etc/oratab file for HP and Linux. Database entries in the oratab file appears in the following format: ORACLE_SID:ORACLE_HOME:{Y|N} In the preceding command, Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. For each database that you want to start up, find the ORACLE_SID entry identified by the sid in the first field. Change the last field for each to Y. For Oracle Real Application Clusters installation, this entry appears in the following format: DB_NAME:ORACLE_HOME:{Y|N} In the preceding command, DB_NAME is the cluster database name. Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. 2. In the /etc/init.d directory, create a dbora script similar to the following, if it does not already exist. Be sure to give the full path of the dbstart utility. #!/bin/sh # Set ORA_HOME to be equivalent to the $ORACLE_HOME # from which you wish to execute dbstart and dbshut; # # Set ORA_OWNER to the user id of the owner of the # Oracle database in ORA_HOME. ORA_HOME=/u01/app/oracle/product/9.2.0.1.0 ORA_OWNER=oracle if [! -f $ORA_HOME/bin/dbstart] See Also: init command in your UNIX system documentation for more information on system startup and shutdown procedures. Configuration Tasks to Perform as the root User 4-6 Installation Guide then echo "Oracle startup: cannot start" exit fi case "$1" in ’start’) # Start the Oracle databases: # The following command assumes that the oracle login # will not prompt the user for any values su - $ORA_OWNER -c $ORA_HOME/bin/dbstart & ;; ’stop’) # Stop the Oracle databases: # The following command assumes that the oracle login # will not prompt the user for any values su - $ORA_OWNER -c $ORA_HOME/bin/dbshut & ;; esac 3. Create symbolic links to the dbora script in the appropriate run-level script directories, as follows: # ln -s /etc/init.d/dbora /etc/rc0.d/K10dbora # ln -s /etc/init.d/dbora /etc/rc3.d/S99dbora Automating Database Startup and Shutdown for AIX (Optional) Oracle Corporation recommends that you configure your system to automatically start Oracle databases when your system starts up, and to shut down Oracle databases when your system shuts down. Automatic database startup and shutdown protects against improper shutdown of the database. Automating Database Startup Perform the following tasks to set up the dbstart and dbshut scripts so that they are called at system startup. This process must be completed for every new database that you want to configure for automated startup: 1. Edit the /etc/oratab file. Configuration Tasks to Perform as the root User Post-Installation 4-7 Database entries in the oratab file appears in the following format: ORACLE_SID:ORACLE_HOME:{Y|N} In the preceding command, Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. For Oracle Real Application Clusters installation, this entry appears in the following format: DB_NAME:ORACLE_HOME:{Y|N} In the preceding command, DB_NAME is the cluster database name. Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. 2. For each database that you want to start up, find the ORACLE_SID entry identified by the sid in the first field. Change the last field for each to Y. 3. Add the dbstart script to the /etc/inittab file: # mkitab "oradb:2:wait:/bin/su oradb -c|/$ORACLE_HOMES/bin/dbstart" In the preceding command, oradb is the identifier of the oracle user for which you want to start the database. Automating Database Shutdown Automate database and system shutdown by creating a script, shut, to start dbshut and the system executable /etc/shutdown. Complete the following steps to create the script: 1. If you have not already done so, edit the database entries of your /etc/oratab file to enable dbstart and dbshut, as described in step 1 of the dbstart instructions. 2. As root, create the shut shell script: # cd /etc cat > shut << EOF ? su oracle_owner -c /usr/oracle/bin/dbshut ? /etc/shutdown $* \ ? [Ctrl-D] # chmod u+x shut 3. Execute the following command to run the shut script and shut down the database: Configuration Tasks to Perform as the root User 4-8 Installation Guide # /etc/shut -h now This closes Oracle databases and shuts down the system with the specified options. Automating Database Startup and Shutdown for Tru64 (Optional) This process must be completed for every new database that you want to configure for automated startup and shutdown. Perform the following tasks to start up and shut down listeners and set up the dbstart and dbshut scripts so that they are called at system startup: 1. Log in as root user. 2. Edit the /etc/oratab file. Database entries in the /etc/oratab file appear in the following format: ORACLE_SID:ORACLE_HOME:{Y|N} In the preceding command, Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. For Oracle Real Application Clusters installation, this entry appears in the following format: DB_NAME:ORACLE_HOME:{Y|N} In the preceding command, DB_NAME is the cluster database name. Y or N specifies whether you want the dbstart and dbshut scripts to start up and shut down the database. 3. For each database that you want to start up, find the ORACLE_SID entry identified by the sid in the first field. Change the last field for each to Y. 4. Change directory to /sbin/init.d. 5. Create a file named oracle, and use chmod to set the privileges to 750. 6. Add the following contents to the /sbin/init.d/oracle file: Note: This script assumes that a password is not set for the listener. If a password is set, the listener will not be stopped. The ORACLE_HOME and ORACLE variables are examples. Use information as appropriate for your installation. Configuration Tasks to Perform as the root User Post-Installation 4-9 #!/bin/sh # # change the value of ORACLE_HOME to be correct for your # installation ORACLE_HOME=/opt/oracle/product/9.2.0.1.0 PATH=${PATH}:$ORACLE_HOME/bin HOST=‘hostname‘ # # change the value of ORACLE to the login name of the # oracle owner at your site # ORACLE=oracle export ORACLE_HOME PATH # if [ ! "$2" = "ORA_DB" ] ; then rsh $HOST -l $ORACLE /sbin/init.d/oracle $1 ORA_DB exit fi # LOG=$ORACLE_HOME/startup.log touch $LOG chmod a+r $LOG # case $1 in 'start') echo "$0: starting up" >> $LOG date >> $LOG # Start Oracle Net if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then echo "starting Oracle Net listener" $ORACLE_HOME/bin/lsnrctl start >> $LOG 2>&1 & fi echo "starting Oracle databases" $ORACLE_HOME/bin/dbstart >> $LOG 2>&1 ;; 'stop') echo "$0: shutting down" >> $LOG date >> $LOG # Stop Oracle Net if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then echo "stopping Oracle Net listener" $ORACLE_HOME/bin/lsnrctl stop >> $LOG 2>&1 Configuration Tasks to Perform as the oracle User 4-10 Installation Guide fi echo "stopping Oracle databases" $ORACLE_HOME/bin/dbshut >> $LOG 2>&1 ;; *) echo "usage: $0 {start|stop}" exit ;; esac # exit 7. Change the .rhosts file in the oracle user login home directory to allow root login access to the account. your_host_name root 8. Link files into the startup and shutdown directories by using the ‘ln -s’ command. # ln -s /sbin/init.d/oracle /sbin/rc3.d/S99oracle # ln -s /sbin/init.d/oracle /sbin/rc0.d/K01oracle This file automatically starts and stops Oracle9i when the system is started or stopped. Configuration Tasks to Perform as the oracle User Perform the following tasks as the oracle user: ❏ Updating UNIX Account Startup Files ❏ Setting Environment Variables ❏ Initializing the oraenv Script ❏ Backing Up the root.sh Script ❏ Setting Initialization Parameters Updating UNIX Account Startup Files Update the startup files of the oracle user and the UNIX accounts of oracle users. Configuration Tasks to Perform as the oracle User Post-Installation 4-11 Setting Environment Variables Set the following environment variables in the.profile or.login file of the oracle user before using Oracle9i products. The settings that you use here should correspond to the settings used during installation as described in "Set Environment Variables" on page 2-36. The syntax for setting environment variables is as follows. For the Bourne or Korn shell: variable_name=value; export variable_name For the C shell: setenv variable_name value Table 4–2 describes the Environment Variable Settings. Caution: Do not define environment variables with names that are identical to those used for Oracle processes such as CKPT, PMON, and DBWR. Table 4–2 Environment Variable Settings Environment Variable Recommended Setting ORACLE_HOME Set the ORACLE_HOME variable to specify the directory containing the Oracle software for a particular release. The OFA recommended value is: $ORACLE_BASE/product/release For example, ORACLE_BASE variable is: /u01/app/oracle, then the ORACLE_HOME variable would be: /u01/app/oracle/product/9.2.0.1.0 CLASSPATH Set the CLASSPATH variable to ensure Java functionality. The CLASSPATH variable is different for various products. CLASSPATH must include the following: $ORACLE_HOME/jlib/<product jar file>: $ORACLE_HOME/product/jlib/product_jar_file See Also: Oracle9i Java documentation for more information on setting the CLASSPATH variable. Configuration Tasks to Perform as the oracle User 4-12 Installation Guide LD_LIBRARY_PATH Set the LD_LIBRARY_PATH variable as $ORACLE_HOME/lib for HP, Linux, Tru64, and Solaris 32-bit. Set the LD_LIBRARY_PATH variable as $ORACLE_HOME/lib32 for Solaris 64-bit. LD_LIBRARY_PATH_64 Set the LD_LIBRARY_PATH_64 variable as $ORACLE_HOME/lib for Solaris 64-bit. SHLIB_PATH Set the SHLIB_PATH variable as $ORACLE_HOME/lib32 for HP. LIBPATH Set the LIBPATH variable as $ORACLE_HOME/lib32: $ORACLE_HOME/lib for AIX. ORACLE_SID Set the ORACLE_SID variable to specify the name of the Oracle Server instance name. Oracle Corporation recommends restricting it to no more than four characters to avoid filename problems on different operating systems, as the sid is incorporated in many files. If you do not remember the value you entered when you were prompted by the Oracle Universal Installer, you can find it listed in the installActions.log file located in the oraInventory_location/ logs directory. The oraInventory_location directory is defined in the /etc/oraInst.loc file in AIX and /var/opt/oracle/oraInst.loc file in HP, Linux, Solaris and Tru64. Table 4–2 Environment Variable Settings (Cont.) Environment Variable Recommended Setting [...]... root.sh script during the installation If after a later 4-16 Installation Guide Configuration Tasks to Perform as the oracle User installation you require information from the original root.sh script, then you can recover it from the backed up root.sh file For example, if you install Oracle9i Management Infrastructure into the same Oracle home directory as a successful Oracle9i Server installation, then the... r3) See Also: Oracle9i Administrator’s Reference Release 2 (9.2.0.1.0) for UNIX Systems for more information on initsid.ora parameters and other tuning and configuring initialization parameters Post -Installation 4- 17 Post -Installation for Installed Oracle Products Post -Installation for Installed Oracle Products Perform the following required post -installation steps as necessary for your installation. .. Administrator’s Guide for more information on how to change the default password policy If the upgraded Oracle Internet Directory is integrating with other Oracle components, appropriate access control policies will need to be set up to grant necessary privileges to the Oracle components See Oracle Internet Directory Administrator’s Guide for more information 4-20 Installation Guide Post -Installation. .. network connectivity over TCP/IP See Also: Oracle9i Net Services Administrator’s Reference for more information on configuring a complete Oracle network "Oracle Net Configuration Assistant" on page 1-9 for more information on how Oracle Net Configuration Assistant configures your installation or how to run it as a standalone tool Post -Installation 4-21 Post -Installation for Installed Oracle Products... multi-node upgrades Default Subscriber Configuration The following information needs to be added to the root Oracle Context in the entry identified by the following DN "cn=Common, cn=Products, 4-18 Installation Guide Post -Installation for Installed Oracle Products %RootOracleContextDN%" By default, the RootOracleContextDN is "cn=OracleContext" Table 4–5 lists the attributes in the Root Oracle Context Table 4–5... identifies the node in the DIT under which all the groups are placed You can update these attributes by using the Oracle Directory Manager Note: Post -Installation 4-19 Post -Installation for Installed Oracle Products See Also: Oracle Internet Directory Administrator’s Guide for more information on these attributes Password Policy Configuration If the password policy exists in the earlier version of Oracle Internet... start The following example is specific to Solaris 32-bit 1 Verify that the default IPC protocol address for external procedure is set For example, LISTENER = (ADDRESS_LIST= (ADDRESS= 4-22 Installation Guide Post -Installation for Installed Oracle Products (PROTOCOL=IPC)(KEY=EXTPROC)) 2 Add static service information for the listener by setting a SID_DESC in the listener.ora file For example, # Add a... name MGW_AGENT to the tnsnames.ora file For example, MGW_AGENT = (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC)(KEY=EXTPROC))) (CONNECT_DATA= (SID=mgwextproc) (PRESENTATION=RO))) 4-24 Installation Guide Post -Installation for Installed Oracle Products In the preceding example, the KEY value is the IPC Protocol defined in the listener.ora file, and the SID value is the net service name defined in... same Oracle home directory as a successful Oracle9i Server installation, then the Oracle Universal Installer replaces the contents of the existing root.sh script during the installation Backing up the root.sh file after each product installation insures that you have all root.sh files available for reference if necessary Setting Initialization Parameters When you create a typical startup database using... ORAENV_ASK=NO /usr/local/bin/oraenv For the C shell: set ORAENV_ASK = NO source /usr/local/bin/coraenv unset ORAENV_ASK Note: The C shell uses the settings in coraenv file instead of the oraenv file 4-14 Installation Guide Configuration Tasks to Perform as the oracle User Multiple-Instance System On a multiple-instance System, include a list of instance names and commands necessary to initialize the oraenv script . $ORACLE_HOME/network /trace 77 7 rwxrwxrwx or 73 0 rwx-wx The oracle user and members of the ORAINVENTORY group have access to trace files when 73 0 is used in the production environment. 77 7 allows broad. Installed Oracle Products 4-18 Installation Guide Post -Installation for Installed Oracle Products Perform the following required post -installation steps as necessary for your installation. Not all. installation or how to run it as a standalone tool. Post -Installation for Installed Oracle Products 4-22 Installation Guide Configuring Oracle Messaging Gateway Perform the following post-installation