Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBD-ORACLE (ORA-12705: NLS parameter value problem)

Status
Not open for further replies.

sloppyhack

Technical User
Apr 17, 2001
111
US
I've been connecting to an oracle database via Perl for years. I updated my DBD-Oracle driver to the most current one and now I keep getting error "ORA-12705: invalid or unknown NLS parameter value" and it wont make the connection.

The only NLS value that I'm seeing on the machine I'm connecting from is NLS_LANG. I've tried setting that to AMERICAN_AMERICA.WE8ISO8859P1 and AMERICAN_AMERICA.WE8MSWIN1252 and 'NA' with no results. I have a seperate older machine that can connect and I've tried to mimic the NLS_LANG settings on that machine but I still get the same errors. It must be something with that new DBD-Oracle driver. The machine I'm now having the problems on is using Oracle 9i but the last DBD-Oracle driver worked just fine with that version so no idea why the new version wouldn't. I doubt it's a compatability problem.

Anyone else had similar problems...or can anyone suggest a fix? I've tried just about everything I know to do other than switch back to an older version of the DBD-Oracle driver. Any help or suggestions would be greatly appreciated.

Cheers,

Sloppyhack
 
SUGGESTION:
Go with what you KNOW works, until you have time to sort out the problem, Friday evenings aren't for this ;-)

Spend an hour a week on CPAN, helps cure all known programming ailments ;-)
 
Yeah. It's usually a silly little problem. If I can't find the solution within the next day or so...I'll revert everything back to older versions and hope that fixes things. Seems like someone would have come across this before.

Cheers,

Sloppyhack
 
OK. It's fixed. We're thinking it was something on the db server side that was screwed up. A server restart fixed the problem.

Cheers,

Sloppyhack
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top