Error importing LONG RAW data (TYPE INSERT) about ora2pg HOT 5 CLOSED

Hi,

Thanks for the report, it seems that the function utl_raw.cast_to_varchar2() used to extract RAW type doesn't work with LONG RAW. Do you have any idea of what function to use that can do the same with this type ?

from ora2pg.

It appears that LONG RAW cannot be converted to VARCHAR2 directly due to max size of the two data types.
http://www.dbasupport.com/forums/showthread.php?5342-How-to-read-LONG-RAW-column-into-VARCHAR2

Why do we need to convert RAW/LONG RAW to VARCHAR2 again?

from ora2pg.

This issue should be fixed by the last commit 339423f, could you give it a try an let me know?

from ora2pg.

I tested with the new revision and the problem appears to be fixed. thanks.

Could you let me know if the behavior (LONG RAW conversion) now is back to how it was in 10.1 (before changes in 11.1)? If not, what is the change in the behavior?

Thanks again.
Prabhat

from ora2pg.

Yes this is a come back to the original behavior. Patch in 11.1 was to force hex decoding because someone complain about hex data stored in bytea. This is not something I used to export because it is an obsolete datatype so I've not tested the patch by myself. After give it some try my though is that DBD::Oracle is just handling the datatype as expected: data are returned in binary format and not as hexa so it don't need to be converted as varchar2.

from ora2pg.