dxxShredXML limitations, dimension limitation?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • thefirstwml

    dxxShredXML limitations, dimension limitation?

    I am planning to load large XML files into relational tables using the
    dxxShredXML stored procedure. There is a major limitation on the size
    of the files, and I read on this group that this can be solved by
    creating a new stored procedure.

    However, there was also a question of dimension limitations (error at
    12MB). Does that refer to the number of side tables and the amount of
    data that can be stored there? Does anyone know if there is a
    solution to the problem below?


    <<
    Hi,

    I'm trying to load a XML file into a table DB2 (Version 7.2) with XML
    Extender.
    It work fine if my file have a dimension 1K

    But if my file have bigger dimension (12 M ) I get this error
    message:

    parse err 10 in file C:\temp\dxx11 line 26301 col 49: DXXQ047E Parser
    error
    on
    line 26301 column 49: Expected end of tag 'CodiceClienteC apogruppo'

    My xml file is valid (I'm sure), but load fail.

    This is my command:
    "C:\dxx\bin\shr ed.exe" DBNAME filename.dad "C:\temp\filena me.xml"

    I work on PC with Win2000.

    I have increased the CLOB limit in dxxShredXML and dxxInsertXML
    following
    this steps:

    1) db2 DROP PROCEDURE db2xml.dxxShred XML


    2) db2 create procedure db2xml.dxxShred XML( in dadBuf Clob(100K),

    in XMLObj Clob(20M),

    out returnCode integer,

    out returnMsg varchar(1024))
    external name 'db2xml!dxxShre dXML'
    language C
    parameter style DB2DARI
    not deterministic
    fenced
    null call;


    but we have same results.
    [color=blue][color=green]
    >>[/color][/color]
Working...