Table-Export to XML

Hi all!
I'm a Newbie in BC4J, but I have to create an apllication with this technology.
My problem is, that one table should be exported to XML. I know that the standard Apllication, created by a wizard got this feature, but I didn't found the sourcecode.
Is there anybody, who knows how to implement an XML-Export?
Thanx
Peter Zerwes

Get the ViewObject reference that you want to export, e.g, in an AM say there's Dept/Emp VOs setup as masterdetail,
you may then get the DeptVO and call one of the writeXML() apis on it.
See javadoc for oracle.jbo.ViewObject and oracle.jbo.XMLInterface.writeXML().

Similar Messages

How to export table contents in xml file format through SQL queries

hi,
i need to export the table data in to xml file format. i got it through the GUI what they given.
i'm using Oracle 10g XE.
but i need to send the table name from Java programs. so, how to call the export commands from programming languages through. is there any sql commands to export the table contents in xml format.
and one more problem is i created each transaction in two tables. for example if we have a transaction 'sales' , that will be saved in db as
sales1 table and sales2 table. here i maintained and ID field in sales1 as PK. and id as FK in sales2.
i get the combined data with this query,
select * from sales1 s1, sales2 s2 where s1.id=s2.id order by s1.id;
it given all the records, but i'm getting two ID fields (one from each table). how to avoid this. here i dont know how many fields will be there in each table. that will be known at runtime only.
the static information is sales1 have one ID field with PK and sales2 will have one ID filed with FK.
i need ur valuable suggestions.
regards
pavan.

You can use DBMS_XMLGEN.getXML('your Query') for generating data in tables to XML format and you can use DBMS_XMLGEN.SETROWSETTAG to change the parent element name other wise it will give rowset as well as DBMS_XMLGEN.SETROWTAG for row name.
Check this otherwise XMLELEMENT and XMLFOREST function are also there to convert data in XML format.

Export table to formatted xml

I have an oracle table i have to export as formatted xml
I really want the data to look like this : (and need to get rid of the cdata)
<?xml version='1.0' ? XML_DATE = "2012-06-26 08:12:09 PM">
<APPLICATION NAME = "XMLTESTING">
     <WEBPAGE>
          <PROJECT>
<column1>ABC</column1>
<column2>DEF</column2>
<column3>GHI</column3>
<column4>JKL</column4>
<column5>MNO</column5>
</PROJECT>
<PROJECT>
<column1>ABG</column1>
<column2>DRF</column2>
<column3>GLY</column3>
<column4>JAL</column4>
<column5>MPO</column5>
</PROJECT>
<PROJECT>
<column1>BBC</column1>
<column2>GEF</column2>
<column3>LHI</column3>
<column4>JCL</column4>
<column5>MWO</column5>
</PROJECT>
</WEBPAGE>
</APPLICATION>
create table "XML_TESTING" (
"column1" varchar2(50byte),
"column2" varchar2(50byte),
"column3" varchar2(50byte),
"column4" varchar2(50byte),
"column5" varchar2(50byte)
INSERT into XML_TESTING values ('ABC','DEF','GHI','JKL','MNO');
INSERT into XML_TESTING values ('ABG','DRF','GLY','JAL','MPO');
INSERT into XML_TESTING values ('BBC','GEF','LHI','JCL','MWO');
CREATE TABLE xml_cl(result CLOB);
DECLARE
ctxqry DBMS_XMLGEN.ctxHandle;
result CLOB;
BEGIN
ctxqry := dbms_xmlgen.newContext('SELECT * FROM xml_testing');
DBMS_XMLGEN.setRowTag(ctxqry,'APPLICATIO NAME = "XML TESTING"');
--DBMS_XMLGEN.setMaxRows(ctxqry,5);
DBMS_XMLGEN.setrowsettag(ctxqry,'WEBPAGE');
LOOP
result := DBMS_XMLGEN.getXML(ctxqry);
EXIT WHEN
DBMS_XMLGEN.getNumRowsProcessed(ctxqry)=0;
INSERT INTO xml_cl VALUES(result);
END LOOP;
END;
SELECT * FROM xml_cl
THEN I EXPORT TO XML FROM HERE.
this is how xml currently looks
<?xml version='1.0' encoding='Cp1252' ?>
<RESULTS>
     <ROW>
          <COLUMN NAME="RESULT"><![CDATA[<?xml version="1.0"?>
<WEBPAGE>
<APPLICATIO_x0020_NAME_x0020__x003D__x0020__x0022_XML_x0020_TESTING_x0022_>
<column1>ABC</column1>
<column2>DEF</column2>
<column3>GHI</column3>
<column4>JKL</column4>
<column5>MNO</column5>
</APPLICATIO_x0020_NAME_x0020__x003D__x0020__x0022_XML_x0020_TESTING_x0022_>
<APPLICATIO_x0020_NAME_x0020__x003D__x0020__x0022_XML_x0020_TESTING_x0022_>
<column1>ABG</column1>
<column2>DRF</column2>
<column3>GLY</column3>
<column4>JAL</column4>
<column5>MPO</column5>
</APPLICATIO_x0020_NAME_x0020__x003D__x0020__x0022_XML_x0020_TESTING_x0022_>
<APPLICATIO_x0020_NAME_x0020__x003D__x0020__x0022_XML_x0020_TESTING_x0022_>
<column1>BBC</column1>
<column2>GEF</column2>
<column3>LHI</column3>
<column4>JCL</column4>
<column5>MWO</column5>
</APPLICATIO_x0020_NAME_x0020__x003D__x0020__x0022_XML_x0020_TESTING_x0022_>
</WEBPAGE>
]]></COLUMN>
     </ROW>
</RESULTS>
hope someone can help.
did alot of searching and reading and just cant find an answer
thank you

Use SQL/XML functions to build and serialize the document as CLOB in a single query :
SQL> SELECT XMLSerialize(document
2           XMLElement("APPLICATION",
3             XMLAttributes('XMLTESTING' as "NAME")
4           , XMLElement("WEBPAGE",
5               XMLAgg(
6                 XMLElement("PROJECT",
7                   XMLForest("column1", "column2", "column3", "column4", "column5")
8                 )
9               )
10             )
11           )
12           as clob
13           indent --< for formatting purpose only
14         )
15 FROM xml_testing
16 ;
XMLSERIALIZE(DOCUMENTXMLELEMEN
<APPLICATION NAME="XMLTESTING">
<WEBPAGE>
    <PROJECT>
      <column1>ABC</column1>
      <column2>DEF</column2>
      <column3>GHI</column3>
      <column4>JKL</column4>
      <column5>MNO</column5>
    </PROJECT>
    <PROJECT>
      <column1>ABG</column1>
      <column2>DRF</column2>
      <column3>GLY</column3>
      <column4>JAL</column4>
      <column5>MPO</column5>
    </PROJECT>
    <PROJECT>
      <column1>BBC</column1>
      <column2>GEF</column2>
      <column3>LHI</column3>
      <column4>JCL</column4>
      <column5>MWO</column5>
    </PROJECT>
</WEBPAGE>
</APPLICATION>
Then you can call DBMS_XSLPROCESSOR.CLOB2FILE to write the CLOB to a file, no need of an intermediate table.

Exporting data from database tables to a XML file

Hi,
We want to export data from Oracle database tables to an XML
file. What tool can we use for this purpose, and how do we go
about it ?
Can we extract data only from an Oracle8 database, or can we
extract data from Oracle7.3 databases too ?
Any help in this regard would be appreciated.
Thanks
Dipanjan
null

Dipanjan (guest) wrote:
: Hi,
: We want to export data from Oracle database tables to an XML
: file. What tool can we use for this purpose, and how do we go
: about it ?
: Can we extract data only from an Oracle8 database, or can we
: extract data from Oracle7.3 databases too ?
: Any help in this regard would be appreciated.
: Thanks
: Dipanjan
Start by downloading the XML SQL Utility and make sure you have
the approriate JDBC 1.1 drivers installed for your database.
There are samples which will get you going included in the
archive.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Internal Table Data to XML

Hi
I have a requirement of writing internal table data to XML. Any idea where i should start.
I have pretty good experience with ABAP and basic knowledge in XML.
There are good blogs which talk about transformations and other stuff but they are not able to give me clear path to my solution.
Could somebody give me a basic example or some reference material where i can move the data in internal table (assume Sales order details of a day) to XML.
Thanks

Refer the program -
In this implementation we will only focus on the creation of the XML file and the transfer to the user. You can not create a XML document directly. You have to use a so called ixml factory first.
TYPE-POOLS: ixml.
DATA: l_ixml TYPE REF TO if_ixml.
l_ixml = cl_ixml=>create( ).
This iXML factory can create an empty XML document object named l_document.
DATA: l_document TYPE REF TO if_ixml_document.
        l_document = l_ixml->create_document( ).
At this point you can add the nodes (elements, attributes) into the document. First you have to declare the root element node.
DATA: l_element_root TYPE REF TO if_ixml_element.
This node we have to give a name and add it (create_simple_node) to the document object l_document, which will be the parent of this node.
l_element_root = l_document->create_simple_element(
            name = 'flights'
          parent = l_document ).
Next we can add child nodes to there parent node using the same method of the document object.
DATA: l_element_airline TYPE REF TO if_ixml_element,
l_element_airline = l_document->create_simple_element(
               name = 'airline'
             parent = l_element_root ).
An attribute can be add easily using the method set_attribute of the element node.
l_rc = l_element_airline->set_attribute( name = 'code' value = 'LH401' ).
Now we have finished the document object. Regretfully it can not be displayed in any form due to the fact that it is a binary object.
The next step is to convert the created document to a flat file. To achieve this we have to create a stream factory, which will help us to create an output stream.
DATA: l_streamfactory   TYPE REF TO if_ixml_stream_factory.
l_streamfactory = l_ixml->create_stream_factory( ).
In this case, we will convert the document into an output stream which is based on an internal table of type x.
TYPES: BEGIN OF xml_line,
          data(256) TYPE x,
        END OF xml_line.
DATA: l_xml_table       TYPE TABLE OF xml_line,
        l_xml_size        TYPE i,
        l_rc              TYPE i,
        l_ostream         TYPE REF TO if_ixml_ostream.
l_ostream = l_streamfactory->create_ostream_itable( table = l_xml_table ).
When we have created the output stream we can do the rendering from the document into the stream. The XML data will be stored in the internal table automatically.
DATA: l_renderer        TYPE REF TO if_ixml_renderer.
l_renderer = l_ixml->create_renderer( ostream = l_ostream
                        & nbsp;              document = l_document ).
l_rc = l_renderer->render( ).
In the last step we upload the file to the sapgui
l_xml_size = l_ostream->get_num_written_raw( ).
CALL METHOD cl_gui_frontend_services=>gui_download
   EXPORTING
     bin_filesize = l_xml_size
     filename     = 'c:\temp\flights.xml'
     filetype     = 'BIN'
   CHANGING
     data_tab     = l_xml_table
   EXCEPTIONS
     OTHERS       = 24.
This finished the first step-of-three. As mentioned before the next log will focus on the conversion from xml files (back) to abap tables.
REPORT z_xit_xml_dom_create.
TYPE-POOLS: ixml.
TYPES: BEGIN OF xml_line,
          data(256) TYPE x,
         END OF xml_line.
DATA: l_ixml            TYPE REF TO if_ixml,
        l_streamfactory   TYPE REF TO if_ixml_stream_factory,
        l_ostream         TYPE REF TO if_ixml_ostream,
        l_renderer        TYPE REF TO if_ixml_renderer,
        l_document        TYPE REF TO if_ixml_document.
DATA: l_element_flights TYPE REF TO if_ixml_element,
        l_element_airline TYPE REF TO if_ixml_element,
        l_element_flight TYPE REF TO if_ixml_element,
        l_element_from    TYPE REF TO if_ixml_element,
        l_element_to      TYPE REF TO if_ixml_element,
        l_element_dummy   TYPE REF TO if_ixml_element,
        l_value           TYPE string.
DATA: l_xml_table       TYPE TABLE OF xml_line,
        l_xml_size        TYPE i,
        l_rc              TYPE i.
DATA: lt_spfli          TYPE TABLE OF spfli.
DATA: l_spfli           TYPE spfli.
START-OF-SELECTION.
Fill the internal table
    SELECT * FROM spfli INTO TABLE lt_spfli.
Sort internal table
    SORT lt_spfli BY carrid.
Start filling xml dom object from internal table
    LOOP AT lt_spfli INTO l_spfli.
      AT FIRST.
      Creating a ixml factory
        l_ixml = cl_ixml=>create( ).
      Creating the dom object model
        l_document = l_ixml->create_document( ).
      Fill root node with value flights
        l_element_flights = l_document->create_simple_element(
                    name = 'flights'
                    parent = l_document ).
      ENDAT.
      AT NEW carrid.
      Create element 'airline' as child of 'flights'
        l_element_airline = l_document->create_simple_element(
                    name = 'airline'
                    parent = l_element_flights ).
      Create attribute 'code' of node 'airline'
        l_value = l_spfli-carrid.
        l_rc = l_element_airline->set_attribute( name = 'code' value = l_value ).
      Create attribute 'name' of node 'airline'
        SELECT SINGLE carrname FROM scarr INTO l_value WHERE carrid EQ l_spfli-carrid.
        l_rc = l_element_airline->set_attribute( name = 'name' value = l_value ).
      ENDAT.
      AT NEW connid.
      Create element 'flight' as child of 'airline'
        l_element_flight = l_document->create_simple_element(
                    name = 'flight'
                    parent = l_element_airline ).
      Create attribute 'number' of node 'flight'
        l_value = l_spfli-connid.
        l_rc = l_element_flight->set_attribute( name = 'number' value = l_value ).
      ENDAT.
    Create element 'from' as child of 'flight'
      CONCATENATE l_spfli-cityfrom ',' l_spfli-countryfr INTO l_value.
      l_element_from = l_document->create_simple_element(
                  name = 'from'
                  value = l_value
                  parent = l_element_flight ).
    Create attribute 'airport' of node 'from'
      l_value = l_spfli-airpfrom.
      l_rc = l_element_from->set_attribute( name = 'airport' value = l_value ).
    Create element 'to' as child of 'flight'
      CONCATENATE l_spfli-cityto ',' l_spfli-countryto INTO l_value.
      l_element_to = l_document->create_simple_element(
                  name = 'to'
                  value = l_value
                  parent = l_element_flight ).
    Create attribute 'airport' of node 'from'
      l_value = l_spfli-airpto.
      l_rc = l_element_to->set_attribute( name = 'airport' value = l_value ).
    Create element 'departure' as child of 'flight'
      l_value = l_spfli-deptime.
      l_element_dummy = l_document->create_simple_element(
                  name = 'departure'
                  value = l_value
                  parent = l_element_flight ).
    Create element 'arrival' as child of 'flight'
      l_value = l_spfli-arrtime.
      l_element_dummy = l_document->create_simple_element(
                  name = 'arrival'
                  value = l_value
                  parent = l_element_flight ).
    Create element 'type' as child of 'flight'
      CASE l_spfli-fltype.
        WHEN 'X'.
          l_value = 'Charter'.
        WHEN OTHERS.
          l_value = 'Scheduled'.
      ENDCASE.
      l_element_dummy = l_document->create_simple_element(
                  name = 'type'
                  value = l_value
                  parent = l_element_flight ).
    ENDLOOP.
    IF sy-subrc NE 0.
      MESSAGE 'No data into db table ''spfli'', please run program ''SAPBC_DATA_GENERATOR'' with transaction ''SA38''' TYPE 'E'.
    ENDIF.
Creating a stream factory
    l_streamfactory = l_ixml->create_stream_factory( ).
Connect internal XML table to stream factory
    l_ostream = l_streamfactory->create_ostream_itable( table = l_xml_table ).
Rendering the document
    l_renderer = l_ixml->create_renderer( ostream = l_ostream
                                          document = l_document ).
    l_rc = l_renderer->render( ).
Saving the XML document
    l_xml_size = l_ostream->get_num_written_raw( ).
    CALL METHOD cl_gui_frontend_services=>gui_download
      EXPORTING
        bin_filesize = l_xml_size
        filename     = 'c:\temp\flights.xml'
        filetype     = 'BIN'
      CHANGING
        data_tab     = l_xml_table
      EXCEPTIONS
        OTHERS       = 24.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
<?xml version="1.0"?>
<flights>
     <airline code="AA" name="American Airlines">
          <flight number="0017">
               <from airport="JFK">NEW YORK,US</from>
               <to airport="SFO">SAN FRANCISCO,US</to>
               <departure>110000</departure>
               <arrival>140100</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0064">
               <from airport="SFO">SAN FRANCISCO,US</from>
               <to airport="JFK">NEW YORK,US</to>
               <departure>090000</departure>
               <arrival>172100</arrival>
               <type>Scheduled</type>
          </flight>
     </airline>
     <airline code="AZ" name="Alitalia">
          <flight number="0555">
               <from airport="FCO">ROME,IT</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>190000</departure>
               <arrival>210500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0788">
               <from airport="FCO">ROME,IT</from>
               <to airport="TYO">TOKYO,JP</to>
               <departure>120000</departure>
               <arrival>085500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0789">
               <from airport="TYO">TOKYO,JP</from>
               <to airport="FCO">ROME,IT</to>
               <departure>114500</departure>
               <arrival>192500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0790">
               <from airport="FCO">ROME,IT</from>
               <to airport="KIX">OSAKA,JP</to>
               <departure>103500</departure>
               <arrival>081000</arrival>
               <type>Charter</type>
          </flight>
     </airline>
     <airline code="DL" name="Delta Airlines">
          <flight number="1984">
               <from airport="SFO">SAN FRANCISCO,US</from>
               <to airport="JFK">NEW YORK,US</to>
               <departure>100000</departure>
               <arrival>182500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="1699">
               <from airport="JFK">NEW YORK,US</from>
               <to airport="SFO">SAN FRANCISCO,US</to>
               <departure>171500</departure>
               <arrival>203700</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0106">
               <from airport="JFK">NEW YORK,US</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>193500</departure>
               <arrival>093000</arrival>
               <type>Scheduled</type>
          </flight>
     </airline>
     <airline code="JL" name="Japan Airlines">
          <flight number="0407">
               <from airport="NRT">TOKYO,JP</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>133000</departure>
               <arrival>173500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0408">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="NRT">TOKYO,JP</to>
               <departure>202500</departure>
               <arrival>154000</arrival>
               <type>Charter</type>
          </flight>
     </airline>
     <airline code="LH" name="Lufthansa">
          <flight number="2407">
               <from airport="TXL">BERLIN,DE</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>071000</departure>
               <arrival>081500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="2402">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="SXF">BERLIN,DE</to>
               <departure>103000</departure>
               <arrival>113500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0402">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="JFK">NEW YORK,US</to>
               <departure>133000</departure>
               <arrival>150500</arrival>
               <type>Charter</type>
          </flight>
          <flight number="0401">
               <from airport="JFK">NEW YORK,US</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>183000</departure>
               <arrival>074500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0400">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="JFK">NEW YORK,US</to>
               <departure>101000</departure>
               <arrival>113400</arrival>
               <type>Scheduled</type>
          </flight>
     </airline>
     <airline code="QF" name="Qantas Airways">
          <flight number="0005">
               <from airport="SIN">SINGAPORE,SG</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>225000</departure>
               <arrival>053500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0006">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="SIN">SINGAPORE,SG</to>
               <departure>205500</departure>
               <arrival>150500</arrival>
               <type>Scheduled</type>
          </flight>
     </airline>
     <airline code="SQ" name="Singapore Airlines">
          <flight number="0988">
               <from airport="SIN">SINGAPORE,SG</from>
               <to airport="TYO">TOKYO,JP</to>
               <departure>163500</departure>
               <arrival>001500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0158">
               <from airport="SIN">SINGAPORE,SG</from>
               <to airport="JKT">JAKARTA,ID</to>
               <departure>152500</departure>
               <arrival>160000</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0015">
               <from airport="SFO">SAN FRANCISCO,US</from>
               <to airport="SIN">SINGAPORE,SG</to>
               <departure>160000</departure>
               <arrival>024500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="0002">
               <from airport="SIN">SINGAPORE,SG</from>
               <to airport="SFO">SAN FRANCISCO,US</to>
               <departure>170000</departure>
               <arrival>192500</arrival>
               <type>Scheduled</type>
          </flight>
     </airline>
     <airline code="UA" name="United Airlines">
          <flight number="0941">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="SFO">SAN FRANCISCO,US</to>
               <departure>143000</departure>
               <arrival>170600</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="3504">
               <from airport="SFO">SAN FRANCISCO,US</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>150000</departure>
               <arrival>103000</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="3516">
               <from airport="JFK">NEW YORK,US</from>
               <to airport="FRA">FRANKFURT,DE</to>
               <departure>162000</departure>
               <arrival>054500</arrival>
               <type>Scheduled</type>
          </flight>
          <flight number="3517">
               <from airport="FRA">FRANKFURT,DE</from>
               <to airport="JFK">NEW YORK,US</to>
               <departure>104000</departure>
               <arrival>125500</arrival>
               <type>Scheduled</type>
          </flight>
     </airline>
</flights>
Regards,
Amit
Reward all helpful replies.

Do you need to generate HTML table rows from XML in InDesign?

General issue: you export XML and you get a bunch of content for xml elements that were a table in inDesign. But they don't have any rows, just cell after cell. What will make rows in your output?
Solution: XSLT; you need to use the @aid:tcols attribute of exported XML to determine the number of columns that your table should be. This is written in XSLT 1.1 so it shoud work with an export from InDesign. If you have problems with using it on export of XML, try using it on the XML afetr it has been exported, in Oxygen or other XSLT processor. Best to save acopy of your files before using the XSLT with them. Copy all of the plain text and past into a new file, save with your own filename, ending with .xsl file extension. Then when exporting XML from InDesign CS3-5, browse to your new .xsl file and select it. PLEASE read about XSLT files at w3c.schools or other resource if you want to understand what is going on with this file.
BTW 
<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.1"
    xmlns:aid="http://ns.adobe.com/AdobeInDesign/4.0/"
    xmlns:aid5="http://ns.adobe.com/AdobeInDesign/5.0/" exclude-result-prefixes="xsl aid aid5">
    <xsl:output method="html" indent="yes" encoding="UTF-8"
        doctype-public="http://www.w3.org/TR/xhtml/DTD/xhtml-transitional.dtd"/>

    <xsl:param name="tableElem">//*[local-name()][@aid:table='table']</xsl:param>
    <xsl:param name="colheadStyle">
        <xsl:value-of select="//*[local-name()][@aid:theader][1]"/>
        
    </xsl:param>


    <xsl:param name="cellStyle">
        <xsl:value-of select="//*[local-name()][@aid:table='cell' and not(@aid:theader)][1]"/>
    </xsl:param>
    
    
    <xsl:template match="Story">
        <html>
            <head>
                <title>Sample Table</title>
            </head>
            <body>
                <xsl:apply-templates>
                    <xsl:with-param name="colheadStyle" select="$colheadStyle"/>
                    <xsl:with-param name="cellStyle" select="$cellStyle"/>
                </xsl:apply-templates>
            </body>
        </html>
    </xsl:template>
   
    <xsl:template match="Table">
        <xsl:param name="colheadStyle">
            <xsl:value-of select="$colheadStyle"/>
        </xsl:param>
        <xsl:param name="cellStyle">
            <xsl:value-of select="$cellStyle"/>
        </xsl:param>
        <xsl:variable name="cellsPerRow">
            <xsl:value-of select="@aid:tcols"/>
        </xsl:variable>
        <table>
            
            <tr>
                <xsl:apply-templates select="*[@aid:theader='']">
                    <xsl:with-param name="colheadStyle" select="$colheadStyle"/>
                    <xsl:with-param name="cellStyle" select="$cellStyle"/>
                </xsl:apply-templates>
            </tr>
            
            <xsl:for-each
                select="*[@aid:table='cell'][not(@aid:theader='')][position() mod $cellsPerRow = 1]">



                <tr>
                    <xsl:apply-templates
                        select=".|following-sibling::*[@aid:table='cell'][not(@aid:theader='')][position() < $cellsPerRow]"
                    />
                </tr>
            </xsl:for-each>
        </table>
    </xsl:template>
    <xsl:template match="*">
        <xsl:param name="colheadStyle">
            <xsl:value-of select="$colheadStyle"/>
        </xsl:param>
        <xsl:param name="cellStyle">
            <xsl:value-of select="$cellStyle"/>
        </xsl:param>
        <xsl:variable name="cellsPerRow">
            <xsl:value-of select="parent::Table/@aid:tcols"/>
        </xsl:variable>
        <xsl:choose>
            
            <xsl:when test="parent::Table and @aid:theader">
                <th>
                    <xsl:apply-templates>
                        <xsl:with-param name="colheadStyle" select="$colheadStyle"/>
                        <xsl:with-param name="cellStyle" select="$cellStyle"/>
                    </xsl:apply-templates>
                </th>
                <xsl:if test="(position() = last()) and (position() < $cellsPerRow)">
                    <xsl:call-template name="FillerCells">
                        <xsl:with-param name="cellCount" select="$cellsPerRow - position()"/>
                    </xsl:call-template>
                </xsl:if>
            </xsl:when>
            <xsl:when test="parent::Table and @aid:table='cell' and not(@aid:theader)">
                <td>
                    <xsl:apply-templates>
                        <xsl:with-param name="colheadStyle" select="$colheadStyle"/>
                        <xsl:with-param name="cellStyle" select="$cellStyle"/>
                    </xsl:apply-templates>
                </td>
                <xsl:if test="(position() = last()) and (position() < $cellsPerRow)">
                    <xsl:call-template name="FillerCells">
                        <xsl:with-param name="cellCount" select="$cellsPerRow - position()"/>
                    </xsl:call-template>
                </xsl:if>
            </xsl:when>

            <xsl:otherwise>
                <xsl:element name="{name()}">
                    <xsl:if test="@aid:pstyle">
                        <xsl:attribute name="class">
                            <xsl:value-of select="@aid:ptyle"/>
                        </xsl:attribute>
                    </xsl:if>
                    <xsl:apply-templates>
                        <xsl:with-param name="colheadStyle" select="$colheadStyle"/>
                        <xsl:with-param name="cellStyle" select="$cellStyle"/>
                    </xsl:apply-templates>
                </xsl:element>
            </xsl:otherwise>
        </xsl:choose>
    </xsl:template>
    
    <xsl:template match="text()">
        <xsl:variable name="myString">
            <xsl:value-of select="string-length(normalize-space(.))"/>
        </xsl:variable>
        <xsl:choose>
            <xsl:when test="parent::Story">
                <xsl:if test="$myString > 0">
                    <xsl:element name="p">
                        <xsl:attribute name="class">text</xsl:attribute>
                        <xsl:value-of select="normalize-space(.)"/>
                    </xsl:element>
                </xsl:if>
            </xsl:when>
            <xsl:otherwise>
                <xsl:value-of select="normalize-space(.)"/>
            </xsl:otherwise>
        </xsl:choose>
    </xsl:template>
   
    <xsl:template match="br">
        <br />
    </xsl:template>
    
    
    
    
    <xsl:template name="FillerCells">
        <xsl:param name="cellCount"/>
        <td> </td>
        <xsl:if test="$cellCount > 1">
            <xsl:call-template name="FillerCells">
                <xsl:with-param name="cellCount" select="$cellCount - 1"/>
            </xsl:call-template>
        </xsl:if>
    </xsl:template>
</xsl:stylesheet>
Message was edited by: HoneoyeFalls
Sample XML file exported from IDD
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Story><Table xmlns:aid="http://ns.adobe.com/AdobeInDesign/4.0/" xmlns:aid5="http://ns.adobe.com/AdobeInDesign/5.0/" aid:table="table" aid:trows="2" aid:tcols="2"><colHead aid:table="cell" aid:theader="" aid:crows="1" aid:ccols="1" aid:ccolwidth="44">1 colHead</colHead><colHead aid:table="cell" aid:theader="" aid:crows="1" aid:ccols="1" aid:ccolwidth="56">2 colHead</colHead><tabletext aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="44">1 tabletext</tabletext><tabletext aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="56">2 tabletext</tabletext><tabletext aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="44">row 2 1 tabletext</tabletext><tabletext aid:table="cell" aid:crows="1" aid:ccols="1" aid:ccolwidth="56">row 2 2 tabletext</tabletext></Table>
<table><tr><th>normal HTML table heading</th></tr>
<tr><td>normal HTML table<br/>cell text</td></tr></table></Story>

You can use RECORD type declaration:
SQL> declare
2   type rec_type is record (
3    ename emp.ename%type,
4    sal emp.sal%type
5   );
6   type rc is ref cursor return rec_type;
7   rc1 rc;
8   rec1 rec_type;
9 begin
10   open rc1 for select ename, sal from emp;
11   loop
12    fetch rc1 into rec1;
13    exit when rc1%notfound;
14    dbms_output.put_line(rec1.ename || ' ' || rec1.sal);
15   end loop;
16   close rc1;
17 end;
18 /
SMITH 800
ALLEN 1600
WARD 1250
JONES 2975
MARTIN 1250
BLAKE 2850
CLARK 2450
SCOTT 3000
KING 5000
TURNER 1500
ADAMS 1100
JAMES 950
FORD 3000
MILLER 1300or use, for example, VIEW to declare rowtype:
SQL> create view dummy_view as select ename, sal from emp;
View created.
SQL> declare
2   type rc is ref cursor return dummy_view%rowtype;
3   rc1 rc;
4   rec1 dummy_view%rowtype;
5 begin
6   open rc1 for select ename, sal from emp;
7   loop
8    fetch rc1 into rec1;
9    exit when rc1%notfound;
10    dbms_output.put_line(rec1.ename || ' ' || rec1.sal);
11   end loop;
12   close rc1;
13 end;
14 /
SMITH 800
ALLEN 1600
WARD 1250
JONES 2975
MARTIN 1250
BLAKE 2850
CLARK 2450
SCOTT 3000
KING 5000
TURNER 1500
ADAMS 1100
JAMES 950
FORD 3000
MILLER 1300 Rgds.

Structure inDesign document and export as XML for use in the web

Hello everyone,
I just recently started using inDesign and I am fascinated by its possibilities! I use it for a project where a finished inDesign layout that is used for a printed publication is now supposed to be transformed for implementing it on a web site. My job is to export the inDesign document as an XML file. After massive reading the last weeks I'm quite familiar with the structuring and tagging in inDesign. Though there's some issues I do not understand. Your precious advice would be of highest meaning to me
The programmer who will later use my XML output for the web-transformation needs the document structured in different levels like "Root > Chapter > Subchapter > Text passage / table". I already structured the document with tags like title, text passage, table, infobox,... but the structure is just linear, putting one item following to another.
How can I structure the document with reoccuring tags that enable me to identify the exact position of an item in the document's structure? So that I can say for example "text passage X" is located in chapter 4, subchapter 1. This has to be done because the document is supposed to be updated later on. So maybe a chapter gets modified and has to be replaced, but this replacement is supposed to be displayed.
I hope my problem becomes clear! That's my biggest issue for now. So for any help I'd be very thankful!

Our print publications are created in InDesign CS5 for Mac then the text is exported to RTF files then sent to an outside company to be converted to our XML specifications for use by our website developers. I would like to create a workflow in which our XML tags are included in the InDesign layouts and then export the XML from the layouts.
Some more detail about what kind of formatting is necessary might be helpful.
I know that IDML files contain the entire layout in XML format. Is it a good idea to extract what we need from IDML, using the already-assigned tags?
Well, if you want to export the whole document, it's the only reasonable approach.
We use a workflow system such that each story is a seperate InCopy document, stored in ICML format (Basically a subset of IDML). Our web automation uses XSLT to convert each story into HTML for use on our web site; it also matches it up with external metadata so it knows what is a headline and what is not, etc.. It is not exactly hassle free, and every once in a while someone uses a new InDesign feature that breaks things (e.g., our XSLT has no support for paragraph numbering, so numbered paragraphs show up without their numbers).
You could do the same thing with with IDML, you'd just have to pick out each story, but that's small potatoes compared to all the XSL work you're going to have to do.
On the other hand, there may be better approaches if you're not going to export the whole document. For instance, you could use scripting to export each story as an RTF file, and then you could convert the RTF files into HTML using other tools.

Marked up index exported to XML

Hi,
I'm very new to ID. I am currently importing Excel tables into Indesign. Basically, my book/chapters are made up of tables. Next, I need to create an index therefore, I started marking up my content (creating index entry page references). Once our book is done we need to export this content to XML. I realize i can map styles to tags for the export to XML. However, my question is how can I export the markedup index content to xml? The whole idea of going from Excel to ID was so that we wouldn't have to do the index twice.
Any advice would be much appreciated.

With Scripting, you can do just about everything, except the one thing I wanted to show (off): creating a run of text in memory, then loading your 'place text cursor' with it ...
Anyway, this little javascript shows you how to "get" the index entries themselves out of InDesign. This is just the list of entries; each entry in itself (going by the name of "Topic") contains a list of PageReferences -- zero or more -- that point to the actual text insertion point where each of the entries proper reside in your full text. Weeding them out one by one should also be possible, and even automatically putting XML tags around them, but you have to remember they need to be "visible" in your plain text to be able to export. With that, I mean it might well be possible to write a script that writes out every entry as "plain text" (and possibly, including the correct tags), but they *will* appear inside the text where you inserted the actual index entry. Hence, my suggestion of very small and invisibly colored text.
I guess you'll need to think about how to handle this.
This is my "proof of concept" scriptlet; it only gathers the index entry list (with possible sub-entries) and displays them as an alert:
var list = [ "My Index" ];
for (i=0; i< app.activeDocument.indexes[0].topics.length; i++)
     list.push (app.activeDocument.indexes[0].topics[i].name);
     for (j=0; j<app.activeDocument.indexes[0].topics[i].topics.length; j++)
          list.push (" >> "+app.activeDocument.indexes[0].topics[i].topics[j].name);
alert (list.join("\r"));

How to download internal table data into xml file?

Hi,
Experts,
I have downloaded internal table data into XLS format using GUI_DOWNLOAD Function module, But i didn't Know how to download internal table data into XML format please post some ideas/inputs on this issue.
Thank you,
Shabeer ahmed.

check this
data : gd_repid type sy-repid.
GD_REPID = SY-REPID.
DATA : L_DOM TYPE REF TO IF_IXML_ELEMENT,
       M_DOCUMENT TYPE REF TO IF_IXML_DOCUMENT,
       G_IXML TYPE REF TO IF_IXML,
       W_STRING TYPE XSTRING,
       W_SIZE TYPE I,
       W_RESULT TYPE I,
       W_LINE TYPE STRING,
       IT_XML TYPE DCXMLLINES,
       S_XML LIKE LINE OF IT_XML,
       W_RC LIKE SY-SUBRC.
DATA: XML TYPE DCXMLLINES.
DATA: RC TYPE SY-SUBRC,
      BEGIN OF XML_TAB OCCURS 0,
      D LIKE LINE OF XML,
      END OF XML_TAB.
data : l_element           type ref to if_ixml_element,
       xml_ns_prefix_sf     type string,
       xml_ns_uri_sf        type string.
CLASS CL_IXML DEFINITION LOAD.
G_IXML = CL_IXML=>CREATE( ).
CHECK NOT G_IXML IS INITIAL.
M_DOCUMENT = G_IXML->CREATE_DOCUMENT( ).
CHECK NOT M_DOCUMENT IS INITIAL.
CALL FUNCTION 'SDIXML_DATA_TO_DOM'
EXPORTING
   NAME = 'REPAIRDATA'
   DATAOBJECT = IT_FINAL_LAST1[]
IMPORTING
   DATA_AS_DOM = L_DOM
CHANGING
   DOCUMENT = M_DOCUMENT
EXCEPTIONS
   ILLEGAL_NAME = 1
   OTHERS = 2.
CHECK NOT L_DOM IS INITIAL.
W_RC = M_DOCUMENT->APPEND_CHILD( NEW_CHILD = L_DOM ).
*Start of code for Header
* namespace
t_mnr = sy-datum+4(2).
CALL FUNCTION 'IDWT_READ_MONTH_TEXT'
EXPORTING
    LANGU         = 'E'
    MONTH         = t_mnr
IMPORTING
   T247          = wa_t247
concatenate sy-datum+6(2)
            wa_t247-ktx
            sy-datum(4) into t_var1.
concatenate sy-uzeit(2)
            sy-uzeit+2(2)
            sy-uzeit+4(2) into t_var2.
clear : xml_ns_prefix_sf,
        xml_ns_uri_sf.
l_element = m_document->get_root_element( ).
xml_ns_prefix_sf = 'TIMESTAMP'.
concatenate t_var1 t_var2 into xml_ns_uri_sf separated by space.
clear : t_var1,
        t_var2,
        t_mnr,
        wa_t247.
l_element->set_attribute( name = xml_ns_prefix_sf
                          namespace = ' '
                          value = xml_ns_uri_sf ).
clear : xml_ns_prefix_sf,
        xml_ns_uri_sf.
xml_ns_prefix_sf = 'FILECREATOR'.
xml_ns_uri_sf    =   'SAP'.
l_element->set_attribute( name = xml_ns_prefix_sf
                          namespace = ' '
                          value = xml_ns_uri_sf ).
clear : xml_ns_prefix_sf,
        xml_ns_uri_sf.
xml_ns_prefix_sf = 'CLAIMGROUP'.
xml_ns_uri_sf    = '1'.
l_element->set_attribute( name = xml_ns_prefix_sf
                          namespace = ' '
                          value = xml_ns_uri_sf ).
clear : xml_ns_prefix_sf,
        xml_ns_uri_sf.
xml_ns_prefix_sf = 'CLAIMTYPES'.
xml_ns_uri_sf    = 'W'.
l_element->set_attribute( name = xml_ns_prefix_sf
                          namespace = ' '
                          value = xml_ns_uri_sf ).
*End of Code for Header
CALL FUNCTION 'SDIXML_DOM_TO_XML'
EXPORTING
DOCUMENT = M_DOCUMENT
IMPORTING
XML_AS_STRING = W_STRING
SIZE = W_SIZE
TABLES
XML_AS_TABLE = IT_XML
EXCEPTIONS
NO_DOCUMENT = 1
OTHERS = 2.
LOOP AT IT_XML INTO XML_TAB-D.
APPEND XML_TAB.
ENDLOOP.
*Start of Code for File name
concatenate p_file
            '\R'
            '000_119481'
            sy-datum+6(2) sy-datum+4(2) sy-datum+2(2)
            sy-uzeit(2)   sy-uzeit+2(2) sy-uzeit(2) '.xml' into p_file.
*End of Code for File name
CALL FUNCTION 'WS_DOWNLOAD'
EXPORTING
BIN_FILESIZE = W_SIZE
FILENAME = p_file
FILETYPE = 'BIN'
TABLES
DATA_TAB = XML_TAB
EXCEPTIONS
OTHERS = 10.
IF SY-SUBRC = 0.
              MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Oracle Business Rules decision tables - export

This is a beginner's question.. Suppose that you want to use an Oracle Business Rules (OBR) decision table, for example to check company’s eligibility for financing based on their country and business type (PRIVATE or PUBLIC). You would define a corresponding decision table in JDeveloper with true/false assignments in the Actions. Is it possible to export this decision table somehow? Ideally we would want to have a web service returning the decision table data as XML, which would then be used to generate PDF or a dynamic webpage etc. Then we would have OBR as the only point of data entry.

I moved this to "SOA Suite and OC4J 11g Technology Preview"
Business Rules - Decision Tables and Buckets
Chandresh

How to insert data into a table from an xml document

using the XmlSql Utility, how do I insert data into a table from an xml document, using the sqlplus prompt.
if i use the xmlgen.insertXML(....)
requires a CLOB file, which i dont have, only the xml doc.
Cant i insert directly from the doc to the table?
the xmlgen examples I have seen first convert a table to a CLOB xmlString and then insert it into another table.
Isnt there any other way?

Your question is little perplexing.
If you're using XML SQL Utility from
the commandline, just use putXML.
java OracleXML putXML
null

Creating a Pivot Table in a XML publishe

When creating a Pivot Table in a XML publisher in Word, is there a way for a Pivot table to respect the fact that it's inside of a group function? I'm looping over site , and within each site I want to create a Pivot Table that has Months going across and SUB inventories going down, but only for that site.

Hello,
create one column in criteria and change it's fx to case when 1=0 then Products."Prod Name" else 'Tota Loanl' end
Now go to pivot and drag this column to Columns block of pivot. But keep this column up of Measure Labels and Now, go to column Format values.
Mention cell horizontal alignment to Center
see the following screenshot, Header is the column i created with the above functionality.
!http://i852.photobucket.com/albums/ab83/kishorg86/Header.jpg!

Inserting data from a table to an XML file

I want to insert the values from this xml file emp.xml into a table Employees :
<EMPLOYEES>
<EMP>
<EMPNO>7369</EMPNO>
<ENAME>SMITH</ENAME>
<JOB>CLERK</JOB>
<HIREDATE>17-DEC-80</HIREDATE>
<SAL>800</SAL>
</EMP>
<EMP>
<EMPNO>7499</EMPNO>
<ENAME>ALLEN</ENAME>
<JOB>SALESMAN</JOB>
<HIREDATE>20-FEB-81</HIREDATE>
<SAL>1600</SAL>
<COMM>300</COMM>
</EMP>
<EMP>
</EMPLOYEES>
and here is my Employee table in Oracle 9i database
SQL> DESC EMPLOYEE;
Name Null? Type
EMPNO NUMBER
EMPNAME VARCHAR2(10)
JOB VARCHAR2(10)
HIREDATE DATE
SAL NUMBER
After getting help from the members i was able to do the insert of data from the xml file to the table..how to do the insert of data from the table to the xml file.
Regards,
Renu

Hello michaels , thank you for the solution, still i am having some problems
Here is what i have done :
1.
SQL> CREATE DIRECTORY my_table_dir AS 'E:\table_files'
2 ;
Directory created.
2.
SQL> select * from myemp;
ENAME
SMITH
ALLEN
3.
This is the content of the existing xml file saved in the directory E:\table_files as emp.xml
<EMPLOYEES>
<EMP>JIM</EMP>
<EMP>RICK</EMP>
</EMPLOYEES>
4.
Now i executed this code :
declare
emp_xml xmltype;
begin
select sys_xmlagg (column_value, sys.xmlformat ('EMPLOYEES')) emp_xml
into emp_xml
from table (xmlsequence (cursor (select *
from myemp
where ename in ('SMITH', 'ALLEN')),
sys.xmlformat ('EMP')
dbms_xslprocessor.clob2file (emp_xml.getclobval (), 'E:\table_files', 'emp.xml');
end;
And the Error i got is :
declare
ERROR at line 1:
ORA-29280: invalid directory path
ORA-06512: at "SYS.UTL_FILE", line 18
ORA-06512: at "SYS.UTL_FILE", line 424
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 46
ORA-06512: at line 12

ORA-19007 when coping a table with an xml type in it to a new schema in the

ORA-19007 when coping a table with an xml type in it to a new schema in the same database.
Hi all,
When I copy a table with an xml type in it to a new schema in the same database I get an ora-19009.
The setup is as follows I have a schema a with table TABLE_WITH_XMLTYPE where data is:
CREATE
TABLE TABLE_WITH_XMLTYPE
FOLDER_ID NUMBER (10, 0) NOT NULL,
SEARCH_PROPERTIES XMLTYPE ,
CONSTRAINT TABLE_WITH_XMLTYPE PK PRIMARY KEY (FOLDERID) USING INDEX
XMLTYPE COLUMN SEARCH_PROPERTIES XMLSCHEMA
"http://xxxxxxx.net/FolderProperties.xsd" element "FolderProperties"
VARRAY SEARCH_PROPERTIES."XMLDATA"."PROPERTIES"."PROPERTY" STORE AS TABLE
PROPERTY_TABLE
(PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX)) ORGANIZATION INDEX OVERFLOW
Both schemas have the following xml schema registered as a local xml schema
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xxxxxxx.net/FolderProperties.xsd',
SCHEMADOC =>
'<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
xdb:storeVarrayAsTable="true">
<xs:element name="FolderProperties"
type="FolderPropertiesType"
xdb:defaultTable="FOLDER_SEARCH_PROPERTIES" />
<xs:complexType name="FolderPropertiesType" xdb:SQLType="FOLDERPROPERTIES_T">
<xs:sequence>
<xs:element name="FolderID" type="FolderIDType" minOccurs="1" xdb:SQLName="FOLDER_ID"/>
<xs:element name="Properties" type="PropertiesType" xdb:SQLName="PROPERTIES"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PropertiesType" xdb:SQLType="PROPERTIES_T">
<xs:sequence>
<xs:element name="Property" type="PropertyType" maxOccurs="unbounded"
xdb:SQLName="PROPERTY" xdb:SQLCollType="PROPERTY_V"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PropertyType" xdb:SQLType="PROPERTY_T">
<xs:sequence>
<xs:element name="DateValue" type="DateType" xdb:SQLName="DATE_VALUE"/>
<xs:element name="NumValue" type="NumType" xdb:SQLName="NUM_VALUE"/>
<xs:element name="StringValue" type="StringType" xdb:SQLName="STRING_VALUE"/>
</xs:sequence>
<xs:attribute name="Name" xdb:SQLName="NAME" xdb:SQLType="VARCHAR2">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
<xs:simpleType name="FolderIDType">
<xs:restriction base="xs:integer"/>
</xs:simpleType>
<xs:simpleType name="DateType">
<xs:restriction base="xs:dateTime"/>
</xs:simpleType>
<xs:simpleType name="NumType">
<xs:restriction base="xs:decimal"/>
</xs:simpleType>
<xs:simpleType name="StringType">
<xs:restriction base="xs:string" />
</xs:simpleType>
</xs:schema>',
LOCAL => TRUE,
GENTYPES => TRUE,
GENTABLES => FALSE);
END;
when I try to do the following insert:
insert into schemaB.TABLE_WITH_XMLTYPE ( FOLDER_ID, SEARCH_PROPERTIES)
select FOLDER_ID, SEARCH_PROPERTIES from schemaB.TABLE_WITH_XMLTYPE;
I’ll get an ora-19007.
Can some one point me in the right direction how to solve this error.
Thanks Roelof.

Who did you create the second table, in other words, how did you COPY the table as you said...
If you created the second table via a CTAS (create table as select) then you will have created a table that is not the same as the original one. AFAIK I have once created an enhancement request for this after discovering that JDeveloper, for example, creates a "copy" via a CTAS which creates the wrong structure. Double check via package DBMS_METADATA.
SQL> set long 1000000
SQL> select DBMS_METADATA('TABLE','TABLE_WITH_XMLTYPE','SchemaA') from dual;
SQL> select DBMS_METADATA('TABLE','TABLE_WITH_XMLTYPE','SchemaB') from dual;If you have got two different tables, than Mark's solution should help.
M.
Edited by: Marco Gralike on Feb 15, 2009 11:16 AM

ORA-00942 error on truncating a table with a XML Index

Oracle Version: 11.2.0.1.0
When truncate command fails with error "ORA-00942: table or view does not exist" when run against a table with an XML Index defined
SQL> CREATE TABLE XML_TEST
2 (
3 ID INTEGER,
4 TESTXML SYS.XMLTYPE
5 );
Table created.
SQL> truncate table XML_TEST;
Table truncated.
SQL> CREATE INDEX xmlindex ON XML_TEST(TESTXML)
2 indextype IS xdb.xmlindex
3 parameters ('PATH TABLE MY_PATH_TABLE');
Index created.
SQL> truncate table XML_TEST;
truncate table XML_TEST
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> Drop Index xmlindex;
Index dropped.
SQL> truncate table XML_TEST;
Table truncated.

No, I don't think that explanation is correct. I don't think it has to do with user privs. besides, we don't
adjust rowids on an import -- we recreate the index, just like a b-tree index import would.
This should be working. It's most likely a bug in our (i.e. Text) import code -- SYS.XMLTYPE is a little
strange because under the covers it's actually a function-based index.
I will test it out and file a bug if I can reproduce the behavior on solaris.

Table-Export to XML

Similar Messages

Maybe you are looking for