|
| 以 PDF 格式下载本书
HA-ORACLE Maintenance
7
- This chapter gives instructions for the maintenance procedures that may need to be performed when you are running HA-ORACLE.
- Use the following table to locate specific information in this chapter.
-
7.1 Overview of HA-ORACLE Operations
- Once configured, the administration of HA-ORACLE should be the same as administration of any ORACLE database.
- During administration, you should never edit or delete the haoracle_support(4) or the haoracle_config_v1(4) files.
-
Note - You should never use the ORACLE mirroring utilities to create mirrors in a Solstice HA configuration. You must use Solstice DiskSuite mirroring for ORACLE database on both UFS file systems and on raw devices.
7.2 HA-ORACLE Fault Monitoring
- The status field in the haoracle_databases(4) file should always be set to on. When the field is set to on, the instance is considered to be under Solstice HA fault monitoring. HA-ORACLE will start up and shut down the instance and will provide fault monitoring.
-
Caution - You should never set the status field to off, because it will impact availability. When the field is set to off, the database is considered to be in maintenance mode and is not maintained by HA-ORACLE. The database will not be started or shut down during membership transactions and there will be no fault monitoring. If the database has a problem, it will not be detected by HA-ORACLE.
7.3 Shutting Down and Starting Databases
- Before performing any maintenance on an HA-ORACLE database, the database should be taken out of service. Use the following procedure to perform this task:
-
-
Stop the database instance by using the haoracle(1M) command.
-
# haoracle stop instance_name
|
-
-
Shut down the database instance by using the ORACLE sqldba(1M) command.
-
Restart the database instance by using the haoracle command.
-
# haoracle start instance_name
|
|
|