Kbase P93421: Progress and ORACLE permissions
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/11/2004 |
|
Status: Unverified
GOAL:
Progress and ORACLE permissions
FIX:
When you create or update a schema holder for an ORACLE database, you must be able to connect to the database and have SELECT privileges on specific system objects. SELECT privileges on system objects are required because the Progress Data Dictionary cannot access the data dictionary tables in the ORACLE database without them; it must access those tables to create a schema holder.
To connect a schema holder for an ORACLE database, you must provide a valid user ID and password combination for ORACLE at connection time. Use the User ID (-U) parameter to provide the user ID and the Password (-P) parameter to provide the password.
When Progress performs a schema pull, it reads ORACLE's SYS.* tables. Those tables are the actual schema tables that describe ORACLE's tables, indexes, stored procedures.
Here's a full list of those tables:
sys.argument$
sys.col$
sys.com$
sys.con$
sys.dual
sys.icol$
sys.ind$
sys.link$
sys.obj$
sys.procedure$
sys.seq$
sys.syn$
sys.tab$
sys.ts$
sys.user$
sys.view$
In order to allow an ORACLE user to read those tables, the user needs at least SELECT privileges on ALL those tables.
Once you have set up the schema holder, the required ORACLE privileges vary among users depending on their applications. For example, the user running a Progress application that queries, but does not update, a table in the ORACLE database must connect to the ORACLE database with a user and password that provides at least SELECT privileges on the table.
Note that in addition to the permissions required by the applications that users run, users must have SELECT permission on the sys.dual system table.
In summary, the user ID and password combination required to run an application depends on:
- The ORACLE database tables the application accesses
- The type of access required on those tables
A database administrator has to establish all user ID and password combinations within ORACLE with an ORACLE product, such as SQL*DBA.