opmnctl start fails when ORA_NLS10 parameter is set

Post author:Amit Bansal
Post published:4 April, 2010
Post category:10g
Post comments:1 Comment

I got into this issue , where in while starting Grid Control components, opmnctl command failed with following errors

./opmnctl start
globalInitNLS: NLS boot file not found or invalid
 -- default linked-in boot block used
XML parser init: error 201.
globalInitNLS: NLS boot file not found or invalid
 -- default linked-in boot block used
XML parser init: error 201.
globalInitNLS: NLS boot file not found or invalid
 -- default linked-in boot block used
XML parser init: error 201.
opmnctl: opmn start failed

On checking environment variables, I found ORA_NLS10 env variable was set. Unsetting it resolved the issue.

Tags: 10g, NLS

Amit Bansal

Experienced professional with 16 years of expertise in database technologies. In-depth knowledge of designing and implementation of Disaster Recovery / HA solutions, Database Migrations , performance tuning and creating technical solutions. Skills: Oracle,MySQL, PostgreSQL, Aurora, AWS, Redshift, Hadoop (Cloudera) , Elasticsearch, Python

This Post Has One Comment

bhallar 14 Apr 2010 Reply

I had faced the similar issue and which got resolved by unsettling the ORA_NLS10 parameter,Peoples having the same issue in with 9i with ORACLE_NLS33

http://forums.oracle.com/forums/thread.jspa?messageID=745614