My Oracle Support Banner

Guided SR: ORA 600 [qccprg:ocistmtprepare2] (Doc ID 1961311.1)

Last updated on JANUARY 12, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

ORA 600 [qccprg:ocistmtprepare2] appear in alert log for JB_CDC$_DEFAULT_PURGE_JOB when using CDC

Even after the application of Patch 19780001 which contains the fix for Bug 19487518  as referenced in Note 1938815.1

Alert log contains:

Errors in file <path>/sid_ora_24002.trc:
ORA-12012: error on auto execute of job 4960
ORA-14012: resulting partition name conflicts with that of an existing partition
ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298

Trace file contains:

ORA-00600: Interner Fehlercode, Argumente: [qccprg:ocistmtprepare2], [14012], [ORA-14012: Resultierender Partitionsname kollidiert mit dem einer vorhandenen Partition
], [], [], [], [], [], [], [], [], []

========= Dump for incident 100173 (ORA 600 [qccprg:ocistmtprepare2]) ========

*** 2015-01-12 10:50:00.964
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=d1hnqzcpxxjk1) -----
DECLARE job BINARY_INTEGER := :job;  next_date TIMESTAMP WITH TIME ZONE := :mydate;  broken BOOLEAN := FALSE;  job_name VARCHAR2(30) := :job_name;  job_subname VARCHAR2(30) := :job_subname;  job_owner VARCHAR2(30) := :job_owner;  job_start TIMESTAMP WITH TIME ZONE := :job_start;  job_scheduled_start TIMESTAMP WITH TIME ZONE := :job_scheduled_start;  window_start TIMESTAMP WITH TIME ZONE := :window_start;  window_end TIMESTAMP WITH TIME ZONE := :window_end;  chain_id VARCHAR2(14) :=  :chainid;  credential_owner varchar2(30) := :credown;  credential_name  varchar2(30) := :crednam;  destination_owner varchar2(30) := :destown;  destination_name varchar2(30) := :destnam;  job_dest_id varchar2(14) := :jdestid;  log_id number := :log_id;  BEGIN  SYS.DBMS_CDC_PUBLISH.PURGE();  :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
0x54345a7e0       843  package body SYS.DBMS_CDC_PUBLISH
0x54344ebf8         1  anonymous block

----- Call Stack Trace -----
OCIKSIN qccprg_purgeSplitAndDropPartition qccprg_physicalPurgeTable qccprg_purgeChangeSet qccprg_purgeAllSets qccpub_purgeEP
spefcmpa spefmccallstd pextproc peftrusted psdexsp rpiswu2 psdextp pefccal pefcal pevm_FCAL pfrinstr_FCAL pfrrun_no_tool pfrrun
plsql_run peicnt kkxexe opiexe kpoal8 opiodr kpoodr upirtrc kpurcsc kpuexec OCIStmtExecute jslvec_execcb jslvswu jslve_execute0
jslve_execute rpiswu2 kkjex1e kkjsexe kkjrdp opirip opidrv sou2o opimai_real main

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
References


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