Standby Apply archives errors with THREAD_NUM[0] Is Empty

Read our docs Standby Errors out while applying Archive logs.

Problem Details

Problem Statement

Error Occurs while applying archivelog in standby

Applicable Error Code

20140711 21:47:14 Standby::Auxiliary::trace-> main::cmn_mail_logs: 
mail_log: 201407112147 - Dbvisit Standby error.
THREAD_NUM[0] is empty. Please contact Dbvisit support.
Dbvisit Standby terminated.
Return code = 408

Affected Versions

Version 6.0,7.0 and Database Version 9.2

Affected Platforms

Platform Independent

Description

When running Dbvisit Standby on the DR server the following error message is displayed, meaning that the archive logs are not applied:

20140711 21:47:14 Standby::Auxiliary::trace-> main::cmn_mail_logs: mail_log: 201407112147 - Dbvisit Standby error.
THREAD_NUM[0] is empty. Please contact Dbvisit support.
Dbvisit Standby terminated.
Return code = 408

Solution

This issue arises when using Oracle database version 9.2 specifically, where you have an archive_log_format without %t (threadnum) specified within it.

As a workaround (if you cannot change the archive log format) then add the following two lines to the DDC file on the primary server, and run Dbvisit Standby on the primary again (it will copy the changed DDC file to the standby). Then run Dbvisit Standby on the DR server after this.

THREAD_DEST = Y
THREAD_SOURCE = Y

This issue was first raised by a customer running on version 7.0.16, but it will likely exist in versions 7 and below, meaning that the workaround will be required in these environments where this issue arises.

Mike Donovan July 14, 2014 12:42

We're here to help!

Comments