My Oracle Support Banner

Problems with Reverse Engineering of an SQL Server database after importing (Doc ID 424733.1)

Last updated on DECEMBER 18, 2019

Applies to:

Oracle Data Integrator - Version 4.1.01.05 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

After importing a Microsoft SQLServer database from an external source to be used as a Data Server in Integration Interfaces, the Standard Reverse Engineering of a Model based on this database does not result in the creation of any Datastores. Moreover, no error message is displayed and even the customized Reverse Engineering performed with KRM JDBC(Jython) does not deliver any Datastores. This is confirmed by consulting the Reverse Log file which indicates no table or column names whatsoever.
Note : The connection name for the Data Server entry is used as the values for the 'Owner (Schema)' and 'Owner (Work Schema)' fields of the Physical Schema entry.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.