The thing that is probably throwing an error is the NLS_CHARACTERSET. Here are my parameters from a properly configured instance:
PARAMETER VALUE ------------------------ ---------------------------- NLS_LANGUAGE AMERICAN NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS ., NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-RR NLS_DATE_LANGUAGE AMERICAN NLS_CHARACTERSET AL32UTF8 NLS_SORT BINARY NLS_TIME_FORMAT HH.MI.SSXFF AM NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR NLS_DUAL_CURRENCY $ NLS_NCHAR_CHARACTERSET UTF8 NLS_COMP BINARY NLS_LENGTH_SEMANTICS BYTE NLS_NCHAR_CONV_EXCP FALSE On Tue, Jul 6, 2010 at 8:05 PM, Axton <[email protected]> wrote: > LANG and NLS_LANG should definitely be set. NLS_LANG tells the Oracle > client how to encode/decode the data sent to and from the db. The product > documentation covers the proper settings. > > On Tue, Jul 6, 2010 at 7:28 PM, Fatima <[email protected]> wrote: > >> ** Hi everyone, >> We are upgrading from ARS 6.3 on: >> - Solaris 10 >> - Oracle 9i >> - Apache Tomcat 5.5.26 >> to ARS 7.5 on: >> - Solaris 10 >> - Oracle 10g >> - Apache Tomcat 5.5.29 >> >> The Oracle upgrade from 9i to 10g went fine. We upgraded ARS 6.3 to ARS >> 7.1 fine. >> With the ARS 7.5 patch 5 installer, we get an error indicating that our >> underlying database is not Unicode but ARS is configured as Unicode. >> Although our database is Unicode, our NLS Parameters are as follows: >> >> SQL> SELECT * FROM V$NLS_PARAMETERS; >> >> PARAMETER VALUE >> ---------------------------------------------------------------- >> ---------------------------------------------------------------- >> NLS_LANGUAGE AMERICAN >> NLS_TERRITORY AMERICA >> NLS_CURRENCY $ >> NLS_ISO_CURRENCY AMERICA >> NLS_NUMERIC_CHARACTERS ., >> NLS_CALENDAR GREGORIAN >> NLS_DATE_FORMAT DD-MON-RR >> NLS_DATE_LANGUAGE AMERICAN >> NLS_CHARACTERSET >> AR8ISO8859P6 >> NLS_SORT BINARY >> NLS_TIME_FORMAT >> HH.MI.SSXFF AM >> NLS_TIMESTAMP_FORMAT DD-MON-RR >> HH.MI.SSXFF AM >> NLS_TIME_TZ_FORMAT >> HH.MI.SSXFF AM TZR >> NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR >> HH.MI.SSXFF AM TZR >> NLS_DUAL_CURRENCY $ >> NLS_NCHAR_CHARACTERSET AL16UTF16 >> NLS_COMP BINARY >> NLS_LENGTH_SEMANTICS BYTE >> NLS_NCHAR_CONV_EXCP FALSE >> >> Does anyone know exactly which parameters does the installer check to know >> if the database is Unicode or not, so we can ensure they are set correctly. >> The OS LANG and NLS_LANG parameters are not set, do they need to be set to >> any specific value? >> >> The weird thing is that the ARS 7.5 patch 3 installer runs smoothly >> without this error, but we prefer to go to patch 5. >> >> Thanks, >> Fatima Amin >> _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
