My Oracle Support Banner

Disconnected Mode clients fail with XML-22008 due to XDO Engine of BIP10g (Doc ID 2104618.1)

Last updated on APRIL 18, 2023

Applies to:

Siebel CRM - Version 15.0 [IP2015] and later
Information in this document applies to any platform.
BI Publisher 11g


After upgrading BI Publisher from BIP10g to BIP11g and creating or modifying templates with BIP Desktop 11g, reports generate successfully with Connect clients (thin clients) but not with Disconnected clients (connected to server or local database).

The following error can be found after increasing xdodebug.cfg:

<Line 75, Column 107>: XML-22008: (Error) Namespace prefix 'ref' used but not declared.

[020216_112458489][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) is called.
[020216_112458490][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) done. All inputs are cleared.
[020216_112458491][oracle.apps.xdo.template.FOProcessor][ERROR] End Memory: max=96MB, total=38MB, free=18MB
[020216_112458492][][EXCEPTION] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeNewXSLStylesheet(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
at Source)
at Source)
at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
at com.siebel.apps.shared.xmlp.XMLPAdapter.createOutput(
at com.siebel.apps.shared.xmlp.XMLPReportBusvc.doInvokeMethod(
at com.siebel.eai.SiebelBusinessService.invokeMethod(
Caused by: org.xml.sax.SAXException: Namespace prefix 'ref' used but not declared.
oracle.xdo.parser.v2.XPathException: Namespace prefix 'ref' used but not declared.
at oracle.xdo.parser.v2.XSLProcessor.reportException(
at oracle.xdo.parser.v2.XSLProcessor.newXSLStylesheet(
... 14 more



 Issue started after upgrading BI Publisher from 10g to 11g, modifying/creating new templates with BIP Desktop 11g and deploying to Disconnected clients.


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.