ORA-24345: A Truncation or null fetch error occurred -ora2pg

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

ORA-24345: A Truncation or null fetch error occurred -ora2pg

Daulat Ram-2

Hi team ,

I am getting the below error while fetching the data from Oracle 12c using ora2pg.

 

DBD::Oracle::st fetchall_arrayref failed: ORA-24345: A Truncation or null fetch error occurred (DBD SUCCESS_WITH_INFO: OCIStmtFetch, LongReadLen too small and/or LongTruncOk not set)ERROR no statement executing (perhaps you need to call execute first) [for Statement "SELECT "USERS_ID","NAME","USERS" FROM "GBOPSUI"."USER_GROUP_USERS_V5" a"] at /usr/local/share/perl5/Ora2Pg.pm line 14110.

 

 

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.

 

Thanks,

Daulat

 

Reply | Threaded
Open this post in threaded view
|

RE: ORA-24345: A Truncation or null fetch error occurred -ora2pg

Daulat Ram-2
H,

We are using  below the ora2pg version and the data types for tables.

bash-4.2$ ora2pg -v
Ora2Pg v20.0
bash-4.2$

SQL> SELECT distinct data_type FROM dba_tab_columns WHERE owner='GBOP;

DATA_TYPE
--------------------------------------------------------------------------------
TIMESTAMP(6)
FLOAT
CLOB
NUMBER
CHAR
DATE
VARCHAR2
BLOB

SQL>

We are getting the same issue for tables which are having blob, clob and char data types.

Thanks,
Daulat

-----Original Message-----
From: Luca Ferrari <[hidden email]>
Sent: Tuesday, August 13, 2019 8:32 PM
To: Daulat Ram <[hidden email]>
Cc: [hidden email]; [hidden email]
Subject: Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg

On Tue, Aug 13, 2019 at 10:23 AM Daulat Ram <[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg

Adrian Klaver-4
On 8/13/19 10:34 AM, Daulat Ram wrote:

> H,
>
> We are using  below the ora2pg version and the data types for tables.
>
> bash-4.2$ ora2pg -v
> Ora2Pg v20.0
> bash-4.2$
>
> SQL> SELECT distinct data_type FROM dba_tab_columns WHERE owner='GBOP;
>
> DATA_TYPE
> --------------------------------------------------------------------------------
> TIMESTAMP(6)
> FLOAT
> CLOB
> NUMBER
> CHAR
> DATE
> VARCHAR2
> BLOB
>
> SQL>
>
> We are getting the same issue for tables which are having blob, clob and char data types.

The ora2pg issue below seems to have more information on this:

https://github.com/darold/ora2pg/issues/342

>
> Thanks,
> Daulat
>
> -----Original Message-----
> From: Luca Ferrari <[hidden email]>
> Sent: Tuesday, August 13, 2019 8:32 PM
> To: Daulat Ram <[hidden email]>
> Cc: [hidden email]; [hidden email]
> Subject: Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg
>
> On Tue, Aug 13, 2019 at 10:23 AM Daulat Ram <[hidden email]> 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
>


--
Adrian Klaver
[hidden email]


Reply | Threaded
Open this post in threaded view
|

RE: ORA-24345: A Truncation or null fetch error occurred -ora2pg

Daulat Ram-2
Hi Adrian ,

We have the below output. What we need to change.

bash-4.2$ ora2pg -c ora2pg.bidder.conf -t SHOW_ENCODING

Current encoding settings that will be used by Ora2Pg:
        Oracle NLS_LANG AMERICAN_AMERICA.AL32UTF8
        Oracle NLS_NCHAR AL32UTF8
        Oracle NLS_TIMESTAMP_FORMAT YYYY-MM-DD HH24:MI:SS.FF6
        Oracle NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS
        PostgreSQL CLIENT_ENCODING UTF8
        Perl output encoding ''
Showing current Oracle encoding and possible PostgreSQL client encoding:
        Oracle NLS_LANG AMERICAN_AMERICA.WE8MSWIN1252
        Oracle NLS_NCHAR WE8MSWIN1252
        Oracle NLS_TIMESTAMP_FORMAT YYYY-MM-DD HH24:MI:SS.FF6
        Oracle NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS
        PostgreSQL CLIENT_ENCODING WIN1252
bash-4.2$

thanks

 
-----Original Message-----
From: Adrian Klaver <[hidden email]>
Sent: Tuesday, August 13, 2019 11:27 PM
To: Daulat Ram <[hidden email]>; Luca Ferrari <[hidden email]>
Cc: [hidden email]; [hidden email]
Subject: Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg

On 8/13/19 10:34 AM, Daulat Ram wrote:

> H,
>
> We are using  below the ora2pg version and the data types for tables.
>
> bash-4.2$ ora2pg -v
> Ora2Pg v20.0
> bash-4.2$
>
> SQL> SELECT distinct data_type FROM dba_tab_columns WHERE owner='GBOP;
>
> DATA_TYPE
> --------------------------------------------------------------------------------
> TIMESTAMP(6)
> FLOAT
> CLOB
> NUMBER
> CHAR
> DATE
> VARCHAR2
> BLOB
>
> SQL>
>
> We are getting the same issue for tables which are having blob, clob and char data types.

The ora2pg issue below seems to have more information on this:

https://github.com/darold/ora2pg/issues/342

>
> Thanks,
> Daulat
>
> -----Original Message-----
> From: Luca Ferrari <[hidden email]>
> Sent: Tuesday, August 13, 2019 8:32 PM
> To: Daulat Ram <[hidden email]>
> Cc: [hidden email]; [hidden email]
> Subject: Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg
>
> On Tue, Aug 13, 2019 at 10:23 AM Daulat Ram <[hidden email]> 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
>


--
Adrian Klaver
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg

Adrian Klaver-4
On 8/14/19 2:39 AM, Daulat Ram wrote:
> Hi Adrian ,
>
> We have the below output. What we need to change.

I am not an ora2pg user so I don't know what to suggest for below. I
would say the best thing to do would be to file an issue here:

https://github.com/darold/ora2pg/issues

Along with the original error message include the below and the
settings, if any, for NLS_*, CLIENT_ENCODING from your ora2pg.conf file.

>
> bash-4.2$ ora2pg -c ora2pg.bidder.conf -t SHOW_ENCODING
>
> Current encoding settings that will be used by Ora2Pg:
>          Oracle NLS_LANG AMERICAN_AMERICA.AL32UTF8
>          Oracle NLS_NCHAR AL32UTF8
>          Oracle NLS_TIMESTAMP_FORMAT YYYY-MM-DD HH24:MI:SS.FF6
>          Oracle NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS
>          PostgreSQL CLIENT_ENCODING UTF8
>          Perl output encoding ''
> Showing current Oracle encoding and possible PostgreSQL client encoding:
>          Oracle NLS_LANG AMERICAN_AMERICA.WE8MSWIN1252
>          Oracle NLS_NCHAR WE8MSWIN1252
>          Oracle NLS_TIMESTAMP_FORMAT YYYY-MM-DD HH24:MI:SS.FF6
>          Oracle NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS
>          PostgreSQL CLIENT_ENCODING WIN1252
> bash-4.2$
>
> thanks


--
Adrian Klaver
[hidden email]