Workflow Log Reference

Purpose

Defines the primary log locations used to support troubleshooting across common workflow operations. It is intended to help administrators and support engineers quickly identify the correct logs for provisioning, patching, scaling, backup, upgrade, and related lifecycle activities.

Scope

This procedure applies to the following workflow categories:

  • Database and database home lifecycle operations
  • Grid and database upgrade activities
  • Backup and recovery operations
  • Data Guard operations
  • PDB lifecycle operations
  • VM, storage, and OCPU scaling actions
  • SSH key, encryption key, and virtual IP operations

Prerequisites

Before reviewing logs, confirm the following:

  • The database name (<dbname>) is known.
  • The database home name (<dbHome>) is known, if applicable.
  • The workflow type has been identified.
  • You have access to the relevant host or system where the logs are stored.
  • For DomU/KVM-related operations, verify whether workflow logs are expected on DomU. In several cases, no DomU-specific logs are required.

Table 6-34 Log Reference

Workflow Primary log location
Database Home Creation / Deletion
  • /var/opt/oracle/log/<dbHome>/create/*
  • /var/opt/oracle/log/<dbHome>/delete/*
Database Creation / Deletion
  • /var/opt/oracle/log/<dbname>/database/create/*
  • /var/opt/oracle/log/<dbname>/database/delete/*
Database Backup /var/opt/oracle/log/<dbname>/dtrs/rman/bkup/*
Grid Upgrade Precheck / Upgrade /var/opt/oracle/log/grid/upgrade/*
Grid Patch Precheck / Apply /var/opt/oracle/log/grid/patch/*
Memory Reshape
  • /var/opt/oracle/log/precheck_memory_resize/precheck_memory_resize_<YYYY-MM-DD_HH24_*>.log
  • /var/opt/oracle/log/available_mem_script/available_mem_script_<YYYY-MM-DD_HH24_*>
DomU / KVM Guest OS Precheck / Upgrade

All nodes: /var/log/cellos/*

dbserver_patch logs

  • Cloud UI Console: /u02/dbserver.patch.zip_exadata_ol*Linux-x86-64.zip/dbserver_patch_*/patchmgr_log.<TIMESTAMP>
  • Command line:
    • /root/patch/dbserver_patch_<patchmgr_version>/patchmgr.*
    • /root/patch/dbserver_patch_*/Diag_patchmgr*
Data Guard Provisioning (Add Standby)
  • /var/opt/oracle/log/<dbname>/dataguard/*
  • /var/opt/oracle/log/<dbname>/dataguard/prepareForStandby/*
  • /var/opt/oracle/log/<dbname>/dataguard/configureStandby/*
Data Guard Switchover /var/opt/oracle/log/<dbname>/dataguard/switchover/*
Data Guard Reinstate /var/opt/oracle/log/<dbname>/dataguard/reinstate/*
DB Upgrade / Precheck /var/opt/oracle/log/<dbname>/database/upgrade/*
SSH Key Addition /var/log/secure/var/log/messages/opt/oracle/dcs/log/dcs-agent-n.log
Add / Drop VM No DomU workflow logs are required.
OCPU Scaling No DomU workflow logs are required.
Storage Scaling /var/opt/oracle/log/precheck_asm_resize/precheck_asm_resize_YYYY-MM-DD_HH24:MI:SS*.log
DB Update No DomU workflow logs are required.
PDB Create / Terminate / Clone
  • Create: /var/opt/oracle/log/<dbname>/pdb/create/*
  • Terminate: /var/opt/oracle/log/<dbname>/pdb/delete/*
  • Clone: /var/opt/oracle/log/<dbname>/pdb/clone/*
PDB Stop / Start / Bounce
  • Start: /var/opt/oracle/log/<dbname>/pdb/open/*
  • Stop: /var/opt/oracle/log/<dbname>/pdb/close/*
  • Bounce: /var/opt/oracle/log/<dbname>/pdb/bounce/*
Add / Edit Automatic Backup
  • /var/opt/oracle/log/<dbname>/dtrs/rman/bkup/*
  • /var/opt/oracle/log/dtrs/*
  • /var/opt/oracle/log/dtrs/jobs/*
Encryption Key Operations
  • /opt/oracle/dcs/log/dcs-agent-n.log
  • /opt/oracle/dcs/log/dcs-agent-requests-n.log
Attach Virtual IP Address
  • /opt/oracle/dcs/log/dcs-agent-n.log
  • /opt/oracle/dcs/log/dcs-agent-requests-n.log

Procedure

  1. Identify the workflow being performed.
  2. Confirm the database name, database home name, and host context as applicable.
  3. Navigate to the log location listed in the Log Reference section.
  4. Review the relevant log files for errors, warnings, timestamps, and workflow-specific messages.
  5. If no issue is found in the primary log location, check adjacent system logs or DCS logs where applicable.
  6. Escalate the issue with the collected log evidence if required.

Troubleshooting

If logs are not found or appear incomplete:

  • Confirm the workflow completed on the expected host.
  • Verify the database name and database home name used in the path.
  • Check whether the operation generated logs on a different node.
  • For DomU/KVM guest OS operations, confirm whether workflow-specific logs are expected in DomU. In some cases, no DomU logs are required.
  • Review supporting OS or DCS logs such as /var/log/messages, /var/log/secure, and /opt/oracle/dcs/log/* when relevant.
  • If timestamps are available, use them to correlate events across multiple logs.

Parent topic: Reference Guides for Exadata Cloud Infrastructure