Skip to main content

Resolving ORA-01109 and ORA-00600 when provisioning Oracle vPDB to a RAC CDB in Oracle 19.9 or later (KBA9238)




KBA# 9238



When provisioning a vPDB to a Linked RAC CDB running Oracle 19.9 or later, you may encounter an ORA-00600 or ORA-01109 error such as the following:

Failed to execute query on source database due to: StatementCallback; uncategorized SQLException for SQL [set role all]; SQL state [64000]; error code [1109]; ORA-01109: database not open ; nested exception is com.delphix.exception.UnwrappedExecutionException: (originally: org.springframework.jdbc.UncategorizedSQLException) . An error was received when executing the query. This typically indicates that the connection to the database has been lost.

Error Code

Suggested Action
Check connectivity.

In some cases, the Provision operation might succeed, but the CDB may fail shortly afterwards.

When this occurs, the CDB's alert log will include an ORA-00600 error referencing the krccfl_chunk function:

Recovery of Online Redo Log: Thread 2 Group 8 Seq 404 Reading mem 0
  Mem# 0: +ASMSTORE/CDBNAME/ONLINELOG/group_8.912.1105472143
  Mem# 1: +ASMSTORE/CDBNAME/ONLINELOG/group_8.23232.1105472145
Errors in file /oracle/product/diag/rdbms/cdbname/instancename/trace/instancename_smon_22052.trc  (incident=192337) (PDBNAME=CDB$ROOT):
ORA-00600: internal error code, arguments: [krccfl_chunk], [0x7FFFF02091E0], [128], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/product/diag/rdbms/cdbname/instancename/incident/incdir_192337/instancename_smon_22052_i192337.trc

This error is caused by a change in recovery behavior in Oracle 19.9 and later, where data files must be accessible to all RAC nodes before recovery can complete successfully for a RAC PDB. It is described further in Oracle's document Ora-600 Krccfl_chunk When Block Change Tracking enabled (Doc ID 2046745.1).


This issue is only known to occur when all of the following are present:

  • The Continuous Data Engine is running version or earlier
  • The Target CDB is running as a RAC Cluster
  • The Target CDB is running Oracle 19.9 or later
  • The Target CDB has Block Change Tracking Enabled

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases



This issue is resolved in Continuous Data Engine and later (issue reference: DLPX-74681). These versions include changes to the recovery process to avoid triggering this behavior.

In cases where an upgrade is not possible, you can disable Block Change Tracking on the Target CDB to allow recovery to complete, as listed in the workaround of the Oracle document Ora-600 Krccfl_chunk When Block Change Tracking enabled (Doc ID 2046745.1):

SQL> alter database disable block change tracking;
SQL> alter database open;

Please work with your database administrator(s) to ensure that this change is appropriate for your Target CDB environment.

If any failed vPDBs are still present within the Target CDB once this is resolved, it should be possible to open the vPDB within each CDB instance, and then delete the failed vPDB from the Management Interface of the Continuous Data Engine.



Related Articles

The following articles may provide more information or related information to this article: