There may be occasions when it is necessary to capture Oracle Clusterware or Oracle Database log files.

There are several means of capturing Oracle-related logs within a Storage Foundation environment. Two such scripts are getdbac and getsfrac - both residing in /opt/VRTSvcs/bin. They both function in the same way. The former is called by the VRTSexplorer script when it detects that the VRTSdbac package is installed

 

Further below is output produced when running the getdbac or getsfrac script. Please note that both are only present if the VRTSdbac package is present or Storage Foundation for Oracle RAC is present.

When running either of the scripts, requests will be made for oracle environment variables and database names as per below:

# type getdbac
getdbac is /opt/VRTSvcs/bin/getdbac
# getdbac
Starting getdbac
getdbac: Collecting data for node1
Please enter ORACLE_BASE for node1
/app/oracle
Please enter ORA_CRS_HOME for node1 [Required for Oracle 10g only]
/app/crshome
Please enter ORACLE_HOME for node1
/app/oracle/orahome
Please enter DB_NAME for node1
latestdb
Collecting Oracle CRS logs
Collecting Oracle binaries -- please wait
Collecting VCSMM data -- please wait
Collecting LMX data -- please wait
.
.
getdbac: completed. results in /tmp/vcsopslog.0720_18_10_43.node1.tar.Z

The above file can then be forwarded onto Veritas Technical Support via the usual methods


Supplementary information on getdbac and getsfrac

The getdbac and getsfrac scripts capture the following sort of Oracle information:

# ls
adump   bdump   cdump   dpdump  hdump   pfile   udump

In particular, the bdump directory will contain specific database alert logs and trace files; the pfile will contain the relevant init.ora file

Other files collected are below, and relate to other parts of the stack within the Storage Foundation for Oracle RAC product:

# pwd
/tmp/vcsopslog.0720_18_10_43.node1

# ls
date                     ora_trc.node2.tar  vcsmmdmp.node2     vxfenpkg.node1
dbacpkg.node1      shared.keys              vxdgact.node1      vxfenpkg.node2
dbacpkg.node2      strg.32.node1      vxdgact.node2      vxfentab.node1
hostname                 strg.32.node2      vxdisk.node1       vxfentab.node2
lmxout.node1       strg.64.node1      vxdisk.node2       vxprint.node1
lmxout.node2       strg.64.node2      vxdisks.shared           vxprint.node2
messages.node1     vcsmmdeb.node1     vxfen.keys
messages.node2     vcsmmdeb.node2     vxfendbg.node1
ora_trc.node1.tar  vcsmmdmp.node1     vxfendbg.node2

 

Note that both of the scripts can be run without impacting production