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 PRECHECK-OracleVersion.log file contains a detailed log of the most latest precheck action, such as PSU-PRECHECK-19.0.0.0.log or JVM-PRECHECK-19.0.0.0.log.
4. The PATCH-OracleVersion.log file, for example, PATCH-19.0.0.0.log, is a detailed log of the latest patch action.
5. The PATCH-OracleVersion.log file contains a detailed log of the most latest patch action, such as PSU-PATCH-19.0.0.0.log or JDK-PATCH-19.0.0.0.log or OJVM-PATCH-19.0.0.0.log.
6. The ROLLBACK-OracleVersion.log file file, for example, ROLLBACK-19.0.0.0.log, is a detailed log of the latest rollback action.
7. The ROLLBACK-OracleVersion.log file file contains a detailed log of the most latest patch action, such as PSU-ROLLBACK-19.0.0.0.log or OJVM-ROLLBACK-19.0.0.0.log or JDK-ROLLBACK-19.0.0.0.log.
8. The logs folder contains a 6-month history of precheck, patch, and rollback logs.
9. Patch issues:
   Important:

   If an OPatch file exists, verify that it is the correct version. If Opatch file is incorrect, either replace it manually with the correct version or delete it and allow the Fixlet to download the appropriate file.

   If the cluster is in Rolling Mode, switch it to Normal Mode before proceeding with the patching process.

   Confirm that all required resources, such as databases, are running properly.