-
Notifications
You must be signed in to change notification settings - Fork 342
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
TEST_DATA : ERROR: ORA-00911: caractère non valide #1841
Comments
Please upgrade to latest development code this have been fixed normally. |
Hi nohup ora2pg -c config/ora2pg.conf > rapport_TEST_DATA [postgres@dcgyy5eo DEVPATOU2]$ tail -f rapport_TEST_DATA |
Hi |
Hi |
No fix are planned, avoid adding comments in the ora2pg.conf setting value is the solution. I know this is default ora2pg.conf but this is just not allowed. |
Hi
After completing the migration from Oracle 19 to PostgreSQL 15, I want to compare the data between the source Oracle database and the target PostgreSQL database.
For this, I specified "TYPE TEST_DATA" in the
ora2pg.conf
file.I get the following error message :
ERROR: ORA-00911: caractère non valide (DBD ERROR: error possibly near <> indicator at char 211 in 'SELECT "CODE_PARAM_TRAIT_CAT","CODE_TYP_PARAM","CODE_TRAIT_CAT","CODE_ENTR_CAT","CODE_SORT_CAT","NUM_LOI","ID_MATRICE_CAT","ORDRE_PARAM","LIB_PARAM_TRAIT_CAT","DESC_PARAM" FROM "CTR"."PARAM_TRAIT_CAT" a WHERE (1<>=1 # Apply to all tables) ORDER BY 1 FETCH FIRST 10000 ROWS ONLY')
Can't call method "execute" on an undefined value at /usr/local/share/perl5/Ora2Pg.pm line 21376.
Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Oracle::db handle (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=XXXXXX))(CONNECT_DATA=(SID=CTRNAT))) at /usr/local/share/perl5/Ora2Pg.pm line 21376.
Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Oracle::db handle (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=XXXXXXX))(CONNECT_DATA=(SID=CTRNAT))) at /usr/local/share/perl5/Ora2Pg.pm line 21376.
is this a bug ?
Ora2Pg v24.1
<<
The text was updated successfully, but these errors were encountered: