OBIA 11g: Session SDE_FUSION_HRASSIGNMENTHISTORYDIMENSION Fails With "Error Occured While Running Below SDS Parsing SQL"
(Doc ID 2755184.1)
Last updated on DECEMBER 03, 2021
Applies to:
Oracle Business Intelligence Applications - Version 11.1.1.10.3 to 11.1.1.10.3 [Release 11g]Information in this document applies to any platform.
Symptoms
Session SDE_FUSION_HRASSIGNMENTHISTORYDIMENSION with customization fails with the below error.
<Field name="CecSessReqId" type="com.sunopsis.sql.DbInt"><![CDATA[null]]></Field>
<Field name="ContextCode" type="java.lang.String"><![CDATA[GLOBAL]]></Field>
<Field name="ErrorMessage" type="java.lang.String"><![CDATA[ODI-1217: Session TEST_RC4 (17868) fails with return code 20942.
ODI-1226: Step Diagnostics Raise Exception fails after 1 attempt(s).
ODI-1232: Procedure Diagnostics Raise Exception execution fails.
ODI-1228: Task Procedure-Diagnostics Raise Exception-Raise Diagnostic Error fails on the target connection BIAPPS_DW.
Caused By: java.sql.SQLException: ORA-20942: ODI-1590: The execution of the script failed.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "<string>", line 370, in <module>
::: Error occured while running below SDS parsing SQL :
: create or replace view BIDEV_DW.C$_17868_2_1ASGDFF as
select
SQ_ASGDFF_ASGDFF.s_k_5000 AS S_K_5000,
SQ_ASGDFF_ASGDFF.s_k_5001 AS S_K_5001,
SQ_ASGDFF_ASGDFF.ASGDFF_SRC_LAST_UPDATE_DATE AS ASGDFF_SRC_LAST_UPDATE_DATE,
SQ_ASGDFF_ASGDFF.s_k_5004 AS S_K_5004,
Default.STTS.ASSIGNMENT_ATTRIB1_CHAR AS X_ASSIGN_STATUS_DESC,
SQ_ASGDFF_ASGDFF.ASSIGNMENT_ATTR1_CHAR AS ASSIGNMENT_ATTR1_CHAR
from
(
select
ASGDFF. => ORA-20942:
ORA-06512: at line 73
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:495)
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:447)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1055)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:624)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:253)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:613)
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 |