convert db2 stored procedure to aws postgresql

#Convert db2 stored procedure to aws postgresql drivers#
#Convert db2 stored procedure to aws postgresql driver#

This is a file that you previously created by clicking Tools, then Migration, then Create Database Capture Scripts. Offline Capture Source File (Offline mode): The.

#Convert db2 stored procedure to aws postgresql drivers#

If the desired platform is not listed, you probably need the appropriate JDBC driver, which you can get by clicking Help, then Check for Updates, or by clicking the Add Platform link and adding the necessary entry on the Database: Third Party JDBC Drivers preferences page. To add a connection to the list, click the Add (+) icon to edit the selected connection, click the Edit (pencil) icon.Īvailable Source Platforms (Online mode) List of third-party databases that you can migrate. Mode: Online causes the migration to be performed by SQL Developer when you have completed the necessary information in the wizard Offline causes SQL Developer to perform the migration using a file (the Offline Capture Source File) that you specify.Ĭonnection (Online mode): The database connection to the third-party database to be migrated. The Source Database page of the wizard specifies the third-party database to be migrated. Truncate: If this option is enabled, the repository is cleared (all data from previous migrations is removed) before any data for the current migration is created.

#Convert db2 stored procedure to aws postgresql driver#

(For migrations, you should set the third party JDBC driver preference before creating the connection.) For example, create a database connection named Sales_Sybase to a Sybase database named sales.Ĭonnection: The database connection to the migration repository to be used. If you do not already have a database connection to the third-party database to be migrated, create one. Right-click the Migration_Repository connection, and select Migration Repository, then Associate Migration Repository to create the repository. (For multischema migrations, you must grant the RESOURCE role with the ADMIN option and you must also grant this user the CREATE ROLE, CREATE USER, and ALTER ANY TRIGGER privileges, all with the ADMIN option.)Ĭreate a database connection named Migration_Repository that connects to the MIGRATIONS user. If you do not already have a migration repository and a database connection to the repository, create them as follows:Ĭreate an Oracle user named MIGRATIONS with default tablespace USERS and temporary tablespace TEMP and grant it at least the RESOURCE role and the CREATE SESSION, CREATE VIEW, and CREATE MATERIALIZED VIEW privileges.

The migration repository is a collection of schema objects that SQL Developer uses to manage metadata for migrations. The Repository page of the wizard requires that you specify the database connection for the migration repository to be used.