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.
Outline
The document consists of the following 6 chapters and 1 appendix:
● Chapter 1 Feature
● Chapter 2 Environment setup
● Chapter 3 Operation
● Chapter 4 Command
● Chapter 5 Notice
● Chapter 6 Message
● Appendix A
Notational convention
The document conforms to the following notational conventions:
● Describes points to be taken notice of.
●
● Describes by using an example.
Describes information a user can refer to.
Trademarks
Solaris, NFS, Sun Microsystems are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States and other countries.
Sun's logo mark and Solaris are registered trademarks of Sun Microsystems, Inc.
ORACLE and Oracle Applications are trademarks or registered trademarks of Oracle
Corporation.
Requests
No part of this document may be reproduced or copied without permission of FUJITSU LIMITED.
The contents of this document may be revised without prior notice.
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2003
2
Contents
Configuration and Administration Guide .................................................................................................................. 1
2.1 Set up environment ................................................................................................................................... 8
2.2 Install and set up PRIMECLUSTER software............................................................................................ 9
2.3 Install and set up Oracle software ........................................................................................................... 10
3.1 Set up Oracle-related script..................................................................................................................... 24
3.2 Oracle stop during cluster operation........................................................................................................ 25
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.
Module structure
For Oracle operation on PRIMECLUSTER, the module consists of the followings:
Environment setup WizardEnvironment setup tool to enable Oracle operation on
DetectorModule to monitor Oracle
ScriptsControl Oracle startup and stop
Setup/operation commandCommands used to set up and operate
PRIMECLUSTER
Environment setup
The environment setup tool provides “ORACLE” Wizard that creates userApplication in the
environment configuration of PRIMECLUSTER RMS.
Monitoring
A detector monitors Oracle instances and Oracle listeners. The detector is connected to Oracle
using system user to monitor the Oracle instance. Then, it periodically creates, updates, and
deletes dummy table, which is created in the system user’s default tablespace by executing the
SQL command. This enables the detector to detect a logical failure as well as the process state
of the Oracle instance. When the Oracle instancehangs, and if the SQL command is not
returned within a specified time, the detector times out to notify a user of the failure. The two
types of monitoring of the Oracle listener are process detection and the “tnsping” command.
Startup and stop control
Along with the state transition of a cluster system, scripts automatically start or stop Oracle
instances or Oracle listeners. These scripts first check and then start up the Oracle instance.
If damage has occurred, the scripts automatically recover the Oracle instance. For example, if
the Oracle instance fails during online backup, the scripts automatically execute “end backup” to
start up the Oracle instance (When the AutoRecover is set to “Yes”.) When stopping the Oracle
instance, the scripts stop it in the immediate mode (default). If this does not occur properly, the
scripts stop the instance in the abort mode. This means operational node switchover can be
performed at high-speed.
5
1.2 Operating Environment
Scalable operation
In scalable operation with Oracle9i RAC, Oracle is operated on all nodes. Regardless of which
node a client is connected to, the client is able to use the database.
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. In the event of a failure, business operation is
switched to one of the standby nodes, and the resources in this standby node are activated.
Then, the client can be connected to the running node using the logical IP address without
modifying any settings.
6
Chapter 2 Environment setup
7
2.1 Set up environment
This section explains a general setup procedure of Oracle operating on a PRIMECLUSTER
system.
Scalable operation (Oracle9i RAC)
No
Outline
One arbitrary node Other nodes
1 Install and set up PRIMECLUSTER Install and set up PRIMECLUSTER
Install PRIMECLUSTER Wizard for
2
Oracle
3 Install and set up Oracle software Install and set up Oracle software
4 Create userApplication
5 Create and set up an Oracle database
6
7 Create and set up Oracle resources
Install PRIMECLUSTER Wizard for
Oracle
Set up an Oracle database
Standby operation
No
Outline
Operational node Standby nodes
1 Install and set up PRIMECLUSTER Install and set up PRIMECLUSTER
Install PRIMECLUSTER Wizard for
2
Oracle
3 Install and set up Oracle software Install and set up Oracle software
4 Create userApplication
5 Create and set up an Oracle database
6
7 Create and set up Oracle resources
Further details of each step are described below.
Install PRIMECLUSTER Wizard for
Oracle
Set up an Oracle database
8
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.
Standby operation requires PRIMECLUSTER Enterprise Edition or PRIMECLUSTER HA Server.
Set up cluster system
Set up a cluster system including network systems and shared disk units according to the
PRIMECLUSTER manual.
9
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.
The setup examples are shown below:
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=200
set semsys:seminfo_semmns=400
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
● /etc/services
Set up a port number for the Oracle listener.
listener 1521/tcp oracle
● Oracle User
Create DBA (database administrator) user to allow a user to install Oracle and operate.
The user ID and the group ID should be identical on all nodes.
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.
Installation
● Oracle
Install Oracle using Oracle user. Install a program on each node’s local disk. The
database needs to be created on the shared disk when a cluster system is configured, not
when Oracle is installed. The details will be described later in this document.
● Oracle9i RAC
Install Oracle9i RAC using root user. Refer to the Oracle9i RAC manual.
For further details, refer to the Oracle manual.
11
2.4 Create userApplication
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.
See “Chapter 6 Cluster application configuration” of “PRIMECLUSTER Installation/Administration
Guide” for the userApplication Configuration Wizard setup.
2.4.1 Application-Create
The Oracle environment setup is described with the following illustrations:
● Scalable operation (Oracle9i RAC)
userApplication is configured as shown in the illustration.
12
● Standby operation
userApplication is configured as shown in the illustration.
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. See “Chapter 6 Cluster
application configuration” of “PRIMECLUSTER Installation/Administration Guide”. In scalable
operation, userApplication should be created for each node. In standby operation, one
userApplication should be created for all operational nodes. The recommended values are as
follows:
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.
13
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 Location Note
Init.ora file Local Allocate on a local disk of each node
Server parameter file Share
Control files Share
Data files Share
Redo log files Share
Archive log files Arbitrary Allocate either on a local disk or a shared disk
● Create database (Scalable operation with Oracle9i RAC)
Create a database on an arbitrary node. This database should be accessible from other
nodes.
Refer to the Oracle9i RAC manual.
● Create database (Standby operation)
Operational node
Create a database on an operational node. Standby nodes have to access this database.
Refer to the Oracle manual.
Standby node
Set up directory generation, file copy, and link. The configuration should be the same as
that of the operational node where the database is generated.
Under $ORACLE_HOME/dbs
Under $ORACLE_BASE/admin/$ORACLE_SID
The access privilege to the generated directory and file should be the same as that of the
operational node.
Set up an output location on the standby nodes if you use archive log operation.
14
The required files in the operational node can be backed up in a tar format by executing
the “cloracpy” command. Refer to “Chapter 4.4”.
Mutual standby / N:1 Standby operation
Create a database on an operational node.
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<ORACLE_SID>.ora