PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide 4.2 - Linux for Itanium -

Contents

Chapter 5 Notice

Particular attention must be given to the operation of PRIMECLUSTER Wizard for Oracle.

Prerequisites and requirements

• Operating several different versions of Oracle products on a PRIMECLUSTER system is not supported. For the Oracle products supported, refer to "Readme" and "Handbook".
• A user name, user ID, group name, and group ID should be identical on all the nodes to install Oracle.
• If multiple ORACLE_HOME are configured on one server, a different user name must be assigned respectively.
• An Oracle database must be configured on the shared disk.
• Setting Oracle log output on the shared disk is not recommended. When a disk device fails, log might not be output, or the Oracle instance might not be started.
• For Oracle archive log files, you should pay close attention to the following points:
  - In the case of allocating the file on a local disk
• If Oracle recovery is required, the Oracle archive log files on both nodes will be put together.
• - In the case of allocating the file on a shared disk
• You should pay close attention to insufficient space to archive.
• The Oracle "TWO_TASK" environment variable cannot be used. For details, refer to "2.2.7 Oracle Database Creation and Setting".
• The setting to connect to an Oracle database must not be described in login.sql of an Oracle user. For details, refer to "2.2.7 Oracle Database Creation and Setting".
• The password file authentication cannot be used. Use OS authentication.
• PRIMECLUSTER Wizard for Oracle connects to Oracle instance with SYSDBA system privilege to start up or stop Oracle instance/database. In this case, local connection in operating system authentication is used. Therefore, the following requirements should be satisfied. (If not, startup and stop of Oracle instance/database might fail.)
  - Oracle user that is set for Oracle instance resource in "2.2.9 userApplication with Oracle Resources" or "2.3.5 userApplication with Oracle RAC Instances and Listeners" should belong to OSDBA group.
  - SQLNET.AUTHENTICATION_SERVICES parameter should not define in sqlnet.ora file.
  The other connections (ex. user own connection for maintenance) can use the password file authentication cannot be used. Use OS authentication.
• A command (e.g. script) that has interactive mode should not be described in Oracle user's profile. (e.g. /etc/profile, .bash_profile, .cshrc, .profile)
  It may cause failure of userApplication startup or shutdown.
  For details, refer to "2.2.2 Oracle Installation and Configuration" or "2.3.2 Oracle Installation and Configuration".
• In Oracle 10g or later environment, operating system authentication of Listener should be enabled. For details, refer to "2.2.7 Oracle Database Creation and Setting".

Features and functions

• The detector connects itself to the database using system user access privileges to monitor Oracle instances. It also monitors Oracle operation by creating a monitoring table on the system user default table space. The size of the table is only a few bytes. The table data is periodically updated, so the REDO log is updated, and the archive log data is output.
• Stopping an Oracle instance in the "immediate" mode fails in the following situations:
  - A DBA user is being connected to the Oracle instance, or
  - Online backup is the Oracle instance is in progress
  If this occurs, Wizard for Oracle will shut down the Oracle instance with "abort" mode.
• The time required for Oracle instance startup and stop varies depending on the database size. The default startup timeout is 10 minutes. The default stop timeout is 3 minutes.
  The RMS command "hvshut" has its own timeout. Even though hvshut times out, userApplication stop processing will be continued along with RMS stop.
• If a database failure is detected during Oracle instance startup, the database will automatically be recovered. Note that if Oracle RAC is used in a system, automatic recovery will not be performed.

  

  # cd /opt/FJSVclora/usr # mv ./_mount10EndBackup.sh ./mount10EndBackup.sh # mv ./_mount20EndBackup.sh ./mount20EndBackup.sh # mv ./mount05EndBackup_MediaRecover.sh ./_mount05EndBackup_MediaRecover.sh

  
  

  
  For details, refer to "2.4.1 Oracle Online/Offline Script".

• In Oracle RAC 10g scalable operation, an RMS resource is created based on the resource name of Oracle RAC 10g. For details, refer to"2.3.2 Oracle Software Installation and Configuration".
• MonitorOnly can be enabled in the following cases. For details, refer to "2.2.9 userApplication with Oracle Resources".
  - One resource of "Instance" type and one resource of "Listener" type exist, and StartPriority is set to "Same". In this case, MonitorOnly only for the one of them can be enabled.
  - More than one resources of "Instance" type exist. In this case, MonitorOnly for the one of them cannot be enabled, but all of the others can be enabled.
  - More than one resources of "Listener" type exist. In this case, MonitorOnly for the one of them cannot be enabled, but all of the others can be enabled.
• Do not execute "srvctl" or "sqlplus" commands to shut down Oracle instance. It might cause mismatched status between RMS and Oracle RAC.

Configuration

• Be aware of the exit code and timeout duration when the following scripts are set:
  PreOnlineScript, PostOnlineScript, PreOfflineScript, PostOfflineScript, and FaultScript.
  For details, refer to "2.4.1 Oracle Online/Offline Script".

Operations

• For information on how to change the Oracle system user password while a cluster system is running, refer to "3.3 Oracle System User Password Change".

Others

• If an Oracle instance is stopped in the abort mode, it will automatically be recovered at the next instance startup.

Contents