Did this article resolve your question/issue?



How to find what Database Startup Parameters values are used

« Go Back


TitleHow to find what Database Startup Parameters values are used
URL Name19146
Article Number000148634
EnvironmentProduct: Progress
Version: 8.x, 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
How to find the Parameters used when the Database was started
Where to find the database startup parameters used
How To Find What Database Startup Parameters Are Used
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Several methods can be used to find the Database’s Startup Parameters:
  • Data Administration (GUI) or Data Dictionary (TTY)
  • Database Log file
  • OpenEdge Console UI or (retired) Progress Explorer Tool
  • ProTools (Windows only)
  • ABL Session System Handle STARTUP-PARAMETERS Attribute (OpenEdge 10)
  • VST _servers. _SrvParam* (OpenEdge 11.5)

Data Administration (GUI) or Data Dictionary (TTY)

Navigate to: Utilities menu > Information

An editor widget is displayed with several sections. The pertinent sections are:

Currently Selected Database (database codepage and database collation)
Environment/Startup Parameters
session stream - a value of the cpstream startup parameter.
session charset- the value of the cpinternal startup parameter.  

Database Log file 

When the Database starts a Multi-user session, Progress will display in the Database log file the startup parameters that the database has acknowledged, between the following two lines:
BROKER  0: Multi-user session begin. (333)

BROKER  0: Database connections have been enabled. (10471)

Prior to OpenEdge 11.5, if PROLOG is used to truncate the lg file this information could no longer be available. Refer to Article:
OpenEdge Console UI or (retired) Progress Explorer Tool

Highlight the specific database. The properties of the default configuration will list the startup options. This information is stored in <install Directory>\properties\ file although default values that exist for unspecified startup parameters will not be written.
  1. Select Option 6: Shared Resources, or
  2. R&D > 1: Status Display > 12: Startup Parameters 
ProTools (Windows)

Use the Session icon to present a dialog that displays all client session attributes. There is no information about the connected database(s).

ABL Session System Handle STARTUP-PARAMETERS Attribute (OpenEdge 10)

_db-xl-name FORMAT "X(15)" LABEL "Db codepage"
_db-coll-name      FORMAT "X(15)" LABEL "Db collation"

When working with Dataservers (Oracle, Progress/400, etc., replace the FIND with a FOR EACH to look at the schema holder and foreign database settings.

The code can be extended to display additional SESSION ATTRIBUTES such as CPCASE, CPLOG, CPPRINT, DATE-FORMAT, etc. and FUNCTIONS DBCODEPAGE(n) and DBCOLLATION(n). Refer to the extended code example in Article: VST Queries: _Startup or _DbParams, _Servers

VST queries can be queried from a shared-memory or client-server connection to the database.
Last Modified Date11/20/2020 7:16 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.