This shows you the differences between two versions of the page.
|
integration:rdbms:oracle:databases [2011/04/04 02:50] 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:datatypes|Datatypes]] | | ||
| - | [[integration:rdbms:oracle:indexes|Indexes]] | | ||
| - | [[integration:rdbms:oracle:queries|Queries]] | | ||
| - | [[integration:rdbms:oracle:updates|Updates]] | | ||
| - | [[integration:rdbms:oracle:example|Example]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Databases ==== | ||
| - | |||
| - | The [[dev:sql:statements:create_database:home|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 in the previous section. | ||
| - | |||
| - | The CREATE DATABASE statement must include the database name, the Oracle version, and the Oracle user and password. | ||
| - | |||
| - | <code> | ||
| - | create database "SIMPLE" | ||
| - | type oracle | ||
| - | version "11" | ||
| - | user "myuser" | ||
| - | password "mypassword" | ||
| - | index_directory "idx" | ||
| - | in "simple.xml"; | ||
| - | </code> | ||
| - | |||
| - | === Using SQL*Net === | ||
| - | |||
| - | Omnidex is frequently installed on a separate server than the Oracle database. In fact, this is preferable since it allows both Omnidex and Oracle to operate at their best without competing for resources. This means that Omnidex often accesses the Oracle database through SQL*Net. When using SQL*Net, simply state the name of the SQL*Net service in the SERVICE clause. | ||
| - | |||
| - | <code> | ||
| - | create database "SIMPLE" | ||
| - | type oracle | ||
| - | version "11" | ||
| - | user "myuser" | ||
| - | password "mypassword" | ||
| - | service "simple" | ||
| - | index_directory "idx" | ||
| - | in "simple.xml"; | ||
| - | </code> | ||
| - | |||
| - | === Oracle Security === | ||
| - | |||
| - | Omnidex uses a single user and password to access an Oracle database. Oracle database administrators should provide an appropriate user and password that gives access to all of the database objects referenced in the Omnidex Environment Files. | ||
| - | |||
| - | When connecting to an Omnidex Environment File, it is generally not possible to pass different user and passwords dynamically; however, there is an exception to this rule. The user and password can reference [[appendix:reference:envvar:home|environment variables or shell commands]]. This can provide a rudimentary mechanism for providing dynamic user and passwords. Care should be taken when using this approach, though. All users passed should have access to all database objects declared in the Omnidex Environment File, and should also have access to all rows in the tables. | ||
| - | |||
| - | |||
| - | ===== ===== | ||
| - | |||
| - | **[[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}} | ||