1. Database Upgrade Guide
  2. Logging and Diagnostics

Logging and Diagnostics

Review any logging and diagnostic information in the following log files: WSRanking, WFUpgrade, and TaskUpgrade.

WSRanking Logs

To review detailed logs for the WSRanking utility, see the WSRanking_xxxxxxxxx subdirectory in the following (or equivalent) folder location:

...\ses\siebsrvr\log\PostInstallDBSetup_xxxxxxxxx

The Workspace Ranking utility makes a minor schema update to increase the column length of one of the Workspaces related columns (WS_OBJ_VER).

WFUpgrade Logs

To review detailed logs for the WFUpgrade utility, see the WorkflowUpgrade.log file in the following (or equivalent) folder location: 

...\ses\siebsrvr\log\PostInstallDBSetup_xxxxxxxxx

The Workflow Upgrade utility runs in both development (Design Time Repository or DR) and production (Runtime Repository or RR) environments. The utility generates RR definitions for Workflow Processes, if it has not previously been executed.

  • Workflow DR Upgrade. There may be multiple versions of the same workflow in different Workspaces; however, only one version of a workflow can be used at runtime in the DR environment. Each workflow must have a corresponding S_RR_WORKFLOW record. The WFUpgrade utility takes care of this by generating RR definition records in S_RR_WORKFLOW for each workflow version in MAIN and Integration branches.

  • Workflow RR Upgrade. In RR environments, RR definitions for workflows are generated from the S_WFA_DPLOY_DEF table.

TaskUpgrade Logs

To review detailed log for the TaskUpgrade utility, see the TaskUpgrade.log file in the following (or equivalent) folder location:

...\ses\siebsrvr\log\PostInstallDBSetup_xxxxxxxxx

The Task Upgrade utility runs in both development (DR) and production (RR) environments. The utility generates RR definitions for Tasks, if it has not previously been executed.

  • Task DR Upgrade. There may be multiple versions of the same task in different Workspaces; however, only one version of a task can be used at runtime in the DR environment. Each task must have a corresponding S_RR_TASK record. The TaskUpgrade utility takes care of this by generating Runtime Repository definition records in S_RR_TASK for each task version in the MAIN and Integration branches.

  • Task RR Upgrade. In RR environments, RR definitions for tasks are generated from the S_TU_TASK table.

Resumable Utilities

Review the standard utility logs and resume state information when diagnosing Post Installation Database Update or RepositoryUpdate execution.

For PostInstallDBSetup, review the following logs:

  • WSRanking logs in the WSRanking_xxxxxxxxx subdirectory.
  • Workflow Upgrade information in WorkflowUpgrade.log.
  • Task Upgrade information in TaskUpgrade.log.
  • Other logs in the applicable PostInstallDBSetup_xxxxxxxxx directory.
For resumable executions, the following additional state and diagnostic information is available.

Resume State

The state.json file in the run log directory contains the checkpoint and substep state for the logical execution and its execution attempts.

The S_APP_VER_HIST.RESUME_STATE_JSON column contains a compact, durable locator and validation reference for the logical execution.

Use the resume state information to identify:

  • The logical execution and execution mode.
  • The attempt number.
  • The current and previous execution status.
  • The active checkpoint and substep.
  • The operations completed, skipped, failed, pending, in progress, or blocked.
  • Applicable error information.
  • The current and previous log directories.

The resume state also records execution information required to validate whether an unfinished execution is compatible with the current invocation.

RepositoryUpdate Diagnostic Information

For RepositoryUpdate executions involving repository bulk imports, review the Repository.log and any archived copies of the log.

The repository import log provides the information used to reconcile generated Repository files after a failed bulk-import operation.

Repository.log.progress provides supporting progress information, but is not treated as final evidence that an individual generated Repository file completed successfully.

Retaining Logs and State

Administrators must retain the update history and associated utility log directory when investigating or resuming an unfinished execution.

Do not manually modify RESUME_STATE_JSON or state.json.

When a previous log directory can be resolved, a resumed attempt continues to use the saved log location so that information from the original and resumed attempts remains available together.