OBIA 11g Executing Domain Load Plan failed with error-ODI-1529: Refresh of variable "<SCHEMANAME>.13P_CALENDAR_ID" failed
(Doc ID 1921861.1)
Last updated on NOVEMBER 28, 2019
Applies to:Business Intelligence Applications Consumer - Version 126.96.36.199.1 and later
Information in this document applies to any platform.
Getting the following error after successfully generating and while executing the Domain load plan:
ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with: ADF_FACES-60096:Server Exception during PPR, #4
The installation (seem to have) worked well , with no errors up to "Running the Domains Load Plan". Generate Load plans succeeded.
The first error in the module was :
ODI-1519: Serial step "Start Load Plan (InternalID:1500)" failed because child step "Global Variable Refresh (InternalID:2500)" is in error.
ODI-1529: Refresh of variable "<SCHEMANAME>.13P_CALENDAR_ID" failed :
select CASE WHEN 'Global Variable Refresh' in (select distinct group_code from C_PARAMETER_VALUE_FORMATTER_V where PARAM_CODE= '13P_CALENDAR_ID')THEN (select param_valuefrom C_PARAMETER_VALUE_FORMATTER_Vwhere PARAM_CODE= '13P_CALENDAR_ID'and group_code='Global Variable Refresh'and datasource_num_id = '#<SCHEMANAME>.WH_DATASOURCE_NUM_ID')ELSE(select param_value from C_GL_PARAM_VALUE_FORMATTER_V where PARAM_CODE= '13P_CALENDAR_ID' and datasource_num_id = '#<SCHEMANAME>.WH_DATASOURCE_NUM_ID')ENDfrom Dual
0:72000:java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
Upon investigating and setting up audit trail for users on the BI database (188.8.131.52 EE), user found that the process was attempting to connect to a schema by the name of " NULLBIACM_IO" .
User schema names in the database are :
- <PREFIX>_BIACOMP and
The error was:
ODI-1228: Task SrcSet0 (Loading) fails on the target ORACLE connection <PREFIX>_BIACOMP.Caused By: java.sql.SQLSyntaxErrorException: ORA-01918: user 'NULLBIACM_IO' does not exist
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