After Roll Back of OPLA Patch, Error ORA-04098: Trigger 'AGILE_ODIWORK.T$ODM_USER_GROUP' Is Invalid and Failed Re-Validation on Full Load (Doc ID 2042652.1)

Last updated on NOVEMBER 23, 2015

Applies to:

Oracle Product Lifecycle Analytics - Version 3.3.1.2 and later
Information in this document applies to any platform.

Symptoms

Unable to run Full Load with below error after rolling back the patch
 

Error
ODI-1226: Step odi_int_ODM_USER_GROUP_9223_full fails after 1 attempt(s).
ODI-1240: Flow odi_int_ODM_USER_GROUP_9223_full fails while performing a Integration operation. This flow loads target table null.
ODI-1228: Task odi_int_ODM_USER_GROUP_9223_full (Integration) fails on the target ORACLE connection TRG_ODMCONN_PHYSICAL.
Caused By: java.sql.SQLSyntaxErrorException: ORA-04098: trigger 'AGILE_ODIWORK.T$ODM_USER_GROUP' is invalid and failed re-validation


Steps
Apply patch:1966531, and roll back the patch according to the instruction in "Oracle Product Lifecycle Analytics Patch Installation Readme Nov 2014 3.3.1.3.0" as below:
1. Restore the following schemas by importing the previously backed up database export dumps to schemas with the same username and password:
 a. ODI Work Repository
 b. Stage or ODM Schema
 c. MDS Schema
2. Remove the temp tables (i$, j$ and C$) from all the schemas.
3. Restore the RPD file by importing it from its backup location.
4. Change the ETL configuration to run Data Mart or Stage and MDS in FULL load mode.


Changes

Applied OPLA patch:1966531 to upgrade to OPLA 3.3.1.3 and uninstalled the patch

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms