Kbase P745: Create a new Schema holder to resolve Error 6067 with 8.3A Client to 7.x Oracle Dataserver _probrkr
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 7.x
Progress 8.3x
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 is seen when creating a new schema holder from the 8.3x client machine
Progress 8.3x client on one machine
7.x Oracle DataServer broker on another machine
8.3C Client connecting via H, S, N to 7.x Oracle _probrkr
Cannot upgrade to Progress 8.3A, therefore can not use the 8.x Oracle DataServer broker, _probrkr.exe
User does not have access to SQL/NET nor any other Oracle Client on the machine where Progress V8.3x client is installed
CAUSE:
The Progress 8.3A ORACLE DataServer relies on code in the Progress version 8 server (probrkr) when checking the schema against the ORACLE system tables. This functionality is to support the fact that Progress 8.3A supports both ORACLE 7 and ORACLE 8.
When an older version of the probrkr, such as Progres 7.x broker, is used error 6067 is displayed since this older broker version does not verify the schema check of the system tables.
FIX:
1. Create a schema holder from the machine where V7 Oracle dataserver is installed
2. Create the an empty Progress 8.3A schema holder on the machine where Progress V8.x client is installed.
3. Dump the .df of the schema holder on the V7 broker machine and load definitions into the newly created SH on V8 client machine.