| PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide 4.2 - Linux for Itanium - |
|
Contents
|
| Chapter 2 Environment Setup | > 2.4 Information | > 2.4.2 ASM (Automatic Storage Management) |
The ASM instance and database are only created on the operating node. The standby nodes will only operate the database on the shared disk of the operating node.
ASM instance name must begin with "+". The default name is "+ASM".
Refer to the Oracle manual.
Set up the standby nodes in the same configuration (directory creation, file copy, and links) as the operating node where the AMS instance and database are created.
Under $ORACLE_HOME/dbs
Under $ORACLE_BASE/admin/$ORACLE_SID
$ORACLE_BASE/admin/<ASM instance name>
The access privilege to the directories and files must be also the same as that on the operating node.
If you set where archive log is output on the operating node, it is necessary to set the same on the standby nodes.
Set CSS daemon, and start it. The operation node is set and started automatically. In one side, standby node is not set and started automatically.
If required files on the operating node is backed up in the tar format with the /opt/FJSVclora/sbin/cloracpy command, configuration information of the ASM instance will not be backed up. Copy the following file manually in the tar format:
$ORACLE_BASE/admin/<ASM instance name>
Check if the disk group in which the Oracle database is created is set for the ASM instance initialization parameter "ASM_DISKGROUPS".
For the initialized parameter of the ASM instance, refer to the Oracle manual.
When creating userApplication, create an ASM instance resource and Oracle instance resource. Register them in each userApplication.
The NULLDETECTOR attribute is automatically set to the flag of the ASM instance resource. This value cannot be changed.
|
Contents
|