ok i brought it in as varchar and cast as date.
On Sun, Mar 22, 2009 at 12:27 PM, zach cruise <zachc1980@gmail.com> wrote:
> On Sun, Mar 22, 2009 at 3:39 AM, Craig Ringer
> <craig@postnewspapers.com.au> wrote:
>> zach cruise wrote:
>>> when importing from oracle 10g
>>
>> Importing how? CSV dump and load? DB link of some sort?
>
> odbc (see email) specifically Microsoft OLE DB Provider for Oracle
>
>> Operating system and version? Oracle version?
>
> windows 2k3
> oracle 10g (see email)
> postgresql 8.1 (see email)
>
>>> i get "multiple step ole db generated
>>> error".
>>
>> From what program ? Where?
>
> navicat (see email)
>
> again, i narrowed this down to a date/timestamp column that gets
> imported ok if imported as varchar. there is another date/timestamp
> column that gets imported error-free, and other tables also get
> imported ok. based on my narrowing-down, it appears less likely error
> is at os/odbc/postgresql/oracle level but more likely at
> database/table/column/row level (esp since all problem rows =
> '01-JAN-01' (never null) but that could be a false-alarm).
