Troubleshooting EBS-BI integrated authentication can be a tiresome activity, so here’s a shortcut that might help. If you suspect the problem lies with EBS then you can leave OBIEE out of the equation.
-
Login to EBS
-
Click the BI link from EBS
-
Should be first a request to EBS server, which returns 302 and redirects to
http://<bi server>:<port>/analytics/saw.dll?Dashboard&acf=101507310
-
Record the value of acf (eg
101507310
)
-
Record the value of the cookie that’s passed to BI. It should normally match the EBS TNS name (but doesn’t have to). In this example it’s EBSBIS1A, and the value is
_ACpwGUoeCKUX7GilVh7ZZKR:S
-
Use sqlplus to open a connection to the EBS database using the ID that BI connects as (eg EBS_BI)[sourcecode]$sqlplus EBS_BI/password@EBSDATABASE
SQL*Plus: Release 11.1.0.6.0 - Production on Mon May 17 13:10:11 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> [/sourcecode]
-
Enter this statement, substituting values as appropriate
call /* acf */ APP_SESSION.validate_icx_session(‘cookie value’); eg: [sourcecode]SQL> call /* 101507310 */ APP_SESSION.validate_icx_session(’_ACpwGUoeCKUX7GilVh7ZZKR:S’);[/sourcecode] -
Expect to get:[sourcecode]Call completed.
SQL>[/sourcecode]
-
If the cookie ID is invalid you’ll get [sourcecode]ERROR at line 1: ORA-06510: PL/SQL: unhandled user-defined exception ORA-06512: at “APPS.APP_SESSION”, line 315 [/sourcecode]
After writing this I discovered My Oracle Support article 758392.1 which has the same info plus a bit more.