XML implementation for Oracle8i

Hi,
I have been following these threads as I will be working with an
application that is using XML for the data very soon. When I
spoke to your support group they said that if I needed to use
IFS or ConText I would have to upgrade to Oracle 8.1.6.
However in your reply to Priva in Jul, 99 you said this:
"XML can be used in different ways with Oracle. You can use the
XML SQL utility to read/write XML to/from object-relational
tables/views. You can use IFS to save XML files into different
tables with user-defined mappings. You can store the XML in a
CLOB in the database and index it using ConText. You can read
more about these under http://www.oracle.com/xml page."
Can 8.1.5 handle IFS and/or ConText? Also is IFS the same thing
as iFS?
Thanks for the help.
Roger
null

Syd (guest) wrote:
: Oracle XML Team wrote:
: : Roger (guest) wrote:
: : : Hi,
: : : I have been following these threads as I will be working
with
: : an
: : : application that is using XML for the data very soon. When
I
: : : spoke to your support group they said that if I needed to
use
: : : IFS or ConText I would have to upgrade to Oracle 8.1.6.
: : : However in your reply to Priva in Jul, 99 you said this:
: : : "XML can be used in different ways with Oracle. You can
use
: : the
: : : XML SQL utility to read/write XML to/from object-
relational
: : : tables/views. You can use IFS to save XML files into
: different
: : : tables with user-defined mappings. You can store the XML
in a
: : : CLOB in the database and index it using ConText. You can
read
: : : more about these under http://www.oracle.com/xml page."
: : : Can 8.1.5 handle IFS and/or ConText? Also is IFS the same
: : thing
: : : as iFS?
: : : Thanks for the help.
: : : Roger
: : The Internet File System, iFS, is going to be released as
part
: : of 8.1.6. You will have to upgrade to 8.1.6 to use it.
8.1.5's
: : interMedia support (formerl Context) already has XML section
: : searching capability.
: : Oracle XML Team
: : http://technet.oracle.com
: : Oracle Technology Network
: Since 8.1.5 does not include the iFS, does this suggest that
: there is no "practical/automatic" way of storing XML documents
: into the 8i database? From what I understand, within the
: Oracle iFS you must "register" the XML data type and thus
: provide a "database descriptor" defining the mapping from XML
to
: the table columns & BLOBS. I am about to start a project which
: has XML at the heart of the system and I was hoping V8.1.5 had
: some significant XML storage/retrieval capabilities. Also,
when
: will 8.1.6 be GA on the Sun/Solaris?
: Thanks.
: Syd
Currently you can store XML documents in LOBs or use the XML SQL
Utility here to break it apart across a view. 8.1.6 is due out
end of 99-early 2000.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Similar Messages

  • How do I determine/set the XML implementation for WLS 6.1?

    I can't find anywhere on the console that shows or allows one to change the XML
    implementation that is used in the Weblogic Server (6.1).
    I tried putting the xml jars prior to the weblogic.jar in the classpath, but did
    not see any changes to the problem I am having (see previous post), and do not
    know how to tell if I impacted the server at all.
    Thanks,
    kEn

    Thanks.  That .cfg file shows Times Regular for the following characters, but none of these characters are the regular alphabet, (are they?) so there must be yet another place?
    mathchar.cfg    53      < plus        2b Times Regular>
    mathchar.cfg    54      < equal       3d Times Regular>
    mathchar.cfg    70      < gg          c8 Times Regular>
    mathchar.cfg    71      < ll          c7 Times Regular>
    mathchar.cfg    93      < fact        21 Times Regular>
    mathchar.cfg    94      < dagger      a0 Times Regular>
    mathchar.cfg    98      < minus       d0 Times Regular>
    mathchar.cfg    106      < uequal      3d Times Regular>
    mathchar.cfg    112      < diff        64 Times Regular>
    mathchar.cfg    116      < ucomma      2c Times Regular>
    mathchar.cfg    117      < semicolon   3b Times Regular>
    mathchar.cfg    118      < optotal     64 Times Regular>
    mathchar.cfg    127      < power       5e Times Regular>
    I've determined (by comparing equation string to body string visually) that Times is in fact the font being used.  I just don't see yet how that gets determined.  Any further thoughts?

  • Oracle8.1.5 and XML parser for PL/SQL

    Hi,
    Does XML parser for PL/SQL work with Oracle 8.1.5? Did any one install the
    same and if so what are steps to follow? I ran initjvm.sql to install
    JServer and then tried to load jar files using loadjava, but it's giving
    error. It's working fine with Oracle8.1.6.
    Any idea?
    Thanks,
    Jayanta
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jayanta Ghosh ([email protected]):
    Hi,
    Does XML parser for PL/SQL work with Oracle 8.1.5? Did any one install the
    same and if so what are steps to follow? I ran initjvm.sql to install
    JServer and then tried to load jar files using loadjava, but it's giving
    error. It's working fine with Oracle8.1.6.
    Any idea?
    Thanks,
    Jayanta<HR></BLOCKQUOTE>
    Oracle XML Parser has differents distributions for 8.1.5 and 8.1.6 databases, try the correct version, then runs the oraclexmlsqlload.csh from the lib directory of XSU distribution.
    Best regards, Marcelo.
    null

  • XML manual installation for oracle8i

    i want install xml for oracle8i.how can i install.i want step by step instructions.were can i find this documents.mention the link.

    IStall the XDK as such
    DETAILED STEPS
    How to Install the Original 8.1.7 XDK on any 8.1.7 Database Version
    These steps apply if the initxml.sql script has never been run:
    1. Log into SQL*Plus as SYS and run the following script:
    For both UNIX and Windows:
    SQL> [ORACLE_HOME]/oracore/admin/initxml.sql
    2. Run the following commands to create synonyms for PL/SQL packages that were
    not created by the above script:
    --drop public synonym xmldom;
    create public synonym xmldom for xmldom;
    --drop public synonym xmlparser;
    create public synonym xmlparser for xmlparser;
    --drop public synonym xslprocessor;
    create public synonym xslprocessor for xslprocessor;
    3. Execute the following script:
    For both UNIX and Windows:
    SQL> [ORACLE_HOME]/rdbms/admin/catxsu.sql
    Regards
    Coby D. Adams Jr.

  • ANN: Oracle XML Parser for Java v2.0.0.1

    A new maintenance release of the Oracle Parser for Java is
    available for download. It has the following fixes and changes:
    Bug fixes for #920536, i.e. Cannot access element attributes via
    XSLT; #898423. i.e. ElementDecl's in DTDs; #774774, i.e. DOM
    extensions using XSL pattern matching; #863890 i.e. SAX
    IOException not thrown.
    New APIs in the following new interface:
    1. oracle.xml.parser.v2.NSResolver
    - resolveNamespacePrefix( find the namespace definition in scope
    for a given namespace prefix )
    New APIs in the following classes:
    1. oracle.xml.parser.v2.XMLNode
    - selectNodes( Selects nodes from the tree which match the given
    pattern; client can provide an NSResolver implementation to
    resolve namespace prefixes in the pattern ).
    2. oracle.xml.parser.v2.ElementDecl
    - getParseTree( Returns the root Node of Content Model parse
    tree, which could then be traversed node by node using
    getFirstChild() and getLastChild(). The Node types are: PLUS,
    COMMA, ASTERISK, ELEMENT, QMARK ).
    This is the first beta patch release for v2.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

    unzip -l appsborg2.zip | grep 9.0.4
    0 04-18-03 20:10 .xdkjava_version_9.0.4.0.0_production
    do i still need to do that step?No, you do not have to since "XML Parser for Java v9.0.4" is already installed as part of appsborg2.zip

  • XML file for GigE Vision camera

    Hello,
    I am working on a design of GigE Vision camera. It should be very simple linescan camera. I implemented the whole required GigE Vision register set, can communicate with the camera in MAX. The problem is that I need to creata this XML file for the camera.There is this XML file here: 
    http://www.emva.org/cms/upload/Standards/GenICam_D​ownloads/SFNC_Reference_Version_2_0_0_Schema_1_1.x​...
    What should I do with it? My first version of the camera will have 2 funcions: turn it on and turn it off I am bit confused, because the xml file template has lots of functions, that I don't really need. Should I delete them? Or leave inside with default values? What does minimal configuration XML file need?
    Regards,
    Linus
    Solved!
    Go to Solution.

    linru wrote:
    Thank you very much! Perhaps I was too concentrated on digging through various documents and missed the important info.
    And one more question: how does NI software build the *.icd file? By reading XML file? Or by reading registers in my camera? 
    Both. The XML is processed by the GenApi software component which then translates it to register operations. The XML file thus controls what features are visible based both on the XML file as well as the camera registers (features in the XML may be conditionally available based on the <pIsImplemented< tag). Next, the IMAQdx ICD file contains the subset of features in the XML file that are available and are tagged as <Streamable>, meaning they can be saved to a settings file.
    Eric

  • How to specify the XML Declaration for an XML variable

    I need to set the XML declaration for my XML variable as
    follows:
    var employees:XML =
    <?xml version="1.0" encoding="utf-8"?>
    <employees>
    <employee ssn="123-123-1234">
    <name first="John" last="Doe"/>
    <address>
    <street>11 Main St.</street>
    <city>San Francisco</city>
    <state>CA</state>
    <zip>98765</zip>
    </address>
    </employee>
    <employee ssn="789-789-7890">
    <name first="Mary" last="Roe"/>
    <address>
    <street>99 Broad St.</street>
    <city>Newton</city>
    <state>MA</state>
    <zip>01234</zip>
    </address>
    </employee>
    </employees>;
    However, if I specify <?xml version="1.0"
    encoding="utf-8"?>, I get a design time and compile error. If I
    remove it it works fine. But the server to which I send this XML is
    expecting the declaration. Can somebody help me with this?
    Thanks

    I work mostly with the Java versions of the parser so you'll have to make the translation to C++. As far as I know, you can't use the SAX API to access to the encoding.
    You need to use the DOM along with Oracle's extension to the basic DOM functionality. Oracle's package, oracle.xml.parser.v2 defines a class which implements the Document interface called XMLDocument. This class has a method, getEncoding(), which returns the encoding. You would use the method in getDocument() in the Parser base class inherited by DOMParser to retrive the XMLDocument.
    Jeff

  • XML Parser for PL/SQL - charset

    Hi,
    I'm using XML Parser for PL/SQL and have some trouble with encoding of results xmldom.writeToBuffer and xmldom.writeToCLOB procedures.
    Some tags in my DOM documents contain text values in RUSSIAN (server nls_charset is CL8ISO8859P5). When I write document in varchar2 variable, buffer content is in UTF8 encoding ( convert UTF8->CL8ISO8859P5 -OK).
    xmldom.setCharset(doc, 'ISO-8859-5') just after xmldom.newDOMDocument has no effect.
    xmldom.setCharset(doc, 'CL8ISO8859P5') has no effect also.
    Explicit charset direction in third parameter of
    xmldom.writeToBuffer and xmldom.writeToCLOB procedure has no effect.
    When I write document in CLOB, and then read part of CLOB in varchar2 buffer - result contain '?' in place of all russian text characters.
    What's a problem?
    How can I force XML Parser write XML in server charset?
    Platform:
    Oracle8i Enterprise Edition Release 8.1.6.1.0
    JServer Release 8.1.6.1.0
    Oracle XML Parser for PL/SQL v 1.0.2

    I have the same problem. But in my case I am allowed only to use XML Parser for PL/SQL.
    Characterset 'WE8ISO8859P1' is used. And the language is latvian.
    After parsing a XML document and printing its contents, all latvian characters are replaced by "f".
    xmldom.setcharset(doc,'WE8ISO8859P1') has no effect.

  • Efficient searching in a large XML file for specific elements

    Hi
    How can I search in a large XML file for a specific element efficiently (fast and memory savvy?) I have a large (approximately 32MB with about 140,000 main elements) XML file and I have to search through it for specific elements. What stable and production-ready open source tools are available for such tasks? I think PDOM is a solution but I can't find any well-known and stable implementations on the web.
    Thanks in advance,
    Behrang Saeedzadeh.

    The problem with DOM parsers is that the whole document needs to be parsed!
    So with large documents this uses up a lot of memory.
    I suggest you look at sometthing like a pull parser (Piccolo or MPX1) which is a fast parser that is program driven and not event driven like SAX. This has the advantage of not needing to remember your state between events.
    I have used Piccolo to extract events from large xml based log files.
    Carl.

  • Error in Sun XML schema for servlet2.4 deployment descriptor?

    Hi,
    I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
    When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
    This error is on line 744, and is caused by the snippet:
    <xsd:simpleContent>
    <xsd:extension base="j2ee:nonEmptyStringType"/>
    </xsd:simpleContent>
    Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

    XMLSpy is known to be flawed. From my own experience of implementing
    validators and data-binding tools, and from my experience of working in the
    W3C Schema working group, I can tell you that there are countless cases
    where XMLSpy violates the schema specification.
    I checked the corresponding part of the schema, but it looks correct to me.
    So I suspect that this is another bug in XMLSpy.
    Try Xerces. That's probably the best in terms of conformance to the spec.

  • How to trigger XML messages for FWO

    Hello Experts,
    I’d like to trigger a XML outbound message after creation of an air forwarding order (FWO) in my TM system. It could not be a confirmation. I need this XML to provide the results of charges calculation in a legacy system (B2B communication).
    Could someone help me in this?
    Regards,
    Alberto.

    Dear Alberto,
    You can follow below steps to achive the same.
    1 You have to setup PPF framework.
    A. You will be having output profile (which is for processing the actions in background) assigned to Air FWO document type.
    B.Go to PPF customizing (Tcode - SPPFCADM) -> Select the Action profile -> Create Action definition ->choose the processing time as 'Processing when saving the document'-> processing type as 'Method call' -> Create the BADI implementation for definition EXEC_METHODCALL_PPF''. Here you can check if any filter before you trigger XML Message.
    2.You have to create a custom Proxy and proxy class to generate the XML message and send to target system.
    You will call this proxy class in BADI implementation EXEC_METHODCALL_PPF and build the XML message with required Charges data.
    After all the setup is done, you can test and make sure you have XML message generated in SXI_MONITOR / SXMB_MONI t-code.
    Let me know any challenges while doing it.
    Thanks,
    Bharath.

  • XML Parser for PLSQL and BIG5/UTF-8

    I'm trying store data in traditional chinese submitted by IE5 (through oXMLHttpRequest.send() and javascript), I tried both 'encoding="BIG5"' and 'encoding="UTF-8"'.
    It seems that the parser ignore all characters that are not ascii regardless of their encoding.
    Any thoughts will be much appreciated
    procedure UpdateXMLProc(xmlSrc varchar2)
    is
    p xmlparser.parser;
    doc xmldom.DOMDocument;
    nlist xmldom.DOMNodeList;
    list_len pls_integer;
    node1 xmldom.DOMNode;
    node2 xmldom.DOMNode;
    node3 xmldom.DOMNode;
    begin
    p := xmlparser.newParser;
    xmlparser.parseBuffer(p, xmlSrc);
    doc := xmlparser.getDocument(p);
    nlist := xmldom.getElementsByTagName(doc, 'ROW');
    list_len := xmldom.getLength(nlist);
    -- loop through elements
    for j in 0..list_len-1 loop
    node1 := xmldom.item(nlist, j);
    -- get primary key values
    node2 := xmldom.getFirstChild(node1);
    loop
    -- get the text node and if not null get value
    node3 := xmldom.getFirstChild(node2);
    if not xmldom.isNull(node3) then
    -- THIS OUTPUT MAY ALTER CHARACTER IF IT'S NOT ASCII
    htp.p(xmldom.getNodeValue(node3));
    end if;
    -- get next field
    node2 := xmldom.getNextSibling(node2);
    exit when (xmldom.isNull(node2));
    end loop;
    end loop;
    -- THIS OUTPUT WILL BE IN THE SAME ENCODING AS THE ORIGINAL
    htp.p(xmlSrc);
    end;
    null

    I just ran the initjvm.sql,initdbj.sql and
    initsqlj.sql.
    Still getting the error.
    Please help!!!!
    Thanks
    Jay
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jay ([email protected]):
    I have Oracle8i Release 8.1.5.0.0 - ProductionWith the Java option
    PL/SQL Release 8.1.5.0.0 - Production version
    runnig in sun sparc server.
    While I am loading Oracle XML Parser for PLSQL(using plxmlparser_V1_0_1.tar.gz) have a problem. When I try to load the xmlparser.jar class and I get the
    following messages:
    initialization complete
    Error while accessing MD5 table
    ORA-00942: table or view does not exist
    loading : org/w3c/dom/DOMImplementation
    Error while loading org/w3c/dom/DOMImplementation
    ORA-04068: existing state of packages has been discarded
    ORA-04063: package body "TEST.LOADLOBS" has errors
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1
    creating : org/w3c/dom/DOMImplementation
    Error while creating class org/w3c/dom/DOMImplementation
    ORA-00406: COMPATIBLE parameter needs to be 8.1.0.0.0 or greater
    Error while accessing MD5 table
    ORA-00942: table or view does not exist
    loading : org/w3c/dom/html/HTMLDivElement
    Error while loading org/w3c/dom/html/HTMLDivElement
    ORA-04068: existing state of packages has been discarded
    ORA-04063: package body "TEST.LOADLOBS" has errors
    ORA-06508: PL/SQL: could not find program unit being called
    and so on.
    Could anyone please tell me if I need to do any pre-installation steps.
    Thanks
    Jay<HR></BLOCKQUOTE>
    null

  • XML parser for C 2.0.4

    Can someone from the Oracle xmlteam for the C parser please look at OTN Technical discussion XML parser for C 2.0.2 - LPX-00208 in the OTN XML Discussions? The last part of it is about 2.0.4.
    Thanks!
    John Butler

    1. I installed my own memory handlers once and now I see that it keeps on allocating memory in block like this:
    104016
    65552
    65552
    65552
    65552
    65552
    until a total of: 275 MB !!
    This memory is freed when xmlterm() is called.
    2. It complains about 'The procedure entry point slpupath could not be located in the dynamic link library oracore8.dll' when I try with the 8.1.6 DLL's...
    And since Oracle8.1.7 is not out yet for NT, this is a problem...

  • ANN: Oracle XML Parser for Java v2.0.2

    The new version of the Oracle XML Parser for Java v2 is
    available for download and has the following features and
    changes:
    1. Conformance to the XSLT/XPATH August WD.
    Note that there are several changes between April99 XSLT draft
    and the August99 XSLT/Xpath draft and these changes have been
    implemented in the XSL Processor. The XSL Processor has been
    modified to accept XPath syntax for expressions and patterns.
    Stylesheets might have to be modified to be conformant to the
    August XSLT/XPath draft before they can be used with this
    release.
    Some of the changes between April draft and the August draft
    are:
    a. Expressions in the stylesheet must match the XPath
    production Expr.
    b. Some of the attribute names and element names in XSL
    namespace have changed.
    c. Some new functions have been added to XPath CORE function
    library.
    Please refer to the August XSLT/XPath draft for more details.
    This is the first production release for v2.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

    The link has been fixed. You will go to the v2 download page
    now. Sorry for the inconvience.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    Renilton Oliveira (guest) wrote:
    : I didn't find the file for version 2.0.0.0 as well.
    : Renilton
    : Andrei Filimonov (guest) wrote:
    : : I tried to download XML Parser for Java v2 it seems that
    only
    : v
    : : 1.0.1.4 is available. Could you please give an exact URL for
    : v2
    : : download?
    : : Andrei Filimonov
    : : Oracle XML Team wrote:
    : : : The Oracle XML v2 parser is now available for download
    here
    : as
    : : : an early beta release and is written in Java. It features
    : an
    : : : improved architecture over the Oracle XML v1 parser and
    has
    : : : shown better performance on small to large XML documents.
    : It
    : : : will also be able to format the XML document according to
    a
    : : : stylesheet, having integrated an XSLT processor.
    : : : Version 2 of the XML Parser for Java, besides
    incorporating
    : an
    : : : XSLT processor, has been re-architected from version 1.
    This
    : : has
    : : : resulted in a number of changes to the class names
    : especially
    : : : those that support Namespaces. See v2changes.txt and
    : the .diff
    : : : difference files in the sample directory.
    : : : Oracle XML Team
    : : : http://technet.oracle.com
    : : : Oracle Technology Network
    null

  • How to parse an XML document with oracle8i

    Has anyone a good link or an example how to decode and store an XML document into an oracle8i database.
    I' ve found only good things for oracle9i.
    Thank you
    Roger

    Here is an example of parsing xml taken fro Oracle8i 8.1.7 xdk.
    This one uses external OS files to pase, but could be easily converted to
    use CLOB or VARCHAR2 string for parsing XML documents.
    IF you wanted to use CLOB to store and manipulate xml documents you can use XMLParser and XMLDom
    packages along with the DBMS_LOB package to do that.
    -- This file demonstates a simple use of the parser and DOM API.
    -- The XML file that is given to the application is parsed and the
    -- elements and attributes in the document are printed.
    -- The use of setting the parser options is demonstrated.
    set serveroutput on;
    create or replace procedure domsample(dir varchar2, inpfile varchar2,
    errfile varchar2) is
    p xmlparser.parser;
    doc xmldom.DOMDocument;
    -- prints elements in a document
    procedure printElements(doc xmldom.DOMDocument) is
    nl xmldom.DOMNodeList;
    len number;
    n xmldom.DOMNode;
    begin
    -- get all elements
    nl := xmldom.getElementsByTagName(doc, '*');
    len := xmldom.getLength(nl);
    -- loop through elements
    for i in 0..len-1 loop
    n := xmldom.item(nl, i);
    dbms_output.put(xmldom.getNodeName(n) || ' ');
    end loop;
    dbms_output.put_line('');
    end printElements;
    -- prints the attributes of each element in a document
    procedure printElementAttributes(doc xmldom.DOMDocument) is
    nl xmldom.DOMNodeList;
    len1 number;
    len2 number;
    n xmldom.DOMNode;
    e xmldom.DOMElement;
    nnm xmldom.DOMNamedNodeMap;
    attrname varchar2(100);
    attrval varchar2(100);
    begin
    -- get all elements
    nl := xmldom.getElementsByTagName(doc, '*');
    len1 := xmldom.getLength(nl);
    -- loop through elements
    for j in 0..len1-1 loop
    n := xmldom.item(nl, j);
    e := xmldom.makeElement(n);
    dbms_output.put_line(xmldom.getTagName(e) || ':');
    -- get all attributes of element
    nnm := xmldom.getAttributes(n);
    if (xmldom.isNull(nnm) = FALSE) then
    len2 := xmldom.getLength(nnm);
    -- loop through attributes
    for i in 0..len2-1 loop
    n := xmldom.item(nnm, i);
    attrname := xmldom.getNodeName(n);
    attrval := xmldom.getNodeValue(n);
    dbms_output.put(' ' || attrname || ' = ' || attrval);
    end loop;
    dbms_output.put_line('');
    end if;
    end loop;
    end printElementAttributes;
    begin
    -- new parser
    p := xmlparser.newParser;
    -- set some characteristics
    xmlparser.setValidationMode(p, FALSE);
    xmlparser.setErrorLog(p, dir || '/' || errfile);
    xmlparser.setBaseDir(p, dir);
    -- parse input file
    xmlparser.parse(p, dir || '/' || inpfile);
    -- get document
    doc := xmlparser.getDocument(p);
    -- Print document elements
    dbms_output.put('The elements are: ');
    printElements(doc);
    -- Print document element attributes
    dbms_output.put_line('The attributes of each element are: ');
    printElementAttributes(doc);
    -- deal with exceptions
    exception
    when xmldom.INDEX_SIZE_ERR then
    raise_application_error(-20120, 'Index Size error');
    when xmldom.DOMSTRING_SIZE_ERR then
    raise_application_error(-20120, 'String Size error');
    when xmldom.HIERARCHY_REQUEST_ERR then
    raise_application_error(-20120, 'Hierarchy request error');
    when xmldom.WRONG_DOCUMENT_ERR then
    raise_application_error(-20120, 'Wrong doc error');
    when xmldom.INVALID_CHARACTER_ERR then
    raise_application_error(-20120, 'Invalid Char error');
    when xmldom.NO_DATA_ALLOWED_ERR then
    raise_application_error(-20120, 'Nod data allowed error');
    when xmldom.NO_MODIFICATION_ALLOWED_ERR then
    raise_application_error(-20120, 'No mod allowed error');
    when xmldom.NOT_FOUND_ERR then
    raise_application_error(-20120, 'Not found error');
    when xmldom.NOT_SUPPORTED_ERR then
    raise_application_error(-20120, 'Not supported error');
    when xmldom.INUSE_ATTRIBUTE_ERR then
    raise_application_error(-20120, 'In use attr error');
    end domsample;
    show errors;

Maybe you are looking for