Kbase P744: Use SQLNet/Net8 to resolveError 6067 with 8.3x client to 7.x Oracle Dataserver Broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 7.x
Progress 8.3
Oracle DataServer
SYMPTOM(s):
Please verify the -VO startup parameter specifies the proper version of Oracle that you are using. Please also verify you have SELECT privileges on the needed system tables. (6067)
Error 6067 occurs when creating a new schema holder
Progress 8.3 client is running on one machine
Progres 7.x Oracle DataServer _probrkr/_orasrv process is running on another machine
Progress 8.3 client connects to Oracle DataServer V7 broker through H, S, N
Can not upgrade the Oracle DataServer to Progress 8.x
CAUSE:
Starting in Progress 8.3 ORACLE DataServer relies on code in the Progress version 8 server (probrkr/_orasrv) when checking the schema against the ORACLE system tables. This functionality is to support the fact that Progress 8.3 supports both ORACLE 7 and ORACLE 8.
When an older version of the probrkr/_orasrv, such as Progres 7.x is used, error 6067 is displayed since this older process does not verify the schema check of the system tables.
FIX:
Use ORACLE SQL*NET to connect to ORACLE instead of using Progress networking, this avoids the use of the probroker completely, so v7 probrkr will not be involved. You will have to install ORACLE SQL*NET and dataserver license on the client machine and configure SQL*Net to connect to remote Oracle instance.