Super user
/opt/FJSVclora/bin/clgetoralog [ -n RMSconfiguration ] [ -d output_directory ] [ -a ]
clgetoralog collects Oracle information for troubleshooting. The “clgetoralog” command collects Oracle setup information and log files on a PRIMECLUSTER system.
The information will be collected in the “<hostname>_<yymmddHHMMSS>_clgetoralog.tar” file.
The “clgetoralog” command collects
Initialization parameter file
$ORACLE_HOME/dbs/*.ora
$ORACLE_BASE/admin/$ORACLE_SID/pfile/*.ora
Oracle alert log
background_dump_dest/*.log
$ORACLE_BASE/admin/$ORACLE_SID/bdump/*.log
$ORACLE_HOME/rdbms/log/*.log
$ORACLE_HOME/dbs/*.log
Under $ORACLE_BASE/diag
listener.ora, tnsnames.ora
$ORACLE_HOME/network/admin/*.ora
Listener log
$ORACLE_HOME/network/log/*.log
Oracle Clusterware Information
$ORA_CRS_HOME/crs/admin/*
$ORA_CRS_HOME/crs/log/* ($ORA_CRS_HOME/log/<hostname>/crsd/*)
V/L, configuration, and log files of PRIMECLUSTER Wizard for Oracle
V/L and log files (switchlog) of RMS
V/L, configuration, and patch information of PRIMECLUSTER
System information
uname -a (system basic information)
uptime (system operating time)
psrinfo -v
/usr/platform/`arch -k`/sbin/prtdiag
cat /etc/release (Solaris version)
cat /var/sadm/system/admin/CLUSTER (Solaris software group)
cat /var/sadm/ptf/newprev/Rcontents (PTF information)
grep -h “Install Solaris” /var/sadm/install_data/*OK (RSPC information)
pkgparam -v FJSVbse (ESF information)
isainfo -b, isainfo -v (instruction set architectures information)
sysdef -i (kernel parameter)
ipcs (shared resources)
swap -l (swap information)
ptree -a, ps -efZ, ps -efL -o (process information)
zonename, zoneadm list -vc (zone information)
ntpq -p (NTP information)
/var/adm/messages files
System information (Solaris 10 only)
showrev -p (patch information)
Information
The fjsnap command can also be used to collect troubleshooting information.
Specify RMS configuration name for RMSconfiguration.
If this option is specified, clgetoralog command collects RMS configuration information in addition to the information described in “Function”. When the cluster application has been built by using GUI (userApplication Configuration Wizard), the RMS configuration name is “config”. The RMS configuration name can be confirmed by the following command while RMS is running.
# /opt/SMAW/bin/hvdisp -a | grep Configuration
Configuration: /opt/SMAW/SMAWRrms/build/config.usIf this option is not specified, clgetoralog command collects only information described in “Function“.
Specify the directory where information is collected. Then, the command will store the “<hostname>_<yymmddHHMMSS>_clgetoralog.tar” file in the directory. If the directory specified does not exist, it will automatically be created.
If this option is omitted, the command will store the “<hostname>_<yymmddHHMMSS>_clgetoralog.tar” file under the default directory (/var/tmp).
The option will collect the following information in addition to the information described in [Function]:
Group of currently active RMS configuration files (all RMS configuration files with the -n option)
RMS log files (/var/opt/reliant/log/*)
RMS environment variable configuration file (/usr/opt/reliant/bin/hvenv.local)
/var/adm/messages*
/etc/hosts, /etc/inet/hosts
/etc/passwd
/etc/services, /etc/inet/services
/etc/system
/etc/vfstab
/etc/vfstab.pcl
showrev -p
0: Normal termination
Non-0: Abnormal termination
Note
This command gets the value of background_dump_dest or diagnostic_dest parameter from the initialization parameter file or the server parameter file, and searches the Oracle alert log and listener log. However, if these parameter files can not be read(e.g. the server parameter file exists on a shared disk that is not mounted), the logs are not also collected.
To prevent it, define the alert log and listener log in /opt/FJSVclora/etc/clgetoralog.conf using the full path so that you can securely collect them. Where they are stored is defined in background_dump_dest parameter. (background_dump_dest/diagnostic_dest parameter can be found in the initialization parameter file or the server parameter file. It can be also displayed by SQL “show parameter dest”.)
The following example shows how to define /opt/FJSVclora/etc/clgetoralog.conf:
COLLECTOBJ=/oracle/admin/orclsid/bdump/alert_orclsid.log COLLECTOBJ=/oracle/product/network/log/listener.log
* background_dump_dest = /oracle/admin/orclsid/bdump
Start with “COLLECTOBJ=” and specify the file name using the full path after “=”.
Wild card characters “*” cannot be used in the middle of the path name.
COLLECTOBJ=/oracle/admin/orclsid/bdump/*.trc [OK] COLLECTOBJ=/oracle/admin/*/bdump/*.trc [NG]
If the size of the troubleshooting information including the information which defined /opt/FJSVclora/etc/clgetoralog.conf exceeds 10MB, the troubleshooting information is collected except for the information which defined /opt/FJSVclora/etc/clgetoralog.conf.
The -a option will collect the troubleshooting information including the information which defined /opt/FJSVclora/etc/clgetoralog.conf even if the size exceeds 10MB.