Salesforce

OEE/OEM: Pica Limit is 8192 instead of 1000000

Printable View
« Go Back

Information

 
TitleOEE/OEM: Pica Limit is 8192 instead of 1000000
URL NamePica-Limit-8192-not-1000000
Article Number000183799
EnvironmentProduct: OpenEdge Replication
Version: 10.2B08, 11.2.x and later
OS: All supported platforms
Other: AdminServer, OEM, OEE
Question/Problem Description
PICA cannot be set higher than 8192 in OpenEdge Console
Database service communication area size cannot be higher than 8192
The maximum value for dbservicecommareasize has not been raised in the AdminServer/OE Console:
Invalid value for "Database service communication area size" property. Range is 4 .. 8192. Default is 64
 
Editing conmgr.properties dbservicecommareasize greater than 8192 before the AdminServer is started:
The database can no longer be seen in the OpenEdge Console 
Exception : com.progress.common.property.PropertyManager$PropertyException
   Message (throw): Juniper: Failed to load.
   Message (excp):  The following errors occurred whilst loading a property file:  In group "configuration.source.defaultconfiguration":  Invalid property value: "32768" for property: "DBServiceCommAreaSize"

Editing conmgr.properties dbservicecommareasize greater than 8192 after the AdminServer is started:
Despite the error:
[ConnectionManager]   * The following errors occurred whilst loading a property file:  In group "Configuration.source.defaultconfiguration":  Invalid property value: "32768" for property: "DBServiceCommAreaSize". 
The source database starts and -pica is set to the higher value confirmed in the lg file:
(13870) Database Service Manager - IPC Queue Size (-pica) : 32.0  MBytes.
PROMON 16. Database Service Manager, "Communication Area Size"
Steps to Reproduce
Clarifying Information
Enhancement PSC00249549 raised -pica from 8192 to 1000000 (OpenEdge 10.2B08, 11.2, and 11.3)
Error Message
Defect NumberEnhancement PSC00249549
Enhancement Number
Cause
Enhancement PSC00347955 for the AdminServer has not been implemented to support Enhancement PSC00249549 which raised -pica from 8192 to 1000000
Resolution
Upgrade to OpenEdge 11.6.3, 11.7.0 or later where the juniper.schema file used to identify the min/max values for a parameter has been updated to increase the max value of "Database service communication area size" to 1000000 for replication enabled source databases managed by the AdminServer in the configuration UI.
Workaround
To set pica higher than 8192 KB:

Method 1

When the replication enabled source database is managed by the AdminServer, 
To use a buffer for the replication AI notes greater than 8192
  1. set the dbservicecommareasize <= 8192
  2. set pica in otherargs
Example:
[configuration.source.defaultconfiguration]
    dbservicecommareasize=8192
    otherargs=-pica 32768

If the dbservicecommareasize was greater than 8192 before the AdminServer is started:
  1. Stop the AdminServer
  2. Edit DLC/properties/conmgr.properties and change the dbservicecommareasize to any value LE 8192 and set pica in the otherargs.
  3. Restart the AdminServer
Method 2

1. Copy <DLC>\java\schema.jar as schema.zip 
2. Extract com\progress\schema\juniper.schema 
3. Open it via editor and find this 

[Property.Integer.Configuration.DBServiceCommAreaSize] 
DisplayName=Database service communication area size 
Control=TextField 
Min=4 
Max=8192 
Default=64 

4. Change the Max=8192 to Max=1000000, save it 
5. Copy juniper.schema back to .zip file, rename it to schema.jar and put back to <DLC>\java 
6. Restart adminserver
Notes
Keyword Phrase
Last Modified Date3/5/2019 7:42 AM
Powered by