synchronize
- Karl Henselin
Upgrades the Oracle DDL of a specified schema to the supplied baseline. The baseline id is supplied by an artifact created by the createBaseline operation. The DDL is pulled from the DDL Repository and applied to the database specified by Oracle Database URL and Oracle Database Schema Name(s). The schema names must be the same in the different environments.
When deploying a baseline that contains rename views, sequences, or synonyms, the value of Target Property FDORA_USER must be the owner of the objects. Running the operation as another user will fail with ORA-04043.
When renaming columns and tables in the same build, set the properties like:
FDORA_TABLE_RENAMESÂ -Â schema.old_table = schema.new_table
FDORA_COLUMN_RENAMESÂ -Â schema.old_table.old_column = schema.new_table.new_column
Â
As of release 5.5.0.1, you can specify renames without Schema prefixes, provided that you also leave the project property FDORA_SCHEMA_NAME blank. In this case, the schema will be set to the value of FDORA_USER and this value will be used for all renames.
Â
FDORA_TABLE_RENAMESÂ -Â old_table = new_table
FDORA_COLUMN_RENAMESÂ -Â old_table.old_column = new_table.new_column
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle Database URL |
| Yes | The JDBC URL for the target Oracle database. This should be a complete JDBC URL (e.g. |
Oracle Database User |
| Yes | The username that will be used to connect to the target Oracle Database. NOTE*** If the project property FDORA_SCHEMA_NAME is not set, then this becomes the schema. |
Oracle Database Password |
| Yes | The password for Oracle Database User. |
Target JDBC Driver Path. |
| Yes | Path containing JDBC driver for target database connection. |
DDL Repo JDBC Driver Path |
| Yes | Path containing JDBC driver for DDL repository database connection. |
DDL Repository URL |
| Yes | The JDBC URL for the DDL repository. This should be a complete JDBC URL (e.g. jdbc:oracle:thin:@localhost:1521:xe) |
DDL Repository User |
| Yes | The userid used to connect to the DDL repository. |
DDL Repository Password |
| Yes | The password for the DDL repository userid. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle Database Schema Name(s) |
| No | Comma-separated list of schemas controlled by this project. Leave this parameter blank if you want to have schema name different across environments. If it isn't provided, |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Column Drop Action |
| No | Determines what action to take for "dropping" columns. Can be set to Defaults to |
Preview Execution |
| No | Whether to bypass actual execution of the DDL, and simply run the compare. Defaults to true. For Pre-deploy workflow this should be checked to only run compare and generate report for review. In addition |
Automatically rollback changes if the deployment fails |
| No | If a deployment failure occurs, should the database be rolled back to the previous state? Defaults to false. If true, the snapshot taken as the deployment starts will be rolled back to. If false, the database will be left in the state it is in after the first failure. The deployment stops after the first failure occurs. |
Fail the workflow if it is rolled back successfully |
| No | Added in 4.0.3.65. If a deployment failure occurs, but it is successfully rolled back to the previous version, should the workflow still be failed? Defaults to true. |
Include Tablespaces |
| No | Setting this to true causes create statements to include tablespace information where appropriate. This adds the tablespace clause to all creates. Defaults to false. Requires segments attributes to be enabled also. |
Include Segment attributes |
| No | Setting this to true causes create statements to include tablespace segment attribute information where appropriate. Defaults to false. |
Include Storage |
| No | Setting this to true causes create statements to include storage information where appropriate. This adds the STOREAGE clause with its values on all creates. Defaults to false.  Requires segments attributes to be enabled also. |
Outputs
Output Name | Required | Description |
|---|---|---|
| No | This is the baseline ID currently deployed to the target environment OR the baseline ID created from this deployment. |
| No | This is the baseline ID being deployed to this environment. |
| No | The ID to track the DDL used for this deployment. |
| No | Count of tables dropped. |
| No | Count of tables created. |
| No | Count of tables altered. |
| No | Count of columns dropped. |
| No | Count of columns added. |
| No | Count of columns modified. |
| No | Count of constraints dropped. |
| No | Count of constraints added. |
| No | Count of constraints modified. |
| No | Count of indexes dropped. |
| No | Count of indexes created. |
| No | Count of indexes altered. |
| No | Count of views dropped. |
| No | Count of views created. |
| No | Count of views altered. |
| No | Count of sequences dropped. |
| No | Count of sequences created. |
| No | Count of sequences altered. |
| No | Count of procedures dropped. |
| No | Count of procedures created. |
| No | Count of procedures altered. |
| No | Count of triggers dropped. |
| No | Count of triggers created. |
| No | Count of triggered altered. |
| No | Count of synonyms dropped. |
| No | Count of synonyms created. |
| No | Count of functions dropped. |
| No | Count of functions created. |
| No | Count of functions altered. |
| No | Count of types dropped. |
| No | Count of types created. |
| No | Count of types altered. |
| No | Count of type body drops. |
| No | Count of type body creates. |
| No | Count of type body alters. |
| No | Count of packages dropped. |
| No | Count of packages created. |
| No | Count of packages altered. |
| No | Count of package body drops. |
| No | Count of package body creates. |
| No | Count of package body alters. |
| No | Count of materialized view drops. |
| No | Count of materialized view creates. |
| No | Count of materialized view alters. |
| No | Count of materialized view log drops. |
| No | Count of materialized view log creates. |
| No | Count of materialized view log alters. |
| No | Count of object grants. |
| No | Count of tables in the new baseline. |
| No | Count of indexes in the new baseline. |
| No | Count of constraints in the new baseline. |
| No | Count of sequences in the new baseline. |
| No | Count of procedures in the new baseline. |
| No | Count of views in the new baseline. |
| No | Count of synonyms in the new baseline. |
| No | Count of materialized views in the new baseline. |
| No | Count of materialized view logs in the new baseline. |
| No | Count of table renames processed. |
| No | Count of column renames processed. |
| No | Count of constraint renames processed. |
| No | Count of index renames processed. |
| No | Count of view renames processed. |
| No | Count of sequence renames processed. |
| No | Count of trigger renames processed. |
| No | Count of synonym renames processed. |
| No | Count of object privileges in the new baseline. |
| No | Returns true if changes exist as part of execution of this operation. This output can be saved in FD_REVIEW_REQUIRED output for Pre-deploy workflow and in addition FD_REVIEW_GROUP to assign Review tasks to specific group(s). |
Artifacts
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
The plugin currently requires the source and target schema names to be the same.
- style