Supported versions
TBD
Supported editions
Express, Standard and Enterprise.
Supported schema elements and metadata
Dataedo reads following metadata from Oracle databases.
- Tables
- Columns
- Data type with length
- Nullable
- Default value
- Virtual column specification
- Primary keys
- Columns
- Unique indexes
- Columns
- Unique constraints
- Columns
- Foreign keys
- Columns
- Triggers
- When triggered
- Script
- Columns
- Views
- Columns (see tables)
- Script
- Procedures
- Script
- Parameters
- Functions
- Script
- Parameters
- Returned value
- Dependencies
Comments
Dataedo reads and writes Oracle comments from/to following objects:
- Tables
- Columns
- Views
- Columns
Data profiling
Datedo supports following data profiling in Oracle:
- Tables
- Rows count
- Column distribution
- Distinct values
- Non-distinct values
- Empty
- NULL
- Numeric columns profile
- Minimum value
- Maximum value
- Average of values
- Variance of values
- Standard deviation
- Span as difference between min and max value
- Number of distinct values
- String columns profile
- Min value as first string in alphabetical order
- Max value as last string in alphabetical order
- Number of distinct values
- Date columns profile
- Min value as earliest date
- Max value as latest date
- Span as difference between min and max dates
- Number of distinct dates
- Top N values
- Top 10/100/1000 popular values
- All values if less than 1000 distinct
- 10 Random values
Read more about profiling in a Data Profliling documentation.
Limitations
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:
- all_constraints
- all_cons_columns
- all_objects
- all_tab_columns
- all_tab_comments
- ALL_ARGUMENTS
- ALL_CONSTRAINTS
- ALL_CONS_COLUMNS
- ALL_INDEXES
- ALL_IND_COLUMNS
- ALL_SOURCE
- ALL_TRIGGERS
- dual
Oracle Client
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
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).