ORA-12705: invalid or unknown NLS parameter valuespecified

[Former Member]

Hi

We just upgraded Oracle upgrade in BW landscpae without any problem. Now I'm in the process to upgrade Oracle from 92050 to 10.2.x. for XI landscpae. Here XI is running on HP-Unix and brtools and sapkernel version is 6.40. and Oracle client software version is 92050.

As per databse upgrade guide of Oracle 10g, I upgraded the dboraslib, brtools and SAP kernel (disp+work). After that i upgraded the oracle client software to 92080.

I restarted the server. Now when i executung jobs in DB13 or when i'm creating a new tablespace, it failed with "ORA-12705: invalid or unknown NLS parameter valuespecified".

I perfored the same steps in BW upgrade and this problem has not occured. I checked the env variable of orasid and sidadm. It seem to be fine.

Any reason for this problem?

Regards

Amar

[Former Member]

Hi,

because you are using 10.2.0 as database version, you must import brtools 7.00.

if you want to use brtools 6.40 with 10h you need to set the variable

BR_ORA_NLS33 to /oracle/client/92x_64/ocomon/nls/admin/data.

can you send your env for sidadm

Thanks

[Former Member]

Hello Ahmed

Thanks for your reply. Right now, i'm just doing preparation step for oracle upgrade. Oracle has not been yet upgraded to 10.2.x. Databse is still 92050. I just upgraded the dboraslib, sap kernel and oracle client as per database upgrade guide. When i execute "R3trans -x", it work fine. there is no error messgae.

Following is the env variable for our server for sidadm:

SAPSYSTEMNAME=XDV

DIR_LIBRARY=/usr/sap/XDV/SYS/exe/run

SHLIB_PATH=/usr/sap/XDV/SYS/exe/run:/usr/sap/XDV/SYS/exe/runU

JAVA_HOME=/opt/java1.4

THREAD=NOPS

dbms_type=ORA

dbs_ora_tnsname=XDV

dbs_ora_schema=SAPXDV

ORACLE_PSRV=XDV

ORACLE_SID=XDV

DB_SID=XDV

ORACLE_HOME=/oracle/XDV/920_64

ORACLE_BASE=/oracle

ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data

NLS_LANG=AMERICAN_AMERICA.UTF8

SAPDATA_HOME=/oracle/XDV

rx2n0v4:xdvadm 8>

Thanks once again.

Amar

[Former Member]

Hi,

ok put then BR_ORA_NLS33 to NLS files for 9.2.0.5 as brtools use ORA_NLS33 which point to 9.2.0.8 you upgraded.

BR_ORA_NLS33 = /oracle/SID/920_64/ocommon/nls/admin/data

Let me know

Thanks

[Former Member]

and once you upgrade to 10g, import brtools 7.00 and unset the variable....

[Former Member]

As per oss note 592657 (step 10), i have added the following in my sidadm env:

BR_ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data

and it fixed our problem. Not sure this is the right way to fix problem as i have never used this env in past but following oss note also recommended to use this parameter.

As per oss note 651797, the BR tools may fail with an ORA-12705. If this happens, set the environment variable BR_ORA_NLS33 to notify the BR tools about the location of the NLS files to be used:

BR_ORA_NLS33 = /oracle/client/92x_<bits>/ocommon/nls/admin/data

Otherwise, the BR tools will use the NLS files on $ORACLE_HOME, which may be incompatible with the libraries used on oracle/client/92x_<bits>.

As per oss note 539922, Consequently, an Oracle client with a lower patch level than the server is always used - in particular, this means that the version of the Oracle Client Library used cannot be greater than the version of the NLS files that are used.

In our server, oracle client version is new one and version of NLS files in $oracle_home is older..

Regards

Amar

[Former Member]

As i mentioned in my last message that i updated the env variable of

SIDADM and it solve ORA-12705.

I have not added the following to ORASID

BR_ORA_NLS33 = /oracle/client/92x_<bits>/ocommon/nls/admin/data and it

give me the same error message when i try to extend the tablespace with

brtools.Here i used ORASID to run brtools...

###############################################################################

BR1001I BRSPACE 6.40 (45)

BR1002I Start of BRSPACE processing: sdweqkon.tse 2007-09-19 22.04.17

BR0484I BRSPACE log file: /oracle/XDV/sapreorg/sdweqkon.tse

BR0280I BRSPACE time stamp: 2007-09-19 22.04.17

BR0301E SQL error -12705 at location BrDbaConnect-2

ORA-12705: invalid or unknown NLS parameter value specified

BR0310E Connect to database instance XDV failed

BR0700E Fatal errors occurred - terminating processing...

BR0280I BRSPACE time stamp: 2007-09-19 22.04.17

BR0301W SQL error -12705 at location BrDbaConnect-2

ORA-12705: invalid or unknown NLS parameter value specified

BR0310W Connect to database instance XDV failed

BR1008I End of BRSPACE processing: sdweqkon.tse 2007-09-19 22.04.17

BR0280I BRSPACE time stamp: 2007-09-19 22.04.17

BR1007I BRSPACE terminated with errors

###############################################################################

do i need to add the same env variable in ORASID? I'm not sure wether orasid or sidadm is the right user to run brtools...Pls confirm.

[Former Member]

Hi Amarjit,

Not BR_ORA_NLS33, but only ORA_NLS33 = /oracle/client/92x_64/ocommon/nls/admin/data for <sid>adm user, and ORA_NLS10 for ora<sid> user.

And download the new ora dll. (also upgrade your kernel to the lastest level)

Regards,

Fendi Suyanto

[Former Member]

Forgot one thing.

Please install the Oracle client 10 and add /oracle/client/10x_64/instantclient in

SHLIB_PATH also.

Hope this can solve your problem, (last time its solve my problem)

Regards,

Fendi Suyanto

[Former Member]

Hi,

ORA_NLS33 is used for NLS messages. if there is a lot of oracle 9i installations in your system. you need to set BR_ORA_NLS33 to avoid BLS problems. it is just a workaround. as you have 9.2.0.8 client and 9.2.0.5 database software.

you have to set it sidadm and orasid env

Thanks

[Former Member]

Hi Ahmed

I upgraded the oracle. All post processing steps has been completed. Now when i start the server with startsap, it is failing with "Can not find executable sqlplus". Samethinh happen if i shutdown the sap with stopsap command.

I'm able to start the server with sqlplus "/as sysdba" and after that startsap work.

Any reason for this error?

[Former Member]

Solved. It was the env variable problem of SIDADM.