The Oracle database plugin uses two operations to synchronize the database structures within a schema. In the source or build environment, the user has the option to either use the recreateBuildDB operation to drop and recreate the database objects based on a supplied SQL/DDL file. The second option is to make the changes in the build database using a tool like SQL Developer or SQL plus. The createBaseline operation is used by the build process in FlexDeploy to store this version of the schema in a DDL repository. During the deployment, the sync operation will then compare this baseline to the existing baseline in that environment. The compare generates the creates, drops, or alters that are necessary to make the target database structures look like the source database structures. Additional operations are available to recompile invalid objects, refresh materialized view, or drop unused columns. These operations can optionally be included in the defined workflow.

The plugin respects table locks, so if a table has locks disabled, the operations will not be able to delete them or modify them. This is a precaution against user error. If you wish to drop or change them, please enable locks first.

DDL Repository

The baselines are stored in a DDL repository. You must create the DDL Repository schema, see install and update scripts at . DDL repository needs to be created in FDDB schema, script provided does not create FDDB schema, you may do that per your company standards. If you are upgrading from version prior to 5.1.07, then run upgrade/v4.6.0.3-to-5.1.0.7/migration.sql to upgrade your repository schema. Then, run upgrade/5.1.0.7-to-5.2.3.1/migration.sql and upgrade/5.2.3.1-to-5.4.0.4/migration.sql.  If you were already at a version higher then 5.1.0.7, then only the second migration.sql needs to be executed.  If you are creating DDL repository schema, then just run install/DDLRepositoryCreateScript.sql.

Supported Versions

• Oracle Database 11.2, 18c, 21c (Express, Standard, and Enterprise Edition)

• Oracle Database 12.1, 19c (Standard, and Enterprise Edition) 
  

  • Features delivered by Oracle in 12.1 (like invisible columns) are not currently supported by the plugin.

Key Features

• Manage deployments of entire schema(s).

• Manage package-based deployment of objects in a schema(s).

• Supports a wide range of object types.

• Source changes from an SCM or "Build Database".

• Ability to sync a schema from different starting points.

• Manage object renames.

• Ability to simulate deployments so that generated DDL can be reviewed ahead of time.

• Grants are managed with each object.

• Constraints are managed with each Table and View object.

User Permission Requirements

The users specified in FDORA_USER and FDORA_DDL_USER require these permissions:

• GRANT EXECUTE on dbms_crypto to <YOUR USER NAME>;

• GRANT SELECT_CATALOG_ROLE TO <YOUR USER NAME>;

• GRANT SELECT ANY DICTIONARY TO <YOUR USER NAME>;

• grant READ on sys.dba_transformations to <YOUR USER NAME>;

• grant READ on sys.dba_objects to <YOUR USER NAME>;

• grant READ on sys.dba_queues to <YOUR USER NAME>;

• grant READ on sys.dba_queue_tables to <YOUR USER NAME>;

• FDORA_USER needs Create and alter Permissions for the schemas being synced. Using the schema owner as FDORA_USER may be the easiest solution, and is needed if triggers don’t have schema-qualified table references.

Supported Oracle Object Types

• Sequence

• Table

• Index

• Constraints

• View

• Synonym

• Function

• Trigger

• Type

• Type Body

• Package

• Package Body

• Procedure

• Columns

• Index

Plugin Operations

Appendix

• Setting up an SSH tunnel to a remote database

• Supported and Unsupported Table and Index options