| PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide 4.2 - Linux for Itanium - |
|
Contents
|
| Chapter 4 Command |
Super user
/opt/FJSVclora/bin/clgetoralog [-n RMSconfiguration ] [-d output_directory ] [-a ]
clgetoralog collects Oracle information for troubleshooting. "clgetoralog" command collects Oracle setup information and log files on a PRIMECLUSTER system. The information will be collected in the "<hostname>_<yymmddHHMMSS>_clgetoralog.tar.Z" (or tar.gz)" file.
The "clgetoralog" command collects
- Initialized 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
- 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)
cat /proc/cpuinfo (CPU information)
cat /proc/version (Linux version)
sysctl -a (kernel parameter)
ipcs (shared resources)
cat /proc/swaps (swap information)
ptree -pal, ps -efw, ps -ewm -o (process information)
ntpq -p (NTP information)
/var/log/messages file
"pclsnap" command can also be used to collect troubleshooting information.
[ -n RMSconfiguration ]
Specify the RMS configuration name for RMSconfiguration.
If this option is specified, clgetoralog command will collect RMS configuration information in addition to the information described in "Function". You can check the RMS configuration name using the following command if RMS is running.
|
# /opt/SMAW/bin/hvdisp -a | grep Configuration |
If this option is omitted, the command will collect information described in "Function" only.
[ -d output_directory ]
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 Z" (or tar.gz)" file under the default directory (/var/tmp/).
[ -a ]
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/log/messages (all generations)
- /etc/hosts
- /etc/passwd
- /etc/services
- /etc/fstab
- /etc/fstab.pcl
If this option is omitted, the command will collect information described in "Function" only.
0: Normal termination
Non-0: Abnormal termination
This command gets the value of background_dump_dest parameter from the initialized parameter file or the server parameter file, and searches the Oracle alert 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 alert log is not also collected.
To prevent it, define the alert log in /opt/FJSVclora/etc/clgetoralog.conf using the full path so that you can acquire the alert log. Where the alert log is stored is defined in background_dump_dest parameter. (background_dump_dest parameter can be found in the initialized parameter file or the server parameter file. It can be also displayed by SQL "show parameter background_dump_dest".)
The following example shows how to define /opt/FJSVclora/etc/clgetoralog.conf:
|
COLLECTOBJ=/oracle/admin/orclsid/bdump/alert_orclsid.log |
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) |
If wild card characters are frequently used, and the data size becomes larger than 10MB, you can not collect troubleshooting information.
|
Contents
|