| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg |
| Date: | 2019-08-13 15:02:17 |
| Message-ID: | CAKoxK+417CrR9MeVkbXw2huKWZn2=2CU5fHrmDoQtX6eUbNWJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Tue, Aug 13, 2019 at 10:23 AM Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com> wrote:
> Initially did not have LongReadLen set, so I thought this was the cause. But, I have set LongReadLen, on the db handle, equal to 90000000.
Apparently this is an oracle problem because it acceppted data longer
than its type, so my guess would be that in your table you have a
char(n) column that could be enlarged before the migration.
<https://support.oracle.com/knowledge/Siebel/476591_1.html>
Hope this helps.
And please report the version of ora2pg when asking for help.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-08-13 15:08:50 | Re: Bulk Inserts |
| Previous Message | Luca Ferrari | 2019-08-13 14:48:43 | Re: Question on pgwatch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daulat Ram | 2019-08-13 17:34:22 | RE: ORA-24345: A Truncation or null fetch error occurred -ora2pg |
| Previous Message | 王若楠 | 2019-08-13 14:15:09 | performance bottlenecks on lock transactionid |