JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information


1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

Monitoring the Runtime Status of the Geographic Edition Software

Viewing the Geographic Edition Log Messages

Displaying Configuration Information for Partnerships and Protection Groups

How to Display Configuration Information About Partnerships

How to Display Configuration Information About Protection Groups

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins


Viewing the Geographic Edition Log Messages

All the Geographic Edition components produce messages that are stored in log files.

Information about the loading, running, and stopping Geographic Edition components in the common agent container is recorded in the following log files. The most recently logged messages are in file 0, then 1, and 2.

System log messages are stored in the /var/adm/messages log file.

Each cluster node keeps separate copies of the previous log files. The combined log files on all cluster nodes form a complete snapshot of the currently logged information. The log messages of the Geographic Edition modules are updated on the node where the Geographic Edition software is currently active. The data replication control-log messages are updated on the node where the data replication resource is currently Online.

For data replication modules that are based on script-based plug-ins, you can set the DEBUG property to TRUE for more verbose messages to aid in troubleshooting.