You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While exporting SYNONYMs from Oracle, it exports the CREATE OR REPLACE VIEW DDLs with full name of view with schema_name included and that schema will be same as the schema in which the synonym is present in Oracle sourceDB, but the schema with that name is not present in target and hence import schema fails with error of does not exist.
Example-
CREATE OR REPLACE VIEW sakila_demo.offices AS SELECT * FROM sakila_demo.locations;
Error in import schema -
ERROR: relation "sakila_demo.locations" does not exist (SQLSTATE 42P01)
as locations table is imported in public schema.
The text was updated successfully, but these errors were encountered:
Adding this case in analyze-schema and leaving it on user to do the needful manually like removing the schema name from the DDL or create the schema/required objects in the respective schema in the target.
Voyager explicitly remove the schema name from the DDLs at the end of export-schema phase.
While exporting SYNONYMs from Oracle, it exports the
CREATE OR REPLACE VIEW
DDLs with full name of view with schema_name included and that schema will be same as the schema in which the synonym is present in Oracle sourceDB, but the schema with that name is not present in target and hence import schema fails with error ofdoes not exist
.Example-
Error in import schema -
as
locations
table is imported in public schema.The text was updated successfully, but these errors were encountered: