This shows you the differences between two versions of the page.
|
integration:rdbms:oracle:databases [2011/03/30 21:10] doc |
integration:rdbms:oracle:databases [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Integration: Relational Databases ====== | ||
| - | |||
| - | ===== Oracle ===== | ||
| - | |||
| - | [[integration:rdbms:oracle:home|Overview]] | | ||
| - | [[integration:rdbms:oracle:environments|Environments]] | | ||
| - | **[[integration:rdbms:oracle:databases|Databases]]** | | ||
| - | [[integration:rdbms:oracle:tables|Tables]] | | ||
| - | [[integration:rdbms:oracle:queries|Queries]] | | ||
| - | [[integration:rdbms:oracle:updates|Updates]] | | ||
| - | [[integration:rdbms:oracle:storedproc|Stored Procedures]] | | ||
| - | [[integration:rdbms:oracle:example|Example]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Databases ==== | ||
| - | |||
| - | The [[dev:sql:statements:create_database|CREATE DATABASE]] statement is used to declare an Oracle database within an Omnidex Environment File. This statement can either be issued directly, or it can be extracted from Oracle using the EXTRACT statement as discussed | ||
| - | |||
| - | Databases in Omnidex are of a particular type, and the type , such as Oracle, SQL Server, MySQL, ODBC or File. A database that accessThe CREATE DATABASE Omnidex Environment File contains metadata that describes the Oracle database and the Omnidex configuration. This includes the following connection and schema information: | ||
| - | |||
| - | * Oracle major version number (eg. 10, 11, etc) | ||
| - | * SQL*Net service information | ||
| - | * Oracle user and password | ||
| - | * Oracle schema information tables, columns and datatypes | ||
| - | * Oracle primary and foreign key constraints | ||
| - | * Oracle native indexes | ||
| - | |||
| - | === Generating an Omnidex Environment File === | ||
| - | |||
| - | Omnidex can automatically generate the CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE and CREATE INDEX statements needed for an Omnidex Environment File. The [[dev:sql:statements:extract|EXTRACT]] statement is used to connect to the Oracle database, query the underlying schema information, and generate the appropriate statements. | ||
| - | |||
| - | The extracted CREATE statements represent the best translations that can be automatically generated from Oracle; however, these statements may require edits by the administrator. The documentation on [[integration:rdbms:oracle:databases|Databases]] and [[integration:rdbms:oracle:tables|Tables]] describe specific areas where edits may be required. | ||
| - | |||
| - | <code> | ||
| - | extract DDL | ||
| - | for ORACLE | ||
| - | to "star.sql" | ||
| - | with VERSION="11" | ||
| - | USERNAME="star" | ||
| - | PASSWORD="star" | ||
| - | INDEX_DIRECTORY="idx" | ||
| - | </code> | ||
| - | |||
| - | The EXTRACT statement has several options that supply the connection information and determine the metadata to be extracted. For Oracle, the following options can be used: | ||
| - | |||
| - | == VERSION == | ||
| - | |||
| - | The major version of Oracle. Currently, Oracle versions "10" and "11" are supported. This option is required. | ||
| - | |||
| - | == USERNAME == | ||
| - | |||
| - | The username to be used when accessing Oracle. One username and password is used when connecting to the Oracle database. That login determines that security access to the database and the visibility of the underlying database objects. This option is required. | ||
| - | |||
| - | == PASSWORD == | ||
| - | |||
| - | The password to be used when accessing Oracle. This password must correspond to the username referenced in the USERNAME option. This option is required. | ||
| - | |||
| - | == SERVICE == | ||
| - | |||
| - | If SQL*Net is to be used to access the Oracle database, then the SERVICE option contains the SQL*Net service name. If this option is omitted, then SQL*Net is not used. | ||
| - | |||
| - | == DATABASE == | ||
| - | |||
| - | The DATABASE option controls the logical database name to be recorded in the Omnidex Environment File for this database. This is not an Oracle setting, but rather a logical name given to the database for use in Omnidex statements. This option is required. | ||
| - | |||
| - | == TABLES == | ||
| - | |||
| - | The TABLES option controls the table schema information to be extracted from Oracle. The TABLES option can include a comma-separated list of tables, "USER.*" to extract all tables for a named user, or "*" to extract all tables. If this option is omitted, then all available tables are extracted. | ||
| - | |||
| - | == INDEX_DIRECTORY == | ||
| - | |||
| - | The INDEX_DIRECTORY option declares the directory to contain the Omnidex indexes. This is not an Oracle setting, but rather path designation where indexes should be built. This directory can include either absolute or relative path designations. If this option is omitted, then the indexes will be built in the same directory as the Omnidex Environment File. | ||
| - | |||
| - | |||
| - | ===== ===== | ||
| - | |||
| - | **[[integration:rdbms:oracle:environments|Prev]]** | | ||
| - | **[[integration:rdbms:oracle:tables|Next]]** | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:integration:rdbms:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||