My Oracle Support Banner

[OCI-C] Creating Instance From Backup Fails With ORA-00600[qcisSetPlsqlCtx:tzi init] (Doc ID 2591744.1)

Last updated on SEPTEMBER 25, 2019

Applies to:

Oracle Database Cloud Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

Symptoms

In OCI-C environment a new instance was being created from a backup of another running instance in same domain.
Database was restored and recovered.
At the end when the database was being opened in resetlog mode following ORA-00600 error is being encountered and it only creates a default new instance:

ORA-00600: internal error code, arguments: [qcisSetPlsqlCtx:tzi init], [],

The new instance is created with Apr 2018 PSU by default.
The source DB (from where the backup is being used) is in Jul 2019 PSU.
The dbda log shows the following:

....
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ALTER DATABASE OPEN RESETLOGS
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: *
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ERROR at line 1:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ORA-00600: internal error code, arguments: [opiodr: call 2], [], [], [], [], [], [], [], [], [], [], []
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ORA-00600: internal error code, arguments: [qcisSetPlsqlCtx:tzi init], [], [], [], [], [], [], [], [], [], [], []
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ALTER DATABASE DISABLE BLOCK CHANGE TRACKING
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: *
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ERROR at line 1:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ORA-19759: block change tracking is not enabled
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ALTER DATABASE OPEN RESETLOGS
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: *
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ERROR at line 1:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ORA-00600: internal error code, arguments: [opiodr: call 2], [], [], [], [], [], [], [], [], [], [], []
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs: ORA-00600: internal error code, arguments: [qcisSetPlsqlCtx:tzi init], [], [], [], [], [], [], [], [], [], [], []
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs:
2019-09-13 23:59:04 - dbda::INFO _manage_redo_logs:
2019-09-13 23:59:04 - dbda::ERROR ORA Error
2019-09-13 23:59:04 - dbda::ERROR Unknown DB Instance condition (ORA)
2019-09-13 23:59:04 - dbda::ERROR _manage_redo_logs: FAILED
2019-09-13 23:59:04 - dbda::ERROR ORA Error

at /var/opt/oracle/ocde/assistants/dbda/dbda line 1400
main::configure() called at /var/opt/oracle/ocde/assistants/dbda/dbda line 504
eval {...} called at /var/opt/oracle/ocde/assistants/dbda/dbda line 475
2019-09-13 23:59:04 - dbda::ERROR Unknown DB Instance condition (ORA)

at /var/opt/oracle/ocde/assistants/dbda/dbda line 1400
main::configure() called at /var/opt/oracle/ocde/assistants/dbda/dbda line 504
eval {...} called at /var/opt/oracle/ocde/assistants/dbda/dbda line 475
2019-09-13 23:59:04 - ERROR : ibkup begin has failed, please check logs. You might be able to restore the dbcs env and re-run ibkp begin
2019-09-13 23:59:04 - ERROR : ibkup begin has failed, please check logs. You might be able to restore the dbcs env and re-run ibkp begin
at /var/opt/oracle/ocde/assistants/dbda/dbda line 1401
main::configure() called at /var/opt/oracle/ocde/assistants/dbda/dbda line 504
eval {...} called at /var/opt/oracle/ocde/assistants/dbda/dbda line 475
2019-09-13 23:59:04 - ERROR: ERROR : ibkup begin has failed, please check logs. You might be able to restore the dbcs env and re-run ibkp begin
...

The DST version from both source and target:

Target:

SQL> select NAME, VALUE$ from SYS.PROPS$ where NAME like ('DST_%_TT_VERSION');

NAME VALUE$
------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION 28
DST_SECONDARY_TT_VERSION 0

Source:

SQL> select NAME, VALUE$ from SYS.PROPS$ where NAME like ('DST_%_TT_VERSION');

NAME VALUE$
------------------------------ ------------------------------
DST_PRIMARY_TT_VERSION 31
DST_SECONDARY_TT_VERSION 0

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.