6 Mandatory step before PDB/SEED sync
- Login into the Application Entity PDB/SEED as sys user.
- Create function fn_error_handler.fnc.
- Alter the DB Syncing error handling
parameters
ALTER DATABASE PROPERTY SET SYNC_ERROR_HANDLER = 'sys.fn_error_handler';
- Below are the errors handled during sync in Application PDB / Entity PDB:
Oracle Docs - - Oracle Error Cause Action ORA-24344 A sql/plsql compilation error occurred. Return OCI_SUCCESS_WITH_INFO along with the error code ORA-06512 Backtrace message as the stack is unwound by unhandled exceptions. Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA ORA-65297 An operation was attempted that can only be performed outside an application action (install, uninstall, upgrade, or patch) Perform the operation outside an application action. ORA-65274 An operation was attempted that can only be performed in an application action (install, uninstall, upgrade, or patch). Begin an application action. ORA-00001 An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level Either remove the unique restriction or do not insert the key ORA-01430 An ALTER TABLE ADD statement specified the name of a column that is already in the table. All column names must be unique within a table. Specify a unique name for the new column, then re-execute the statement ORA-02264 The specified constraint name has to be unique. Specify a unique constraint name for the constraint ORA-01434 A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names may be listed by querying the data dictionary. Specify the name of an existing synonym in the DROP SYNONYM statement. ORA-00955 An attempt was made to create a database object (such as a table, view, cluster, index, or synonym) that already exists. A user's database objects must have distinct names. Enter a unique name for the database object or modify or drop the existing object so it can be reused. ORA-06550 Usually a PL/SQL compilation error. None ORA-04063 Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types. Fix the errors and/or create referenced objects as necessary.
- Below are the errors handled during sync in Application PDB / Entity PDB: