My Oracle Support Banner

DIPC/DIPC-C Data Synchronization Fails with ORA-39006: internal error ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.DBMS_DATAPUMP" (Doc ID 2433943.1)

Last updated on APRIL 23, 2019

Applies to:

Data Integration Platform Cloud Classic - Version 18.2.3 and later
Data Integration Platform Cloud - Version 18.2.3 and later
Information in this document applies to any platform.

Symptoms

This knowledge article reflects updated product names. Data Integration Platform Cloud (DIPC) was formerly known as Autonomous Data Integration Platform Cloud (ADIPC). Data Integration Platform Cloud Classic (DIPC Classic or DIPC-C) was formerly known as Data Integration Platform Cloud (DIPC). Please see KM <document 2493395.1> for the full list of recently renamed PaaS services.
NOTE: In the examples contained in this article, values used represent a fictitious sample for clarity. Any similarity to actual environments, past or present, or users, living or dead, is purely coincidental and not intended in any manner.

During a synchronization of data between two schemas in the same Pluggable Database (PDB), the Data Integration Platform Cloud Classic (DIPC-C) or Data Integration Platform Cloud (DIPC) job fails with the following error message:

ODI-1228: Task Procedure-Initial load_PROC-DBLINK_DATAPUMP fails on the target connection <encrypted_connection_string>.
Caused By: java.sql.SQLException: ORA-39006: internal error ORA-06512:
  at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512:
  at "SYS.DBMS_DATAPUMP",
line 4932 ORA-06512:
  at "SYS.DBMS_DATAPUMP", line 6844 ORA-06512:
  at line 71 ORA-06512:
  at line 145 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:407)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1113)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:546)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:603)
  at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:218)
  at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:31)
  at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000)
  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1316)
  at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2168)
  at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2100)
  at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:363)
  at oracle.odi.runtime.agent.execution.sql.SQLCommand.execute(SQLCommand.java:205)
  at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:142)
  at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:28)
  at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:52)
  at oracle.odi.runtime.agent.execution.SessionTask.processTask(SessionTask.java:206)
  at oracle.odi.runtime.agent.execution.SessionTask.doExecuteTask(SessionTask.java:117)
  at oracle.odi.runtime.agent.execution.AbstractSessionTask.execute(AbstractSessionTask.java:886)
  at oracle.odi.runtime.agent.execution.SessionExecutor$SerialTrain.runTasks(SessionExecutor.java:2225)
  at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:610)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:718)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:611)
  at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)
  at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doProcessStartAgentTask(TaskExecutorAgentRequestProcessor.java:800)
  at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.access$2700(StartScenRequestProcessor.java:85)
  at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:917)
  at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:180)
  at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:108) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
  at oracle.odi.runtime.agent.execution.job.OdiJob.call(OdiJob.java:73)
  at oracle.odi.runtime.agent.execution.job.OdiJob.call(OdiJob.java:73)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at java.lang.Thread.run(Thread.java:748)

Changes

 

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
Changes
Cause
Solution
 For the source database schema
 For the target database schema
References


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