Re: NLS message catalog access error

  I have no experience with either Oracle or DDE, but have seen other occurences of similar NLS message catalog errors.

  It would be nice if you could somehow find the path and filename of the relevant message catalog, i.e. strings(1) and grep(1) things for pointers to a message catalog. The pathname will probably have "nls" in it and the message catalog filename will probably end in ".cat". Once you have found the .cat file, you can use the dumpmsg(1) command to convert it to normal ASCII text and you will probably find that the message catalog indeed has no set 3 or no message id 1 in that set. In 'my' case the version of the message catalog did not match with the version of the software which was referencing it (caused by incorrectly installing a patch).

Charley Hudson (chudson_at_compuserve.com) wrote:
> I am getting the following error message while debugging my
> multithreaded Oracle 8.0.6 Pro*C application under DDE on HPUX 10.20:

> ?(dde/catgets) NLS message catalog access error.
> -- catalog: invalid catalog id, set id = 3, message id = 1

> This error occurs attempting to connect to an Oracle database after a
> call to the Oracle Pro*C routine sqlcxt.

> I am able to connect to Oracle successfully with SQL*Plus and other apps
> that connect to Oracle with Pro*C.

> Can anyone explain what might be going wrong here? My interpretation of
> the error message is that something has called catgets with an invalid
> catalog descriptor (first arg to catgets). If so, would this indicate
> that a required message catalog file is missing ?

> Thanks,
> Charley Hudson
> JDA Software, Inc.
Received on Thu Nov 25 1999 - 09:01:37 CST