My Oracle Support Banner

OBIEE 11g: Error: " [APP: bipublisher#11.1.1] Illegal parameter value: p_stm=000054 <userid removed for security reasons>" Passing a Dashboard Prompt Value to an Embedded BI Publisher Report (Doc ID 1622467.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Business Intelligence Suite Enterprise Edition - Version to [Release 11g]
Business Intelligence Server Enterprise Edition - Version to [Release 11g]
Information in this document applies to any platform.


In OBIEE, you have a dashboard using dashboard prompts which populate presentation variables. The dashboard includes pages with embedded BI Publisher Reports.
When you open the reports you get the following error: 

[2013-08-27T08:03:11.377+02:00] [bi_server1] [ERROR] [] [oracle.xdo] [tid: 21] [userId: <anonymous>] [ecid: 80027211986643af:-4b5ffddd:140bd66d83b:-8000-0000000000000d4a,0] [APP: bipublisher#11.1.1] Illegal parameter value: p_stm=000054 <userid removed for security reasons>
[2013-08-27T08:03:11.378+02:00] [bi_server1] [TRACE] [] [oracle.xdo] [tid: 21] [userId: <anonymous>] [ecid: 80027211986643af:-4b5ffddd:140bd66d83b:-8000-0000000000000d4a,0] [APP: bipublisher#11.1.1] [SRC_CLASS: oracle.xdo.servlet.monitor.AbstractOccurrence] [SRC_METHOD: errored] MonitoringEvent errored: class oracle.xdo.servlet.monitor.ReportRequestEvent:scheduled=false,report_runtime_property={},HTML_SESSION_ID=7Z6yScQpCYwj7VzbYKks2VVGTFPpvZypJk07LhjQW2LT7TlyCnkN!898819337!1377583166283,timezone=Europe/Amsterdam,_xuil=de,oracle.dms.context.http.WebRequestContextProcessed=true,_svg=false,userName=<userid removed for security reasons>,locale=de,format=xml,reportName=/Werkstatt/Reporting/Reports/<Template name removed for security reasons>.xdo,templateName=<Report name removed for security reasons>KW,_xservreq=weblogic.servlet.internal.RequestEventsFilter$EventsRequestWrapper@270a7b72
[2013-08-27T08:03:11.379+02:00] [bi_server1] [WARNING] [] [oracle.xdo] [tid: 21] [userId: <anonymous>] [ecid: 80027211986643af:-4b5ffddd:140bd66d83b:-8000-0000000000000d4a,0] [APP: bipublisher#11.1.

But these are valid parameter values. If you open the report from the catalog and use the same parameter values, it works fine.
Having done so, the report now opens without error in the dashboard.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.