Troubleshooting

Troubleshooting in Oracle DB involves diagnosing and resolving issues that might arise while you work with the database server, applications, or related components.

The following files found in the /var/opt/BESClient/ORACLE folder are useful for troubleshooting issues:

  1. The SIDlist.txt file contains the database information from /etc/oratab or /var/opt/oracle/oratab (Solaris) folders. The file also contains useful information that the Update policy action added: PSU patch level, OJVM patch level, the current OPatch version, and the Oracle user. These are the databases that the precheck, patch, and rollback Fixlets recognize, so Fixlets act on these databases.
    Important: If a database is not in the /etc/oratab or /var/opt/oracle/oratab (Solaris) then it is not included in the SIDlist.txt file., which means that Fixlets do not patch that database. Likewise, if the +ASM or +ASMn databases are not in the oratab file then they are not included in the SIDLIST.txt file, which means the server is not identified as RAC or ASM. Servers with no +ASM* database in the oratab folder are assumed to be standalone database servers. If a database looks like it's not getting prechecked or patched, verify that it's in the oratab file.
  2. The PRECHECK-OracleVersion.log file, for example, PRECHECK-19.0.0.0.log, is a detailed log of the latest precheck action.
  3. The PATCH-OracleVersion.log file, for example, PATCH-19.0.0.0.log, is a detailed log of the latest patch action.
  4. The ROLLBACK-OracleVersion.log file file, for example, ROLLBACK-19.0.0.0.log, is a detailed log of the latest rollback action.
  5. The logs folder contains a 6-month history of precheck, patch, and rollback logs.