Oracle Access Requirements
Before you can access Oracle, the following conditions must be met:
• The correct version of Oracle must be in the PATH and accessible.
UNIX:
This condition requires both the binary path and shared library path be set correctly, and that read and execute permissions be granted to access the Oracle installation files. Assigning the 'ingres' operating system user ID to the operating system user group called 'oinstall' can satisfy this requirement.
Note: Running sqlplus from a shell (UNIX) or command prompt (Windows) shows whether Oracle is currently in the PATH.
• User logins must be defined to the Oracle instance.
• Permission must be granted to access each Oracle database.
• The ingres user must be granted the following permissions:
– DBA
– connect
– resource
• Non-privileged users must be granted the following permissions:
– connect
– resource
• If database events are to be used with the Oracle gateway, the DBMS_ALERT package must be installed. For more information about using the Supplied PL/SQL packages, see the Oracle documentation. For more information about using the dbevent support in the Oracle gateway, see Developing Portable Applications.
• Enterprise Access 3.0-to-Oracle does not support multitenant container databases (CDBs) introduced in Oracle 12c. To use Enterprise Access 3.0 with an Oracle 12c DBMS, the database must not be a CDB.
Grant User Permissions (Oracle)
The following example shows how to create an appropriately privileged DBMS user 'ingres' with the password 'ingres' and a non-privileged DBMS user 'fred' with the password 'secret'.
To grant permissions
1. Connect as a database administrator to the Oracle instance
2. Assign the permissions as follows:
grant dba, connect, resource to ingres identified by ingres;
grant connect, resource to fred identified by secret;