Oracle can be used as either a Source or Target Server (subject to Licencing) If used as a target tables the Precision Bridge Archiving Wizard can be uset to generate target tables (see related link below)
If used as a source, please note the restrictions in the related link below.
Oracle can also be used as an external lookup server or reporting target (see related links below)
To use Oracle as the Source Server, select Oracle from the Source Server Type dropdown.
To use Oracle as the Target Server, select Oracle from the Target Server Type dropdown.
Pre-requisites:
- Only Oracle Version 12.2 or greater is currently supported.
- Oracle JDBC Driver; First check that you have setup the path to the corresponding JDBC driver. See Configuring Access to an Oracle Database for more details.
The connection details will be displayed and must be completed as follows:
Data Source: The name of your Oracle server or IP address.
Service Name: The name of the oracle service. Note that this is the Service Name, not the SID.
Port: The port number for this service (default 1521).
User Name: The name of the oracle user to connect with.
Password: The oracle password for this user.
If you want to retain the login details for each instance, select the Save Authentication option. After selecting this option, the username and password are stored and do not need to be entered again the next time you open the same project from the same client machine. Otherwise you will need to re-enter them each time you open the project.
Use a User Defined Connection URL for the Oracle Connection
Sometimes you may wish to connect to Oracle using a more complex connection URL which contains additional connection parameters. This may be the case for example if you wish to connect to an Oracle RAC.
To define your own connection string, check Define Connection URL. A text area will be shown allowing you to enter a connection string. Note that when Precision Bridge connects (via JDBC), the connection string used will be jdbc:oracle:thin:@<your connection url>
Additional Options Tab
The following additional connection details are optional, and can be configures on the Additional Options tab:
Inc Schemas: By default, only tables owned by the current user will be available as a data source/target in the project. To add tables from other schemas, a comma delimited list of schema names can be entered
Tablespace: By default, tables in all tablespaces (or not in any tablespace) will be available as a data source/target in the project. To restrict available tables to those in a single tablespace, enter the table space identifier here.
Session Initialisation Statement Tab
This section is also optional, and allows a stored procedure to be run after the connection has been established. This can be used to set additional session variables.
Note that a single statement only is supported, and a terminating semicolon should not be added.
If there is any error in calling this statement, Precision Bridge will report an error in the connection process.
Testing the Connection
In order to check that the relevant servers can be accessed using the credentials provided, click on the Test button on the right.
If the selected server is reachable then a confirmation message will be displayed. If the server is not reachable then a failure/timeout message will be displayed. If the Oracle server is still not reachable, check that you can connect using the same credentials from a native Oracle client application such as SQL Developer.
Related Articles:
Configuring access to Oracle Data
The Precision Bridge Archiving Wizard
Configuring an External Lookup Server Connection
Writing Migration Reports to Database Tables
Restrictions on use of Oracle DB data source
Comments
0 comments
Please sign in to leave a comment.