1. Global Data Services Concepts and Administration
  2. Using Global Data Services Log and Trace Files

Using Global Data Services Log and Trace Files

To diagnose GDS problems, use logs to pinpoint issues and enable tracing/logging to capture detailed runtime evidence.

If logging and tracing has been enabled for GDS components, you can find the exact location of a given global service manager's log and trace files using the status gsm command as shown in the following example.

GDSCTL>status gsm

Alias                     MYGSM
Version                   19.1.0.0.1
Start Date                22-OCT-2022 14:05:11
Trace Level               support
Listener Log File         /scratch/oracle/diag/gsm/myhost/mygsm/alert/log.xml
Listener Trace File       /scratch/oracle/diag/gsm/myhost/mygsm/trace/ora_1829_
 47542149303936.trc
Endpoint summary          (ADDRESS=(HOST=myhost.com)(PORT=1571)(PROTOCOL=tcp))
GSMOCI Version            0.1.7
Mastership                N
Connected to GDS catalog  Y
Process Id                1833
Number of reconnections   0
Pending tasks.     Total  0
Tasks in  process. Total  0
Regional Mastership       TRUE
Total messages published  34261
Time Zone                 -07:00
Orphaned Buddy Regions:   None
GDS region                east
Network metrics:
   Region: euro RTT:34 Bandwidth:40

In this example `*myhost* is the global service manager host name and mygsm` is the name of the global service manager.

Although not strictly a GDS component, the LISTENER log file can be helpful resolving some issues. The text-based LISTENER log can be found in `/scratch/oracle/diag/gsm/*hostname*/*gsm_name*/trace directory. The file is called alert_gsm*.log (for example, alert_gsm1.log`).

If logging and tracing have not been enabled for GDS components, then follow the steps below to do so:

  1. Enable logging for GDSCTL. On the GSM host, edit the $ORACLE_HOME/network/admin/gsm.ora file and add the following:

_GDSCTL=(log=ALL)

This will log any commands run using GDSCTL in the following log file on the GSM host. $ORACLE_HOME/network/admin/GDSCTL.log
2. Enable tracing for GSM processes.

GDSCTL> set trace_level -gsm ** SUPPORT

This will generate trace files in DIAGNOSTICS_DEST for GSM. For example, $ORACLE_BASE/diag/gsm/**/**/trace
3. Enable tracing on the catalog database.

SQL> alter system set events '10798 trace name context forever, level 7';
4. Enable tracing on the GDS pool databases.

SQL> alter system set events '10798 trace name context forever, level 7';

To disable logging and tracing, follow the steps below:

  1. Turn off GSM tracing.

    GDSCTL> set trace_level -gsm ** OFF

  2. Turn off GDSCTL command logging by editing the gsm.ora file and removing the following line:

    _GDSCTL=(log=ALL)

  3. Turn off tracing on the catalog database and GDS pool databases.

    SQL> alter system set events '10798 trace name context forever, level 0';

Parent topic: GDS Logs and Tracing