Re: why ora1801
From: haomiao <miaohaoz_at_ustc.edu>
Date: Fri, 4 Jul 2008 17:16:13 -0700 (PDT)
Message-ID: <d486028d-7eed-4b48-b881-1fb9968e9627@f36g2000hsa.googlegroups.com>
Date: Fri, 4 Jul 2008 17:16:13 -0700 (PDT)
Message-ID: <d486028d-7eed-4b48-b881-1fb9968e9627@f36g2000hsa.googlegroups.com>
> The two systems could have different NLS_DATE_FORMAT ;
> ignoring the fact each piece mentioned above is unsupported.
the NLS_DATE_FORMAT in both systems is same
YYYYMMSSHH24MISS
both in unix enviroment and oracle session parameter.
If I change the tbl_txn_mon_t.sa_comm_date to 81, ora-1801 disappear. So ora1801 in my sco system should be result of the wrong length of tbl_txn_mon_t.sa_comm_date.
Why oracle not report 1801, instead of "the sa_comm_date is too
short"?
And why Aix not report 1801?
Received on Fri Jul 04 2008 - 19:16:13 CDT