Particular attention must be given to the operation of PRIMECLUSTER Wizard for Oracle.
Prerequisites and requirements
PRIMECLUSTER Wizard for Oracle has specific system requirements and component prerequisites that need to be understood prior to operation.
In PRIMECLUSTER Wizard for Oracle, Environment that Oracle on shared disk is not supported. Install Oracle software to a local disk of each node.
More than one Oracle product which version/release is different can be installed on the same node. However, the version and release should be same on an operating node and standby nodes.
For the Oracle products supported, see “Software Release Guide” 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.
Set up directory path of local disk to ORACLE_HOME, because environment that Oracle software is installed on shared disk is not supported.
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.
Oracle archive log files can be set on local disks. In such a case, if Oracle recovery is required, the Oracle archive log files on both nodes will be put together.
The Oracle “TWO_TASK” environment variable cannot be used. For details, see “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, see “2.2.7 Oracle Database Creation and Setting”.
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 be defined in sqlnet.ora file.
The other connections (e.g. user own connection for maintenance) can use the password file 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 resource monitoring or userApplication startup or shutdown.
For details, refer to “2.2.2 Oracle Installation and Configuration” or “2.3.2 Oracle Software Installation and Configuration”.
Environment that Oracle user's home directory and profile are located on the shared disk is not supported. Oracle user's home directory and profile must be located on the local disk of each node.
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”.
Oracle user should have access privileges for /tmp directory.
The programs of PRIMECLUSTER Wizard for Oracle working with Oracle user use /tmp directory. If Oracle user does not have access privileges for /tmp directory, the programs do not work correctly and startup or shutdown of Oracle fails.
Using of the "su -" command is not supported for user scripts(prestartup*, nomount*, mount*) under /opt/FJSVclora/usr.
Features and functions
Below are guidelines and precautions to be taken in using the features and functions provided by PRIMECLUSTER Wizard for Oracle.
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:
- An Oracle 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 scalable operation with Oracle9i RAC is used in a system, automatic recovery will not be performed. If recovery is required, specify the following file names under the “/opt/FJSVclora/usr” directory:
Example
# cd /opt/FJSVclora/usr
# mv ./_mount10EndBackup.sh ./mount10EndBackup.sh
# mv ./_mount20EndBackup.sh ./mount20EndBackup.sh
# mv ./mount05EndBackup_MediaRecover.sh
./_mount05EndBackup_MediaRecover.shSee
For details, see “3.6 User Scripts for Oracle Startup”.
In scalable operation with Oracle RAC 10g or later, an RMS resource is created based on the resource name of Oracle RAC. For details, see “2.3.2 Oracle Software Installation and Configuration”.
MonitorOnly can be enabled in the following cases. For details, see “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
Below are guidelines and precautions to be taken in configuring an environment that allows for PRIMECLUSTER Wizard for Oracle operations.
Be aware of the exit code and timeout duration when the following scripts are set:
PreOnlineScript, PostOnlineScript, PreOfflineScript, PostOfflineScript, and FaultScript.
For details, see “2.4.1 Oracle Online/Offline Script”.
Operations
Users need to take a special precaution when changing the SYSTEM password for PRIMECLUSTER Wizard for Oracle as follows:
For information on how to change the Oracle SYSTEM user password while a cluster system is running, see “3.3 Oracle SYSTEM User Password Change ”.
Others
Users need to take the following special precaution when operating PRIMECLUSTER Wizard for Oracle:
If an Oracle instance is stopped in the abort mode, it will automatically be recovered at the next instance startup.