Kbase P60732: APW, BIW, AIWs, quiet points not available when Oracle DataServer 9.1C is installed with Enterprise
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Oracle DataServer
Progress 9.1C
SYMPTOM(s):
Getting error 4966 when trying to start Asynchronous Page Writers
This version of PROGRESS does not support Asynchronous Page Writers (proapw). (4966)
Getting error 4967 when trying to start Before-Image Writers
This version of PROGRESS does not support the Before-Image Writer (probiw). (4967)
Getting error 4968 when trying to start After-Image Writers
This version of PROGRESS does not support an After-Image Writer (proaiw). (4968)
Getting error 8572 when trying to use quiet points
This version of PROGRESS does not support quiet points. (8572)
Enterprise Database license and Oracle DataServer license is installed within the same cfg file
CAUSE:
Bug# 20010709-025
CAUSE:
In Progress 9.1C, Oracle DataServer has included the Workgroup Database Server bits within it's license. Prior to Progress 9.1C, the only database licensing bit that was installed with Oracle DataServer was Personal Database. Because of this change in 9.1C, user is limited/restricted to the functionality and/or the capability of the WorkGroup Database license even when Enterprise Database license is installed. Refer to Solution 15340, "Differences between the Progress Workgroup Database Server licence and the Enterprise Database Server licence" to understand the limitations of WorkGroup Database license.
FIX:
You have two options.
Option 1. Upgrade to the latest Progress 9.1C Patch, or Progress 9.1D or higher.
Option 2. Separate the two licenses in current version.
There are two ways to accomplish this:
1) Maintain two different installation directories for Progress 9.1C, and make sure you do NOT keep the Enterprise Database Server and the ORACLE DataServer together in the same install. You might have one directory for the ORACLE DataServer, with all the other products in another directory, for instance.
NOTE: This is not an option for Windows installations, where you cannot install the same Progress version in more than one directory.
2) Maintain two different progress.cfg files and set PROCFG to the appropriate one, depending on the task you wish to perform. For instance, you might install the Enterprise Database Server first, then copy the file progress.cfg to another location or to the same location with a different name, and then install the other products you need to install.
For the two options, point the DLC to the correct installation directory and PROCFG to the correct configuration file, depending on the task you need to perform.
If you use the scripts proserve, proapw, probiw, proaiw and proquiet, you might want to set PROCFG (to the configuration file with the Enterprise Database Server license) in the scripts itself. This will not work if you start the database from Progress Explorer or dbman. Make sure PROCFG is at the beginning (near the DLC variable setting).