XML document content not replaced

I insert XML documents into iFS using the WebUI via browse. I insert them again after making changes. The new content does not replace the old content. I do not see the new content when viewing the document and search does not find the new content. These documents do not have a type definition and are not parsed. I've tried inserting the new ones after deleting the old ones and I still get the content of the documents that I inserted the first time. Any ideas?

Hi Greg,
Did you remember to check Parse File on Upload?
If yes please forward the XML file and also let me know what version of 9iFS you're using.
Hanne.

Similar Messages

XML document could not be created because server memory is low( SCOM 2012 R2).

Hi
I am facing below issue in the scom 2012 r2.
please find the error below
On SCOM MS:
Alert name :Data Warehouse relationship synchronization process failed to write data
Alert description :Data Warehouse relationship synchronization process failed to write data to the Data Warehouse database. Failed to store data
in the Data Warehouse. The operation will be retried.
Exception 'SqlException': Sql execution failed. Error 6624, Level 16, State 1, Procedure sp_xml_preparedocument, Line 1, Message: XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.
Event id in Operation log:
Event id :33333
Data Access Layer rejected retry on SqlError:
Request: DataWarehouseSynchConfigChangeTypeGet -- (InstalledManagementPackXml=<ManagementPacks><ManagementPack>7b9f4239-7351-e72b-4ce4-d6c56ddb401d</ManagementPack><ManagementPack>848edb97-9da5-e2ae-24d4-56...),
(RETURN_VALUE=-6)
Class: 16
Number: 6624
Message: XML document could not be created because server memory is low. Use sp_xml_removedocument
to release XML documents.
ON SCOM DB server:
SQL version : SQL 2012 SP1 X64 bit Host all SCOm db (SCOM DB,SCOM DW,Reporting)
Ervent id : 28005 ,Application log,source: MSSQLSERVER
Please suggest me in this regard.
Thanks
sridhar v

For fix error 33333, you can refer below links
http://opsmgradmin.blogspot.com/2011/05/scom-event-id-33333-in-scom-from-source.html
http://systemcenterblog.blogspot.com/2009/11/error-id-33333-data-access-layer.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

XML document does not appear to contain a properly formed DOCTYPE header

Hi,
I've created an ejb which uses the studio API to start/execute etc the workflow
tasks in a generic way. The same ejb contain certain method which I want to use
as business operations in my workflows. However, when I deploy this ejb as a separate
application by putting the required jar files in class path it works fine, but
when I deploy it as a part of WLI application for accessing the business operations
in workflow I'm getting the following error. I'm entering ejbcomponent entry under
the wli application tag of config.xml and putting the jar file in the lib directory
where other jar files are placed. I couldn't understand the reason why it is failing
when I deploy it as a part of WLI application and not when I deploy it independently.
Module Name: TestWLPI, Error: The XML parser encountered an error in your deployment
descriptor. Please ensure that your DOCTYPE is correct. You may wish to compa
re your deployment descriptors with the WebLogic Server examples to ensure the
format is correct. The error was:
weblogic.xml.process.ProcessorFactoryException: XML document does not appear to
contain a properly formed DOCTYPE header
at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:281)
at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:224)
at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:267)
at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:242)
at weblogic.ejb20.dd.xml.DDUtils.processAltDD(DDUtils.java:220)
at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:102)
at weblogic.ejb20.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:500)
at weblogic.ejb20.deployer.EJBModule.loadDescriptor(EJBModule.java:207)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:714)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)

javax.xml.stream.XMLStreamException: javax.xml.stream.XMLStreamException: Premature end of file encountered
at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:80)
at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:110)
at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:128)
at weblogic.application.descriptor.VersionMunger.<init>(VersionMunger.java:74)
at weblogic.application.descriptor.VersionMunger.<init>(VersionMunger.java:63)
at weblogic.servlet.internal.WlsWebAppReader2.<init>(WlsWebAppReader2.java:59)
at weblogic.servlet.internal.WebAppDescriptor$MyWlsWebAppDescriptor.createXMLStreamReader(WebAppDescriptor.java:316)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:402)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
Any Suggestions plz???
Thanks

EC SALES LIST - Belgique: XML file: Content not accepted in prolog

Hy tou you all,
We've implemented all Ec sales list note oss for Belgium but at the upload in the delcaration vat system the xml file is not accepted : "Content not accepte in prolog"; Did this message encured to you ?
Thanks,
TF

HI,
I hope you are asking about below legal changes
http://www.minfin.fgov.be/portail2/fr/e-services/intervat/calendrier.html
and SAP DS colleagues are working on same and they are planning to release the note
within soon.
For same information will check the service market place.
Thank you.
Regards
Madhu M

Xml Document is not formed correctly.. Help me..

Using the .xsd files provided to me, I created XMLBeans using the schema project in weblogic 8.1 sp2.
These XMLBeans are used to create a XML document in my Weblogic Integration process. The values in the xml document are retrieved from a database (which cannot administered/viewed by me). XML document was formed perfectly. But recently when I tried running the application again, I found that the xml is not created properly.
When I tried to print the xml message, it displays the xml message with the first letter changed from '<' to '<'.
eg.
<batch_document>
</batch_document> is displayed as
<batch_document>
</batch_document>
What may be the reason behind this change. Is it possible because of some invalid data from the backend? If so, what could be the data?
Is there any special characters which when inserted between the elements makes the document like this?
The code that creates the xml document looks like this ...
BatchDocumentDocument bDoc= BatchDocumentDocument.Factory.newInstance();
BatchDocument bd= bDoc.addNewBatchDocument();
System.out.println(bDoc.toString());
The print statement prints the xml message as
<batch_document>
</batch_document>
I would be grateful even if I am answered with any of these questions.
Thanks in advance.

Hello Elango,
Have you tried validating the instance document using the validate() method
-Raj
<Elango SV> wrote in message news:[email protected]..
Using the .xsd files provided to me, I created XMLBeans using the schema
project in weblogic 8.1 sp2.
These XMLBeans are used to create a XML document in my Weblogic
Integration process. The values in the xml document are retrieved from a
database (which cannot administered/viewed by me). XML document was formed
perfectly. But recently when I tried running the application again, I
found that the xml is not created properly.
When I tried to print the xml message, it displays the xml message with
the first letter changed from '<' to '<'.
eg.
<batch_document>
</batch_document> is displayed as
<batch_document>
</batch_document>
What may be the reason behind this change. Is it possible because of some
invalid data from the backend? If so, what could be the data?
Is there any special characters which when inserted between the elements
makes the document like this?
The code that creates the xml document looks like this ...
BatchDocumentDocument bDoc= BatchDocumentDocument.Factory.newInstance();
BatchDocument bd= bDoc.addNewBatchDocument();
System.out.println(bDoc.toString());
The print statement prints the xml message as
<batch_document>
</batch_document>
I would be grateful even if I am answered with any of these questions.
Thanks in advance.

OLE: Why placeholders of MS Word document are not replaced?

Hi Experts, I am using OLE to create Word Documents within a LOOP. The problem I have is that the Word Documents are created and seved well but the placeholders (&nom_prov') and (&ncod_prov') are not replaces by the values (in the example: test1 and test2).
Anybody can help me in with that issue?
LOOP AT lt_partner1 INTO ls_partner1.
AT FIRST.
    CREATE OBJECT zword 'WORD.BASIC'.
    CALL METHOD OF zword 'FILEOPEN' EXPORTING #1 = 'C:\DOCS\PRUEBA_1.DOC'.
ENDAT.
CALL METHOD OF zword 'EDITSELECTALL'.
CALL METHOD OF zword 'EDITCOPY'.
CALL METHOD OF zword 'FILENEW'.
CALL METHOD OF zword 'EDITPASTE'.
CALL METHOD OF zword 'STARTOFDOCUMENT'.
CALL METHOD OF zword 'WW2_EDITREPLACE' EXPORTING #1 = '&cod_prov'
    #2 = 'test 1'. "ls_partner1-nif.
CALL METHOD OF zword 'WW2_EDITREPLACE' EXPORTING #1 = '&nom_prov'
    #2 = 'test 2'. "ls_partner1-name_org1.
CALL METHOD OF zword 'STARTOFDOCUMENT'.
CALL METHOD OF zword 'EDITSELECTALL'.
CALL METHOD OF zword 'EDITCLEAR'.
CALL METHOD OF zword 'EDITPASTE'.
lv_contador = lv_contador + 1.
CONCATENATE 'C:\DOCS\' 'PRUEBA' lv_contador '_' sy-datum '.DOC' INTO lv_file_save_as.
CALL METHOD OF zword 'FILESAVEAS' EXPORTING #1 = lv_file_save_as.
CALL METHOD OF zword 'DOCCLOSE' EXPORTING #1 = 2.
AT LAST.
   CALL METHOD OF zword 'APPCLOSE'.
   FREE OBJECT zword.
ENDAT.
ENDLOOP.

Hello, I have found out what was the problem. In the end I have used method EDITREPLACE and not WW2_EDITREPLACE and I put the method EDITREPLACE more to the end of my ABAP Code:
REPORT z_prueba_oliver.
TYPES: BEGIN OF ty_partner,
             nif            TYPE bu_partner,
             name_org1      TYPE bu_nameor1,
             conting_com    TYPE c LENGTH 2,
             fecha_efecto   TYPE zbufecha_ef,
             END OF ty_partner.
DATA: lt_partner1     TYPE TABLE OF ty_partner,
             ls_partner1     TYPE ty_partner,
             lv_file_save_as TYPE c LENGTH 40,
             lv_contador     TYPE n LENGTH 3.
* Include necesario para la declaracion de objetos OLE2
INCLUDE ole2incl.
* Declaraciones para la llamada a WORD.
DATA zword TYPE ole2_object.
CLEAR zword.
ls_partner1-nif = 'X7510034M'.
ls_partner1-name_org1 = 'Razon Social 1'.
APPEND ls_partner1 TO lt_partner1.
ls_partner1-nif = 'X7510034M'.
ls_partner1-name_org1 = 'Razon Social 2'.
APPEND ls_partner1 TO lt_partner1.
ls_partner1-nif = 'X7510034M'.
ls_partner1-name_org1 = 'Razon Social 3'.
APPEND ls_partner1 TO lt_partner1.
ls_partner1-nif = 'X7510035M'.
ls_partner1-name_org1 = 'Razon Social 4'.
APPEND ls_partner1 TO lt_partner1.
ls_partner1-nif = 'X7510035M'.
ls_partner1-name_org1 = 'Razon Social 5'.
APPEND ls_partner1 TO lt_partner1.
LOOP AT lt_partner1 INTO ls_partner1.
AT FIRST.
    CREATE OBJECT zword 'WORD.BASIC'.
* Se abre el fichero que contiene la plantilla de la carta
    CALL METHOD OF zword 'FILEOPEN'
      EXPORTING
      #1 = 'C:DOCSPRUEBA_1.DOC'.
ENDAT.
* Se selecciona todo el texto del archivo PRUEBA_1.DOC
CALL METHOD OF zword 'EDITSELECTALL'.
* Se copia el texto seleccionado al portapapeles
CALL METHOD OF zword 'EDITCOPY'.
* Se crea un documento nuevo, al que WORD llama documento1
CALL METHOD OF zword 'FILENEW'.
* Se pega el texto del portapapeles a documento1
CALL METHOD OF zword 'EDITPASTE'.
* Posicionar al principio del documento
CALL METHOD OF zword 'STARTOFDOCUMENT'.
* Posicionar al principio del documento
CALL METHOD OF zword 'STARTOFDOCUMENT'.
* Se selecciona todo
CALL METHOD OF zword 'EDITSELECTALL'.
* Se borra la selección
CALL METHOD OF zword 'EDITCLEAR'.
* Se incorpora el texto original de PRUEBA_1.DOC
CALL METHOD OF zword 'EDITPASTE'.
*IF ls_partner1-conting_com is initial.*
   *CALL METHOD OF zword 'EDITREPLACE'*
    *EXPORTING*
    *#01 = '#linea2y3#'*
    *#02 = 'texttexttexttext'*
    *#03 = 0*
    *#04 = 0*
    *#05 = 0*
    *#06 = 0*
    *#07 = 0*
    *#08 = 0*
    *#09 = 0*
    *#10 = 1*
    *#11 = 0*
    *#12 = 1.*
*else.*
     *CALL METHOD OF zword 'EDITREPLACE'*
    *EXPORTING*
    *#01 = '#linea2y3#'*
    *#02 = 'texttexttexttext'*
    *#03 = 0*
    *#04 = 0*
    *#05 = 0*
    *#06 = 0*
    *#07 = 0*
    *#08 = 0*
    *#09 = 0*
    *#10 = 1*
    *#11 = 0*
    *#12 = 1.*
*ENDIF.*
*CALL METHOD OF zword 'EDITREPLACE'*
    *EXPORTING*
    *#01 = '#codprov#'*
    *#02 = ls_partner1-nif*
    *#03 = 0*
    *#04 = 0*
    *#05 = 0*
    *#06 = 0*
    *#07 = 0*
    *#08 = 0*
    *#09 = 0*
    *#10 = 1*
    *#11 = 0*
    *#12 = 1.*
CALL METHOD OF zword 'EDITREPLACE'
    EXPORTING
    #01 = '#nomprov#'
    #02 = ls_partner1-name_org1
    #03 = 0
    #04 = 0
    #05 = 0
    #06 = 0
    #07 = 0
    #08 = 0
    #09 = 0
    #10 = 1
    #11 = 0
    #12 = 1.
* Se reemplaza el campo #nomprov# con el valor de la tabla interna.
CALL METHOD OF zword 'EDITREPLACE'
    EXPORTING
    #01 = '#FECHA_EFECTO#'
    #02 = '10 de Junio de 2010'
    #03 = 0
    #04 = 0
    #05 = 0
    #06 = 0
    #07 = 0
    #08 = 0
    #09 = 0
    #10 = 1
    #11 = 0
    #12 = 1.
lv_contador = lv_contador + 1.
CONCATENATE 'C:DOCS' 'PRUEBA' lv_contador '_' sy-datum '.DOC' INTO lv_file_save_as.
* Se cierra el documento activo, documento1 con opción de salir sin salvar
CALL METHOD OF zword 'FILESAVEAS' EXPORTING #1 = lv_file_save_as.
* Se cierra el documento activo PRUEBA.DOC con opción salir sin salvar
CALL METHOD OF zword 'DOCCLOSE' EXPORTING #1 = 2.
AT LAST.
*   Se cierra WORD
    CALL METHOD OF zword 'APPCLOSE'.
*   Se libera el objeto ZWORD
    FREE OBJECT zword.
ENDAT.
ENDLOOP.

Sharepoint Foundation 2010 some document content not being crawl

Hi,
I have run sharepoint foundation search job and full craw as below :
> Stsadm -o spsearch -action fullcrawlstart
BUT in the same word document some contents were being crawled but some of it not.
Example Below : I can search "Border Terraces" but when I key in "BT140" it always return "We did not find any results for BT140."
WHY???
======================================
Date: 29.04.14
Invoice: BT140
To: Border Terraces

Did you add your site to trusted site list?
http://sharepoint.stackexchange.com/questions/15098/your-client-does-not-support-opening-this-list-with-windows-explorer
--Cheers

Pdf document contents not accessible by JAWS in Firefox

Hi experts. I am using JAWS screen reader for accessibility in my ASP.NET website. I have one link button in my web page. when clicking this button it will opens a pdf document. For using firefox this pdf document not accessed or read by JAWS screen reader. But this pdf accessed fine when browsing my site with Internet explorer. I have using JAWS 13.0. Firefox version 12.0. Can anyone please give me solution for that as soon as possible. this one is very urgent. Thank you...

There is a technical difference between the PDF rendering components in IE and Firefox. IE uses an ActiveX control while Firefox uses a "Netscape-style" plugin. Do you know whether your JAWS software can work with both?
As a workaround, you can launch PDFs from Firefox into Adobe Reader. To do that, try changing your application preference here:
orange Firefox button ''or'' classic Tools menu > Options > Applications
In the search box, type pdf and pause while the list is filtered. Change the drop-down control on the right side from "Use Adobe Acrobat (in Firefox)" to "Always Ask".
(If your Firefox is current set to use Foxit or another non-Adobe reader, you could try changing it to "Use Adobe Acrobat (in Firefox)" and see whether that actually works.)

Date insertion from large XML document (clob) into relation table very slow

Hi Everybody!
I'm working with Oracle 9.2.0.5 on Microsoft Windows Server 2003 Enterprise Edition.
The server (a test server) is a Pentium 4 2.8 GHz, 1GB of RAM.
I use a procedure called PARITOP_TRAITERXMLRESULTMASSE to insert the data contained in the pXMLDOC clob parameter in the table pTABLENAME. (You can see the format of the XML document below). The first step on this procedure is to verify that the XML document is not empty. If not, the procedure needs to add a node in the document, in every <ROW> tag. This added node is named âRST_IDâ. Itâs the foreign key of each record. I can retrieve the value of each <RST_ID> node in an other table in which the data has been previously added (by the calling procedure). When each of the <ROW> elements has been treated, the PARITOP_INSERTXML procedure is called. This procedure uses DBMS_XMLSAVE.INSERTXML to insert the data contained in the XML document in the specified table.
(Below, you can see the code of my procedures.)
With this information, can you tell me why this treatment is very very very slow with a large XML document and how I can improve it?
Thank you for your help!
Anne-Marie
CREATE OR REPLACE PROCEDURE "PARITOP_TRAITERXMLRESULTMASSE" (
pPRC_ID IN PARITOP_PARC.PRC_ID%TYPE,
pRST_MONDE IN PARITOP_RESULTAT.RST_MONDE%TYPE,
pXMLDOC IN CLOB,
pTABLENAME IN VARCHAR2)
AS
Objectif :InsÃ©rer le contenu du XML passÃ© en paramÃ¨tre (pXMLDOC) Ã la table passÃ©e en paramÃ¨tre (pTABLENAME)
La table passÃ©e en paramÃ¨tre doit Ãªtre une table ayant comme clÃ© Ã©trangÃ¨re le champs "RST_ID" .
(Le noeud RST_ID est donc ajoutÃ© Ã tous les document XML. Ce rst_id est
dÃ©terminÃ© Ã partir de la table PARITOP_RESULTAT grÃ¢ce Ã pPRC_ID et
pRstMonde fournis en paramÃ¨tre)
result_doc CLOB;
XMLDOMDOC XDB.DBMS_XMLDOM.DOMDOCUMENT;
NODE_ROWSET DBMS_XMLDOM.DOMNODE;
NODE_ROW DBMS_XMLDOM.DOMNODE;
vUE_ID PARITOP_RESULTAT.UE_ID%TYPE;
vRST_ID PARITOP_RESULTAT.RST_ID%TYPE;
nodeList DBMS_XMLDOM.DOMNODELIST;
BEGIN
BEGIN
vUE_ID := 0;
vRST_ID := 0;
XMLDOMDOC := DBMS_XMLDOM.NEWDOMDOCUMENT(pXMLDOC);
IF NOT GESTXML_PKG.FN_PARITOP_DOCUMENT_IS_NULL(XMLDOMDOC) THEN
NODE_ROWSET := DBMS_XMLDOM.item(DBMS_XMLDOM.GETCHILDNODES (DBMS_XMLDOM.MAKENODE(XMLDOMDOC)),0);
for i in 0..dbms_xmldom.getLength(DBMS_XMLDOM.getchildnodes(NODE_ROWSET))-1 loop
NODE_ROW := DBMS_XMLDOM.ITEM(DBMS_XMLDOM.GETCHILDNODES(NODE_ROWSET), i) ;
nodeList := DBMS_XMLDOM.GETELEMENTSBYTAGNAME(DBMS_XMLDOM.makeelement(NODE_ROW) , 'UE_ID');
IF vUE_ID <> DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0))) THEN
vUE_ID := DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0)));
--on ramasse le rst_id
SELECT RST_ID INTO vRST_ID
FROM PARITOP_RESULTAT RST
WHERE RST.PRC_ID = pPRC_ID
AND RST.UE_ID = vUE_ID
AND RST.RST_MONDE = pRST_MONDE
AND RST_A_SUPPRIMER = 0;
END IF;
GESTXML_PKG.PARITOP_ADDNODETOROW(XMLDOMDOC, NODE_ROW, 'RST_ID', vRST_ID);
end loop;
RESULT_DOC := ' '; --Ã garder, pour ne pas que ca fasse d'erreur lors du WriteToClob.
dbms_xmldom.writeToClob(DBMS_XMLDOM.MAKENODE(XMLDOMDOC), RESULT_DOC);
--Insertion du document XML dans la table "tableName"
GESTXML_PKG.PARITOP_INSERTXML(RESULT_DOC, pTABLENAME);
DBMS_XMLDOM.FREEDOCUMENT( XMLDOMDOC);
end if;
EXCEPTION
[â¦exception treatementâ¦]
END;
END;
The format of a XML clob is :
<ROWSET>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6223</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>92.307692307692307</CMP_INDICESELECTION>
<CMP_PVRES>94900</CMP_PVRES>
<CMP_PVAJUSTE>72678.017699115066</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>72678.017699115095</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>72678.017699115037</CMP_PVAJUSTEMAX>
<CMP_PV>148000</CMP_PV>
<CMP_VALROLE>129400</CMP_VALROLE>
<CMP_PVRESECART>4790</CMP_PVRESECART>
<CMP_PVRHAB>101778.01769911509</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>148000</CMP_PVA>
</ROW>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6235</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>76.92307692307692</CMP_INDICESELECTION>
<CMP_PVRES>117800</CMP_PVRES>
<CMP_PVAJUSTE>118080</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>118080</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>118080</CMP_PVAJUSTEMAX>
<CMP_PV>172000</CMP_PV>
<CMP_VALROLE>134800</CMP_VALROLE>
<CMP_PVRESECART>0</CMP_PVRESECART>
<CMP_PVRHAB>147180</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>172000</CMP_PVA>
</ROW>
</ROWSET>
PARITOP_COMPARABLE TABLE :
RST_ID NUMBER(10) NOT NULL,
VEN_ID NUMBER(10) NOT NULL,
CMP_SELMAN NUMBER(1) NOT NULL,
CMP_UTILISE NUMBER(1) NOT NULL,
CMP_INDICESELECTION FLOAT(53) NOT NULL,
CMP_PVRES FLOAT(53) NULL,
CMP_PVAJUSTE FLOAT(53) NULL,
CMP_PVRHAB FLOAT(53) NULL,
CMP_TVM FLOAT(53) NULL
ROCEDURE PARITOP_INSERTXML (xmlDoc IN clob, tableName IN VARCHAR2)
AS
insCtx DBMS_XMLSave.ctxType;
rowss number;
BEGIN
--permet d'insÃ©rer les champs du XML dans la table passÃ©e en paramÃ¨tre.
--il suffit que les champs XML aient le mÃªme nom que les champs de la table
BEGIN
insCtx := DBMS_XMLSave.newContext(tableName); -- get context handle
DBMS_XMLSAVE.SETDATEFORMAT( insCtx, 'yyyy-MM-dd HH:mm:ss');--attention, case sensitive
DBMS_XMLSAVE.setIgnoreCase(insCtx, 1);
rowss := DBMS_XMLSAVE.INSERTXML(insCtx , xmlDoc);
DBMS_XMLSave.closeContext(insCtx);
EXCEPTION
[â¦]
END;
END;
PROCEDURE PARITOP_ADDNODETOROW (
XMLDOMDOC DBMS_XMLDOM.DOMDOCUMENT,
NODE_ROW dbms_xmldom.DOMNode,
NOM_NOEUD VARCHAR2,
VALEUR_NOEUD VARCHAR2)
AS
--PERMET D'AJOUTER UN NOEUD AVEC 1 SEULE VALEUR DANS une ROW D'UN XML.
--UTILE SURTOUT POUR LES CLÃS ÃTRANGÃRES
domElemAInserer DBMS_XMLDOM.DOMELEMENT;
NODE dbms_xmldom.DOMNode;
NODE_TMP dbms_xmldom.DOMNode;
BEGIN
domElemAInserer := DBMS_XMLDOM.createElement(XMLDOMDOC, NOM_NOEUD) ;
NODE := DBMS_XMLDOM.MAKENODE(domElemAInserer); --cast
NODE := DBMS_XMLDOM.APPENDCHILD(NODE_ROW,NODE);
NODE_TMP := DBMS_XMLDOM.MAKENODE(DBMS_XMLDOM.CREATETEXTNODE(XMLDOMDOC, VALEUR_NOEUD ) );
NODE := DBMS_XMLDOM.APPENDCHILD(NODE,NODE_TMP );
END;

Hi Everybody!
I'm working with Oracle 9.2.0.5 on Microsoft Windows Server 2003 Enterprise Edition.
The server (a test server) is a Pentium 4 2.8 GHz, 1GB of RAM.
I use a procedure called PARITOP_TRAITERXMLRESULTMASSE to insert the data contained in the pXMLDOC clob parameter in the table pTABLENAME. (You can see the format of the XML document below). The first step on this procedure is to verify that the XML document is not empty. If not, the procedure needs to add a node in the document, in every <ROW> tag. This added node is named âRST_IDâ. Itâs the foreign key of each record. I can retrieve the value of each <RST_ID> node in an other table in which the data has been previously added (by the calling procedure). When each of the <ROW> elements has been treated, the PARITOP_INSERTXML procedure is called. This procedure uses DBMS_XMLSAVE.INSERTXML to insert the data contained in the XML document in the specified table.
(Below, you can see the code of my procedures.)
With this information, can you tell me why this treatment is very very very slow with a large XML document and how I can improve it?
Thank you for your help!
Anne-Marie
CREATE OR REPLACE PROCEDURE "PARITOP_TRAITERXMLRESULTMASSE" (
pPRC_ID IN PARITOP_PARC.PRC_ID%TYPE,
pRST_MONDE IN PARITOP_RESULTAT.RST_MONDE%TYPE,
pXMLDOC IN CLOB,
pTABLENAME IN VARCHAR2)
AS
Objectif :InsÃ©rer le contenu du XML passÃ© en paramÃ¨tre (pXMLDOC) Ã la table passÃ©e en paramÃ¨tre (pTABLENAME)
La table passÃ©e en paramÃ¨tre doit Ãªtre une table ayant comme clÃ© Ã©trangÃ¨re le champs "RST_ID" .
(Le noeud RST_ID est donc ajoutÃ© Ã tous les document XML. Ce rst_id est
dÃ©terminÃ© Ã partir de la table PARITOP_RESULTAT grÃ¢ce Ã pPRC_ID et
pRstMonde fournis en paramÃ¨tre)
result_doc CLOB;
XMLDOMDOC XDB.DBMS_XMLDOM.DOMDOCUMENT;
NODE_ROWSET DBMS_XMLDOM.DOMNODE;
NODE_ROW DBMS_XMLDOM.DOMNODE;
vUE_ID PARITOP_RESULTAT.UE_ID%TYPE;
vRST_ID PARITOP_RESULTAT.RST_ID%TYPE;
nodeList DBMS_XMLDOM.DOMNODELIST;
BEGIN
BEGIN
vUE_ID := 0;
vRST_ID := 0;
XMLDOMDOC := DBMS_XMLDOM.NEWDOMDOCUMENT(pXMLDOC);
IF NOT GESTXML_PKG.FN_PARITOP_DOCUMENT_IS_NULL(XMLDOMDOC) THEN
NODE_ROWSET := DBMS_XMLDOM.item(DBMS_XMLDOM.GETCHILDNODES (DBMS_XMLDOM.MAKENODE(XMLDOMDOC)),0);
for i in 0..dbms_xmldom.getLength(DBMS_XMLDOM.getchildnodes(NODE_ROWSET))-1 loop
NODE_ROW := DBMS_XMLDOM.ITEM(DBMS_XMLDOM.GETCHILDNODES(NODE_ROWSET), i) ;
nodeList := DBMS_XMLDOM.GETELEMENTSBYTAGNAME(DBMS_XMLDOM.makeelement(NODE_ROW) , 'UE_ID');
IF vUE_ID <> DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0))) THEN
vUE_ID := DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0)));
--on ramasse le rst_id
SELECT RST_ID INTO vRST_ID
FROM PARITOP_RESULTAT RST
WHERE RST.PRC_ID = pPRC_ID
AND RST.UE_ID = vUE_ID
AND RST.RST_MONDE = pRST_MONDE
AND RST_A_SUPPRIMER = 0;
END IF;
GESTXML_PKG.PARITOP_ADDNODETOROW(XMLDOMDOC, NODE_ROW, 'RST_ID', vRST_ID);
end loop;
RESULT_DOC := ' '; --Ã garder, pour ne pas que ca fasse d'erreur lors du WriteToClob.
dbms_xmldom.writeToClob(DBMS_XMLDOM.MAKENODE(XMLDOMDOC), RESULT_DOC);
--Insertion du document XML dans la table "tableName"
GESTXML_PKG.PARITOP_INSERTXML(RESULT_DOC, pTABLENAME);
DBMS_XMLDOM.FREEDOCUMENT( XMLDOMDOC);
end if;
EXCEPTION
[â¦exception treatementâ¦]
END;
END;
The format of a XML clob is :
<ROWSET>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6223</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>92.307692307692307</CMP_INDICESELECTION>
<CMP_PVRES>94900</CMP_PVRES>
<CMP_PVAJUSTE>72678.017699115066</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>72678.017699115095</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>72678.017699115037</CMP_PVAJUSTEMAX>
<CMP_PV>148000</CMP_PV>
<CMP_VALROLE>129400</CMP_VALROLE>
<CMP_PVRESECART>4790</CMP_PVRESECART>
<CMP_PVRHAB>101778.01769911509</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>148000</CMP_PVA>
</ROW>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6235</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>76.92307692307692</CMP_INDICESELECTION>
<CMP_PVRES>117800</CMP_PVRES>
<CMP_PVAJUSTE>118080</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>118080</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>118080</CMP_PVAJUSTEMAX>
<CMP_PV>172000</CMP_PV>
<CMP_VALROLE>134800</CMP_VALROLE>
<CMP_PVRESECART>0</CMP_PVRESECART>
<CMP_PVRHAB>147180</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>172000</CMP_PVA>
</ROW>
</ROWSET>
PARITOP_COMPARABLE TABLE :
RST_ID NUMBER(10) NOT NULL,
VEN_ID NUMBER(10) NOT NULL,
CMP_SELMAN NUMBER(1) NOT NULL,
CMP_UTILISE NUMBER(1) NOT NULL,
CMP_INDICESELECTION FLOAT(53) NOT NULL,
CMP_PVRES FLOAT(53) NULL,
CMP_PVAJUSTE FLOAT(53) NULL,
CMP_PVRHAB FLOAT(53) NULL,
CMP_TVM FLOAT(53) NULL
ROCEDURE PARITOP_INSERTXML (xmlDoc IN clob, tableName IN VARCHAR2)
AS
insCtx DBMS_XMLSave.ctxType;
rowss number;
BEGIN
--permet d'insÃ©rer les champs du XML dans la table passÃ©e en paramÃ¨tre.
--il suffit que les champs XML aient le mÃªme nom que les champs de la table
BEGIN
insCtx := DBMS_XMLSave.newContext(tableName); -- get context handle
DBMS_XMLSAVE.SETDATEFORMAT( insCtx, 'yyyy-MM-dd HH:mm:ss');--attention, case sensitive
DBMS_XMLSAVE.setIgnoreCase(insCtx, 1);
rowss := DBMS_XMLSAVE.INSERTXML(insCtx , xmlDoc);
DBMS_XMLSave.closeContext(insCtx);
EXCEPTION
[â¦]
END;
END;
PROCEDURE PARITOP_ADDNODETOROW (
XMLDOMDOC DBMS_XMLDOM.DOMDOCUMENT,
NODE_ROW dbms_xmldom.DOMNode,
NOM_NOEUD VARCHAR2,
VALEUR_NOEUD VARCHAR2)
AS
--PERMET D'AJOUTER UN NOEUD AVEC 1 SEULE VALEUR DANS une ROW D'UN XML.
--UTILE SURTOUT POUR LES CLÃS ÃTRANGÃRES
domElemAInserer DBMS_XMLDOM.DOMELEMENT;
NODE dbms_xmldom.DOMNode;
NODE_TMP dbms_xmldom.DOMNode;
BEGIN
domElemAInserer := DBMS_XMLDOM.createElement(XMLDOMDOC, NOM_NOEUD) ;
NODE := DBMS_XMLDOM.MAKENODE(domElemAInserer); --cast
NODE := DBMS_XMLDOM.APPENDCHILD(NODE_ROW,NODE);
NODE_TMP := DBMS_XMLDOM.MAKENODE(DBMS_XMLDOM.CREATETEXTNODE(XMLDOMDOC, VALEUR_NOEUD ) );
NODE := DBMS_XMLDOM.APPENDCHILD(NODE,NODE_TMP );
END;

Error while building xml document

Hi Everyone,
I have a problem while building xml document.
I have developed my java files using IBM Eclipse 3.0 and i had no problem while executing the files.
But while i am trying to execute the same code in jdk/bin, xml document is not working..
No error encountered while compiling but while executing when i try to print the xml string it just gives the root element name like [root : null]
Can anyone suggest some solution?

To the values element add xmlns:xsi and xsi:noNamespaceSchemaLocation.
<values xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="file:///c:/schema.xsd">schema.xsd is schema file.

XML Document from XML Schema Bug

When an XML document is generated from an XML Schema the XML document does not have all the elements specified in the XML Schema. The XML document only has the root element.
1. Register an XML Schema.
2. Create an XML document with File>New>General>XML>XML Document from XML Schema. The "Generate only Required Elements" is unchecked.
3. The XML document has only the root element.
In JDeveloper 10.1.3 all the elements in the XML Schema get generated.

Also, the component palette for the XML document generated from the XML Schema does not list all the elements in the XML Schema, only the root element is listed. Even if elements are specified as required in the XML Schema with minOccurs="1" and the "Generate only Required Elements" checkbox is selected only the root element gets generated.

Maximum file size of imported XML document

Is anyone able to tell me if there is a maximum size for XML files that you can import into a PDF document?? I need to know this as my client has a requirement for a very large data set within an interactive PDF generated using LiveCycle designer.

Thanks. I have posted this in the LiveCycle designer forum but have had no reply. I have posted instead within this forum as importing an XML document is not specific to LiveCycle Designer and is instead an Acrobat Pro task and therefore question.

Problem validating XMl document

Hi everyone,
I'm facing a problem validating a XML document with Apache toolkit under windows XP and eclipse 3.0
I generate a pair of public/private keys using the RSA algorithm. The keys are of arbitrary length, but satisfying RSA conditions, ie we can encrypt and decrypt.
I can sign my XML document, but no way to validate it. Validation is only ok when I generate random keys using the KeyPairGenerator.
Do you think that arbitrary length keys don't allow to validate XML document. And do you have any idea how to solve the problem ( I'm not allowed to generate fixed length keys) ?
Thansk a lot for your precious help.

solved!
urghh...forgot to load th eschema..duh. (must be friday)
here's the fixed code:
    // parse the xml document (validate the xml string using a schema file)
    // the xml document does not specified the System ID or location of
    // schema..and use no namespace
    public void parse(HandlerType type, String xmldoc) throws SAXException, IOException {
        File           schema      = schemaMap.get(type);
        DefaultHandler handler     = handlerMap.get(yype);
        XMLReader   reader = XMLReaderFactory.createXMLReader(VENDOR);
        InputSource source = new InputSource(new StringReader(xmldoc));
        reader.setContentHandler(handler);
        reader.setFeature("http://xml.org/sax/features/validation", true);
        reader.setFeature("http://apache.org/xml/features/validation/schema", true);
        reader.setFeature("http://apache.org/xml/features/validation/schema-full-checking", true);
        reader.setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation",
        "file:///" + schema.getAbsolutePath());
        reader.parse(source);
    }

How to write a string as an XML Document

I wrote a web service to receieve a string and then write as an XMl document . But In my writer.java program, I am not doing something right. Please let me know what I am doing wrong.
Below is writer program:
public class Writer
public Writer()
} public void WriteHabFile(String out, String fileName)
XMLDocument doc = new XMLDocument();
try
XMLPrintDriver output=new XMLPrintDriver(new FileOutputStream(new File(fileName)));
output.setEncoding("utf-8");
output.printDocument(doc);
output.close();
catch (Exception e)
System.out.println(e.toString());
public void WriteLanFile(String out2, String fileName2)
XMLDocument doc = new XMLDocument();
try
XMLPrintDriver output=new XMLPrintDriver(new FileOutputStream(new File(fileName2)));
output.setEncoding("utf-8");
output.printDocument(doc);
output.close();
catch (Exception e)
System.out.println(e.toString());
}

The problems is that your XML document is not parsed.

How to parse this kind of XML documents and store in a relational tables

Can u guys help me out ,..how to parse these kind of XML documents..like under PR there Sr,CreationDate and DoBID.. Again under Sr...there are LD, CID,TID, RID and so on.....
so how to parse this kind of data..how to create the structure of the table....pls help me out..
<nk8:PR>
          <nk8:Sr>
               <nk8:LD>---------</nk8:LID>
               <nk8:CID>---------</nk8:CID>
               <nk8:TID>---------</nk8:TID>
               <nk8:RID>---------</nk8:RID>
               <nk8:CC>OnError</nk8:CC>
               <nk8:AID>---------</nk8:AID>
          </nk8:Sr>
          <nk8:CreationDateTime>2002-07-01</nk8:CreationDateTime>
          <nk8:DOBID>---------</nk8:DOBID>
     </nk8:PR>
     <ssm:ER>
          <ssm:PN>---------</ssm:PN>
          <ssm:SN>---------</ssm:SN>
          <ssm:SCt>---------</ssm:SC>
          <ssm:IA>
               <ssm:NT>---------</ssm:NT>
               <nk8:LID>---------</nk8:LID>
               <nk8:CID>---------</nk8:CID>
               <ssm:AN>---------</ssm:AN>
          </ssm:A>
     </ssm:ER>
     </nk8:PR>

First, your XML document is not well formatted. Once you're done with that you can extract the values and store it in a table column.
sql> WITH xml_table AS
2 (SELECT XMLTYPE(
3 '
4 <nk8:PR xmlns:nk8="http://www.w3.org">
5 <nk8:Sr>
6 <nk8:LID>LID Value</nk8:LID>
7 <nk8:CID>CID Value</nk8:CID>
8 <nk8:TID>TID Value</nk8:TID>
9 <nk8:RID>RID Value</nk8:RID>
10 <nk8:CC>OnError</nk8:CC>
11 <nk8:AID>---------</nk8:AID>
12 </nk8:Sr>
13 </nk8:PR>') XMLCOL FROM DUAL)
14 SELECT extractvalue(t.column_value,'//nk8:LID','xmlns:nk8="http://www.w3.org"') "LID",
15   extractvalue(t.column_value,'//nk8:CID','xmlns:nk8="http://www.w3.org"') "CID",
16   extractvalue(t.column_value,'//nk8:RID','xmlns:nk8="http://www.w3.org"') "RID",
17 extractvalue(t.column_value,'//nk8:CC','xmlns:nk8="http://www.w3.org"') "CC"
18 FROM xml_table, table(xmlsequence(extract(xmlcol,'/nk8:PR/nk8:Sr','xmlns:nk8="http://www.w3.org"'))) t;
LID        CID        RID        CC
LID Value CID Value RID Value OnError

XML document content not replaced

Similar Messages

Maybe you are looking for