EGRC 8.6.5.6050 or above: After Applying 8.6.5.6050 or above Patch, Access ETL/Synchronization Is Failing With "ODI-1240: Flow TCG_INTR_Users_21 fails" Error.
(Doc ID 1989106.1)
Last updated on SEPTEMBER 18, 2019
Applies to:
Oracle Application Access Controls Governor - Version 8.6.5 to 8.6.5 [Release 8]Information in this document applies to any platform.
Symptoms
On : 8.6.5.6050 version, Application Access Contr. Gov.
In Oracle Application Access Controls Governor (AACG), models and controls define conflicts among duties that can be assigned in a company’s applications, and identify users who have access to those conflicting duties.
AACG can also implement “preventive analysis” — it can evaluate controls as duties are assigned to users of the company’s applications, preventing them from gaining risky access.
After applying 8.6.5.6050 patch, when attempting to run Access ETL/Synch,
the following error occurs.
ERROR in grc.log
-----------------------
2015-03-04 15:42:48,280 DEBUG [SimpleAsyncTaskExecutor-1] Log4jPrintStream:71 STDOUT (oracle.core.ojdl.logging.ConsoleHandler:118)
2015-03-04 15:42:48,283 DEBUG [SimpleAsyncTaskExecutor-1] Log4jPrintStream:71 STDOUT (oracle.core.ojdl.logging.ConsoleHandler:118) ODI-1226: Step TCG_INTR_Users_21 fails after 1 attempt(s).
Caused by: ODI-1240: Flow TCG_INTR_Users_21 fails while performing a Integration operation. This flow loads target table Users.
Caused by: org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "", line 3, in ?
ImportError: cannot import name EtlExtractorFactory
ERROR in grc_domain.log
-------------------------------------
#### <> <> ODI-1226: Step TCG_INTR_Users_21 fails after 1 attempt(s).
Caused by: ODI-1240: Flow TCG_INTR_Users_21 fails while performing a Integration operation. This flow loads target table Users.
Caused by: org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "", line 3, in ?
ImportError: cannot import name EtlExtractorFactory
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade from 8.6.5.5039 to 8.6.5.6050.
2. Run Access ETL/Synch job for EBS datasource.
3. Monitor the job and check log files.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot run Access ETL/Synch job.
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 |