Xml parser procedur which worked in oracle 8.1.7 not working in oracle 9ir2

Question

hi all,
THE BELOW PROCEDURE TO PARSE A XML WEB PAGE AND RETRIEVE THE DATA INTO TABLE IS WORKING WELL IN ORACLE 8.1.7 , BUT WHEN WE UPGRADED TO oRACLE 9I RELEASE 2 ,,ITS NOT WORKING AND GIVING THESE ERRORS,,
13:44:56 Error: ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException
ORA-06512: at "SYS.XMLNODECOVER", line 0
ORA-06512: at "SYS.XSLPROCESSOR", line 500
ORA-06512: at "XXCNA.XRATESDLOAD", line 37
ORA-06512: at line 2
CAN ANYONE GIVE A TIP?
REGARDS,
VIJAY
CREATE OR REPLACE PACKAGE BODY XRATESDLOAD AS
PROCEDURE XRATESDLOADP
IS
--DECLARE THE REQUIRED XML PARSER, DOM DOCUMENT,NODES AND NODELLISTS
v_parser xmlparser.Parser;
v_doc xmldom.DOMDocument;
v_nl xmldom.DOMNodeList;
v_n xmldom.DOMNode;
--CREATE A PL/SQL TYPE TABLE
TYPE tab_type IS TABLE OF CNA_XRATES_TEXT%ROWTYPE;
     t_tab tab_type := tab_type();
BEGIN
-- Create a parser.
v_parser := xmlparser.newParser;
-- Parse the document and create a new DOM document.
xmlparser.parse(v_parser, 'http://www.xe.com/dfs/datafeed2.cgi?cnaeuropeholdingsltd');
v_doc := xmlparser.getDocument(v_parser);
-- Free resources associated with the Parser now it is no longer needed.
xmlparser.freeParser(v_parser);
-- Get a list of all the CURRENCY nodes in the document using the XPATH syntax.
v_nl := xslprocessor.selectNodes(xmldom.makeNode(v_doc),'/xe-datafeed/currency');
dbms_output.put_line( 'Currency rates processed on '||to_char(sysdate));
--DELETE THE RECORDS IN THE CNA_XRATES_TEXT
delete from CNA_XRATES_TEXT;
dbms_output.put_line( 'Previous records of CNA_XRATES_TEXT table deleted '||to_char(sysdate));
-- Loop through the list and create a new record in a tble collection
-- for each CURRENCY record.
FOR cur_emp IN 0 .. xmldom.getLength(v_nl) - 1 LOOP
v_n := xmldom.item(v_nl, cur_emp);
t_tab.extend;
-- Use XPATH syntax to assign values to he elements of the collection.
t_tab(t_tab.last).CURRENCY_SYMBOL := xslprocessor.valueOf(v_n,'csymbol');
--t_tab(t_tab.last).CURRENCY_NAME     := xslprocessor.valueOf(v_n,'cname');
t_tab(t_tab.last).CURRENCY_RATE := xslprocessor.valueOf(v_n,'crate');
     --t_tab(t_tab.last).CURRENCY_DATE       := xslprocessor.valueOf(v_n, sysdate);
END LOOP;
-- Insert data into the real CNA_XRATES_TEXT table from the table collection.
-- Form better performance multiple collections should be used to allow
-- bulk binding using the FORALL construct but this would make the code
-- too long-winded for this example.
FOR cur_emp IN t_tab.first .. t_tab.last LOOP
INSERT INTO CNA_XRATES_TEXT
(CURRENCY_SYMBOL,
CURRENCY_RATE,
     CURRENCY_DATE)
VALUES
(t_tab(cur_emp).CURRENCY_SYMBOL,
t_tab(cur_emp).CURRENCY_RATE,
     to_char(sysdate));
END LOOP;
dbms_output.put_line( 'Currency rates inserted into CNA_XRATES_TEXT table on '||to_char(sysdate));
COMMIT;
-- Free any resources associated with the document now it
-- is no longer needed.
xmldom.freeDocument(v_doc);
END XRATESDLOADP;
END XRATESDLOAD;
/

Answer 1

Unlike Oracle 7.x, versions 8 and above now internalize the trigger you are looking for within the database itself. So you can no longer have the kind of control over this process as you would have done previously, however the performance has increased according to Oracle.
It is possible to remove these triggers in an emergency as follows:
-- if tab$.trigflag != 0 - then Oracle internal replication triggers are enabled
select * from tab$ where trigflag != 0;
-- to remove Oracle internal replication triggers if replication is not working
-- and needs to be removed in an emergency to allow writing to the tables
-- also do this as sys user
run catrepr
-- also do this as sys user
update tab$ set trigflag=0 where trigflag !=0;
commit;
shutdown immediate;
startup
However this removes all of the triggers - which is not what you want to do in your situation.
You may find some additional helpful commands in the repdoc.txt file on my website:
http://www.dotcomsolutionsinc.net/products/repgen/repgen_example_repdoc1.html
And here is a list of replication setup scripts which could be helpful as well:
http://www.dotcomsolutionsinc.net/products/repgen/repgen_files.html
What is expecially important (as I am sure you know) is the setup of conflict resolution, which I do a little bit differently than I have seen documented elsewhere in order to avoid ORA-1403 errors.
David Simpson
www.dotcomsolutionsinc.net
(Oracle Replication Consulting & Tools)