After Upgrade Of WebLogic From Version 12.1.2 To 12.1.3 - Access Synchronization Not Completing Successfully (Doc ID 2283687.1)

Last updated on OCTOBER 10, 2023

Applies to:

Symptoms

 8.6.6.5020: Access Sync/ETL fails on Weblogic 12.1.3. It works fine on Weblogic 12.1.2.

Error:

2017-07-04 16:58:08,740 DEBUG [Thread-110] EtlService:753 sync
ExecutedTransformCount:57
2017-07-04 16:58:08,740 DEBUG [Thread-110] EtlService:758
getProgressPercentage :42.5373134%
2017-07-04 16:58:11,083 DEBUG [SimpleAsyncTaskExecutor-1]
GrcLogPrintStream:73 STDOUT (oracle.core.ojdl.logging.ConsoleHandler:149)
<Jul 4, 2017 4:58:11 PM UTC> <Warning> <oracle.odi.agent> <BEA-000000> <Could
not rollback with auto-commit set on
java.sql.SQLException: Could not rollback with auto-commit set on

2017-07-04 16:58:11,130 DEBUG [SimpleAsyncTaskExecutor-1]
GrcLogPrintStream:73 STDOUT (oracle.core.ojdl.logging.ConsoleHandler:149)
<Jul 4, 2017 4:58:11 PM UTC> <Error> <Default> <ODI-1217> <Session
LOADACCESSDATACORE (8154) fails with return code 17273.
ODI-1226: Step LoadFunctionQueryOnlyAssociations fails after 1 attempt(s).
Caused by: ODI-1232: Procedure LoadFunctionQueryOnlyAssociations execution
fails.
Caused by: java.sql.SQLException: Could not commit with auto-commit set on

1. On Weblogic 12.1.2, Upgrade to 8.6.6.5000 from 8.6.6.4000.
2. Run Access Synchronization. It completes fine.
3. Upgrade or install new Weblogic 12.1.3 ( with corresponding RCU,ADR)
4. Run Access Synchronization on the same datasource. It Fails.

Business Impact:
users cannot use Weblogic 12.1.3

Cause

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