Error While Running "load_config_item_tags" And "load_config_item_types" (Doc ID 408282.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 6.7.0.1.1 and later
HP 9000 HP-UX 11.0 (32 bit)
***Checked for relevance on 21-Jul-2010***


Symptoms

1. Error occurred while loading config_items_tags_imt.xml

a. command line:

/portal/6.7/pin/sys/data/pricing/example>
load_config_item_tags -dv config_items_tags_imt.xml


b. error returned:

Parsing XML File: config_items_tags_imt.xml
Error at file /app/BR/portal/6.7/pin1d55/sys/data/pricing/example/config_items_tags_imt.xml, line 2, char 240 Message: Schema in ../../../../apps/pin_billd/BusinessConfiguration.xsd has a different target namespace from the one specified in the instance document http://www.portal.com/InfranetXMLSchema.

Error at file /app/BR/portal/6.7/pin1d55/sys/data/pricing/example/config_items_tags_imt.xml, line 2, char 240 Message: Unknown element 'BusinessConfiguration'

Fatal Error at file /app/BR/portal/6.7/pin1d55/sys/data/pricing/example/config_items_tags_imt.xml, line 11, char 2 Message: Expected an element name
Errors occurred during parsing
XML file is invalid.



2. Error occurred while loading config_items_types_imt.xml

a. command line:

/portal/6.7/pin/sys/data/pricing/example>
load_config_item_tags -dv config_items_types_imt.xml


b. error returned:


Parsing XML File: config_items_types_imt.xml
Error at file /app/BR/portal/6.7/pin1d55/sys/data/pricing/example/config_items_types_imt.xml, line 2, char 240 Message: Schema in ../../../../apps/pin_billd/BusinessConfiguration.xsd has a different target namespace from the one specified in the instance document http://www.portal.com/InfranetXMLSchema.

Error at file /app/BR/portal/6.7/pin1d55/sys/data/pricing/example/config_items_types_imt.xml, line 2, char 240 Message: Unknown element 'BusinessConfiguration'

Fatal Error at file /app/BR/portal/6.7/pin1d55/sys/data/pricing/example/config_items_types_imt.xml, line 5, char 2 Message: Expected an element name
Errors occurred during parsing
XML file is invalid.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms