Scenario: Your external data source may be been upgraded in-place.
Example: Your Oracle 11g db has been upgraded in-place to 12c. Your TDV datasource was originally created with our Oracle 11g adapter. This article assumes that no deliberate column type or schema changes were made to the schema during the upgrade.
Resolution
Unfortunately at the time of this writing, we cannot change the underlying TDV adapter for an existing TDV datasource. You will need to introspect the db again with the newer appropriate TDV adapter (ie; in this case, Oracle 12c)
However, you can follow these steps to minimize disruption to your queries that utilize the datasource.
Example for this Oracle scenario:
Introspect Oracle with the newer 12c adapter from any resource path in Studio.
optional step- disable the existing Oracle 11g datasource to suspend any queries against it. Export a copy for safe-keeping.
Delete the Oracle 11g datasource from the Studio resources tree. Do not move (cut/paste) it to another path in the Studio tree.
Move (cut/paste) your new Oracle 12c datasource into the exact original path of the original Oracle 11g datasource.
Give the Oracle 12c datasource the exact same name that the 11g datasource used to have.
The existing views and sqlscript procedures should continue to run normally without the need to rebind them to the new datasource.
Issue/Introduction
This discusses what to do if your external datasource has been upgraded.