Oracle Database URL

FDORA_URL

Yes

The JDBC URL for the target Oracle database.

This should be a complete JDBC URL (e.g. jdbc:oracle:thin:@localhost:1521:xe)

Connecting to Oracle Autonomous Database

You will need client credential zip file (wallet) to connect with Oracle Autonomous Database on Oracle cloud. You can download wallet zip file from Oracle Cloud, you will need admin userid and password to perform this download. See Download Client Credentials (Wallets) for more details on how to download wallet file.

• Since FlexDeploy 9.0.0.9 with Oracle Wallet Credential Type : Instead of maintaining the wallet zip file under the file system, you can now store the wallet zip as an Oracle Credential Type in FlexDeploy. This allows for secure storage and use of the wallet.

  • Use the URL syntax in the following format: jdbc:oracle:thin:@service_low?TNS_ADMIN=$\{\{FDORACLE_WALLET_FILE\}\}</code></p></li><li><p>We must select valid oracle wallet credential for <code>FDORACLE_WALLET_FILE</code> property on target group.</p></li><li><p>Here, <code>${{FDORACLE_WALLET_FILE}} is replaced with the temporary wallet folder path during execution. Once execution is completed, the temporary file is cleaned up automatically.

• Before FlexDeploy 9.0.0.9

  • You must make sure that only authorized users have access to these wallet files. Unzip the client credentials zip file (wallet_databasename.zip) on FlexDeploy server and/or endpoint where it will be used. For example, /home/flexdeploy/.wallets/<wallet_databasename> is folder where specific wallet file was unzipped. Make sure to secure this folder to FlexDeploy and/or Endpoint user, so that it is not readable by all users.

  • We recommend using Oracle Wallet Credential Type for better security and easier management of Wallet usage.

  • Database URL Syntax : jdbc:oracle:thin:@service_high?TNS_ADMIN=/home/flexdeploy/.wallets/<wallet_databasename>

    • service_high is one of the entries in the tnsnames.ora file where client credentials zip file was unzipped. See Predefined Database Service Names for Autonomous Database for details on services.

    • TNS_ADMIN value in URL points to the location of the unzipped client credentials zip file.

  • Database URL Long Connection String Format Syntax : jdbc:oracle:thin:@(description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=<hostname>))(connect_data=(service_name=<serice_name>))(security=(ssl_server_cert_dn=“CN=<hostname>,OU=Oracle BMCS US,O=Oracle Corporation,L=Redwood City,ST=California,C=US”)))

    • Examples for the same can be found here.

If using the Oracle Database Plugin with ADW or ATP databases , use the _low connection. The _medium and _high connections can sometimes throw error ORA-12839: cannot modify an object in parallel after modifying it.

Oracle Wallet File

FDORACLE_WALLET_FILE

No

Since 9.0.0.9 - Provide the Oracle Wallet file, seeCredential Type - Oracle Wallet for more details.

Oracle Database User

FDORA_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

FDORA_PASSWORD

Yes

The password for Oracle Database User.

Target JDBC Driver Path.

FDORA_DRIVER_PATH

Yes

Path containing JDBC driver for target database connection.

Oracle Database Schema Name(s)

FDORA_SCHEMA_NAME

Yes

Comma-separated list of schemas controlled by this project.

Leave this parameter blank if you want to have schema name different across environments.
The plugin will then use the FDORA_USER Target parameter as the schema name.

Refresh method

FDORA_MVIEW_METHOD

No

Method to use to refresh the materialized view.

F-Fast, P-Fast_PCT, ?-Force, C-Complete

Defaults to ?.

Rollback Segment

FDORA_MVIEW_ROLLBACK_SEGMENT

No

Rollback segment to use to refresh the materialized view.

Defaults to None.

Mview Parallelism

FDORA_MVIEW_PARALLELISM

No

Parallelism to use to refresh the materialized view.

Defaults to 0.

FDORA_OUT_REFRESH_COUNT

No

FDORA_OUT_POST_STALE_COUNT

No