Error in importing install_root.xml

Hello Experts,
We are installing Sourcing 7.0 system on Windows 2008 CE 711 with oracle 11.2.0.1DB.
While importing install_root.xml file from DBIMPORT we are experiencing error in the step 'Install Platform System Data'
The error is
AssociatedAttribute=START_DATE - SourceBo=-2147483547:10502:Mail Messaging - ValidatingParent=-2147483547:10502:Mail Messaging - com.sap.odp.api.common.exception.ApplicationException: ID: exception.docommon.scheduled_task.bad_start
     at com.sap.odp.api.common.exception.ChainedExceptionFactory.createApplicationException(ChainedExceptionFactory.java:90)
     at com.sap.odp.common.db.PersistentBo.createApplicationException(PersistentBo.java:3237)
     at com.sap.odp.doccommon.daemon.manage.ManagedDaemonBo.validateHook(ManagedDaemonBo.java:688)
     at com.sap.odp.doc.ContainerBo.validate(ContainerBo.java:1362)
     at com.sap.odp.doc.ContainerDocBo.validate(ContainerDocBo.java:1299)
     at com.sap.odp.doc.AbsDocBo.validate(AbsDocBo.java:3811)
     at com.sap.odp.doc.BizDocBo.validate(BizDocBo.java:2133)
     at com.sap.odp.common.db.AbstractDb.validate(AbstractDb.java:6225)
     at com.sap.odp.common.db.AbstractDb.save(AbstractDb.java:3255)
     at com.sap.odp.doc.ContainerDb.save(ContainerDb.java:213)
     at com.sap.odp.doc.AbsDocDb.save(AbsDocDb.java:968)
     at com.sap.odp.common.db.AbstractDb.save(AbstractDb.java:3215)
     at com.sap.odp.doc.ContainerHome.save(ContainerHome.java:295)
     at com.sap.odp.doc.AbsDocHome.save(AbsDocHome.java:446)
     at com.sap.odp.doccommon.daemon.manage.importer.processors.ManagedDaemonProcessor.saveHook(ManagedDaemonProcessor.java:437)
     at com.sap.odp.doc.importer.AbsDocImportProcessor.processRow(AbsDocImportProcessor.java:187)
     at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processRowInternal(CsvFileProcessor.java:1362)
     at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processFile(CsvFileProcessor.java:280)
     at com.sap.odp.common.install.dataimport.csv.CsvImporter.go(CsvImporter.java:195)
     at com.sap.odp.install.actions.ProcessCsvFile.executeHook(ProcessCsvFile.java:159)
     at com.sap.odp.install.actions.InstallAction.execute(InstallAction.java:203)
     at com.sap.odp.install.engine.ScriptedImportEngine.runSingleItem(ScriptedImportEngine.java:319)
     at com.sap.odp.install.engine.DbSetupEngine.execute(DbSetupEngine.java:186)
     at com.sap.odp.install.tools.gui.DbGuiImporter.go(DbGuiImporter.java:282)
     at com.sap.odp.install.tools.gui.DbGuiImporter$InstallThread.run(DbGuiImporter.java:583)
We are running distibuted environment where in DB and CI are running on different servers and sourcing is being installed on the CI server.
We are using ojdbc5.jar file.
JAVA_HOME = E:\usr\sap\EJQ\SYS\exe\jvm\NTAMD64\sapjvm_5.1.024\sapjvm_5
thanks
Prasanna

Hello Baski,
I tried the following
- Checked the time zone of CI Server - On which DBIMPORT is running and verified it to be same.
-Checked the DB server time zone and verified it to be same
- Restarted both the server nodes.
- Ran the DBIMPORT again with install_root.xml , still get the same error.
AssociatedAttribute=START_DATE - SourceBo=-2147483547:10502:Mail Messaging - ValidatingParent=-2147483547:10502:Mail Messaging - com.sap.odp.api.common.exception.ApplicationException: ID: exception.docommon.scheduled_task.bad_start
     at com.sap.odp.api.common.exception.ChainedExceptionFactory.createApplicationException(ChainedExceptionFactory.java:90)
     at com.sap.odp.common.db.PersistentBo.createApplicationException(PersistentBo.java:3237)
     at com.sap.odp.doccommon.daemon.manage.ManagedDaemonBo.validateHook(ManagedDaemonBo.java:688)
     at com.sap.odp.doc.ContainerBo.validate(ContainerBo.java:1362)
     at com.sap.odp.doc.ContainerDocBo.validate(ContainerDocBo.java:1299)
     at com.sap.odp.doc.AbsDocBo.validate(AbsDocBo.java:3811)
     at com.sap.odp.doc.BizDocBo.validate(BizDocBo.java:2133)
     at com.sap.odp.common.db.AbstractDb.validate(AbstractDb.java:6225)
     at com.sap.odp.common.db.AbstractDb.save(AbstractDb.java:3255)
     at com.sap.odp.doc.ContainerDb.save(ContainerDb.java:213)
     at com.sap.odp.doc.AbsDocDb.save(AbsDocDb.java:968)
     at com.sap.odp.common.db.AbstractDb.save(AbstractDb.java:3215)
     at com.sap.odp.doc.ContainerHome.save(ContainerHome.java:295)
     at com.sap.odp.doc.AbsDocHome.save(AbsDocHome.java:446)
     at com.sap.odp.doccommon.daemon.manage.importer.processors.ManagedDaemonProcessor.saveHook(ManagedDaemonProcessor.java:437)
     at com.sap.odp.doc.importer.AbsDocImportProcessor.processRow(AbsDocImportProcessor.java:187)
     at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processRowInternal(CsvFileProcessor.java:1362)
     at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processFile(CsvFileProcessor.java:280)
     at com.sap.odp.common.install.dataimport.csv.CsvImporter.go(CsvImporter.java:195)
     at com.sap.odp.install.actions.ProcessCsvFile.executeHook(ProcessCsvFile.java:159)
     at com.sap.odp.install.actions.InstallAction.execute(InstallAction.java:203)
     at com.sap.odp.install.engine.ScriptedImportEngine.runSingleItem(ScriptedImportEngine.java:319)
     at com.sap.odp.install.engine.DbSetupEngine.execute(DbSetupEngine.java:186)
     at com.sap.odp.install.tools.gui.DbGuiImporter.go(DbGuiImporter.java:282)
     at com.sap.odp.install.tools.gui.DbGuiImporter$InstallThread.run(DbGuiImporter.java:583)
Can you please suggest any other ideas.
Thanks a lot for your help.

Similar Messages

Getting Error while importing catalog xml

Hi ,
i am new to ATG.
I am getting the below error when i tried to import the xml.
D:\ATG\ATG9.0\home>bin\startSQLRepository -m DynamusicB2C -import ..\DynamusicB2C\config\dynamusic\DynamusicB2CData.xml -repository /atg/commerce/catalog/ProductCatalog
**** info Thu Oct 25 18:05:27 GMT+05:30 2012 1351168527562 /DPSLicense atg.service.ServiceResources->dynamoPrintM
axSessions : Only 20 concurrent sessions can be managed with this license
**** info Thu Oct 25 18:05:27 GMT+05:30 2012 1351168527578 /DPSLicense atg.service.ServiceResources->dynamoPrintM
axDynamoServers : Only 3 Dynamo server(s) can be used concurrently with this license
**** info Thu Oct 25 18:05:27 GMT+05:30 2012 1351168527593 /DPSLicense DPS is licensed to Sprint/United Managemen
t Company - Development
**** info Thu Oct 25 18:05:27 GMT+05:30 2012 1351168527593 /DPSLicense atg.service.ServiceResources->unlimitedLic
enseMsg : This product is licensed for an unlimited number of CPUs.
Nucleus running
*** unable to find GSARepository component: /atg/commerce/catalog/ProductCatalog in configpath: D:\ATG\ATG9.0\DAS\config\config.ja
r;D:\ATG\ATG9.0\DAS\config\oca-ldap.jar;vfs[localconfig-1]=/atg/dynamo/service/groupconfig/ClientNodeTypeVirtualFileSystem;vfs[loc
alconfig-1]=/atg/dynamo/service/groupconfig/ClientInstanceVirtualFileSystem;D:\ATG\ATG9.0\DPS\config\targeting.jar;D:\ATG\ATG9.0\D
PS\config\oca-cms.jar;D:\ATG\ATG9.0\DPS\config\oca-html.jar;D:\ATG\ATG9.0\DPS\config\oca-xml.jar;D:\ATG\ATG9.0\DPS\config\userprof
iling.jar;D:\ATG\ATG9.0\DPS\config\profile.jar;D:\ATG\ATG9.0\DSS\config\config.jar;..\DAS\config\dtmconfig.jar;localconfig;..\DAF\
config\dafconfig.jar
Usage: startSQLRepository <xml-file1> ... <xml-filen> [args]
Starts a GSA repository and executes a set of XML commands.
The startSQLRepository command instantiates a repository and
optionally parses one or more XML files you specify. You
can use it to validate your template definition files,
generate default SQL for your template and import or export
data from your repository. You must specify the -repository
option. All other options are optional.
Pls guide me to succeed the above one.
Thanks and Regards,
Bala P.
Edited by: 967647 on Oct 25, 2012 6:08 AM

In place of ..\DynamusicB2C\config\dynamusic\DynamusicB2CData.xml just use \dynamusic\DynamusicB2CData.xml [path after config].
-RMishra

Error while importing iPlanetResourceObject.xml in OIM

Hi
I am facing error when I am trying to import iPlanetResourceObject.xml in oralce identity manager. i.e error in import selection. Please suggest how to solve this issue.
Thank you

Use the Install Connector via Web GUI functionality provided OOTB. It will automatically take care of all dependencies etc.

Error while Importing ResourceObject xml file in Deployment Manager

Hi Everyone,
I am getting this error while doing Import of HRPeopleSoftResourceObjects.xml ( A Resource Object xml file) in Deployment Manager. I am doing this step for Authoritative(Trusted Source) Reconciliation.
Error Says:- Attribute not present in EntityDefination of User :: ExpectedReturnDate.
ExpectedReturnDate is a UDF (Customize) field. I did Metadata and Sandbox import for this field to create this attribute in OIM. I can see this attribute on User Details screen as well as in User Table in OIM. So, ideally this error should not popup. I have to do this import for Reconciliation.
I pulled and checked all the xml files like(UserEO.xml.xml, userEO.xml.xml, userVO.xml, UserVO.xml.xml) from oracle.iam.console.identity.self-service.ear_V2.0_metadata1 and found ExpectedReturnDate field is available.
I am using: OIM Version - Oracle 11g Release 2
Database version - 11.2.0
Weblogic version - 10.3
Please let me know how to resolve this error.
Appreciate your response and support!
Warm Regards
Vijay Kumar

Appreciate your response Kevin!
I saw your response today. What you have suggested in your post make perfect sense to me.
Yesterday, I was able to create Reconciliation profile successfully. No idea how it worked so, didn't updated my post.
I tried to re-import the UDF, noticed ExpectedReturnDate attribute has little icon in fornt of it on deployment manager screen which says on mouse over "new field". No idea why as I didn't delete it from anywhere, perhaps it didn't get imported properly previously. I stepped ahead and clicked the import button on deployment manager but failed as it was throwing an exception which says udf_usr_expectedReturnDate is available in usr table. That makes sense to me as this column got created in usr table in OIM because of previous import and I didn't delete it either. This raised couple of doubts more as, along with this attribute there were other attributes in the same metadata xml file which were part of previous import and their respective columns were already created in usr table. Then why message poped-up for this field in particular? Anyway I went ahead with the import process.
Now I stopped all the server (Admin, SOA and OIM) and restarted them again and performed the same steps as mentioned above and this time it worked as expected. UDF file got imported successfully.
After this I went to Design Console verified all the fields and created the Reconciliation Profile. I checked OIM database and found RA_ProfileName recon tables got created.
As per your comment, Today I checked the RECON_USER_OLDSTATE table but this table is empty.
Still I have couple of doubts, if Reconciliation Profile got created it should create the xml file under metadata direcectory(in my case path should be: /apps/Oracle/Middleware/Oracle_IDM1/server/metadata/db). Please correct me if I am wrong? I hope it should be physical file not a logical file.
Once again thanks for your response!
Warm Regards
Vijay Kumar

Error when importing spml2.xml

Hi,
I'm trying to configure SPML2. Currently it's not configured, i get error:
javax.servlet.ServletException: There is no Configuration object named 'SPML2'. The SPML 2.0 interface has not been configured.
when trying to use openspml toolkit.
When I'm importing samples/spml2.xml through Configuration / "Import Exchange File" following error occurs:
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: javax/activation/DataSource
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
javax.servlet.ServletException: javax/activation/DataSource
     org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:843)
     org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:776)
     org.apache.jsp.configure.fileimport_jsp._jspService(fileimport_jsp.java:686)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
java.lang.NoClassDefFoundError: javax/activation/DataSource
     java.lang.ClassLoader.defineClass1(Native Method)
     java.lang.ClassLoader.defineClass(ClassLoader.java:620)
     java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1815)
     org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:869)
     org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1322)
I cant figure out what is the cause.. Any tips would be helpful.

Hi,
you should add activation.jar (and possibly mail.jar) to your IDMs WEB-INF/lib folder as stated in the installation guide for running IDM on tomcat.
Regards,
Patrick

Error While Importing Ustream XML Profile

I get this error message while importing my Ustream XML profile.
This is what I'm trying to do.
http://www.ustream.tv/higher-quality
Any help is greatly appreciated.

Which device are you using and at which step this error occurs?
Could you please attach fmle session log file?

Error while importing .xml file in Datatype

Hi SDN,
I am getting this error while importing .xml file in Datatype.
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
Actually I have created datatype in my development box..
but my client doesn't want to develop in development box.
so i have exported that datatype as xsd from datatype editor.
and while importing into sandbox datatype editor i am getting this error..
Any help please......

Hi Rajeev,
now i have an .xml file its not importing into datatype...
error is
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8))
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema targetNamespace="http://abc.com/xa" xmlns="http://abc.com/xa" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="DT_PLANNINGSCHEDULE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">3c6ae480f2f111dbc7ac0002556ad065</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="PlanningSchedule_Output">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c0f15b11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PlanningScheduleHeader">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c1f15b11dbb6ef00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">6c804600f15d11dbc02400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleIssueDate" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d0f15d11db8dd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SchedulePurpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d1f15d11dbac4100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Purpose">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd50f15e11db9eb600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PurposeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd51f15e11dbc47a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d2f15d11dbbc3900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d3f15d11dba00200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d4f15d11dbc7e000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d5f15d11db969a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec100f16411dba2e900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec101f16411db997a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec102f16411dbb75900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec103f16411db8fa500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec104f16411dba93f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">449ec105f16411dba20f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">0de2f450f16511dbaa4700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d0f16711dbbdd800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d1f16711dbcd2600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d2f16711db82f800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d3f16711dbcf6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">9a25b6d4f16711dbcb6200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SellerParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b80f16711dba8c100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb80f16811db82e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb81f16811dba6ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb82f16811db8b4e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb83f16811dbc0ff00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb84f16811dbb8f700123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb85f16811dba46200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb86f16811db98c000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb87f16811dbb25200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1c2fb88f16811dbc7d100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e99ffa30f16811dba27100123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d30f16a11dbb29f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipFromParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b81f16711dbbfce00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d31f16a11db9adf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d32f16a11dbbef100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d33f16a11db9e5600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d34f16a11dbba6d00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d35f16a11db855400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">7c7c4d36f16a11db877300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ShipToParty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">e0422b82f16711db84ec00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Party">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac0f16b11dba49600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartyID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac1f16b11db80c700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac2f16b11db8ea300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac3f16b11dbb5bb00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac4f16b11dbb7bc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">275ecac5f16b11db92a300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Language">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a370c1d6f15d11db9f9a00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LanguageCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">b1b4fd52f15e11dbc06300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationGroupedPlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">c65d41c2f15b11dba9fd00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationGroupedPlanningDetail" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">89515130f17f11db98e400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Location">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832980f17f11db8d4600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationIdentifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d0f18011db8ce800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d1f18011db839900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d2f18011dba45300123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Agency">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d3f18011db9ac700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AgencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d4f18011dbc4ab00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Ident" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">f95b26d5f18011dbcd4400123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfLocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">de832981f17f11db856100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LocationPlanningItemDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257410f18111db8b6f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BasePlanningDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257411f18111db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="LineItemNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257412f18111db847f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerLineItemNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257413f18111dbcf7200123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemIdentifiers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257414f18111dba6f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNumbers">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257415f18111db968700123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BuyerPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257416f18111db9f9100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartNum">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257417f18111dbc32500123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PartID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">d8257418f18111dbcfa900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StandardPartNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67960f18211db839c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67961f18211dbc78900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ProductIdentifierQualifierCoded" type="xsd:integer">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">50b67962f18211dbae6e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ProductIdentifier" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815570f18411dbb4e800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ItemDescription" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">83815571f18411db876f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfItemReferences">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef0f18711dbbafe00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef1f18711db8a7600123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef2f18711db935200123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ReferenceTypeCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef3f18711dba69c00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ReferenceTypeCodedOther" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef4f18711db942b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PrimaryReference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef5f18711db93a800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Reference">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef6f18711dbcebc00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="RefNum" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef7f18711dbce6300123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForecastFrequencyCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef8f18711db937b00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ListOfScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aef9f18711dba61400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ScheduleDetail">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefaf18711db9d4800123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CommitmentLevelCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefbf18711dba59800123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ScheduleDates">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefcf18711db947900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfDateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefdf18711dbc43e00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefef18711dbaa5000123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Date">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59aefff18711dbcde600123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="DateQualifier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af00f18711db87f100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DateQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af01f18711dbc9cf00123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ScheduleQuantities">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af02f18711dbc24100123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ListOfQuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af03f18711db842900123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityCoded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af04f18711dbb59400123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="QuantityValue" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">2e59af05f18711dba6d900123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="UnitOfMeasurement">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2580f18711dbc66f00123fbbc71c</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UOMCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2581f18711db89a000123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="QuantityQualifierCoded" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">a87e2582f18711db9a1500123fbbc71c</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Error while importing data from XML file to a Oracle database

I am getting the following error while importing data
*** atg.xml.XMLFileException: No XML files were found for "/Dynamusic/config/dynamusic/songs-data.xml".
The files must be located under the name "/Dynamusic/config/dyna
*** java.io.FileNotFoundException: D:\MyApp\ATG\ATG10.0.3 (Access is denied)
java.io.FileNotFoundException: D:\MyApp\ATG\ATG10.0.3 (Access is denied)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:120)
        at atg.adapter.gsa.xml.TemplateParser.importFiles(TemplateParser.java:6675)
        at atg.adapter.gsa.xml.TemplateParser.runParser(TemplateParser.java:5795)
        at atg.adapter.gsa.xml.TemplateParser.main(TemplateParser.java:5241)
I have placed the FakeXADataSource and JTDataSource properties files as required. In fact I have been able to import data in all machines. Just this one machine is giving problems. I have also checked out the access rights. Can someone help me please?

Confirm that you have access to D:\MyApp\ATG\ATG10.0.3 and existence of Dynamusic/config/dynamusic/songs-data.xm

Error while importing xml file

Hi,
I am importing the xml file using the executefile function or dbms_aw_xml package and getting following error.
SQL> execute dbms_output.put_line(dbms_aw_xml.executefile('XML_IMPORT_DIR','mod_OPER_DATA_BW.XML'));
BEGIN dbms_output.put_line(dbms_aw_xml.executefile('XML_IMPORT_DIR','mod_OPER_DATA_BW.XML')); END;
ERROR at line 1:
ORA-22288: file or LOB operation FILEOPEN failed
No such file or directory
ORA-06512: at "SYS.DBMS_LOB", line 523
ORA-06512: at "SYS.DBMS_AW_XML", line 22
ORA-06512: at line 1
I checked the permission for the directory is set to public.
Also the physical location has permission set to 755.
any pointers to resolve this.
Thanks in advance.
Thanks
Brijesh

error resolved.
Thanks

Error while importing xml file in calc manager

Hi All,
I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
-Kamran

Hi All,
I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
-Kamran

Error while import XML file from Production to Dev., But has GREEN status

Hi,
I tried to export/import bex queries through XML transportation. Transportation is being done from Production system to Development. In transport connection I selected required query and then I exported to Development. export of file is done successfully.
Now in development system I imported that XML file. It is imported. Giving GREEN symbol and also with GREEN check. But in Log view I found ERRORS. in errors it is mentioned "SAP object 46N3K1OCT22PSBN46O95MQLTJ () cannot be imported". along with long message text "Install the specified objects from Business Content. Only import the metadata afterwards.".
What should I do now as of next step... import of file is stuck..
How can I search object 46N3K1OCT22PSBN46O95MQLTJ (), if I have to install from BC.
I am also unable to find the query in Development Bex analyser.
Thanks for help....
[email protected]

Hi Babloo,
According to the error message, the package may have failed are as follows:
The user account that is used to run the package under SQL Server Agent in PRODUCTION server differs from the original package author.
The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
The package may not run in the following scenarios:
The current user cannot decrypt secrets from the package. This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user
decrypt secrets in the package. In this scenario, we can change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword, then modify the SQL Server Agent job step command line to include this password.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
References:
SSIS package does not run when called from a SQL Server Agent job step
Run an SSIS Package Under a Different Account
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Logon Error in importing XML file by import type - Schema in import Manager

Hi,
I am trying to import the xml file by selecting type XML Schema. I have already created an XML Schema in console based on the XSD file from my desktop and the same is visible in dropdown of XML Schema Tab while importing.
But I am not able to import the XML file based on the XML Schema. I got the Logon Error As : "Cannot load XML file"
Content of the error is like -
(Error:
Commerror80004005 Unsepcified error
Source=mdxml4.dll Description= file:///C:/DOCUM...............
The Namespace provided Differs from the schema's 'http://n............)
Please have you inputs as this is a very critical requirement to pull the XML file based on XML schema automatically based on the ports created in console.
Response wud be highly appreciated.
Thanks & Rgds/Pawan

Hi Jason,
Thanks for your response!
I don't mind you in taking my thread to core MDM stuff. It would be big relief for to have an response on my query.
Actually this is a problem with respect to SRM MDM Catalog.....
I am waiting see the following response threads based on my query..
Thanks once again!
Best Rgds/Pawan

Error while Importing custom udf xml file in prod evnrmnt

hi experts,
I have created 35 UDF'S IN OUR OIM 11GR2 TEST EVNROMENT AND HAVE EXPORTED THE SAND BOX WHICH I HAVE USED WHILE CREATING UDF'S IN FORM DESIGNER'S USER FORM. NOW I HAVE EXPORTED THE SAND BOX AND ALSO EXPORTED THE UDF'S USING THE EXPORT UTITLITY.
IN THE PRODUCTION ENVIRONMENT WHEN I TRY TO IMPORT THE XML FILE I AM GETTING THE FOLLOWING ERROR.....
"Error encountered while reading file"....
pls answer, its urgent....or like how to go about it....thanks

Please check the zip file which you are trying to import.
May be your zip file was not correctly created.
Another option is that before importing the sandbox to prod environment you can try importing the same first in your test environment to make sure your zip was created correctly.
HTH

Error when import XML

I am dealing with a INDD file with XML structure, after import the XML there is always an error occured when I validate it
How to declare it in DTD? Or any way to avoid it?

Especially if you are importing XML with tables, I would recommend creating an ID document with tables, either use the auto-tagging or create your own tags based upon your XML, then exporting it to look how the XML is formed.
Using the namespace as part of the table element should look roughly like this in your XML:
<Table xmlns:aid="http://ns.adobe.com/AdobeInDesign/4.0/" aid:table="table" aid:trows="8" aid:tcols="5">
The above is simply from a quick export of a table in ID. But note that the definitions, the declaration, of what the element parts are follows the namespace portion.
Mike

Error after importing a Resource .xml file

Hellos,
We are moving from development to test.
I wanted to load the Scripted JDBC Resource we have developed. We exported the Resource from idm/debug, removed the id='xxx' elements and then imported the .xml file via Configure/Import file.
Now, I get the error:
ErrorError
java.lang.IllegalStateException: Error attempting to decrypt: Error initializing Encryptor: Missing required Encryption Key: F9388B0C42691A37:7A11431D:1166721AE86:-7FFC
when trying to access the resource in the test environment...
It is a database resource so it has an user/password pair, maybe the Password is causing me grief.
What is this error meaning and how do I resolve it?

greenfan88 wrote:
It is a database resource so it has an user/password pair, maybe the Password is causing me grief.
What is this error meaning and how do I resolve it?That's the point. Password is encrypted with a particular key. Remove password and reenter it on the resourceform.
You could also export the ServerKey from dev, but that seems to be not a good solution (at last, not for me).
regards, M.

Error in importing install_root.xml

Similar Messages

Maybe you are looking for