On Sep 12, 2008, at 5:18 AM, [EMAIL PROTECTED] wrote:
I would first check you NLS settings me thinks this is what is
causeing
the problems and see if you can get 1.17 working with then the later
DBD::Oracles will work.
More detailed information on my NLS settings, this is the standard
default:
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8MSWIN1252
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
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_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 11.1.0.6.0
The linked RDB system is this:
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_DATE_LANGUAGE AMERICAN
NLS_DATE_FORMAT DD-MON-YY
NLS_CHARACTERSET US7ASCII
NLS_SORT BINARY
NLS_CALENDAR GREGORIAN
NLS_NCHAR_CHARACTERSET US7ASCII
Only difference is the NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET,
but none of this involves anything unusual in the characters sets I
believe, it's all ascii data.
--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group
Institutions do not have opinions, merely customs
