Configuration and Administration Guide PRIMECLUSTER™ Wizard for Oracle Configuration and Administration Guide 4.
Preface Purpose The purpose of the document is to outline functions of PRIMECLUSTER Wizard for Oracle. Further, it describes the procedures from installation to operation management. Readers The document is intended for system engineers and system administrators to design, configure, and manage a PRIMECLUSTER system. The reader should have expertise in the PRIMECLUSTER and Oracle system.
Contents Configuration and Administration Guide .................................................................................................................. 1 Chapter 1 Feature............................................................................................................................................... 4 1.1 Feature outline .......................................................................................................................................... 5 1.
Chapter 1 Feature 4
1.1 Feature outline PRIMECLUSTER Wizard for Oracle is a software product that facilitates cluster operation management for Oracle operating on a PRIMECLUSTER system. This is required for scalable operation and standby operation for a cold standby Oracle instance. The scalable operation requires Oracle9i Real Application Clusters (Oracle9i RAC). The standby operation does not require Oracle9i RAC, but requires Oracle cold standby instead.
1.2 Operating Environment Scalable operation In scalable operation with Oracle9i RAC, Oracle is operated on all nodes. node a client is connected to, the client is able to use the database. Regardless of which Standby operation In standby operation, a cluster system consists of an operational node and standby nodes. On the operational node, Oracle applications, a logical IP address and shared disks are active. On the standby nodes, these resources are inactive.
Chapter 2 Environment setup 7
Set up environment 2.1 This section explains a general setup procedure of Oracle operating on a PRIMECLUSTER system.
2.2 Install and set up PRIMECLUSTER software This section explains how to install and set up PRIMECLUSTER. Set up hardware Set up hardware required for PRIMECLUSTER. The shared disk is also required to create the Oracle database. Install software Install PRIMECLUSTER first, referring to “PRIMECLUSTER Installation Guide”. Then, install Oracle Wizard following the instructions of “PRIMECLUSTER Wizard for Oracle Installation Guide”. Scalable operation requires PRIMECLUSTER Enterprise Edition.
2.3 Install and set up Oracle software This section explains how to install and set up Oracle. Initial setup ● /etc/system Set up values in the “/etc/system” file for Oracle in addition to the values for PRIMECLUSTER. The kernel parameter values vary depending on the implemented Oracle versions. Refer to the Oracle installation guide. The parameter values should be identical on all nodes. Before installing Oracle, you need to change the “/etc/system” file and reboot the node.
（.profile ） ORACLE_BASE=/opt/oracle; export ORACLE_BASE ORACLE_HOME=/opt/oracle/product/8.1.7; export ORACLE_HOME ORACLE_TERM=sun-cmd; export ORACLE_TERM ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data; export ORA_NLS33 LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH PATH=$ORACLE_HOME/bin:/usr/bin:/usr/ccs/bin:/usr/ucb; export PATH When “/usr/ucb” is contained in PATH, it needs to be set up after ”/usr/ccs/bin”. For further details, refer to the Oracle manual.
Create userApplication 2.4 This section explains how to set up userApplication creation and Non-Oracle resource setup. Set up the Oracle resource after configuring the database. Then, set up userApplication using “userApplication Configuration Wizard”. This “userApplication Configuration Wizard” follows the Wizard format in which you can select the item from the menu and click a “Next” button.
GDS setup GDS should be set up as “shared disk for concurrent access” for scalable operation and “switching disk” for standby operation. We recommend that you prepare the disk class for Oracle system table space and other Oracle resources respectively. The MONITORONLY attribute should be set up to “NO” for the Oracle system table space and “YES” for the other Oracle resources. userApplication setup Create userApplication using userApplication Configuration Wizard.
2.5 Create and set up Oracle database ● Allocate database Create a database on the shared disk. The shared disk should be active. Each file is allocated as follows: File Init.
On the standby nodes, the database on the shared disk created from the operational node should be enabled. This is the same as other operation methods. Mutual standby 2:1 Standby ● Oracle9i Allocate a server parameter file on the shared disk when using the Oracle9i server parameter file. If this process is omitted or failed, the operational and standby nodes do not work properly. You can set the initialized parameter file as follows: ($ORACLE_HOME/dbs/init.
LISTENER = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521)) ) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = ora9i) (ORACLE_HOME = /opt/oracle/product/9.0.1) (SID_NAME = ora9i) ) ) ― tnsnames.ora Set up the “tnsnames.ora” file to monitor listener operation by executing the “tnsping” command. Also, set up a network service name in the ”tnsnames.ora” file and in the Oracle listener environment of Oracle Wizard.
Create and set up Oracle resource 2.6 This section explains how to register the Oracle-related resource in userApplication. 2.6.1 Create Oracle resource This section explains how to create the Oracle resource using userApplication Configuration Wizard. 1. Select “Create ResourceResource” in the “userApplication Configuration” menu. 2. Select “Oracle” in the “Resource Type” menu.
3. Add the Oracle instance and Oracle listener in the “Set up Resource” menu. ApplilcationName Change the application name. AdditionalInstance Add the Oracle instance resource. AdditionalListener Add the Oracle listener resource. StartPriority Set up a startup order of the Oracle instance and Oracle listener. If you use the Oracle multi-threaded server (MTS), the Oracle listener needs to be started first. 4.
StopTimeout Timeout duration of Oracle stop. Default: 180s (60s - 86400s) AbortTimeout Timeout duration of forced termination in the event of an Oracle stop error. Default: 60s (60s - 86400s) StopModeStop Oracle stop mode in normal time. Default: Immediate mode (abort, immediate, transactional) StopModeFail Oracle stop mode in the event of a failure. Default: Abort mode (abort, immediate) Interval Monitoring interval of Oracle instance.
TNSName Network service name used to monitor the Oracle listener Note: The “tnsping” command is used to monitor the Oracle listener if TNSName is set. This TNSName is set in tnsnames.ora. When TNSName is omitted, the feature to monitor only the listener process is enabled (arbitrary). AutoRecover Feature to recover resources. Note: Select yes to enable this feature. RMS attempts to recover the failed resources to prevent userApplication from switching to other host.
When using Oracle9i RAC, follow the setup procedure from 1. to 6. for the number of other userApplication. 2.6.2 Set up userApplication This section explains how to create the userApplication and Oracle resource, referring to “8.1.1 Modify cluster application configuration” of “PRIMECLUSTER Installation/Administration Guide”.
2.6.3 Check userApplication Execute the “hvcm” command of RMS to start up userApplication and check if it is normally running on all nodes. See “PRIMECLUSTER RMS Configuration and Administration” for the RMS command.
Chapter 3 Operation 23
3.1 Set up Oracle-related script Script files on a PRIMECLUSTER system control each resource startup and stop. Script files in PRIMECLUSTER Wizard also start and stop of the Oracle instance and Oracle listener. Along with this Oracle startup and stop, the scripts can execute user programs and batch process.
3.2 Oracle stop during cluster operation PRIMECLUSTER Wizard for Oracle monitors an Oracle system while PRIMECLUSTER is running. If the Oracle system is stopped, this PRIMECLUSTER Wizard considers it as a failure. Then, the Oracle system is restarted or switched over to a standby node.
3.3 Action definition file The instance-monitoring detector of Oracle Wizard determines what corrective action should be taken from an error code. The action definition file consists of Oracle error numbers, corrective actions, and error messages. ● Action definition file name and path /etc/opt/FJSVclora/FJSVclorafm.
3.4 Solution at the time of switchover Oracle logging When switchover or degeneration occurs, solve the problem referring to Oracle alert logging or trace logging in the same way as the solution in single Oracle operation. PRIMECLUSTER Wizard for Oracle logging PRIMECLUSTER Wizard for Oracle provides information what kind of failure is detected and what corrective action is taken in the following log files: /var/opt/reliant/log/FJSVclora__*.log /var/opt/reliant/log/FJSVclora__*.
3.5 Collect information for troubleshooting The following information is helpful in the event of a failure. Oracle information ● Setup file $ORACLE_HOME/network/admin/*.ora $ORACLE_HOME/dbs/*.ora $ORACLE_BASE/admin/$ORACLE_SID/pfile/*.ora ● Logging file $ORACLE_HOME/rdbms/log/alert_$ORACLE_SID.log $ORACLE_BASE/admin/$ORACLE_SID/bdump/alert_$ORACLE_SID.log $ORACLE_HOME/network/log/.
Chapter 4 Command 29
4.1 hvoradisable - Discontinue monitoring resource User Super user Format /opt/FJSVclora/sbin/hvoradisable application_name resource_name Function It is a feature to discontinue monitoring the specified Oracle instance or Oracle listener resource. This function is used to stop the Oracle instance or Oracle listener for maintenance. It is disenabled while userApplication is stopped. It is enabled when userApplication is activated next time.
4.2 hvoraenable - Restart monitoring resource User Super user Format /opt/FJSVclora/sbin/hvoraenable application_name resource_name Function It is a feature to restart monitoring the Oracle instance or Oracle resource. This function is disenabled while userApplication is stopped. It is enabled when userApplication is activated next time. Execute the “hvoraenable” command while the Oracle instance or Oracle listener is running. Confirm if the resource state is changed from Warning to Online.
4.3 clorapass - Set up password for monitoring User Super user Format /opt/FJSVclora/sbin/clorapass Function It is a feature to specify a password of Oracle system user in PRIMECLUSTER Wizard for Oracle by executing the “clorapass” command. The detector monitoring the Oracle instance is connected to Oracle using system user. For that purpose, this detector requires the password of Oracle system user.
4.4 cloracpy - Oracle environment setup tool for standby node User Oracle DBA user Format /opt/FJSVclora/sbin/cloracpy Function The required files in the operational node can be backed up in a tar format by executing the “cloracpy” command. By deploying this backup data on the standby nodes, the file copy and link settings are enabled. Execute the “cloracpy” command ・$ORACLE_HOME and $ORACLE_BASE should be identical between the operational node and the standby nodes.
4.5 clgetoralog - Collect Oracle information for troubleshooting User Super user Format /opt/FJSVclora/bin/clgetoralog [-n configure_name] [-d output_directory] Function It is a feature to collect Oracle information for troubleshooting. The “clgetoralog” command collects Oracle information and log files on a PRIMECLUSTER system. The “clgetoralog” command collects ・$ORACLE_HOME/dbs/*.log ・$ORACLE_HOME/rdbms/log/ ・$ORACLE_HOME/../../admin/$ORACLE_SID/pfile/*.ora ・$ORACLE_HOME/../..
Chapter 5 Notice This section explains the points you need to pay close attention to. ● The Oracle database needs to be allocated to the shared disk. ● PRIMECLUSTER operated with Oracle products of different versions is not supported. For the supported Oracle products, refer to the installation guide or handbook. ● A user name, user ID, group name, and group ID should be identical on all nodes to install Oracle.
Chapter 6 Message This section lists console messages that are output while PRIMECLUSTER Wizard for Oracle is running. The messages are indicated in the “syslog(3C)” format. Oracle instance detector messages ● [Error] [1202] Cannot map shared memory or get semaphore Cannot map shared memory or get semaphore. Check the system environment.. ● [Error] [1203] Cannot open actionlist Cannot open the action definition file. Check this file.
● [Error] [1219] Cannot read hvgdconfig Cannot read the “hvgdconfig” file. Check this file. ● [Error] [1220] Not Found xx setting in hvgdconfig There is an incorrect setup of resource xx in “hvgdconfig” file. Check this file. ● [Error] [1223] Not found ORACLE_SID in hvgdconfig ORACLE_SID is not found in the “hvgdconfig“ file. Check this file. ● [Error] [1299] ORA-xxxxx An Oracle error was detected. Check Oracle and Oracle Alertlog files.
There is an incorrect setup "Timeout" in the hvgdconfig. Check this file. ● [Error] [0207] Cannot allocate memory hvgdconfig The system error occurred in the mapping memory. system resources. Check the system environment.. There are probably insufficient ● [Error] [0208] Data init error The system error occurred in the getting semaphore. system resources. Check the system environment.. There are probably insufficient ● [Error] [0209] Fork error The system error occurred in the process generation.
Appendix A Setup method using CUI This appendix explains how to create the environment configuration using CUI. A.1 Create userApplication following the procedure of Chapter 2.4 A.2 Create the Oracle resource following the procedure of Chapter 2.6 Create userApplication A.1 This section explains userApplication generation and non-Oracle resource setup. Set up the Oracle resource after configuring the database, and then userApplication using RMS Configuration Wizard.
● Standby operation In standby operation, userApplication is configured as shown in the illustration. A.1.2 Set up scalable operation (Oracle 9i RAC) 1) Select Application-Create in the “Main RMS management menu” page to create userApplication.
2) Select ORACLE (all caps) in the “Application type selection menu” page. 3) Specify the userApplication name of ApplicationName in the “Settings of turnkey wizard ORACLE” page. 4) Select Machines+Basics to set up a node and following menu items. Create the same number of userApplication as that of Oracle instances. Set up a node for each userApplication. For other settings, refer to HELP or PRIMECLUSTER RMS Configuration and Administration.
5) Set up a resource required for the shared disk (ex. GDS) in the “Setting of turnkey wizard ORACLE” page. 6) Return to the Main RMS management menu by executing SAVE+EXIT (Any settings related to Oracle should not be done here). 7) With the procedure from 1) to 6), the node setup is done. For scalable operation, create the same number of userApplication as that of all nodes. This setup procedure should be done on all nodes. A.1.
2) Select ORACLE (in capitals) in the “Application type selection menu” page. 3) Specify the userApplication name of ApplicationName in the “Settings of turnkey wizard ORACLE” page. 4) Select Machines+Basics to set up nodes and following menu items. Set an operational node to Machines[0], and standby nodes to Machines[n]. Select AdditionalMachines to add a node. For other settings, refer to HELP or “PRIMECLUSTER RMS Configuration and Administration”.
5) Set up a resource required for the shared disk (ex. GDS), LocalFileSystems, and IpAddress in the “Settings of turnkey wizard ORACLE” page. 6) Return to the Main RMS management menu by selecting SAVE+EXIT. (Any settings related to Oracle should not be done here.) A.1.4 Configuration-Generate and Configuration-Activate Select Configuration-Generate to set up userApplication. Select Configuration-Activate to enable the userApplication setup.
A.1.5 Check userApplication Execute the “hvcm” command of RMS to start up userApplication and check if it is normally running on all nodes. ● Shared disk – Check access to the shared disk on an operational node. ● Logical IP address – Check access to an operational node. See “PRIMECLUSTER RMS Configuration and Administration” for the RMS command. Create and set up Oracle resource A.2 The Oracle-related resource is registered in userApplication that is created in Chapter 2.4.
3) Select ORACLE in the “Settings of turnkey wizard ORACLE” page. 4) Add the Oracle instance and Oracle listener in the Oracle setup page. AdditionalInstance Add the Oracle instance resource AdditionalListener Add the Oracle listener resource StartPriority Set up a startup order of the Oracle instance and Oracle listener If you use the Oracle multi-threaded server (MTS), the Oracle listener needs to be started first. 5) Set up the Oracle instance. See 4 of “2.6.1 Create Oracle resource” for details.
In scalable operation, userApplication is configured as follows: In standby operation, userApplication is configured as follows: 47
A.2.3 Check userApplication operation Execute the “hvcm” command of RMS to start up userApplication and check if it is normally running on all nodes. See “PRIMECLUSTER RMS Configuration and Administration” for the RMS command.
