Path: news.easynews.com!core-easynews!newsfeed1.easynews.com!easynews.com!easynews!newsfeed1.earthlink.net!elnk-nf2-pas!newsfeed.earthlink.net!newshub.sdsu.edu!headwall.stanford.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: mhaggerty@mbda.gov (Michael Haggerty) Newsgroups: comp.databases.oracle.misc Subject: Re: Oracle XML Parser Problems Date: 6 Jun 2003 08:51:06 -0700 Organization: http://groups.google.com/ Lines: 159 Message-ID: References: <0poDa.68414$g92.1559969@news2.tin.it> NNTP-Posting-Host: 63.77.249.85 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1054914667 25982 127.0.0.1 (6 Jun 2003 15:51:07 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 6 Jun 2003 15:51:07 GMT Xref: core-easynews comp.databases.oracle.misc:98447 X-Received-Date: Fri, 06 Jun 2003 08:50:23 MST (news.easynews.com) Flavio; Thanks! That did the trick. Of course, now I am onto the next error: ------------- The following error has occurred: ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException ORA-06512: at "SYS.XMLPARSERCOVER", line 0 ORA-06512: at "SYS.XMLPARSER", line 91 ORA-06512: at "MHAGGERTY.CHECKXMLINCLOB", line 17 ORA-06512: at line 11 ------------- Looks like the fun never ends. Any ideas? M "FC" wrote in message news:<0poDa.68414$g92.1559969@news2.tin.it>... > "Michael Haggerty" wrote in message > news:a83d9e3a.0306040631.2033bf21@posting.google.com... > > Flavio; > > > > Thank you for your message. The query revealed xmlparsercover is not > > present within Oracle. > > > > My question now becomes how do I go about resolving this? I followed > > the instructions provided by Oracle for installing both the XML Parser > > and the JVM to the letter and am very surprised to find something is > > not present. I am assuming XMLparsercover is part of the XDK install, > > is there a way of going back and auditing this somehow? > > > > Thanks again, your explanation was very helpful. > > > > M > > > > Good, at least the problem was found out. > Oracle 'forgot' to include installation instructions for version 8.1.7, but > I bought a book where they are provided. > I guess if this is standard practice to increase sales of books... > > However you can try to follow the instructions included in a README file > provided with version 9.2, they said the instructions were in the release > notes under the lib directory, but they are actually in a README under the > plsql demo directory, there must be some genius looking after the docs at > Oracle. > > The instructions for version 9.2 seem nearly identical to the printed > version I read on my book, may be some files have been relocated, I just > gave a cursory read at the document, for sure they changed the name of a > script from load.sql to xmlload.sql, everything else looks the same. > > here is the original README document from Oracle, I just stripped out the > text where it talks about running the demo programs: > ----------------------------------------------------------------------- > This directory contains two sample XML applications: domsample and xslsample > > which show how to use the Oracle XML parser for PL/SQL. > > To run these sample programs: > > 1) Load the PL/SQL parser into the database > > You would need to to load the two jar files xmlparserv2.jar and > > xmlplsql.jar by running the 'loadjava' command line tool (located > > typically under $ORACLE_HOME/bin) . These files contain Java classes > > used by the PLSQL XML parser. > > For example, a user 'scott' with password 'tiger' could invoked by > > loadjava from the command line to upload his Java classes in (say) > > scott.jar as follows: > > % loadjava -user scott/tiger -r -v scott.jar > > xmlparserv2.jar and xmlplsql.jar must be uploaded into the database > > using the following sequence of commands: > > % loadjava -user scott/tiger -r -v xmlparserv2.jar > > % loadjava -user scott/tiger -r -v xmlplsql.jar > > Typically, loadjava would output messages containing. > > loading: > > creating: > > resolving: > > If loadjava fails issuing a 'Class not found' error, try unsetting > > the CLASSPATH environment variable. If other failures occur, please > > contact Oracle support to resolve the issue. > > The plsql files located in the $ORACLE_HOME/xdk/admin directory > > need to be loaded into the database as stored procedures. To this, > > first startup SQL*Plus (located typically under $ORACLE_HOME/bin), > > connecting as the same user you used to load the jar files, in the sql > > directory: > > % cd $ORACLE_HOME/xdk/admin > > % sqlplus scott/tiger > > SQL*Plus should come up without any errors. If it does not, please contact > > Oracle support to resolve the issue. > > Then, execute the script xmlload.sql > > SQL>@xmlload > > This will load all the sql files needed by the PLSQL XML parser. > > 2) It is necessary for the user running these samples to have been granted > the > > appropriate java security privileges to read and write from a file on the > > file system. To this, first startup SQL*Plus (located typically under > > $ORACLE_HOME/bin) and connect as a user with admin privileges: > > % sqlplus > > SQL> connect / as sysdba > > > You then need to give special privileges to the user running this sample > > (must be the same one under which you loaded the jar files and plsql files > > in step 1). > > For example, for user 'scott': > > SQL> grant javauserpriv to scott; > > SQL> grant javasyspriv to scott; > > You should see two messages that say "Grant succeeded." > > Now, connect again as the user under which the PL/SQL parser was loaded in > > step 1). > > ... omitted text concerning demo programs