-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
what happen in this error"ERROR: invalid byte sequence for encoding "UTF8": 0x00" #120
Comments
This is the same problem as #114: while a null byte is allowed in a character string in Oracle, it is not allowed in PostgreSQL. You might want to fix the data on the Oracle side. |
if I can't permission modify oracle data,so this problem is not fix? |
There's no way to allow a zero character in PostgreSQL, and oracle_fdw does not have any provisions for modifying the data it gets from Oracle. Is the zero byte in the character string in the Oracle database intentional? |
ERROR: no primary key column specified for foreign Oracle table old release is can't PK ?why need PK column? |
For |
use select translate( column, chr(0),' ' ) in select to convert the invalid byte sequenzes in oracle to something else in oracle pg gives you the column names and the invalid codes before loading into pg I have to do a lot of updates, because the oracledb is infested with this crap, |
@laurenz maybe oracle table encoding is error.
how to fixed this problem.thanks.
The text was updated successfully, but these errors were encountered: