Migrating AutoSys Oracle Database (using autobcp/autobcpdp) to a New Instance Preserving Custom Procedures and Views

Products

• Autosys Workload Automation

Issue/Introduction

When migrating an AutoSys database from one Oracle instance to another (e.g., on-premise to a cloud-based ORAAS), users often need to preserve custom PL/SQL objects such as procedures, views, packages, and functions.

 

Cause

AutoSys's autopbcpdp program has an explicit "exclude=user,view,package,function,procedure,db_link,statistics,type_spec"  in its syntax.

The primary reason for excluding procedures/views from standard imports is the impdp limitation regarding TABLE_EXISTS_ACTION. Unlike tables, there is no native parameter to "Replace" a view or procedure if it exists.

Resolution

• autobcp architecture expects you to have source and destination databases with exact schema objects.  If they are not present, autobcp will not create them. You can run AEDBRefresh or Create or Upgrade database tool to populate the default schema objects first.
• Once the base schema objects exist, autobcpdp can copy over the table contents to sync the databases

Work with a Database Administrator on their recommended approaches to migrate custom views/procedures etc., from one database to another.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.