This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:oracle:environments [2011/03/30 20:12] doc |
integration:rdbms:oracle:environments [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| [[integration:rdbms:oracle:databases|Databases]] | | [[integration:rdbms:oracle:databases|Databases]] | | ||
| [[integration:rdbms:oracle:tables|Tables]] | | [[integration:rdbms:oracle:tables|Tables]] | | ||
| + | [[integration:rdbms:oracle:constraints|Constraints]] | | ||
| + | [[integration:rdbms:oracle:datatypes|Datatypes]] | | ||
| [[integration:rdbms:oracle:queries|Queries]] | | [[integration:rdbms:oracle:queries|Queries]] | | ||
| [[integration:rdbms:oracle:updates|Updates]] | | [[integration:rdbms:oracle:updates|Updates]] | | ||
| - | [[integration:rdbms:oracle:storedproc|Stored Procedures]] | | ||
| [[integration:rdbms:oracle:example|Example]] | [[integration:rdbms:oracle:example|Example]] | ||
| Line 31: | Line 32: | ||
| === Generating an Omnidex Environment File === | === 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. | + | 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:home|EXTRACT]] statement is used to connect to the Oracle database, query the underlying schema information, and generate the appropriate statements. This statement can be issued through OdxSQL, or through any ODBC or JDBC application. |
| - | + | ||
| - | 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> | <code> | ||
| extract DDL | extract DDL | ||
| for ORACLE | for ORACLE | ||
| - | to "star.sql" | + | to "simple.sql" |
| with VERSION="11" | with VERSION="11" | ||
| - | USERNAME="star" | + | USER="simple" |
| - | PASSWORD="star" | + | PASSWORD="simple" |
| + | DATABASE="simple" | ||
| INDEX_DIRECTORY="idx" | INDEX_DIRECTORY="idx" | ||
| </code> | </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: | + | The following options from the [[dev:sql:statements:extract:home|EXTRACT]] SQL statement are used to provide Oracle connection information and control the output of the statement. These options also correlate with the options of the [[dev:sql:statements:create_database:home|CREATE DATABASE]] statement. |
| == VERSION == | == VERSION == | ||
| - | The major version of Oracle. Currently, Oracle versions "10" and "11" are supported. If this option is omitted, then ?? is done. | + | The major version of Oracle. Currently, Oracle versions "10" and "11" are supported. This option is required. |
| - | == USERNAME == | + | == USER == |
| - | 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. | + | The user to be used when accessing Oracle. One user 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 == | == 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. | + | The password to be used when accessing Oracle. This password must correspond to the user referenced in the USER option. This option is required. |
| == SERVICE == | == SERVICE == | ||
| Line 65: | Line 65: | ||
| == DATABASE == | == 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. If this option is omitted, then ?? is used as the database name. | + | 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 == | == TABLES == | ||
| Line 74: | Line 74: | ||
| 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. | 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. | ||
| + | |||
| + | === Limitations of the Omnidex EXTRACT statement === | ||
| + | |||
| + | The extracted CREATE statements represent the best translations that can be automatically generated from Oracle; however, these statements may require edits by the administrator. Edits that may be required include: | ||
| + | |||
| + | * Oracle object names, such as tables, columns, constraints or indexes, are reduced to 32 bytes in length for use in Omnidex. | ||
| + | * Most Oracle binary data is stored in NUMBER datatypes. If the NUMBER datatype is accompanied by scale and precision information, Omnidex can guess at an appropriate matching binary datatype, such as BIGINT, INTEGER, SMALLINT, TINYINT, FLOAT or DOUBLE. If scale and precision are not specified, Omnidex will necessarily use a DOUBLE datatype. For the best performance and ease of development, these datatypes should be changed to the smallest binary datatype that will accommodate the values in the column. | ||
| + | * Oracle National Character datatypes, which are commonly used to store Unicode data, are shown as CHARACTER or STRING datatype, as these are the most universal datatypes in an Omnidex application. If necessary, these can be changed to Omnidex NCHARACTER or NSTRING datatypes. | ||
| + | * Depending on the configuration of the Oracle database, some constraint information may not be available and must be added manually. | ||
| + | |||
| + | === Manually Creating an Omnidex Environment File === | ||
| + | |||
| + | An Omnidex Environment File can also be created by manually issuing CREATE ENVIRONMENT, CREATE DATABASE, CREATE TABLE and CREATE INDEX statements in OdxSQL or using ODBC or JDBC. If these statements are written to a text batch file, then that file can be submitted to OdxSQL using the USE command. | ||
| + | |||
| ===== ===== | ===== ===== | ||