Kbase P378: Error 328 6483 received during schema pull
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/03/2010 |
|
Status: Verified
SYMPTOM(s):
Error 328 6483 received during schema pull
Please also verify you have SELECT privileges on the needed system tables and the proper version of ORACLE was selected when the schema holder was created (328) (6483)
Please also verify you have SELECT privileges on the needed system tables and the proper version of ORACLE (7 or 8) was selected when the schema holder was created (328) (6483)
Error seen when pulling oracle schema into schema holder.
Error seen when trying to update schema holder.
FACT(s) (Environment):
ORACLE database links are not present
User has DBA privileges
All Supported Operating Systems
Progress/OpenEdge Versions
CAUSE:
Connected using a Oracle user id and performing schema pull without sufficient privileges for system objects needed to perform this operation. DBA privileges are not enough.
FIX:
Set the necessary Oracle permissions in order for DataServer to connect and access information within schema holder.
To create schema holder, the user needs to have SELECT privilege on following system objects:
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.user$
sys.view$
sys.ts$
To determine which tables are missing SELECT privileges, you need to log into the Oracle tools as the user that you are using to create the schema holder. You then need to run SELECT statements similar to the following on each of the required tables. If the command displays data then the user has SELECT privileges, however if if generates an error saying that you do not have permission to run that command then you need to grant SELECT permissions on this table:
select * from sys.argument$;
Once you have determined all of the tables that are missing SELECT privileges, you need to logout and re-login as a DBA user (like the "sys" user) and grant the required privileges to the user that will be creating the schema holder (in this example, the username is "myuser"). You will need to run a command similar to the following for each table that was missing SELECT privileges:
grant select on sys.argument$ to myuser;