Table of Contents:
Oracle 9i R1, 9i R2, 10g R1, 10g R2, 11g R1, 11g R2, 12c R1, 12c R2.
Express, Standard and Enterprise.
Supported schema elements and metadata
Dataedo reads following metadata from Oracle databases.
- Data type with length
- Default value
- Virtual column specification
- Primary keys
- Unique indexes
- Unique constraints
- Foreign keys
- When triggered
- Columns (see tables)
- Returned value
Dataedo reads and writes Oracle comments from/to following objects:
Following schema elements currently are not supported:
- Check constraints (vote)
- Non unique indexes (vote)
- Materialized views (planned)
- Packages (planned)
- Primary keys on views (planned)
- Indexes on views (planned)
- Foreign keys with views (planned)
Required access level
Importing database objects requires certain access level in documented database. User specified in "Import objects from database" window should at least have "Connect" role, and "Create session" system privilege.
Importing objects definition from different schema requires either SELECT_ANY_DICTIONARY (recommended) or SELECT permission on any table and view and EXECUTE permission on any procedure and function that are to be documented.
No data is altered in source database during a synchronization process.
Following objects are accessed during schema import process:
To connect to Oracle you need to have Oracle Client software installed on PC that you are connecting to Oracle database from.
Supported client software:
9i or newer.
tnsnames.ora configuration file is not used.
32 vs 64 bit
Dataedo release includes 2 executables - 32 bit and 62 bit. Connecting to Oracle requires using the same architecture as your Oracle client. It is not determined by the architecture of workstation Windows.
If you have 32 bit Oracle client run Dataedo (32 bit).
If you have 64 bit Oracle client run Dataedo (64 bit).