2 Known Issues and Workarounds
Use this information to understand the known issues and workarounds for Oracle Data Transforms.
This chapter contains the following section:
2.1 Connection to an existing repository fails due to missing wallet missing information
Data Transforms uses the information from wallets that are downloaded from the database instance to create a connection to that instance.
If you have provisioned a new Oracle Data Transforms instance and are connecting to an existing repository that is based on Data Transforms 2021.12.24.00 or earlier versions, the connection fails due to missing wallet information.
The workaround for this issue is to upload the wallet manually. Follow these steps:
- Download the wallet from the instance that you want to connect to.
- Login to the Data Transforms interface.
- From the left pane of the Home page, click the Connections tab.
- Click the Actions icon (
) next to the connection and select Edit.
- In the Update Connection page, browse to select the wallet file.
- Select the service.
- Enter the username and password.
- Click Update to apply the changes.
From the Actions menu next to the updated connection, select Test Connection to check whether the connection is successful.
2.2 Connecting to an existing repository from an older Data Transforms instance fails
If you have provisioned an older Oracle Data Transforms instance, and are connecting to an existing repository that is based on a later version of Oracle Data Transforms the connection fails due to auth token expiry.
To avoid this issue Oracle recommends that you connect to a repository that is based on Data Transforms 2022.11.16.00 or later versions.
2.3 Connection to Data Transforms repository fails if the database is renamed
This issue applies to Data Transforms that is available as a separate listing on Marketplace called Data Integrator: Web Edition.
If you rename the database where the repository is located, Data Transforms fails to connect to such repositories. This is because the environment becomes unusable. The workaround to this issue is to reconfigure the environment using the new database name.
Follow these steps:
- Remove the wallet files.
- Login to the compute instance running Oracle Data Transforms as Oracle user.
- Delete the
cwallet.sso
andcwallet.sso.lck
files from the/u01/oracle/transforms_home/common/scripts/
directory.
- Reprovision the Data Transforms instance.
- Access Data Transforms via a browser using the URL format
http://<public-ip address>:9999/oracle-data-transforms
. - On the Administration tab, select the Connect to an existing Repository in an Autonomous Database option.
- In the Autonomous Database Details page, either enter the OCID or browse to select the database where the repository resides.
- Provide the password credentials of the administrator user of the Autonomous Database.
- To configure the Schema details, use the details you specified during repository creation.
- Access Data Transforms via a browser using the URL format
Refer to Provision the Oracle Data Transforms Metadata Repository for more detailed instructions.