[DB-SIG] ORA-12705: Cannot access NLS data files or invalid environment specified

Wong Wah Meng-R32813 R32813 at freescale.com
Thu Mar 10 10:48:06 CET 2011

Thanks Dieter. Yeah I logged a ticket to Oracle and wait for their support to advise me what went wrong. The original guess on ORA_NLS33 could be the culprit is wrong as we managed to find the right folder to set the parameter, the problem still exists. 

I will give an update here after working with Oracle. Thanks!

Wah Meng  

-----Original Message-----
From: Dieter Maurer [mailto:dieter at handshake.de] 
Sent: Thursday, March 10, 2011 4:53 PM
To: Wong Wah Meng-R32813
Cc: db-sig at python.org
Subject: Re: [DB-SIG] ORA-12705: Cannot access NLS data files or invalid environment specified

Wong Wah Meng-R32813 wrote at 2011-3-8 10:16 +0000:
>My oracledb module on HP-UX is unable to connect to database when I export environment variable NLS_LANG="SIMPLIFIED CHINESE_CHINA.ZHS16GBK". There is no issue when such environment variable is exported and the SQLPLUS is issued. The DBA determined that this is an application error. Does anyone know this might be related to the some national language library not properly installed on the server? I noticed that there is no $ORACLE_HOME/ocommon folder on my server where Oracle installed is 11g, and I googled that environemnt variable ORA_NLS33 by default is pointing to $ORACLE_HOME/ocommon/nls/admin/data. Or ORA_NLS33 is no longer in use for Oracle 11g?
>$ python
>Python 1.5.2 (#9, May 23 2000, 14:18:02) [C] on hp-uxB Copyright 
>1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>>> import oracledb
>>>> a=oracledb.oracledb("gen812ora8/gen812db1ora8 at DB1ORA9")
>Traceback (innermost last):
>  File "<stdin>", line 1, in ?
>OracleDbError: LOGON caused a ORA-12705: Cannot access NLS data files 
>or invalid environment specified

I would check the Oracle documentation for error "ORA-12705"
to get indications what can cause this error.

The message indicates that the problem is with the NLS files during "LOGON".
I suppose it is a server problem (but I am not sure). In this case, you may find something relevant in the server log files.

Unfortunately, Oracle error messages are (following the Microsoft example) often less specific than they should and could be:
ideally, they would tell which files or directory could not be accessed.
Maybe, the Oracle documentation helps you to fill the holes left by the error messages.


More information about the DB-SIG mailing list