On our windows box we found that applying the following change to the
registry fixed our issues. Don't know if it is applicable, but we were
seeing similar errors when this got out of whack.
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraClient10g\NSL_LANG=AMERICAN_AM
ERICA.AL32UTF8
~Jim
Thanks Mark.
As you mentioned, It appears to be related to the known issue with the
Oracle Client 10.2.0.4 as documented in SW00333862. Though the article
offers a workaround, in our case, a decision was made to downgrade the
client back to 10.2.0.1, which was on our original build and is
Hi Listers,
We are having issues getting arserver to successfully start after having
patched the Oracle Client to level 10.2.0.4. Has anybody experienced any
issues in this area? The error message we are seeing on startup are:
Thu Mar 11 12:38:41 2010 390600 : Missing data in the SQL
Check to see if your server can ping the database server by name. I had
a similar issue after a client change but was evident in AIE because I
was using the FQDN (which had always worked and was still working on
another server), I changed to the short db name and connected no
problem.
From:
Do you have some localised views of this form installed on Unicode server? If
so it sounds like defect SW00333862. Try the following workaround;
*) start the server with the older client and open the
SRS:ServiceRequestConsole form in the admin tool.
*) Save the background graphic image from
5 matches
Mail list logo
