Env vars for C XML parser

Question

I have had a lot of problems with the Oracle C XML parser. I have put a question in this forum before about SEGV errors when xmlinit is called but I suspects that somthing else (very mystery thing) is the real cause to this problem.
For now is status that I always gets error 201 when I calls xmlinit. My question is therefore: I have set the ORACLE_HOME to my Oracle installation directory. Do I have to set any more env var when I use the Oracle C parser?
null

Answer 1

Yes! When we get the error code 201 from the parser are an error message displayed. It is nearly always when the function xmlinit is called.
But we do not always get this error. Sometimes do we get a SEGV signal and a core dump when xmlinit is called. Sometimes does it work perfectly. It can be different from one compilation to another and feels very mystery. I have searched for some error that can cause this in my own code but not found anything yet. My own code are relatively robust with a lot of error checks and I am not sure that it is my own code that fails but it is only my own code I have access to :)
We used the XML Parser 1.01.0.0 until the last week then we found that there are a newer version available. We are now using the version 2.0.7.0.0 instead but without more success than before.
What I have done for the parser so far is to copy the files lpxus.msb and lpxus.msg to my $ORACLE_HOME/oracore/mesg directory. I have also set the env vars ORA_NLS, ORA_NLS32 and ORA_NLS33 to my $ORACLE_HOME/ocommon/nls/admin/data directory. But I have got the parser to work without have set this env vars sometimes (and sometimes not) and I am really not sure if I have to set them as it says in the README.
We are using the parser only to parse our XML configuration file through calls to several get-function in the DOM api. The encoding for our XML file is plain US-ASCII and we have experimented with this encoding in the file (<?xml version="1.0" encoding="US-ASCII"?>) and as a param to the functions xmlinit and xmlparse. We have also tried to call this function with no coding at all (a NULL-pointer), the encoding ASCII and UTF-8 with no more success than before. We continues to more or less randomly get SEGV-error, error 201 or a working program.
The only params we gives to xmlinit is the errcode (the first param) and sometimes an error message handler function and the encoding. Never any other param.
I think this was a lot of information but I can give more to anyone who need it to help us to get the parser to work. We have spend a lot of time for this now and we'll possibly make a descision about this parser tomorrow. If we not knows that we can get it to work we have to build an another solution without this parser. But it would be a pity because I like the this parser and its apis (if it works).