Progress OpenEdge 11.2.0 Readme

Ports: All
Date: February, 2013
Copyright (c) 1984-2013 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.

Read these On-line Release Notes

It is important to read these on-line release notes. They are the
exclusive release notes for this release.

The on-line release notes are on the distribution medium as one text file, readme.txt.

The readme.txt file includes a list of known issues followed by a list of the issues fixed in this release.

In addition, the distribution medium includes the following HTML report files which list the issues addressed
in this release -  organized by version, issue number (CR ID), or product component.

  * PROGRESS_OE_<release#>_VERSION.htm (Lists fixed issues by Version)
  * PROGRESS_OE_<release#>_ISSUE.htm (Lists fixed issues by Issue Number)
  * PROGRESS_OE_<release#>_COMPONENT.htm (Lists fixed issues by Component)



1. Installation
2. ABL
  Language Issues
  Web Services client
3. Adapter for Sonic ESB
4. ADE Tools and Runtime
  Data Dictionary
  GUI Rendering
  Translation Manager
  Web Rendering
5. AppServer
6. Database
  Database Utilities
  Failover Clusters
7. DataServers
8. Documentation
  Electronic Documentation
  Progress Developer Studio for OpenEdge
9. Graphical User Interface
10. Management
11. OE Mobile
12. Open Client
  Web Services Provider
13. OpenEdge GUI for .NET
14. OpenEdge Replication
15. Porting
16. Progress Developer Studio for OpenEdge
  AppBuilder Support
  Visual Designer
17. REST
18. SQL
19. Web Services Client
20. WebClient
21. WebSpeed

Installation -

Note: OE00121569    Type: Limitation
OpenEdge installation may install Sonic client and container code
RN#: 101A-00291
The OpenEdge installation program may install Sonic Software client and
container code depending on which products get installed. Because the
installation program requires it run as ROOT on Unix, the Sonic Software code
gets installed with those permission set. The OpenEdge installation program
attempts to set the correct permissions for the Sonic code, but this fails on
the HPUX operating system. This will cause the Sonic ESB Container created by
OpenEdge to fail when started unless it is started as ROOT. To resolve this,
run the command 'chmod -R o+w *' from $DLC/sonic as ROOT.

Note: OE00163769    Type: Workaround
Unknown Publisher message with a Netsetup Install
After performing a Netsetup install on Windows the user may see an Unknown
Publisher message when running any OpenEdge .EXE files from a network drive. To
resolve this issue, add the network drive share to the client's trusted zone.

To add the network drive to your trusted zone:

1. Open the Internet Options Dialog Box from an Internet Explorer session.
2. Select the Security Tab.
3. Select the Local Intranet icon from the zones shown.
4. Click the Sites command button, which opens a Local Intranet Dialog Box.
5. Click the Advanced command button, which opens a dialog box where you
add and remove websites from your intranet.
6. Add \\servername\ to the list of websites. Click Close, then OK to return to
the main Internet Options Dialog Box.

You may have to reboot the client for this to take effect.

Note: OE00168104    Type: Known Issue
Sonic container startup shortcut requires quotes for directories with spaces
If you install OpenEdge into a directory with a space in the name (e.g.
C:\Program Files\OpenEdge), the shortcut to start up the sonic container does
not function properly. You can fix the problem by editing the shortcut and
enclosing the Target: and Start in: fields in double quotes.

Note: OE00187147    Type: Known Issue
The WebClient One-Click install fails as a Non-Admin User
The WebClient One-Click install (OCI) (over-the-web install) fails when run by
a non-admin on a system that does not already have the Installshield Setup
Player installed as an Add-On. For this to work, the add-on must already be
installed/registered by an Administrator. Running the WebClient One-Click
install as Administrator just one time will get the Setup Player installed.
After this is done the WebClient One-Click install can be run as a
Non-Administrator. This issue only occurs when installing Over-the-Web. This
issue does not occur when running the WebClient installation directly via the
setup.exe file.

Note: OE00213877    Type: Limitation
Slow Webclient installation on the Windows 2003 Server
While installing WebClient on the Windows 2003 Server, the progress bar might
reach 90% and then stop for more than 20 minutes before completing the
installation. This happens for the non-administrator group users.

Installation - Install

Note: OE00147494    Type: Known Issue
Installation of Failover Clusters -- Windows
You must ensure there are no active instances of the Cluster Administrator
utility prior to installation. To do this, use the Windows Task Manager to
check for processes running the cluadmin.exe image.  If a user associated with
an instance of the Cluster Administrator is not readily identifiable, these
processes can be forcefully terminated as follows:

1. Within Task Manager, select the cluadmin.exe process and press the End
Process button.

2. Answer yes to the popup dialog asking if you really want to terminate
the process.

Failure to shut down all instances of the Cluster Administrator tool results in
a partial installation and fails to properly register the resource and
administrator extension DLLs, causing cluster management to fail.

Note: OE00163889    Type: Known Issue
.Net Framework not installed with unknown default language
Progress Developer Studio and OpenEdge Advanced UI Controls have a dependency
on the Microsoft .NET Framework v4.0.

The OpenEdge installation media includes the English version of the Microsoft
.NET Framework, and the OpenEdge installation process will automatically
install the framework if it is not already your system, provided that your
system's locale is set to English.

If the locale on your system is set to something other than English and the
.NET Framework 4.0 for your locale is not already installed, then Progress
Developer Studio and OpenEdge Advanced UI Controls do not install properly.
OpenEdge will not install the English version of the .NET Framework when the
system locale is not English, and the Advanced UI controls will not install
without the .NET Framework installed.

To work around this problem, install the Microsoft .NET Framework v4.0 for your
locale, prior to installing OpenEdge.

To download different languages of the .NET Framework 4.0 as well as the
Windows 64-bit version:
  - Login to
  - Choose "Progress OpenEdge Deployment Components"
  - Choose "Microsoft .NET Framework" download page

Note: OE00201877    Type: Limitation
OpenEdge support on Windows XP
OpenEdge supports Windows Service Pack 3 and later for the Windows XP platform.

Note: OE00230691    Type: Known Issue
Web Server Type install options are not for the installed Apache Tomcat
This OpenEdge release includes an installed Apache Tomcat Web server. When
installing OpenEdge, note that the Web Server Type install options are for
WebSpeed only, which the installed Tomcat Web server does not support.

Note: OE00230871    Type: Known Issue
File missing while installing Mobile REST Management Agent
When you try to install the Mobile REST Management Agent, the installer
displays an error message stating that it could not find the file ini2reg.exe.
Ignore the message: the component still installs properly.


Note: OE00199964    Type: Behavior Change
STOP in handler for named event now undoes transaction and terminates PUBLISH
The AVM now correctly honors a STOP condition raised in a handler for a named
event: No subsequent handlers run for that instance of PUBLISH, changes made in
the active transaction are undone, and execution continues at the closest
enclosing block that has an ON STOP phrase (or the startup procedure). This
behavior change corrects an issue found in previous OpenEdge releases, whereby
if multiple event handlers were subscribed to a named event, and the STOP
condition was raised in a handler that ran prior to the last handler, the
subsequent handlers ran and no changes were undone in handlers other than the
one in which the STOP occurred. Note that this issue affected only events
raised by the PUBLISH statement. Handlers for strongly typed OO-ABL events were
not subject to the issue, and their behavior is unchanged.

ABL - Internationalization

Note: OE00073374    Type: Known Issue
Thai characters or complex scripts do not display in command prompt or console
The Windows command prompt or console is not enabled for Thai characters or
complex scripts on any version of Windows (XP, Vista or Windows 7).

When trying to read Progress messages sent to the Console while using Thai or
complex scripts, you can:

* Use the English PROMSGS file.

* Use the Thai character or complex script PROMSGS file, but pipe the output of
the command to a file that can be read by any Windows editor.

Note: OE00125227    Type: Behavior Change
Pasting Unicode text into GUI widgets might require font and codepage changes
For the GUI client (prowin32.exe), text widgets such as editors and fill-ins
are Unicode-enabled. If you enter characters into these widgets that are not
supported by the font in use or are not available in the -cpinternal codepage,
the widget value might contain a question mark (?).

For example, if the user were to copy a quoted string from another
Unicode-enabled application, the double quotes copied might be U+201C and
U+201D, the left and right double quotation marks respectively. When copying
these into an OpenEdge editor, the quotation characters might not display
correctly in the editor, and might be converted to question mark (?) when
accessing the value of the editor.

The default font OpenEdge uses for widgets is MS Sans Serif. MS Sans Serif does
not provide a visual representation for these quotation characters. Changing
the editor's font to Courier New instead will allow the characters to display

Many customers use ISO8859-1 as the -cpinternal codepage. The ISO8859-1
codepage does not contain these quotation characters, so they will be
converted to "?" when accessing the value of the editor. Changing -cpinternal
to 1252 instead of ISO8859-1 will allow these characters to be displayed

You should set your font and -cpinternal codepage according to the
characters you will be using in your application.

Prior to OE10, the GUI client used ANSI widgets. If non-ANSI characters
were pasted to ANSI widgets, Windows would provide a conversion from
these characters to ANSI characters. The characters were visually
similar, but not the same.

ABL - Language Issues

Note: OE00147609    Type: Known Issue
CAN-FIND X field-list problem
The FIELDS clause does not guarantee the inclusion or exclusion of fields in
any given query.  The AVM may require additional fields, for example, to
accommodate a key value required by an index.

The application must not reference fields that are missing from the FIELDS
list. In most cases when this occurs a run-time error is generated indicating
that the field is unavailable.

There are situations, for example with a function that includes the NO-ERROR
attribute by default, where it is legitimate to satisfy function requirements
using a field that is missing from the FIELDS list.  Such instances equate the
missing field to the Unknown value (?) or null (for DataServers) in order to
resolve an expression. In other words, the ABL attempts to detect missing
fields with run-time errors where possible. However, there are cases where it
is legitimate to use a missing field in an expression. In such cases, the
missing field will resolve to the Unknown value (?) or native data source null.

Note: OE00147778    Type: Limitation
INT64 ActiveX support requires oleaut32.dll version 5.1.2600.2180 or later
To support the INT64 data type with ActiveX controls or ActiveX Automation
objects, C:\windows\system32\oleaut32.dll must be version 5.1.2600.2180 or
later. If your application uses an earlier version of oleaut32.dll and a
parameter of INT64 data type is passed to a COM object, the results are
unpredictable and may result in an error.  This is true even if it is an input
parameter and the number in the variable is within the 32-bit range.
Therefore, if you do not have the correct version of oleaut32.dll, you should
not use the INT64 data type with COM objects.

Note: OE00221998    Type: Behavior Change
Decimal PAUSE interval is no longer rounded to nearest integer
The AVM now processes the PAUSE interval (specified by "n" in a "PAUSE n"
statement) accurately to the nearest millisecond. For example, for "PAUSE 0.6",
the AVM now suspends processing for 600 milliseconds, whereas in previous
releases the value was rounded up to 1 second.

ABL - Web Services client

Note: OE00147860    Type: Known Issue
Xmethods Web services used for demonstration in samples
This product and accompanying documentation contain references to the Weather -
Temperature and StockQuotes XMethods Demo services provided by XMethods, Inc.
( Copyright 2003 XMethods, Inc.  All rights reserved. Any use
of these services by you shall be for demonstration purposes only.

Adapter for Sonic ESB -

Note: OE00192621    Type: Limitation
Agents remain locked when ESB Adapter returns a Fault in Sonic Workbench
When using the OpenEdge Adapter for Sonic ESB with a session-free AppServer and
persistent procedures, it is important that you release the persistent
procedure when your ESB process completes, to prevent having a locked agent.

When the adapter returns a fault, you must ensure the Release operation is done
in your Fault process. This requires you to keep track of your process ID and
have access to it in your Fault process.

In the Progress Developer Studio for OpenEdge/Sonic Workbench development
environment, Sonic intercepts all fault returns so that it can display the
result.  Consequently, Fault processes are never run. Setting the Command
Parameter ESB Fault Return Mode to "Continue Process with Fault"  discards the
original message where your Procedure ID is stored, so this is not a viable

To free up locked agents on the AppServer, you must restart your development

Using Persistent Procedures within Sonic ESB processes is discouraged because
it greatly complicates the handling of Faults and makes your session-free
AppServer operate no differently than a session-managed AppServer.

Note: OE00215955    Type: Behavior Change
Connnection string limitation for session-managed native ESB Adapter
The combined length of the connection string (composed of  a user-id, password,
and information fields) must not exceed 30,000 non-Unicode characters when
connecting to an AppServer. Exceeding the string length causes an AppServer

ADE Tools and Runtime -

Note: OE00108492    Type: Behavior Change
Generic comment deletion code removed from triggers
Deletion triggers have been updated to not generically remove comments,
security allocation and multi-media records due to performance impact. A new
ERWin trigger template db/af/erw/afercustrg.i has been provided that customers
can use to re-generate their own triggers without the generic deletion code.
Customers can also update their triggers with specific code to do the deletion
in such a specific way that should not have any performance impact.

ADE Tools and Runtime - Data Dictionary

Note: OE00126947    Type: Behavior Change
Mandatory fields are not marked as NOT NULL during protoodbc
When running a pro-to-odbc migration against a DB2 data source, fields marked
as "mandatory" in the OpenEdge database were being created in generated SQL
script and the foreign data source without the NOT NULL syntax.  This leads to
a situation where these fields are null capable in the foreign database.

To make DB2 consistent with the MS SQL Server and Oracle DataServers, the
OpenEdge DataServer for ODBC will now set the NOT NULL constraint on SQL
columns derived from mandatory fields for DB2 data sources.

Note: OE00168857    Type: Known Issue
Initial value rules for logical fields in the GUI Dictionary
By default, when you create a logical field through the GUI Data Dictionary, it
sets the Initial Value as the first value in the Format. For example, if the
Format is "male/female", the Initial value defaults to male. The exception to
the first item rule is when the format is "yes/no" or "true/false". For those
cases, the tool uses the OpenEdge default value for a logical field, "no" and
"false", respectively.

Note: OE00210034    Type: Product Notice
Changes in Database Administration utility menu options
The Database Administration utility menu options have changed:

For dumping and loading, the menu option previously titled "
Security Authentication Records", is renamed to "Security Domains".  For
   Admin -> Dump Data and Definitions -> Security Domains
   Admin -> Load Data and Definitions -> Security Domains

For database options (Admin -> Database Options...), the name of two options
have changed:
- "Use Application User Id for Auditing" is renamed to
  "Use Application Domain Registry"
- "Disallow Blank UserId" is renamed to "Disallow Blank UserId Connections"

For security, the menu options and labels have changed.
- "Authentication System Maintenance" is renamed to "Domain Maintenance",
   as shown:
   Admin -> Security -> Domain Maintenance
- "Security Authentication Systems" is simplified to "Authentication Systems",
   as shown:
   Admin -> Security -> Domain Maintenance -> Authentication Systems
- "Authentication System Domains" is simplified to "Domains", as shown:
   Admin -> Security -> Domain Maintenance -> Domains
- The new title of the dialog box is "Domains".
- Field names on the Domains -> Create dialog box are changed:
    "Type" is renamed to "System Type"
    "PAM Options" is renamed to "System Options"

ADE Tools and Runtime - Deployment

Note: OE00088123    Type: Known Issue
Notes on using the Deploy Static Objects tool
When deploying static objects using the Deploy Static Objects tool, please note
the following:

1) You must specify the following extra directories in the Deploy Static
Objects tool, in order for a standard Progress Dynamics WebClient install to



    adm2/image can be used instead of the adeicon directory, but you must manually
copy this file into the target directory. These image directories are not
required for a server install (AppServer of Web).

2) You must manually copy the adm2/dyntreew.wrx file into the target directory,
for WebClient installs.

3) You must manually copy into the target directory for a WebClient

Note: OE00116351    Type: Behavior Change
Static Object Deployment Tool - Option to generate source listing
The Deploy Static Objects tool has the ability to produce a listing file of all
the files that are packaged into a deployment produced by the tool.

The listing file is specified in the UI before the deployment starts building.
If no listing file is specified, then the listing will not be produced. A
default value is provided by the tool, and is for a file called 'listing.log'
in the session's temporary directory.

The listing file consists of the following fields, tab-delimited:
File name
Relative path
Deployment type
Design-only flag

This functionality can be used to determine which files are required for
compilation on 64-bit platforms. A Dynamics client is only supported on
Windows, which is a 32-bit platform, and customers may connect to an AppServer
running on a 64-bit platform; in such a case the code would need to be compiled
against the 64-bit platform, and the listing file will give the ability to
determine which files are required.

Note: OE00132914    Type: Behavior Change
DCU enforces MinVersion with migrations
If a setup XML file has migration setup types (defined by having a
migration_source_branch session property with a non-blank value), then a check
is performed to ensure that the DB version sequence matches that of the
MinimumVersion in the Database node of the setup_type. If these 2 versions
don't match an error is raised and a message shown.

This message is a new message and has a code of 'MSG_cannot_migrate', and
appears in the shipped setup101B.xml. If customers have created their own
setup.xml files, they need to add this message to all the setup types contained
in those XML files.

Note: OE00215883    Type: Workaround
The DynamicsVersion session property must be manually updated
If you are working in an OpenEdge release later than 10.2B, the DynamicsVersion
session property may be set to the wrong release number. This property is not
automatically updated.

To workaround this issue, modify
$DLC/src/dynamics/db/icf/dfd/update_dynamics_version_property.p so that the
value of the DYNAMICS-VERSION preprocessor is set to the relevant OpenEdge
release number (11.2, for example). Compile this file and copy to $DLC/gui,
which is important because the DCU does not run against source code.

ADE Tools and Runtime - GUI Rendering

Note: OE00020074    Type: Limitation
Print Preview and Export to Excel do not work when the data source is an SBO
Print Preview and Export to Excel options available on various browse  
toolbars are not supported for visual objects whose data sources are      
SmartBusinessObjects. These options will do nothing when chosen.

Note: OE00024747    Type: Limitation
Static data objects do not get initial value from Repository
Static SDO proxies (<sdo>_cl) do not get the INITIAL-VALUE from the
Repository's EntityField DefaultValue at run time. The temp-table's
INITIAL-VALUE attribute is a read-only attribute that is compiled into the SDO
temp-table definition from the SDO include.

Note: OE00059495    Type: Behavior Change
RowObjUpd.ChangedFields is obsolete
Prior to Version 10.0A, the RowObjUpd.ChangedFields field was used to figure
out which fields to save in an SDO. This is now obsolete and no longer used.
The SDO now figures out which fields to save to the database tables based on a
comparison of the before-image and the changed record. The ChangedFields field
is not used in any logic, except for a call to bufferCollectChanges, which
updates this field. Since it does not capture all changes, this update is not
reliable and the method will be deprecated in the future.

Note: OE00060333    Type: Known Issue
New records can be duplicated when reading new batch if added while batching
If new records are created that sort higher than the last record in the current
batch, the new record is duplicated when a batch includes the new record.

To prevent this, either ensure that the user is at the last batch when adding
the new records that will get key values that sort higher than the currently
last record or avoid batching when such records can be created.

Note: OE00061359    Type: Known Issue
WebSpeed detail program called from a WebSpeed report program hangs
A WebSpeed detail program called from a WebSpeed report program might hang when
the Add button is used a second time or the Delete button is used. If the
detail program is used separately from the report program, the problem does not

Note: OE00076414    Type: Limitation
ADM2 does not support the READ-ONLY attribute on browse columns
The ADM2 does not support setting the READ-ONLY attribute directly on browse
columns as a way to disable fields.

Field enabling is controlled by the EnabledFields property, that is, you make
columns read-only by removing them from the enabled fields list.

This is not considered to be a bug. Dynamic browser columns are all read-only
at start up, so it would be very difficult to implement a solution to detect if
the READ-ONLY attribute has been set in initializeObject.

Note: OE00087999    Type: Known Issue
Loss of data when changing page while browse is in add
When adding a new record in a browser that is part of a tabbed user interface,
the entered data can be lost or appended to the next record in the browser
under the following conditions:

- The browser is the update source for an SDO.

- The user did not enter all of the required fields in the browser row.

- The user selects a different page before saving the new record.

Note: OE00088005    Type: Limitation
A single toolbar cannot switch navigation between SDOs and SBOs
In a paged container where a SDO is the Data-source of a SBO, you cannot use a
single toolbar to navigate both the SDO and the SBO.

Note: OE00088184    Type: Limitation
Static browsers/browsers in static windows don't get Repository column labels
Browsers running in static windows linked to a static SDO on an AppServer will
not get the column-label from the Repository's EntityField. Instead, the
browser gets the column-label from the database schema. This problem also
applies to any static browser.

Note: OE00094575    Type: Limitation
Error 4054  (.. does not fit..) if ToolbarDrawDirection is "vertical"
The Dynamics layout manager does not handle toolbars where the
ToolbarDrawDirection is set to 'vertical'.

Note: OE00102910    Type: Behavior Change
Read only SDO tables can be specified to remain NO-LOCKed  during transaction
The NoLockReadOnlyTables property can hold a comma-separated list of read-only
(non-updatable) tables that should remain NO-LOCKed during the transaction. A
value of 'ALL' means that all read-only tables should remain NO-LOCKed. Note
that read-only tables defined by this property also are excluded from the
optimistic lock check of changes.

Note: OE00104047    Type: Limitation
CallerProcedure, CallerObject, and CallerWindow are not set in createObjects
The Session Manager's launch in Progress Dynamics sets properties like
CallerProcedure, CallerObject, and CallerWindow in the launched container.
These properties are set before the container is initialized and can thus be
used in an initializeObject override. However, they are not intended for use
during the construction (the execution of the main block) of the container.

The createObjects call is typically done as part of the construction. However,
in previous releases, static non-window containers, like SmartFames and
SmartDataViewers, did call createObjects from initializeObject allowing these
properties to be used also in createObjects.

Now, createObjects is called during the construction of almost all containers.
If a createObject override uses these properties, it is unlikely to work. Any
logic referring to these properties in createObjects should be moved to an
initializeObject override instead. Moving this logic to initializeObject should
not cause any change in behaviour.

Note: OE00107469    Type: Known Issue
SmartFrame objects stored with .w in object name may need two translations
For SmartFrames or SmartWindows that are launched from a static container, the
object name for Title and Page Label translations is resolved from the
procedure:FILE-NAME without path and extension. Therefore, SmartFrame objects
that have the .w extension in their Repository object names might need two
translations, one without the extension for usage in static containers and one
with the extension for dynamic containers.

Note: OE00107568    Type: Known Issue
Error messages for child SDO not returned when CLOB involved
A detailed error message may not be returned to the client while adding a
record to a SmartDataObject under the following circumstances:

- the SDO is running on AppServer
- the SDO contains large object fields
- AutoCommit is false (commit is used to commit multiple updates at once)

The client does receive an "update cancelled" message but should have a
detailed error.  The detailed error is written to the AppServer log file.

This situation is more likely to occur with an SDO that is part of a

Note: OE00109030    Type: Behavior Change
Changes in how Dynamics Window dimension profiles store WINDOW-MAXIMIZED
Progress Dynamics windows now store the WINDOW-MAXIMIZED state together with
the previously stored dimensions in the user profile. The state is stored as a
5th entry in the profile value. In previous versions, this state just overwrote
the old profile. If you close a maximized window and no dimensions have been
saved previously, the window still stores "WINDOW-MAXIMIZED" as the only entry.

With the new behavior, a window can store the WINDOW-MAXIMIZED state without
loosing the stored dimensions for the previously saved WINDOW-NORMAL state. The
next time you launch the window, it displays maximized. But, when the
WINDOW-NORMAL state is applied, the window resumes its previously stored size.

Note: OE00109275    Type: Limitation
The SmartDataBrowser sort profile is not used with SBO data-sources
The sort profile saved for a SmartDataBrowser with a SmartBusinessObject as its
data-source is not used upon restart.

Note: OE00109286    Type: Known Issue
Translation tool does not include SmartDataBrowser search field
The optional search field of a SmartDataBrowser doesn't show up in the
translation window to allow you to add a translation.  

Note: OE00110402    Type: Known Issue
Setting of BaseQuery in initializeObject requires synchronization of QueryWhere
If any other query manipulation has been done before changes to the BaseQuery
are made, you need to synchronize QueryWhere and possibly the QueryString. If
the BaseQuery is set in an initializeObject override before SUPER, you might
also need to synchronize QueryWhere in an SDO without any custom query
manipulation. The only cases where BaseQuery can be set without synchronizing
the QueryWhere are on the client (AsDivision = 'client') and in dynamic SDOs on
the server (AsDivision = 'server'). Static SDOs calls setOpenQuery, which calls
setQueryWhere, from the main block (query.i) when connected to the database.
Dynamic objects that are connected to the database will call prepareQuery from


The BaseQuery is the design-time, fixed part of the query. It is part of the
object definition. The design philosophy is that runtime query manipulation can
be done without violating the integrity of this part of the expression.
Consequently, the BaseQuery should not be changed after any query manipulation
has been done.

However, it is quite common for applications to need to set this when an SDO
instance is launched. (For example, to filter data on department or company key
based on the userid.)

Various examples and documentation have shown and stated that this can be done
in an initializeObject override before the call to SUPER. In particular, older
documentation examples showed this being done with setOpenQuery, which also
synchronizes the physical query by calling QueryWhere. This was a problem on a
client since setQueryWhere used to always prepare the physical query.
setQueryWhere has since become more lightweight, but setOpenQuery still calls
the server and should still be avoided in an AppServer session.

Note: OE00110532    Type: Known Issue
stripLookupfields is not used in the new lookup API
In previous versions, the stripLookupFields procedure was called on each
display to figure out if the SmartDataFields could be resolved by the viewer's
DataSource. The new lookup API does not use this procedure.

Note: OE00111488    Type: Limitation
SDO Cache does not include Auditing & Comments tick-information
The data caching and data sharing support does not always cache auditing and
comment information. This information is retrieved only for certain instances
and would only be cached if the actual object that did the initial server
retrieval was set up to include this information. Data objects that retrieve
their data from the cache may thus be unable to show the correct tick-mark in
the toolbar if the initial server request did not include this information.

Note: OE00112018    Type: Limitation
Sharing data object, browse and viewer out of sync showing data
The support for SharedData does not actively refresh viewers or browse
viewports when data is changed by another DataObject. To refresh a browse, you
must currently scroll the record out of the viewport. To refresh a viewer, you
must currently navigate to another record and back. Note that a viewer on a
hidden page does not refresh itself if it is on the same record as when it was
hidden. So, in this case, it does not help to navigate to another record and
back in the browser.

Note: OE00112062    Type: Limitation
DynCombo support for a DataObject as data source does not include static SDO
The option to define an SDO DataSource for a DynCombo is not supported for
static SDOs.

Note: OE00112320    Type: Known Issue
BaseQuery must have NO-LOCK after WHERE
A child SDO loses parent filter criteria if its BaseQuery has the NO-LOCK
option before the WHERE criteria.

When two SmartDataObjects are linked in a parent/child relationship, with or
without a SmartBusinessObject, the child SDO might lose its filtering by the
parent SDO. In previous versions, this happened if the child SDO was generated
by the Object Generator with Follow joins turned on. This generated a BaseQuery
with NO-LOCKs before the join criteria and caused the ADM to add the
foreignfield criteria to the query incorrectly.

As a workaround, opening and saving the SDO in the AppBuilder alters the
BaseQuery to put the NO-LOCKs after the join criteria as expected by the ADM.

Note: OE00112600    Type: Limitation
Widgets on static SmartDataBrowser are not enabled on dynamic containers
When a static SmartDataBrowser contains other objects on its frame, those
objects are not enabled when the static SmartDataBrowser is run on a dynamic
container.  When that static SmartDataBrowser is run on a static container,
those objects are enabled.

Note: OE00112836    Type: Known Issue
assignNewValue w/ invalid values behaves different in new lookup API
The old and new lookup APIs behave differently when passing invalid value
parameters to assignNewValue if the lookup key field is different from the
lookup displayed field.

With the old API (pre-2.1B/10.0B02 behavior and 2.1B/10.0B02 behavior with
keep_old_api set to TRUE), passing an invalid key field value or an invalid
displayed field value to assignNewValue displays blank in the lookup field when
assignNewValue is invoked. If changes to the record are saved, blank is stored
in the record's key field.

With the new API (2.1B/10.0B02 default behavior), passing an invalid key field
parameter displays blank in the lookup field when assignNewValue is invoked. If
changes to the record are saved, the previous value displays in the lookup
field and the value is not changed in the record's key field. Passing an
invalid displayed field parameter displays the invalid value in the lookup
field when assignNewValue is invoked. If changes to the record are saved, the
previous value displays in the lookup

Note: OE00115074    Type: Behavior Change
Changes to how decimal values are managed in dynamic combos
There were several problems in previous releases developing decimal dynamic
combos with default flag values that contain a numeric decimal point and
deploying with different numeric formats.

Default flag values were always stored in the format used during development.
This prevented deployment to numeric formats other than the one used for
development.  Either errors displayed and no data displayed in the combo or
incorrect data was stored in the repository for the <None> or <All> option.

With 2.1B01, 10.0B03 and 10.1A this has changed to store default flag values
with American numeric format.  They should be entered in the SmartDataField
maintenance tool using the session's format but the tool will replace the
numeric decimal point with a period in the stored value.  At runtime, any
stored periods in the data are replaced with the current session's numeric
decimal point.

A fix program runs as part of the DCU Upgrade to convert existing default flag
values for decimal dynamic combos to American format.  The DCU must run in the
format that was used to develop dynamic combos.

The fix program writes a message to the log file for each default flag value it
attempts to convert.  It writes a message when a value is converted
successfully or writes a message if the conversion fails.  Review the DCU log
file after the upgrade and manually correct any failures.  Any failures that
are not corrected may not behave properly at runtime as the runtime has changed
to attempt to convert stored American formats to the format of the running

There are several Dynamics objects in the repository that store blank default
flag value instance attributes and give messages in the log file.  These are
for the cbSCMTool dynamic combo on the following viewer objects:


The messages for these objects are expected and you can ignore them.

Any dynamic combo instance attributes stored in static viewer code in your
application must be converted manually to American numeric format.

Note: OE00116096    Type: Known Issue
IndexInformation property only contains information for primary table(s)
The IndexInformation property has been changed to only contain index
information for the table(s) that are uniquely represented in one row in the
SDO query. The default table(s) are the EnabledTables or the first table for
read-only SDOs.

The getIndexInfoTables function determines which tables' info is added to the
property. This is not implemented as a property, but can be overridden if
different behavior is needed. If you want the old behavior all data objects,
then add a custom version that returns the value from getTables (all tables in
the query).

Note: OE00121218    Type: Known Issue
The Export to Excel functionality removes leading zeros from character strings
The Export to Excel functionality removes leading zeros from character strings.

Note: OE00124494    Type: Behavior Change
UndoChange action added to all tableio toolbars
Beginning with version 10.1B all shipped toolbars and tableio bands contain a
new UndoChange action. This action replaces the old Reset action as the default
in these toolbars.

This constitutes a behavior change (label and accelerator) for existing
applications that use the shipped toolbars or bands, since the caption is
changed to "Undo" instead of "Reset" and the accelerator is changed to "CTRL-Z"
from "ALT-R".

The new UndoChange action defines some of the translatable text needed for the
context sensitive text in the admmsgs.i include, message number 97. 

Customers that use the shipped toolbars or bands and want to remove the new
action and get the old one back need to customize the class or toolbar.
Customers that already have specific toolbars might need changes either to be
able to use the new action or to remove it.

To remove (hide) the new UndoChange action and get Reset back in shipped
toolbar or band:


The Reset action is already present in the toolbar, so in order to make the
Reset into default, the UndoChange needs to be added to the comma-separated
HiddenActions property.

Existing customer toolbars


Existing customer toolbars may or may not get the new UndoChange action. If the
toolbar or menu is defined with the "Tableio" category or one of the tableio
bands, then the action is added automatically. But, many toolbars add tableio
actions specifically in initAction() or initMenu() overrides in order to
control the order and add rules. The "UndoChange" will need to be added to

customized initAction


Since the getTableioUndoNew may need to load the actions if it is called from a
visual object before the toolbar is initialized, the toolbar initAction has
been changed to setIsActionsLoaded(true). Overrides of initAction that do not
call super must add the same call, using dynamic-function or the {set~ include.

Note: OE00135094    Type: Limitation
DynLookup limit on number of joins may vary on DataServers
In Release 10.1C, the DynLookup supports a join with up to 18 tables instead of
10. But, this limit might not apply when using a DataServer, because there also
is a limit decided by the size of the ROWIDs in the tables. The ROWIDs of the
tables are added to an indexed RowIdent field and the ABL has a limit on the
size of an index.

Starting with Release 10.1B, as long as -tmpbsize 4 (default) or larger is
used, temp-tables use large index keys and can store up to 1970 characters.
This means that, in theory, you can store and index up to 16 ROWIDs returned
from MSSQL server ( 16 * ( 116 + 1 ) - 1 = 1871 characters for rowids +
separators). The different DataServers will return ROWIDs with different
lengths, so the limit will vary.

If this limit is an issue, then you can edit the af/app/afgettemp.p procedure
and remove the following index definition.





The index is used in certain reposition operations on the client. Removing it
has an affect on performance, but this might be unnoticeable or acceptable
since the operation is done on the temp-table on the client.

Note: OE00161453    Type: Limitation
Toolbar never creates a Band more than once per toolbar instance
The toolbar creates only a single instance of each Band for a toolbar instance.
However, the Repository allows multiple instances of the same Band on a
toolbar. Before Release 10.1C, the toolbar created the multiple instances of
the same Band, but the second instance had no menu items. In Release 10.1C, the
second instance of a Band is ignored completely.

Note: OE00162048    Type: Workaround
**Widget ID <n> not unique (<widget-name>) error for recursive Dyn TreeViews
The "Runtime Widget-ID Assignment" tool assigns default gap values for the
imported SmartObjects.

These default values should work without problems in most cases. But, for
Dynamic TreeViews with structure nodes, the default gap value of 2000 for
"TreeNode" might not be large enough.

Since the nodes are created at runtime according to the database data, it is
impossible to know how many tree node levels are going to be created in the
Dynamic TreeView. If this happens and the default gap value of 2000 is not
enough, that default value should be increased as specified in the "Application
Development Environment (ADE) Addenda" Web paper in the "Widget IDs for ADM2
and Progress Dynamics" section.

Note: OE00176891    Type: Limitation
dynlaunch.i fails in thin client with DATETIME, DATETIME-TZ, RAW or ROWID param
Calling a PLIP using dynlaunch.i fails in a thin-client environment if the
procedure call includes DATETIME, DATETIME-TZ, RAW or ROWID parameters.

The client will report this error:

Mismatched number of parameters passed to routine <name>. (3234)

The AppServer agent will report these errors:

BUFFER-FIELD was not found in buffer ttSeqType. (7351)

Lead attributes in a chained-attribute expression (a:b:c) must be type HANDLE
or a user-defined type and valid (not UNKNOWN). (10068)

The workaround is to implement calls with these data types to run as external
procedure calls on the AppServer.

e.g. RUN xxx on gshAstraAppServer (INPUT ...)

Alternatively, you might add CASE statements for the 4 data types in
obtainInitialValueField in adm2/caller.p. (This has not been tested, but is
assumed to be the problem.)

Note: OE00191743    Type: Known Issue
Dynamic SDO with join require calculated fields to be defined in table order
In a Dynamic SDO based on a join, calculated fields will behave incorrectly
under these circumstances:

- Both tables in the join have calculated fields defined in the Repository's
entity definitions.

- Both tables also have one or more of these SDO Entity calculated fields
included in the SDO.

- The calculated fields from the right-hand table of the join appear before
those of the left-hand table in the list of fields in the SDO.

Symptoms include incorrect formatting and incorrect initial values being
provided, as well as calls to the SDO data logic procedure failing with errors
relating to temp-table schema mismatches.

ADE Tools and Runtime - Services

Note: OE00016261    Type: Limitation
Record level transaction hooks must be implemented in the Data Logic Procedure
You must implement a static SmartDataObject's record level transaction hooks
(create*, write*, and delete*) in the Data Logic Procedure. They will only fire
from the SDO if the SDO does not have a Data Logic Procedure.

Note: OE00106187    Type: Known Issue
Static SmartDataFields (e.g. SmartSelect) cannot be translated.
SmartSelect objects are not presented for translation in the Translation window
at runtime.

The work around is to enter translations of SmartSelects in the Translation
Control tool. The same naming convention as for Lookups is used. You must
specify the Widget Type as 'FILL-IN' and the Widget Name as 'fiLookup' in all
cases. You must enter the Object Name as <viewer-name>:<field-name>.

If the static SmartDataViewer containing the SmartSelect is used in a static
container, you must enter the file name of the viewer, including the extension
(.w), in the Object Name. If the viewer is used in a dynamic container, you
must enter the object name of the viewer, without any extension.

This is an example based on a viewer for the Warehouse table using a
SmartSelect for the 'State' field. The file name of the viewer is

Translation for use in a static container:

Object Name: warehousesdv.w:state

Widget Type: Fill In

Widget Name: fiLookup

Translation for use in a dynamic container:

Object Name: warehousesdv:state

Widget Type: Fill In

Widget Name: fiLookup

Note: OE00108151    Type: Behavior Change
Info for all users sent to client
When a user attempts to login in a client-AppServer configuration, the entire
list of users is sent from the AppServer back to the client. This may be an
expensive operation when there is a large number of users in the repository. To
reduce this overhead, adding the session property "abbreviatedUserTable" to all
client and AppServer session types and setting its value to "YES" will result
in only the user that is logging in having his data shipped across from the
AppServer, thereby reducing the traffic.

Note: OE00123050    Type: Limitation
The DataView does not support Dynamics Comments and Auditing
There is no default support for Comments and Auditing when DataViews and
ProDataSets are used.

The following error is returned when attempting to save a comment for a


BUFFER-FIELD RowUserProp was not found in buffer <dataset-buffer-name>.(7351)

The Server Interface implementation could define a RowUserPropfield in the
entity temp-table to store the information needed to trigger Auto Comment and
show tick marks in the Dynamics toolbar's Auditing and Comment actions, similar
to how the SDO handles it. Using this field might make it easier to use
existing Repository Manager APIs and reuse existing SDO code. Note that the
Auditing and Comment information is stored with delimiters in the field. This
makes it difficult to use outside of the ADM and difficult to populate. The
population have to be done for each record and will likely affect performance.

Note: OE00125984    Type: Behavior Change
Translated labels and widgets on same row but different column
When translating static viewers where KeepChildPositions=Yes, translated labels
now use the existing label's width only. Also when translating static viewers,
the label's font, rather than the widget's font, is used to determine the width
of the label.

The translation of simple (LIST-ITEMS) combo-box labels is now supported for
dynamic viewers.

When translating dynamic viewers with KeepChildPositions=Yes, the label moves
to the bottom (back) so that it doesn't overlay any widgets to its left. The
label is not truncated, unless it is longer than the space available.

Note: OE00127924    Type: Known Issue
Progress Dynamics can't find the help file during AppServer sessions
When the help file is set in the "security control" window, Progress Dynamics
can't find the help file using the help-menu-item in an AppServer session.

Note: OE00128539    Type: Behavior Change
Dynamics translated application: performance problems on login
Support has been added for a session property called "cached_translations_only"
which is set via the session definition (in the XML file and/or repository). In
the absence of such a property in the session, the default is YES (the
historical value). If cached_translations_only is false, then translations are
not retrieved at startup, but rather on demand when an object is translated.

ADE Tools and Runtime - Tools

Note: OE00021013    Type: Known Issue
scm_checks_on in Security Control is not supported
In Security Control, there is a toggle that switches on and off checks for the
use of an SCM tool. The use of this setting is not yet implemented in all the
places where it is relevant to check for this setting. SCM functionality is
always enabled when the SCM tool (Roundtable) is in use with Progress Dynamics.

Note: OE00024983    Type: Known Issue
Fields hidden on DynView master layout in design mode if custom layout exists
If a field on a master layout has its HIDDEN attribute set to TRUE, the viewer
typically displays the field in design mode. However, if a customized layout is
made for the viewer, the viewer does not display the hidden field when the
viewer reopens. This is inconsistent with the normal behavior for displaying
hidden fields in master layouts. If you need to modify a hidden field in this
situation, use the ROM tool. Do not modify the hidden field by using the 'List
Objects' button to bring up the property sheet. Doing so removes the field

Note: OE00035615    Type: Known Issue
Netscape Default HTTPS and SSL Support
The AppBuilder uses two OCX controls for remote file management (RFM) for
WebSpeed. One of these controls, CIHTTP v4.00.002, comes from Crescent.
According to current Crescent FAQ documentation on their Web site, OCX controls
do not work with a secured server.

Note: OE00045969    Type: Known Issue
Double Dot Path Notation Causes Failure
When using Netscape WebServers with an NSAPI messenger, the WebServer might
general protection fault if passed a .gif file location that uses a double dot
path notation that goes higher than the docroot, for example,

To avoid this problem when using an NSAPI messenger, do not specify .gif file
locations using double dots if that notation goes higher than the docroot.

Note: OE00070627    Type: Known Issue
Toolbar object modifications are not updated in the Toolbar
Toolbar data are cached on the client as soon as they have been read once   
from the server, so when actions, bands and/or toolbars are changed in the  
Toolbar and menu designer these changes will not always be reflected in new
instances of toolbars.             
Running the Dynamic Launcher and checking the 'Destroy ADM super-procedures'
option will ensure that toolbar data are refreshed. The other option is to  
restart the session.       

Note: OE00086609    Type: Known Issue
HTML after WSTag not sent if WSTag runs another WebSpeed object
If a SpeedScript file contains a WSTag tag that runs another WebSpeed

object, the remaining HTML after the WSTag tag is not sent to the Web


Note: OE00088031    Type: Known Issue
DataFields cut/copied then pasted are associated with RowObject
There is an issue when you cut or copy DataFields from one dynamic viewer and
then paste them to another dynamic viewer built from the same SDO. Until you
save and reopen the second viewer, the AppBuilder shows the new fields as being
associated with the RowObject table instead of their actual database table.

Note: OE00093984    Type: Known Issue
Copy-Paste in DynView is not keeping all the attributes of the widgets
When copying widgets from a DynView to another DynView, some widget attribute
values are missed. For example, when a fill-in is copied, the values of the
ShowPopup and Label attributes are missed in the target DynView. This happens
for all attributes that are read from the Repository.

Note: OE00097484    Type: Known Issue
Client cache viewer tool returns errors
The client cache viewer tool no longer works when run against a current version
of the Repository API.

Note: OE00098133    Type: Known Issue
Error 560 Generating Objects From SDO
Error 560 (Entry outside the range of list) is raised when the Object Generator
is used to create dynamic objects from a prebuilt SDO when the SDO has been
created by the Object Generator, and has subsequently had other tables manually
added, and the product module has sublevels in the path.

Note: OE00103384    Type: Known Issue
RTB: Problems when dyn object and super proc in different module
When modifying a dynamic object where the dynamic object and its super
procedure were created in different product modules, the following error may

The product module <product-module1> and the product module <product-module2>
must be the same. (AF:110)

Note: OE00107793    Type: Known Issue
Dynamic Lookup maintenance window does not destroy its maintenenance SDO
The Dynamic Lookup maintenance window does not destroy its SDO and associated
Data Logic Procedure

Whenever you open the maintenance window of the dynamic lookup from the dynamic
lookup browse, the system launches a new instance of the maintenance window's
SDO and its associated DLP. However, these objects are not destroyed upon
closing the maintenance window.

Note: OE00107875    Type: Known Issue
Cascading security allocations does not work for Data Security
The option to cascade security allocations from a profile user does not  
work for Data security.

Note: OE00109408    Type: Limitation
Help cannot be mapped to static container run from the AppBuilder
It is not possible to map help for a static container that has been run from
the AppBuilder.  The container must be run from the Dynamic Launcher to map
help for it.

Note: OE00168684    Type: Known Issue
Error 7452 in Dynamics Dataset Export Filter
Customers using European numeric settings might see the 7452 error when
pressing the filter button on the Dataset Export screen.

Note: OE00170170    Type: Known Issue
Error: The Root node code must be specified. (AF:1) when creating Dyn TreeViews
When entering data in the "Dynamic TreeView Builder" tool, you must enter the
"Object filename" value first. If you do not enter the Object filename first,
you see the "Root node code must be specified. (AF:1)" error upon saving the

ADE Tools and Runtime - Translation Manager

Note: OE00102201    Type: Known Issue
Changing the TranMan Language combo may cause error (132)
Changing the selected language on the TranMan Data Tab combo does not display
the correct translations after using the 'View', 'Sort' option from the pull
down Menu.

Double clicking on some rows might give the following error:

** This Translation already exists with Sequence number <number> Instance
Number <number> Language  Name "<language>". (132)

Note: OE00110396    Type: Known Issue
Creating a zip file on removable media causes zip errors
Creating a zip file on removable media causes the following errors:

Error occurred while accessing component property/method: MultiVolumeControl.

Out of present range.

Error code: 0x8002000a Zip adetran/common/_zipmgr.w (5890)

Zip: Couldn't open to write. (15).

Note:  Creating a zip file on non-removable storage functions properly.

Note: OE00224401    Type: Known Issue
Creating a .zip file on removable media from Visual Translator causes errors
Creating .zip file on removable media from Visual Translator causes the
following errors:

Error occurred while accessing component property/method: MultiVolumeControl.
Out of present range.

Error code: 0x8002000a Zip adetran/common/_zipmgr.w (5890) Zip: Couldn't open
to write. (15).

Note:  Creating a .zip file on non-removable storage functions properly.

ADE Tools and Runtime - Web Rendering

Note: OE00040946    Type: Limitation
Avoid changing Foreign Keys in Web Objects with joined queries
When you use the Detail Wizard to create a Web object that contains a join, do
not make the foreign key field updateable. If you change the value of the
foreign key in a record, the next stateless request might not be able to find
that record.

When this happens, you get an error that the query could not reposition to that

If your application needs the ability to update the value of the foreign key in
a joined query, you must make sure that the list of ROWIDs in the
"CurrentRowids" attribute contains ROWIDs of the newly joined table, instead of
the originally-joined table.

Note: OE00135596    Type: Known Issue
Two undo/reset buttons on the Standardtoolbar
The new UndoChange toolbar action is not supported in Dynamics Web.

By default, UndoChange replaces the Reset action in shipped toolbars and
Tableio bands. When these toobars and bands are realized in the Web, the Reset
button and menu item remain and function correctly. However, the UndoChange
action may also be realized at runtime as a non-functioning button and menu
item, labeled "Undo 1 (CTRL-Z)".

In order to suppress the UndoChange button and menu item, the UndoChange action
can be set to Hidden, or added to the HiddenActions property, for the toolbar.
For additional information, please see the note for the new UndoChange action
under GUIRENDR / SmartToolbar in this document.

AppServer -

Note: OE00221745    Type: Behavior Change
Support for Actional is removed
Support for Progress Actional (including all Actional interceptors for
OpenEdge), which was first introduced in OpenEdge 10.2B, is removed from
OpenEdge Release 11.1.

AppServer - Broker

Note: OE00203472    Type: Known Issue
Startup time of AppServer broker increases when SSL is enabled (Linux and UNIX)
After upgrading to OpenEdge Appserver V11, the AppServer broker's startup time
might increase if SSL is enabled.  This happens if /dev/random is not populated
with random data.  The SSL libraries used by the AppServer broker require
several kilobytes of random data to properly secure SSL connections to the

To resolve the issue, ensure that /dev/random is populated with enough random
data.  There are two possible solutions:

- Move /dev/random to /dev/random_bak, and then add a simlink from /dev/random
to /dev/urandom.  This makes /dev/random reference /dev/urandom.  Note that
/dev/urandom is less secure.

-  Install and run rngd, the random number generator daemon.  It increases the
entropy pool used /dev/random to provide random data.

Database - Database Utilities

Note: OE00070876    Type: Known Issue
PROUTIL IDXFIX -silent is not silent
Running PROUTIL IDXFIX with the -silent parameter does not suppress the display
of repetitive messages or prevent repetitive messages from being written to the
log file.

Note: OE00153461    Type: Limitation
On overflow condition, specified binary dump does not dump as expected.
While dumping data for a column with datatype BIGINT, an overflow condition
occurs when the specified column value is larger than the max BIGINT value.  No
error message is generated, and the dump continues as if the number specified
is a negative number.

Note: OE00153473    Type: Limitation
Negative integers are not supported by specified binary dump.
Negative integers are not supported by the specified binary dump utility as
input parameters.   You can dump all negative values by specifying a value
range as  "LT 0" for the column, but specifying any negative integer, such as
"LT -1", fails.  The specified binary dump utility cannot interpret command
lines with a "-" negative sign in the input parameter on command line.

Note: OE00192738    Type: Workaround
dbutil.bat supports nine command line parameters
dbutil.bat supports 9 command line parameters. Use proutil.bat if your command
line requires more than 9 parameters.  proutil.bat supports 27 parameters.

Note: OE00199451    Type: Behavior Change
Promon output format is changed to include additional fields
In Release 11.0.0, new columns are inserted into promon reports to provide
information on new fields, for example domains, tenants, and partitions.  Refer
to "OpenEdge Data Management:  Database Administration" for more details.
Understanding the change in column location is particularly important if you
have scripts that parse promon output and act on the parsed results.

Note: OE00230850    Type: Limitation
Linux 8.3 Database Utilities don't work on currently supported Linux OS
The Progress Version 8.3 Database Utilities included in the $DLC/bin/83dbutils
directory do not work with the currently supported Linux operating system
versions for both 32-bit and 64-bit Linux releases. To upgrade an 8.3 database,
you must perform the required truncate BI and 'prostrct convert' migration
steps using an installed version of Progress Version 8.3 on a Linux operating
system certified to run Version 8.3.

Database - Failover Clusters

Note: OE00147498    Type: Limitation
Failover Clusters node ordering
The node the cluster chooses to fail over to is a default preference Clusters
accepts from the cluster manager. If you want to tailor this, you must use your
operating system cluster management utilities. Clusters does not alter node

Note: OE00147499    Type: Limitation
Failover Clusters excluding nodes from fail over
All clustered systems provide a means for disallowing hosts from hosting a
resource. You must use your operating system cluster management utilities to do
this. Clusters does not provide a means to disallow a host.

Note: OE00147501    Type: Limitation
Failover clusters helper processes that do not start on another machine
If any of the helper (APW, BIW, or AIW) processes or the watchdog process
specified to start with a particular database fails, they will not be started
on another machine during a failover.  They will produce an OFFLINE status.

Note: OE00147509    Type: Product Notice
Failover Clusters Sun Cluster uses global devices
Clusters only supports databases stored on global devices.  The Sun Cluster
uses global devices to provide cluster-wide, highly available access to any
device in a cluster, from any node, without regard to where the device is
physically attached.  In general, if a node fails while providing access to a
global device, the Sun Cluster software automatically discovers another path to
the device and redirects the access to that path. The local disks on each
server are not multi-ported, and thus are not highly available devices.
Multi-ported global devices provide more than one path to a device. In the case
of multi-host disks, because the disks are part of a disk device group hosted
by more than one node, the multi-host disks are made highly available.

Note: OE00163001    Type: Known Issue
Restarting on the same node -- HPUX only
A package that fails, attempts to switch to the next node on which it is
configured to run.  If you wish the package to restart on the node where the
failure occurred, you must use the MC/ServiceGuard cmmodpkg utility to
re-enable the package to run on that node.   See your MC/ServiceGuard
documentation for details regarding the syntax of this utility.

Note: OE00192361    Type: Known Issue
An encryption-enabled, manual start db cannot be started by failover clusters
You cannot start a database enabled for failover clusters with your operating
system cluster resource manager if it is also enabled for transparent data
encryption and configured for manual start.

Failover cluster and encryption-enabled databases must be configured for
autostart to be started by the cluster resource manager.

If you attempt to start an encryption-enabled database configured for manual
start with the operating system cluster resource manager, the actual startup

but the cluster resource manager may incorrectly report that the database has
been started.

DataServers -

Note: OE00218857    Type: Behavior Change
Always run r-code against the schema image of the original database
Position-independent rcode is "independent" of the physical position of a
column in the foreign data source.  That is, column positions in the server
table can be rearranged without the need to recompile. However, introducing a
new column or deleting an existing column from an existing record structure
always requires the r-code to be recompiled against the new schema layout. The
r-code is dependent only on a logical identification of the column, and not the
physical position of the column. The logical identification, in the OpenEdge
database, takes place before migrating to a foreign data source, and the
logical identification does not change once the column is defined in the
OpenEdge table. When the columns are rearranged on the server, the code need
not be recompiled, but the foreign schema must be pulled back into the schema
image. This is to ensure that the new physical position of a column is matched
in the schema to the logical identifier that is also known to the r-code.

You can only run r-code or load data (.d file) while connected to a schema
image that is derived from the same database that was migrated and connected to
the server when the code was first compiled and/or the data was first dumped.
This ensures that the same logical column identifier is preserved after
migration and/or after any subsequent schema pulls.

Note: When the server table is re-pulled into the same schema image (after the
columns are rearranged on the server), the logical column identifier is
re-matched to the physical column position so that the r-code can find again
the column in a run-time application.

Note: OE00221190    Type: Behavior Change
Prepended underscore dropped from OE-generated default constraint names
The OpenEdge dictionary tool allows you to generate constraint definitions that
can be added in Oracle and MS SQL Server DataServers and then ported to foreign
data sources.  The generated constraint definitions are given default names
that can be modified by the user before saving.  However, the previous name
generation algorithm placed an underscore at the beginning, followed by an
acronym describing the type of constraint, another underscore, and then some
object names associated with the constraint.

The newly implemented name generation algorithm will work the same as the old
but it will drop the underscore character from the first position.  This is
needed since underscore as the first character in an OpenEdge name is
identified as an indicator of an OpenEdge metaschema object.  To avoid
confusion about object identification and to avoid name validation conflicts,
the underscore prefix is no longer generated for default constraint names.

DataServers - MS-SQL

Note: OE00186542    Type: Workaround
Techniques to load .d file when table has non-updatable column on MSSQLServer
In MSS DataServers, there is a restriction to a load operation from a .d file
when the table has non-updatable columns (i.e. columns on MS SQL server are of
type 'identity' or 'timestamp' or 'rowguid').
You can work-around this restriction by following one of the two options
described below.

Option 1:-
Use dump/load tools of the foreign data source instead of data from a .d file
to load your foreign table.

Note: This is the only way to retain the original values from non-updatable

Option 2:-
If the user wants newly generated values for non-updatable columns stored along
side updatable fields from the given '.d' file, write an ABL program to read
data from the .d file into a temp table and then skip non-updatable fields
while writing the temp table records to the foreign table.

Sample ABL code provided below to perform this task.

Conside a table named "test" on SQL Server side with the sturcture as,

TABLE [test](
[fld1] [int] IDENTITY(1,1) NOT NULL,
[fld2] [varchar](50) NULL,
[fld3] [varchar](50) NULL

****** sample ABL code ******

/* define temp table with the name Temptbl for table test */
define temp-table Temptbl like test.

/* pouplate temp-table Temptbl from the records in the .d file name test.d */
INPUT FROM test.d.
CREATE Temptbl.
IMPORT Temptbl.
/* create a record in the foreign DB */
CREATE test.
BUFFER-COPY Temptbl EXCEPT fld1 TO test.


Note: OE00190218    Type: Known Issue
SQLError not getting message with SNAC-10 driver.
New trigger solution (CR#OE00178470) generates 'PSC-init' and 'PSC-end'
messages on trigger execution. Modified DataServer code gets these messages
using SQLFetch()- SQLError - api calls for 2 times. Observed that SNAC-10
driver is not returning the PSC-end message as part of the 2nd time SQLFetch()
with SQLError()- API calls.

This is a 3rd party SNAC-10 driver issue. Confirmed the same by using a sample
ODBC program.

Note: This behavior has NO impact on DataServer functionality.

Note: OE00195562    Type: Product Notice
ZPRGRS_RECID_BUF_SIZE Option minimum value changed from 44 to 52
The minimum RECID buffer size has changed to 52 (from 44).

The ZPRGRS_RECID_BUF_SIZE option allows the RECID buffer size to be configured
to a customized size for the DataServer session.


This syntax is for setting the buffer size for the RECID area,


    (where nnnn is the new size of the area in bytes. The range limits for nnnn
are   inclusive of values between 52 to 1024.)

Note: OE00198360    Type: Product Notice
Computed column support enabled by MSS DataServer prior to MS SQL Server 2005
Computed columns are resolved differently in the server schemas prior to MS SQL
Server 2005 when compared to how they are resolved in MS SQL Server 2005 and
later versions.  This fix properly resolves computed columns in server schemas
prior to MS SQL Server 2005 so that computed columns are now correctly
identified by the DataServer in all supported releases of MS SQL Server.

Note: OE00217893    Type: Behavior Change
Unicode datatypes mapped to OE CHARACTER truncated during data comparison
In the previous releases, only Non-Unicode data was truncated during data
comparison, while an equivalent Unicode character datatype issued an error due
to the size mismatch of the comparison. To resolve this issue, Unicode
datatypes in MS SQL Server mapped to the OpenEdge CHARACTER datatype in
database tables (defined in the schema holder), get truncated during data
comparison with other Unicode character columns or expressions defined in a
WHERE clause. (This is similar to the non-Unicode data types behavior.) This is
done to achieve compatibility with the OpenEdge database which currently
performs this same WHERE clause value truncation. Therefore, the new behavior
provides consistency across all (Unicode and non-Unicode) character types.

Note: OE00218653    Type: Product Notice
Existing MSS logical schema requires an update to enable certain LOB operations
In MS SQL DataServer, partial LOB operations with non-native MS SQL Server
drivers had resulted in an error. The schema image has been modified to include
additional information that allows for important LOB data type distinctions in
the non-native drivers. As a result, a newly created logical schema with
re-pulled server definitions will no longer experience errors when non-native
drivers are processing DataServer LOB operations. If you want to successfully
use an existing logical schema with non-native driver connections, you must
first run the attached, upd_sqlcols_buf.p, script and then re-pull your table
definitions with LOB data types from the server into the schema holder

Note: OE00218872    Type: Behavior Change
Always run r-code against the schema image of the original database
Position-independent rcode is "independent" of the physical position of a
column in the foreign data source.  That is, column positions in the server
table can be rearranged without the need to recompile. However, introducing a
new column or deleting an existing column from an existing record structure
always requires the r-code to be recompiled against the new schema layout. The
r-code is dependent only on a logical identification of the column, and not the
physical position of the column. The logical identification, in the OpenEdge
database, takes place before migrating to a foreign data source, and the
logical identification does not change once the column is defined in the
OpenEdge table. When the columns are rearranged on the server, the code need
not be recompiled, but the foreign schema must be pulled back into the schema
image. This is to ensure that the new physical position of a column is matched
in the schema to the logical identifier that is also known to the r-code.

You can only run r-code or load data (.d file) while connected to a schema
image that is derived from the same database that was migrated and connected to
the server when the code was first compiled and/or the data was first dumped.
This ensures that the same logical column identifier is preserved after
migration and/or after any subsequent schema pulls.

Note: When the server table is re-pulled into the same schema image (after the
columns are rearranged on the server), the logical column identifier is
re-matched to the physical column position so that the r-code can find again
the column in a run-time application.

Note: OE00223755    Type: Behavior Change
R-code compiled in OpenEdge 11.1 or prior must be recompiled in OpenEdnge 11.2
If you are running an r-code module on a platform with a different address size
than the one it was originally compiled on, you must recompile the r-code
module on the new platform.

For example, an r-code module compiled in an OpenEdge 11.1 environment on a
Windows 32-bit computer will need to be recompiled before it can be executed on
an OpenEdge 11.2 environment on a Windows 64-bit or a Linux 64-bit platform.

NOTE: The r-code incompatibility affects only the modules that contain dynamic
queries, but all modules compiled prior to OpenEdge 11.2 and executed in
OpenEdge 11.2 across platforms with different address sizes must be recompiled
as a compatibility precaution.

Note: OE00226541    Type: Behavior Change
Field name on right side of a MATCHES operator get resolved on the client
In the ABL applications, the MATCHES operator compares a character expression
to a pattern (Sample syntax: <expression> MATCHES <pattern>) and evaluates to
TRUE if the expression satisfies the pattern criteria. The pattern can include
a constant, a field name, a variable name, or an expression whose value is a
character. If MATCHES operator is used in a WHERE clause and the pattern is a
constant, a variable, or an expression whose value can be resolved during ABL
compilation or statement preparation, then wildcards in the pattern will be
replaced with native syntax before the WHERE clause is sent to the foreign data
source via the DataServer interface.

However, if the MATCHES pattern references a table column in the foreign data
source, then any wildcards patterned in the foreign column data cannot be known
and modified before issuing the database request to the server that selects the
records. And, because wildcard expressions in the column data of server
references cannot be resolved in advance, MATCHES patterns with column
references are omitted from any WHERE clause bracket sent to the server.
Instead, such MATCHES predicates must be resolved by the client, including any
pattern filtering required on ABL wildcard expressions in the data content,
after the server returns the result set. Client filtering of MATCHES on a wider
result set bracket returned from the server can have a negative impact on

For better performance, avoid server column references in the MATCHES pattern
when placing requests to a foreign data source via the DataServer interface.

Note: OE00228018    Type: Limitation
R-code with BY fields in ABL must be re-compiled in OpenEdge 11.2
The r-code files generated using versions of OpenEdge prior to 11.2 and those
which have a BY clause with BY field lists must be re-compiled in OpenEdge
11.2. This ensures that the r-code files work well when you run them in
OpenEdge 11.2.

Documentation -

Note: OE00146970    Type: Known Issue
Microsoft Security Update may affect remote access of Online Help
If you receive the following error when accessing the help remotely:
"Action cancelled Internet Explorer was unable to link the web page you
requested. The page might be temporarily unavailable", see the Microsoft
Knowledge Base article titled: "Certain Web sites and HTML Help features may
not work after you install security update 896358 or security update 890175"
located at The article describes the
reasons for the issue and provides workarounds.

Note: OE00146971    Type: Known Issue
Online Help unavailable for editor's dialog boxes
Online help for dialog boxes in the Procedure Editor is not available. The Help
buttons on the dialog boxes do not work because the color-coding editor control
only supports MicrosoftRTM WinHelp (.hlp) files and not MicrosoftRTM  HTML
(.chm) files.

Documentation - ABL

Note: OE00216359    Type: Known Issue
References to certain attributes no longer require casting to access members
Each of the following attributes references an instance of
Progress.Lang.OERequestInfo or Progress.Lang.OEVersionInfo:

attributes of the SESSION system handle

o REQUEST-INFO and RESPONSE-INFO attributes of the server object and
asynchronous request object handles

In previous releases, the object in each instance was stored as a
Progress.Lang.Object, which required a downward cast to access members of the
OERequestInfo or OEVersionInfo class. With release 11.2, these objects are
stored with the respective Progress.Lang.OERequestInfo or
Progress.Lang.OEVersionInfo class type, and therefore no longer require a
downward cast to access their members. However, note that any existing code
that includes this downward cast will continue to work.

In addition, some, but not all of the documentation on using these attributes
has been updated to eliminate any reference to requiring a downward cast. Any
documentation that still notes the need to use a downward cast to access
members of the objects returned by these attributes is incorrect, and this
requirement can be safely ignored.

Documentation - Electronic Documentation

Note: OE00146978    Type: Known Issue
Search of PDF files for UNIX Platforms
On UNIX platforms, the search index is not automatically attached to the
documentation PDF files.  To attach the index file so that you will have search
capabilities, follow these steps:
1. From the Adobe Acrobat Reader, click on the Search icon.  The Adobe Acrobat
Search dialog box appears.
2. In the Adobe Acrobat Search dialog box, click on the Index button and
choose Add.
3. From the drop down list of files, select the oeidx.pdx file and choose OK.

Documentation - Help

Note: OE00146973    Type: Known Issue
Accessing online help for CSSPIN ActiveX Control
If you press F1 to get help on the CSSPIN ActiveX Control, you will get an
error indicating it cannot find the help file. To access the help for the
CSSPIN ActiveX Control, do the following:
1. Select Start->Program->OpenEdge->Help. The OpenEdge Online Help file
2. In the left pane, double-click the ActiveX Control Help folder to expand
it.  Then, select the CSSpin Control help topic.

Note: OE00146975    Type: Known Issue
Accessing online help for CSCOMBO ActiveX Control
If you press F1 to get help on the CSCOMBO ActiveX Control, you will get an
error indicating it cannot find the help file. To access the help for the
CSCOMBO ActiveX Control, do the following:
  1.  Select Start->Program->OpenEdge->Help. The OpenEdge Online Help file
  2.  In the left pane, double-click the ActiveX Control Help folder to expand
it.  Then,   select the CSCombo Control help topic.

Note: OE00146976    Type: Known Issue
Non-existing examples mentioned in online help for CSSPIN
The CSSpin Active X Control Help file mentions the following example:
   Example Location
   Project File Form/Basic File
These example files do not exist.

Documentation - Progress Developer Studio for OpenEdge

Note: OE00211510    Type: Product Notice
Infragistics assembly and namespace changes in version 2011.1
With support for Infragistics Version 2011.1, several of the assemblies, DLL's,
and corresponding namespaces have been changed in OpenEdge Release 11.0.

As a result, you will need to change any existing code that uses the affected

To see a list of the changes:

1. Go to the following URL:

2. Select the link, "Known Issues and Breaking Changes".

3. Select the link, "Breaking Changes in 2011 Volume 1".

Note: OE00215957    Type: Workaround
Problems with context-sensitve help in Progress Developer Studio for OpenEdge
When launching context-sensitive help in Eclipse, Help Not Found errors
sometime occur even when help is available. The error message is, "The context
help for this user interface element could not be found."

If you get a Help Not Found error after pressing F1, or clicking the help icon
in the UI, try one of the following:

1. Click on some other element in the UI and press F1, or click the help icon

2. Click on the "Search for . . ." link in the help pane. A list of relevant
topics appears.

Graphical User Interface - ABL

Note: OE00221498    Type: Behavior Change
Behavior changes when cropping and stretching images
In OpenEdge releases earlier than 11.2, cropping images (using the FROM option
of the Image Phrase, or the optional parameters of the LOAD-IMAGE ( ) method)
and stretching images (using the STRETCH-TO-FIT attribute of the IMAGE widget)
did not always work as specified. In many cases, the cropping and stretching
were ignored or were performed incorrectly. These issues are fixed in OpenEdge
Release 11.2. Applications which use these features may display images
differently than in earlier releases.

Graphical User Interface - ActiveX

Note: OE00212914    Type: Known Issue
Crystal Reports XI causes crash in some environments
Adding an instance of the Crystal Reports XI ActiveX Report Viewer to a window
causes a crash on certain platforms (such as Windows 7 or Windows 2008 Server)
and with certain Report Viewer versions (namely V11.5 or later 11.X versions).
This is a third-party issue, and occurs whether developing in Visual Studio
2010 or with OpenEdge.

Note: OE00214005    Type: Known Issue
VideoSoft IndexTab control does not display properly in some environments
The VideoSoft vsIndexTab OCX does not display at runtime on certain platforms
(for example, Windows 7 64-bit) with Visual Studio 2010.  This is a third party
issue and therefore the problem can be seen in OpenEdge as well.

Management -

Note: OE00146518    Type: Known Issue
Working with Properties
If an "-Xbootclasspath:", "-Xbootclasspath/a:", or "-Xbootclasspath/p:" entry
that contains spaces in the argument value has been added to the or file, the entry must be
manually edited to include quotes around the entire argument value (value to
the right of the colon).

Note: OE00146951    Type: Known Issue
Random errors with mapped drives on MSW
Due to Microsoft Knowledge Base Article #294816, we do not support the running
of a Progress application from a Network Share for Windows Terminal Services or
Citrix running on Windows 2000 Server or Windows 2000 Advanced Server. Terminal
Services users might see errors like "Disk or Network Error" or "C0000006: In
Page I/O Error", etc.  This happens due to a bug in the Windows operating
system where the network redirector only creates one file control block (FCB)
for all user connections so that when the first user to open the files logs
off, the other users lose their connections to files. To work around this
problem, place the program and associated data files on a localvolume, not
network share.

Note: OE00146953    Type: Known Issue
Error when default language not installed
While adding a product after an installation has been completed, if you attempt
to change the default language to a language that has not yet been installed,
and the language is one listed with a non-alphabetic character (e.g. -, (, ))
an error will result that will not accurately reflect the problem. The error
should not prevent the installation from continuing. This problem is apparent
on Windows/NT platforms only and does not occur on UNIX.  The workaround is to
select entries from the pull-down list boxes.

Note: OE00146954    Type: Known Issue
Uninstall fails with Proshell.dll in use
The uninstall will fail if any of the files it attempts to remove are busy. Use
of the Windows Explorer has been known to cause this condition of rendering the
file proshell.dll as in use, thus preventing the uninstall from succeeding,
however this may not be obvious at the time of uninstall.

Note: OE00146959    Type: Known Issue file is renamed
When uninstalling the file is renamed
and copied to the temp directory.

Note: OE00146965    Type: Known Issue
Cannot use an older version of PROMSGS with a current release
Through the automated OpenEdge installation process, Progress Software
Corporation programmatically ensures that a current OpenEdge installation has
the most recent OpenEdge messages in the PROMSGS files. This approach also
ensures that you always have the most up-to-date OpenEdge messages throughout a
release's lifecycle. Do not perform any tasks related to the PROMSGS files
outside of the standard OpenEdge installation process; for example, attempting
to use the PROMSGS environment variable to point to any versions of a PROMSGS
will have unpredictable and potentially undesirable results.

For example, the PROMSGS files installed with the OpenEdge Release 10.1B
contain the most up-to-date messages to support OpenEdge Release 10.1B. After
the initial install, if you install add-on products, or OpenEdge install
service packs that are released after the 10.1B Release date, Progress again
programmatically provides any newer or more recently updated PROMSGS files. As
each OpenEdge add-on product or service pack is installed, the installation
program checks to ensure that the newest copy of the PROMSGS file is being used
by all products.

Note: OE00220985    Type: Limitation
Numbers in DAC may be rounded down for large numbers
Any number, especially sequence current values, edited in the Database
Administration Console of OpenEdge Management are rounded down if the value
exceeds 9007199254740992 (the maximum integer value possible supported in

Management - Management

Note: OE00230012    Type: Known Issue
Missing icons in the Resource menu in IE 10
Some resource icons in the Create New Resource menu do not appear in Internet
Explorer 10.

Note: OE00230014    Type: Known Issue
Menu items appear partially while creating new OpenEdge resources in IE 10
Only some menu items appear when you try to create a new OpenEdge resource in
OpenEdge Management in Internet Explorer 10.

OE Mobile -

Note: OE00231397    Type: Limitation
Mobile client can't use CORS if service uses Basic or Form authentication
OE Mobile supports two types of Mobile Apps: Mobile Web Apps and Native Apps
(using Apache Cordova). Access to OpenEdge Mobile services from a Mobile App
client is through the JSDO or REST web service, both of which are deployed to a
Web server. In 11.2 the following security models are supported for Mobile App
access to the Web server:

Access to JSDO/REST web service from:

* Native App on iOS and Android:  Anonymous, Basic, and Form

* Mobile Web App with UI on the same Web server as the service:  Anonymous,
Basic, and Form

* Mobile Web App with UI on a different Web server from the service:  Anonymous

The case where the UI is on a Web server that is different from where the
service is located is known as cross-domain request. Such cross-domain requests
are normally forbidden, per the same-origin security policy. Cross-origin
resource sharing (CORS) defines a way in which the browser and the server can
interact to determine whether or not to allow the cross-origin request. Such
support is specific to the browser and the security model.

The JavaScript object provides a callback mechanism,
using its onOpenRequest property, that gives the programmer a chance to
overcome this limitation by modifying the requests made by the client when the
JSDO/REST web service is on a different Web server for a Mobile Web App

Open Client - Java

Note: OE00230938    Type: Behavior Change
Proxygen Proxies need to be regenerated if using 11.2 o4glrt.jar
Due to code changes in the Java Open Client runtime, any ProxyGen created Java
proxies need to be regenerated. You can continue using your existing proxies
along with the o4glrt.jar they were created with, or rebuild with the 11.2
version of ProxyGen or bproxygen.

Open Client - Web Services Provider

Note: OE00161041    Type: Limitation
Multiple Dataset parameters and RPC Encoded Web Services with Axis java clients
When defining multiple INPUT DATASET parameters for an OpenEdge web service
that uses RPC/Encoded SOAP messages, do not use the NAMESPACE-URI option in the
DEFINE DATASET statements.

The Apache Axis Java client does not properly handle namepsace declarations
when it sends a SOAP request for an RPC/Encoded SOAP message. As a result, an
incorrect message will be sent and the data will not be loaded into the

Axis may have similar issues with OUTPUT DATASET parameters. SOAP responses
from OpenEdge may not be properly deserialized.

If the NAMESPACE-URI option is required, then either define the OpenEdge Web
service to use Document/Literal or RPC/Literal SOAP messages. Alternatively,
avoid the issue by passing only one dataset in the Web service call.

OpenEdge GUI for .NET -

Note: OE00173368    Type: Workaround
Workaround for Elegant Ribbon control and IsolatedStorageException
The Foss PersistentStateManager class automatically loads and saves application
state in isolated storage, which does not work with the current OpenEdge .NET
bridge architecture.  Setting the
LoadStateAutomaticallyFromIsolatedStorageForDomain property to FALSE disables
the automatic state loading at application startup.  Add this line to your
program that uses the Elegant Ribbon control:

omain = FALSE.

This also means that changes in the quick access toolbar will not be loaded and
saved automatically.  If you need the changes to be kept, manually use the
Load() and Save() methods of the PersistentStateManager class.

Note: OE00180730    Type: Known Issue
ABL extended .NET object subscribed to .NET event may be deleted prematurely
An ABL extended .NET object subscribed to a .NET event may be deleted
prematurely. This bug can be observed with the following conditions:

- An ABL extended .NET object, for example AForm, is visualized
- A .NET object, for example a button, is not on AForm, but one of AForm's
methods is subscribed as the handler for this button's event.
- There is no reference to the button in the implementation of AForm.

If AForm is closed, and therefore Disposed, and all ABL references to it go
away, it will be deleted even though the button subscription is still
outstanding.  In other words, the button, in essense, still has a reference to
the class due to the subscription.  But this does not prevent the object from
being deleted, as it should.

Note: OE00181806    Type: Behavior Change
All dates exchanged between ABL and .NET are now the same except 12
All dates going from .NET to ABL and from ABL to .NET will be exactly the same
except for 12 days. These are the dates 2/29 in the leap years that are
represented by the Julian Calendar (on the Progress side) but not represented
by the Gregorian Calendar (on the .NET side).

(Since the Gregorian Calendar was not created until 10/15/1582, the .NET
DateTime implementation is not correct.)

These dates are:













Note: OE00198019    Type: Limitation
.NET controls that call back to the AVM on other threads are not supported
A .NET object might call back to the AVM to handle an event on a thread other
than the main UI thread. It might also call a .NET method on a different thread
where the method was overridden in a derived ABL class. The AVM does not
support either of these cases and raises a run-time error if they occur.

OpenEdge Replication - Replication

Note: OE00223122    Type: Behavior Change
New entries in the Database Service Manager view
The Database Service Manager Status display in Promon has the following new

*Used HighWater Mark - the maximum number of PICA messages used for this run of
the database
*Area Filled Count - the number of times the PICA queue has been filled for
this run of the database
*Service Latch Holder -  the current holder of the PICA queue; a value of -1
indicates that there is no current holder
*Access Count - the number of times the PICA queue has been accessed for this
run of the database
*Access Collisions - the number of times that there has been collision on
access to the PICA queue during this run of the database (AIW and REPL
attempting simultaneous access)

Access the Database Service Manager Status display by starting promon against
your database and choosing R&D>1>16.

OpenEdge Replication - Utilities

Note: OE00199297    Type: Product Notice
Support added for automatically starting a secondary broker after transition.
Support for automatically starting a secondary broker after transition is added
to replication.  In previous versions, only the primary broker could be started
automatically after transition.

The following new replication properties are added to the transition section of
the source and target db properties files:


Set the property start-secondary-broker to 1 to automatically start a secondary
broker after transition.
Specify appropriate secondary broker startup arguments with the
*-secondary-broker-startup-arguments properties. These properties accept broker
startup parameters and a parameter file using -pf.

Note:  the existing property, restart-after-transition, must also be set to 1.

Porting -

Note: OE00152834    Type: Known Issue
On Windows 7 platforms, sqlexp only works with a numeric port number
On Windows 7 platforms, sqlexp can only connect to the database server if the
port is numeric. For example, specify the port number as 4050 rather than using
a service name like "mydbservice".

Note: OE00172068    Type: Known Issue
fmconfig fails on Red Hat Linux 5 when is missing
fmconfig fails on Red Hat Linux 5 when the library is missing. To
resolve the missing library,  download and install
libXp-1.0.0-8.1.el5.i386.rpm or higher, available at the ftp site listed below.
You can then run the fmconfig command.

To get the library:

1. Navigate to:

2. rpm -Uv libXp-1.0.0-8.1.el5.i386.rpm

Note: OE00172320    Type: Known Issue
Long connection times on Windows 64bit
Occasionally connecting a process to an OpenEdge database on Windows 64bit
takes a long time.

This is an open issue Progress Software is working with Microsoft to resolve
(Microsoft Support Case: SRX080707601602).

Conditions that appear to cause the slow connection include:

* The database buffer pool that is larger than 1.7 GB.

* The C: drive on the machine is smaller than 14 GB.

If you encounter slow connection times, please report the conditions to
Progress Software so that more data can be provided to Microsoft to help
resolve the issue.

Note: OE00177172    Type: Known Issue
Windows 64bit requires more memory for the Operating System
In Windows 64-bit, the operating system requires 2GB of free memory for
acceptable OpenEdge performance.  If your shared memory allocation (database
buffer pool) leaves less that 2GB of free memory, then performing even simple
operations, such as finding a record that is in memory, is extremely slow.

Progress Developer Studio for OpenEdge -

Note: OE00219104    Type: Known Issue
AppBuilder Palette state is either not saved at all or not saved per editor
The state of the AppBuilder Palette is currently not reliably saved after it
has been changed. For example, if you change the Palette to use large icons,
after you restart, the Palette is likely to appear with small icons again. In
some cases the state is saved, but the new state is applied to all GUI windows
when Progress Developer Studio for OpenEdge is restarted.

Note: OE00222151    Type: Known Issue
PDSOE does not generate include files during compilation
PDSOE does not detect that files use WSMETA NAME="wsoptions" CONTENT="include"
in SpeedScript. Hence, the corresponding include files are not generated upon
compiling the HTML files from the OpenEdge Editor

Note: OE00222749    Type: Known Issue
View Design is disabled for imported forms
The View Design menu item on the ABL Editor context menu and the Navigate menu
is disabled when you open an imported form in the ABL Editor. View Design is
enabled as expected once the form has been opened in the Visual Designer Design

Note: OE00222989    Type: Known Issue
Undo only works on one widget at a time
The Undo operation on ABL UI Designer always reverts the changes widget by
widget, also when undoing  changes where multiple widgets were changed in a
single operation.

Note: OE00224591    Type: Known Issue
UI Designer always shows both horizontal and vertical scrollbars
The UI Designer shows both horizontal and vertical scrollbars when either the
height or the width of the window does not fit in the view port.

Note: OE00226567    Type: Known Issue
ABL UI Designer is inconsistent after AVM restart without saving modified files
The following problems occur with ABL UI Designer when you restart the AVM
without saving the modified ABL GUI procedure (.w) files:
* Unsaved widgets remain in the Outline view.
* Asterisk (*) mark appears on the design tab of the modified file.

Note: OE00226858    Type: Known Issue
Inconsistent behavior while generating invocation files for excluded files
When you exclude a file from the build and click Generate ESBOE, PDSOE displays
a message stating that the file is excluded and the invocation file cannot be
generated. However, when you perform the same operation for REST or BPM
(invocation files), PDSOE generates a set of r-code files even for the excluded
files and displays the status (r-code generation information) in the console.

Note: OE00227213    Type: Limitation
Cannot create invocation files (.pidl) for NCNamed procedures and methods
For ABL applications (procedures, methods, and user-defined functions) with
invalid names (which does not follow NCName validation rules)  and those which
include preprocessors, the invocation file (.pidl generation) fails to generate
at the time of creating a REST service.

The practical restrictions of NCName are that it cannot contain several symbol
characters such as , @,$, %, &, /, +, ,, ;, whitespace characters or different
types of parentheses. Further, an NCName cannot begin with a number, period, or
the minus character (-) although they can appear later in an NCName. The
following link describes the NCName validation rules:

Note: OE00227232    Type: Known Issue
Error while creating an ABL GUI procedure when the schema has unsaved changes
When a database schema is modified and not saved, creating a new ABL GUI
procedure (.w) file will generate an error message stating: "Building workspace
has encountered a problem. Errors occurred during the build."

Note: OE00227245    Type: Known Issue
AppBuilder in Developer Studio does not support accelerators
AppBuilder in Progress Developer Studio for OpenEdge does not support keyboard
shortcuts or accelerators.  Run (F2) and Check Syntax (Shift+F2) do work, but
these actions cannot be changed to use different accelerators.

Note: OE00227715    Type: Known Issue
PRO*Tools toolbar options are disabled for static Dynamics objects
PRO*Tools toolbar options are disabled when static objects stored in the
Dynamics Repository are opened in the ABL UI Designer or ABL Editor.

Note: OE00228162    Type: Known Issue
ABL UI Designer only opens AppBuilder procedure (.w) files
AppBuilder procedure files that do not have the .w extension are opened only in
the Text Editor and not in the ABL UI Designer.

Note: OE00228959    Type: Workaround
Eclipse switches to the Console View when the OE Web Server writes to the log
Eclipse switches control from the Servers view to the Console view whenever OE
Web Server writes log. This is standard Eclipse behavior where-in the Console
view gets the control whenever the standard output or error streams change.

Note: OE00230387    Type: Known Issue
Content assist does not function properly for SharedAVM in ABL Scratchpad
After assigning a database connection to a SharedAVM, when you select the
SharedAVM option from the AVM selection drop-down menu in the ABL Scratchpad
view, and then initiate content assistance (<CTRL+SPACE>), the ABL Scratchpad
view does not display DataAware proposals, variables, and program constructs.

Also, it does not provide color coding for the database fields.

Note: OE00231316    Type: Known Issue
REST deployment does not reflect the specified AppServer
REST deployment does not reflect the specified AppServer in the project setup
or any manual changes made to runtime.prop file. It continues to display
restbroker1. You must manually change the value of the appServiceName property
for the deployed service after deployment using either the restman or OE
Explorer tools.

Note: OE00231362    Type: Known Issue
Error message when opening Mobile App using invalid credentials
If you try to open a Mobile App using invalid credentials that were added to
the Preference page, the Progress Developer Studio for OpenEdge does not move
to an unresponsive state, instead an exception is logged silently in the log

Note: OE00231363    Type: Known Issue
Copy Source Local option does not always copy files locally
If you have a Mobile App in your Mobile project and you have modified the
Mobile App in the browser and saved it, Progress Developer Studio for OpenEdge
does not always copy the files locally when you select Copy Source Local from
the context menu.

To solve this issue, restart Progress Developer Studio for OpenEdge.

Note: OE00231429    Type: Known Issue
Only four out of six REST applications are deployed
If you have created six REST applications and try to deploy all of them
together using Progress Developer Studio for OpenEdge, only four applications
are deployed at one point of time.

Note: OE00231568    Type: Known Issue
Start and Stop functionality enabled for remote Apache Tomcat server
When you click Start for a remotely configured Apache Tomcat server, you get an
error message saying, "Only OE Web Server with configured with in box tomcat
can be started".

Note: OE00231613    Type: Known Issue
Session time-out after network outage of more than 30 minutes
The Mobile application designer session gets a time-out if its internet
connection goes down for more than 30 minutes after logging in to the session.
You must restart Progress Developer Studio for OpenEdge to continue working
after the outage.

Note: OE00231704    Type: Known Issue
Run Configuration opens phone emulator instead of tablet emulator
When you create a new Mobile App in Progress Developer Studio for OpenEdge,
using a backup of a tablet application, and run it in Developer Studio, it
opens the phone emulator instead of the tablet emulator.

The workaround for this is to add the following to the file:

<project name>/.mobileapps/<mobile app name>/.mobileapp


Note: OE00231747    Type: Known Issue
Mobile service fails to associate with REST manager instance
The Mobile service that you create on the Create a Mobile service page of the
New OpenEdge Project wizard fails to associate with a REST manager instance
despite selecting the REST manager instance checkbox.

Note: OE00231868    Type: Known Issue
"Save Failed" error on save of new Dynamics object
Attempting to save a Dynamics object in Progress Developer Studio for OpenEdge
results in a Null Pointer Exception and a "Save Failed" error message. Use the
Container Builder opened when the wizard completed to save new Dynamics

Note: OE00231906    Type: Limitation
Space in project name causes New ABL GUI procedure wizard to fail
In a project whose name contains a space, the Create an ABL GUI procedure
wizard launches with an empty Object Type list and an unresponsive Template

Workaround: Do not include spaces in the name of a project that will contain
ABL GUI procedures.

Progress Developer Studio for OpenEdge - AppBuilder Support

Note: OE00223457    Type: Known Issue
Enabling or disabling of Dynamics does not update the project without restart
Enabling or disabling of Dynamics does not automatically restart the project:
the Object type list on the Create an ABL GUI procedure window does not display
Dynamics-specific information after enabling Dynamics and Dynamics-specific
information persists even after disabling Dynamics. You must restart (close and
open) the project for enabling or disabling of Dynamics to take effect.

Note: OE00226121    Type: Limitation
OpenEdge Text Editor does not support editing of freeform queries
The OpenEdge Text Editor does not recognize the DISPLAY and OPEN_QUERY
(pseudo-) triggers of the Freeform query in an AppBuilder file.

The code for the DISPLAY trigger of a Freeform browse is editable and can be
found from the browser node (under Widgets) in the outline view.

The OPEN_QUERY query expression that is in a comment section (&ANALYZE-SUSPEND
_QUERY-BLOCK) is also editable, but is not shown in the outline view. The Text
Editor will not generate the preprocessor definitions with the updated query
expression, so the change will not have any effect until the code is opened in
the ABL UI Designer.  One can force the preprocessor definitions to be
regenerated by opening the UI Design (View Design) and save it from there,
after the code is edited in the Text Editor, or by making a change (such as
move a widget and undo it) before setting focus back to the Text Editor.  One
can also edit the preprocessor definitions directly if the AppBuilder
preference to make generated code read-only is turned off.

Note: OE00227713    Type: Known Issue
Progress Dynamics menu options do not appear for static objects
The Progress Dynamics menu options such as Open Object and Build menu options
will not be available when static objects are open in the ABL UI Designer or
ABL Editor. The menu items will reappear if one clicks on the project in the
Project Explorer.

Note: OE00231813    Type: Known Issue
"DB Required" flag must be coded manually
Progress Developer Studio for OpenEdge lacks tooling support for marking a
procedure or function as "DB Required." Complete the following steps to set
this flag:

1) Turn off the option to Make AppBuilder-generated code read-only (Window >
Preferences - Progress OpenEdge > AppBuilder > Editor).

2) In the source editor, append the token _DB-REQUIRED to the &ANALYZE-SUSPEND
line preceding the declaration of the procedure or function.

3) Switch to the Design view (Shift+F9, or context menu View Design option) and
save the file. Do not save from the source editor. This generates the code with
the {&DB-REQUIRED-START} and {&DB-REQUIRED-END} preprocessors before and after
the procedure or function. (Alternatively, add {&DB-REQUIRED-START} and
{&DB-REQUIRED-END} manually in the source editor.)

Note: To edit these code blocks, you must keep the read-only option turned off.

Progress Developer Studio for OpenEdge - Debugger

Note: OE00212608    Type: Known Issue
Dynamic object monitoring menu is not enabled for WebSpeed
The dynamic object monitoring menu is not enabled for WeSpeed when you debug a
broker unless the debugger has been interrupted at a breakpoint. Any new agent
that is started while the debugger is connected to the broker for debugging
does not have the dynamic object monitoring settings applied to that agent
before the agent is allowed to execute any code.

Note: OE00215646    Type: Behavior Change
Progress Developer Studio for OpenEdge debugger behavior change
Starting in OpenEdge Release 11.0 and continuing in all subsequent releases,
the Progress Developer Studio for OpenEdge debugger does not stop at the first
executable line. Instead, the debugger stops at the line containing the first

Progress Developer Studio for OpenEdge - Editing

Note: OE00228354    Type: Known Issue
Syntax check in ABL editor does not recognize -sw Startup Parameter
An error 15090 appears when ABL editor checks for a syntax even when the syntax
has -sw startup parameter specified.

Note: OE00231691    Type: Known Issue
RUN statement with a large number of parameters causes PDSOE to hang
When you try to add an extra parameter to a RUN statement that already contains
a large number of parameters, Progress Developer Studio hangs with a 100%
utilization of the CPU.

Progress Developer Studio for OpenEdge - Visual Designer

Note: OE00195134    Type: Product Notice
OpenEdge cannot compile/run GUI for .NET code generated using previous versions
When you edit GUI for .NET code generated using a previous version of OpenEdge
Visual Designer, the generated code is updated to the current version of
Progress Developer Studio for OpenEdge and thus might contain new language
constructs that are not compatible with the previous versions of the compiler
and the AVM, and wizard-generated code is incompatible with previous versions.
Such incompatibilities can occur even when you do not explicitly use new
features of the current version.

To compile and execute GUI for .NET code, you must use an OpenEdge version that
matches or is later than the Visual Designer version in which the code was
generated. For example, source code opened in version 11.0 of the Visual
Designer will no longer compile in 10.2B.


Note: OE00226972    Type: Limitation
Limited Compact deployment support
In OpenEdge Release 11.2, the Compact deployment model is restricted to
deploying no more than one OE Web application in a Java container.   Deploying
more than one Compact OE Web application in the same Java container results in
incorrect operations and AppServer access errors.

Note that in OpenEdge, there are two models of building and deploying Web
applications to an Apache Tomcat Java container: Full and Compact.

The Full model includes all application libraries within the Web application
archive (WAR) file. Therefore, the application does not have any dependencies
on libraries from other applications or from the Java container.

The WAR file, in the Compact model, does not include application libraries. The
libraries are manually installed in a shared location within the Java

Note: OE00230021    Type: Known Issue
Error when a REST Manager name contains "#" or "&" characters
A REST Manager name containing a number sign (#) or an ampersand (&) throws a
null pointer exception (java.lang.NullPointerException).

Note: OE00230421    Type: Known Issue
Possible failure during cleaning and re-publishing Web applications in PDSOE
After an initial publish, re-publishing or cleaning a REST/Mobile Web
application from PDSOE may fail when the Tomcat Web server is running on a
Windows platform.

The Windows file locking design allows the OS to keep JAR files and other
resources locked, which can cause undeployment to fail.  This behavior depends
on the file system implementation and has only been seen on Windows.

If file locking is an issue, the REST Management agent will return a
"Deployment failure detected" error message.

A workaround is to stop Tomcat, manually delete the folders, restart Tomcat,
and retry.

Note: OE00231727    Type: Known Issue
REST/Mobile Web applications not immediately available after re-publishing
After re-publishing a REST/Mobile application from PDSOE, the Tomcat Web server
takes some time before making the application accessible. Attempts to access
the application during this period can generate HTTP 404 (Not Found) errors.
After a short time, the application should become available.

To alleviate this problem, the REST Management agent waits an additional time
period before returning a Deploy Successful status to PDSOE.  The additional
period of time, which is set to 30 seconds by default, can be changed by
setting an environment variable named OPENEDGE_WAITAFTERDEPLOY. The variable
must be set in a customization shell script named proset.bat, which must be
added to your OpenEdge work directory.

For example, the following command in a proset.bat file sets the wait interval
to 40 seconds (note that the interval is specified in milliseconds):



Note: OE00159192    Type: Limitation
ESQLC clients can specify an IP protocol version using a parameter
ESQLC clients will default to using the IPv4 protocol. The use of the IPv6
protocol can be selected by using the -ipv6 parameter on the connection URL.
The following is an example of a connection URL where the use the of IPv6
protocol is desired:


The parameter is also available to use with connection URLs for the SQLDump,
SQLoad, and SQLSChema utilities.

SQL - Server

Note: OE00115254    Type: Known Issue
Using aliases in an ORDER BY clause containing set operators
Prior to 11.2, SQL displayed a syntax error when a query containing a set
operator (such as, UNION) included a column alias in the ORDER BY clause.

From release 11.2 onwards, a query containing set operators (UNION, INTERSECT,
or MINUS) can include column names and aliases in the ORDER BY clause. The
column name or alias indicates ordering based on the corresponding column from
all the query expressions (SELECT statements) in the set operator.

Note: OE00135348    Type: Product Notice
ROWID support
The 10.2B07 service pack for OpenEdge SQL enabled the term ROWID to be
recognized and used as a SQL identifier (such as a column name). This occurs
when ROWID is a delimited identifier (in double quotes) in a SQL statement.

For example:

   SELECT custnum, "ROWID" from pub.my_customer where "ROWID" = 10 ;

To enable the feature, it was required to use an OpenEdge startup parameter,
-SQLQuotedRowid, and specify it with the value "std".

For example:

     mprosrv -S 1234 -H myhost -SQLQuotedRowid std

If the new startup parameter was not used or was used and its value was not
"std", then a quoted "ROWID" was interpreted as a reference to the ROWID

From release 11.2 onwards, this startup parameter is no longer required and the
feature is enabled by default.

Any unquoted use of ROWID, as earlier, continues to be interpreted as a
reference to the ROWID function.

To use this feature as in the previous versions, you can use the startup
parameter, -SQLQuotedRowid, with a value other than "std". If the new startup
parameter is used and its value is not "std", then a quoted "ROWID" is
interpreted as a reference to the ROWID function.

Note: OE00216746    Type: Behavior Change
UNION and UNION ALL set operators function properly in 11.2
Queries that contain UNION and UNION ALL set operators no longer report an
internal error. They return a valid result set.

Note: OE00223136    Type: Behavior Change
SQL database server crash problem fixed in 11.2
In OpenEdge releases prior to 11.2, a query containing large number of constant
values in the WHERE IN clause caused the SQL database server (sqlsrv2) to

This issue has been fixed in the 11.2 release.


Note: OE00153600    Type: Known Issue
SQL uses the Java compiler to compile the Java code for a CREATE
TRIGGER or CREATE PROCEDURE statement. If the Java compiler finds errors in
this Java source code, it outputs diagnostic information describing the errors.

A subset of the diagnostics is appended to the SQL-92 error
message which is returned to the client.

The entire set of diagnostics is stored on the server, in the SQL server's
WRKDIR (working directory).  If the owner of the stored procedure/trigger is
OWNER, and the procedure/trigger name is XX, then all the diagnostics are in
the file named OWNER.XX.LST in the SQL server's WRKDIR (working directory).

The WRKDIR is identified by either the environment variable $WRKDIR, or on NT
by the registry entry WRKDIR under the registry key for the Progress software

Note: OE00182091    Type: Behavior Change
Display of null array is changed.
The ARRAY data type is a composite data value that consists of zero or more
elements of a specified data type (known as the element type). If the result
returned from an ARRAY data type is null, it used to be displayed as a string
that consists of ? for each element and seperated by ;. To be consistent with
all other data types, it will be changed to be displayed as null instead of a
string with above format now. Same for the result returned from pro_element

Note: OE00209582    Type: Known Issue
Refused connection and time-out errors with secondary broker fixed in 11.2
In OpenEdge releases prior to 11.2 and 10.2B08, problems (such as, refused
connections and time-out errors) occurred when trying to connect to the server.
These problems occurred when a secondary broker with the -Ma startup parameter
value different from that of the primary broker was used for SQL connections,
and when the number of connections to a SQL server process exceeded the -Ma
startup parameter value of the primary broker.

This problem has been fixed in OE 11.2 and OE 10.2B08.

Note: OE00218460    Type: Behavior Change
Blank passwords accepted by SQLSCHEMA, SQLDUMP, and SQLLOAD utilities
SQLSCHEMA, SQLDUMP, and SQLLOAD utilities accept blank passwords through the
command line. To provide a blank password to these utilities, use an empty
string embedded in single quotes for the password value (for example, -a '').

Note: OE00220355    Type: Known Issue
Support for scalar functions by tenantid_tbl() and tenantname_tbl()
From release 11.2 onwards, all scalar functions are supported when used with
the tenant table functions, tenantid_tbl() and tenantname_tbl().

Note: The tenant table functions also support the aggregate functions: MIN,

Note: OE00220527    Type: Known Issue
Internal error when updating rows fixed in 11.2
Prior to the OpenEdge 11.2 release, when a field containing an index is updated
as part of SQL Trigger execution, the next UPDATE statement for the same field
generates the below error:

Internal error -1214 (see dsmret.h) in SQL from subsystem DSM SERVICES function
dsmKeyDelete called from ix_delete on <user>.<table> for <user>.<index>. Save
log for Progress Technical Support.

SQLState: HY000

ErrorCode: -219901

This problem has been fixed in the OpenEdge 11.2 release.

Note: OE00225837    Type: Workaround
DDL to correct CRC errors when using BINARY DUMP/LOAD
In release 11.2, SQL introduces the following special syntax for Database
Administrators who handle problems while migrating database tables from an
older release database to a newer release database. In some cases, there may be
a CRC mismatch error (when dumping and loading data using BINARY DUMP/LOAD).

To correct this error, Database Administrators can run the following DDL



For more information refer to the OpenEdge SQL Statements chapter of the
OpenEdge Data Management: SQL Reference guide.

Note: OE00228663    Type: Behavior Change
Different error messages for primary, unique and unique index violations
Prior to this release, OpenEdge SQL reports one error message for three types
of unique constraint violations:
1)    Primary key
2)    Unique key
3)    Unique index

The current error message for all the above violations is:
error(-10102): Integrity constraint violation:uniqueness constraint violation

From this release forward, the three violations give different error messages.
The following examples demonstrate the expected error messages in each of
unique constraint case (if run by user "hum")


1.    create table pkeytab( a int, b int, constraint pkeytaba primary key(a));
      insert into pkeytab values(1,1);
      1 record inserted.
      insert into pkeytab values(1,1);

error(-210095): Violation of PRIMARY KEY constraint "PKEYTABA". Cannot insert
duplicate key in object "HUM.PKEYTAB". (16947)

2.     create table ukeytab1( a int, b int, constraint ukeytab1ab unique
    insert into ukeytab1 values(1,1);
    1 record inserted.
    insert into ukeytab1 values(1,1);
error(-210096): Violation of UNIQUE KEY constraint "UKEYTAB1AB". Cannot  insert
duplicate key in object "HUM.UKEYTAB1". (16948)

3.     create table ukeytab2( a int, b int);
create unique index ukeytab2a on ukeytab2(a);
insert into ukeytab2 values(1,1);
1 record inserted.
insert into ukeytab2 values(1,1);
error(-210097): Cannot insert duplicate key in object "HUM.UKEYTAB2" with
unique index "UKEYTAB2A". (16949)

SQL - Tools

Note: OE00221262    Type: Behavior Change
SQLSCHEMA support for table names containing hyphens
Prior to the release 11.2, the SQLSCHEMA utiility exported incomplete table
definitions in case of hyphens in table names. For example, "sam-tab".

This issue has been fixed in the release 11.2 and such table definitions can be
dumped using the SQLSCHEMA utiility without any problem or error.

Web Services Client -

Note: OE00100789    Type: Known Issue
Time zone information lost for some XML datatypes
The XML Schema datatypes, gYearMonth, gYear, gMonthDay, gDay, and gMonth, can
optionally include time zone information. OpenEdge does not handle time zone
information correctly for these datatypes. Any time zone input from the ABL is
lost, as is any time zone information returned from a Web service for these
datatypes. For example, "1953-10-4:00" becomes "1953-10". The one exception is
that Z, indicating Universal Time (UTC), is retained (for example, 1953-10Z
remains 1953-10Z).

Note: OE00103414    Type: Known Issue
Data types defined in imported schemas are not seen by the WSDL Analyzer
RN# 100B-00168
When a WSDL document contains an XML Schema import element, the type and
element definitions of the imported schema are not seen by the analyzer. A
message indicating that a type or element definition could not be found will
appear in the generated documentation.

To work around the problem, copy the xsd:schema elements (and their contents)
from the imported schema document and paste them as children of the wsdl:types
element of the WSDL document.  Also comment out the xsd:import element in the
xsd:schema element.

Double check namespace prefix definitions to ensure the prefixes in the copied
XML are properly defined and can be referenced by other parts of the WSDL

Note: OE00123804    Type: Known Issue
Memory violation when connecting to a Web Service on AIX 5.3
In order to use WebServices on AIX 5.3, the minimum Operating System
requirement is AIX 5.3.04. You can find the version of AIX you are running
using the oslevel -r command.

WebClient -

Note: OE00146960    Type: Known Issue
The WebClient install does not accurately calculate disk space required
The WebClient install does not accurately calculate the amount of disk space
required on the client side to do the install. Prior to the install the user
should probably have around 25 meg of available disk space. Some of this is for
temporary storage of installation files.

Note: OE00147868    Type: Known Issue
Do Not Use Notepad to Edit .htm Files
Do not use Notepad to edit the webclient.htm file or bootstrap.htm file for
customizing your application install. When Notepad saves the file, it changes
the line terminator characters and may make the file work improperly in the

Note: OE00147869    Type: Known Issue
DLLs and EXEs That You May Have to Package with Your Application
Be aware that there may be Progress-supplied DLLs or EXEs that are used by your
application that are not included in the end-user WebClient install. Strictly
speaking, these DLLs and EXEs are not a part of ABL.  For example, there are
some DLLS or EXEs only used during application installation. Other DLLS may be
required if the application uses procedures in the adecomm or adeshar
directories that indirectly use DLLs.  Progress  excludes them from the install
to keep WebClient as small as possible and keep install time over the Internet
as fast as possible. If you need any of these files to install or run your
application, include them in your application installation.  Examples of these
files are listed below by category.

DLLs used by some procedures in adecomm/adeshar:

EXEs that could be used by your install:
* ini2reg.exe
* regsvr32.exe (A Microsoft tool usually, but not always, installed on a
typical PC)

WebSpeed -

Note: OE00194419    Type: Behavior Change
11.1 Webspeed Messenger installation behavior for Windows
From OpenEdge Release 11.1, Webspeed Messenger installation behavior on Windows
has changed as below:

1) WebSpeed Messenger only installation:

The file is created in the $DLC/properties location. Prior to
OpenEdge Release 11.1, it used to be the file. This changed
behavior on Windows is now consistent with the behavior on UNIX.

Note: You can rename the file to the file.

2) WebSpeed Messenger only installation performed over the existing OpenEdge

a) The file is created in $DLC/properties.
b) The existing file is saved as

This changed behavior on Windows is also consistent with the behavior on UNIX.

WebSpeed - Tools

Note: OE00096070    Type: Known Issue
The compileAll option in WebTools has a limitation of URL length of 4096 chars
The compileAll option on AppManager in WebTools has a limitation of URL length
being more than 4096 chars, depending of what web browser is being used. Try to
limit the size of the compiles, number of files if you run into this problem.



Issue Number: OE00177130
     Extended errors not recorded in database log for prorest failure

Extended error information is not recorded in the database log file when a
read of the backup volume fails during a prorestore.

Issue Number: OE00181555
     Repl target fails to transition

The target may not be able to transition when a live transaction exists
during transition and the transaction must be backed out by the
replication agent.

Issue Number: OE00189816
     Online backup EOF error at 1 TB

10.1C online backup failing at 1 TB.  Need to specify -vs to create a
multivolume backup.

Issue Number: OE00194487
     Incorrect access mode requirement for event procedures

Access to the event manager must be determined by the subscribing routine,
not the routine defining/publishing the event. This works for classes, but
not for procedures.

If the method you subscribe is private to the subscribing class, the
publishing class fires it with success, which is the expected behavior,
since the event procedures should only be exposed to the event itself.

However, if an event procedure is made private, error 15536 is raised when
the event fires, which means  the event procedure should be exposed to the
world. It should be considered wrong for "outsiders" to attach private
procedures/methods to an event, (i.e. an outside routine must not be able
to subscribe an event handler to an event if it could not access the
eventhandler itself), but the local procedure/class must be able to attach
its private event managers to an event originating outside the

In other words, if the event handler is accessible to the routine
executing the SUBSCRIBE statement, the PUBLISH must not fail to execute
the event handler, but if it is not visible to the routine executing the
SUBSCRIBE, SUBSCRIBE should fail (at runtime if needed) with error 15536).

In the case of classes it works like this, but in the case of procedures
it does not.

Issue Number: OE00068620
     Undo transaction with update/delete may crash client

The client may crash randonmly if you delete a dynamic buffer in a
different sub-transaction (from the one that connected the buffer to a
record), if the subtransaction that deleted the dynamic buffer needs to be

Issue Number: OE00176504
     ABL SSl Socket hangs on CONNECT statement

The SOCKET:CONNECT() client socket on SSL mode hangs forever if the server
is unresponsive to the client's connection request.

Issue Number: OE00199964
     STOP fails to back out with persistent trigger subprocedures

The STOP condition doesn't function as expected when there are multiple
handlers for a named event. If there are multiple handlers and one of them
raises the STOP condition, the handlers that haven't yet run should not be
executed, but they are. If the handlers that have run have made changes in
a subtransaction, those changes are not backed out.

Issue Number: OE00201101
     RETURN ERROR <error-object-expression> fails to compile

A RETURN ERROR statement that returns an error object based on
Progress.Lang.Error raises error 14913 during compilation.

Issue Number: OE00220428
     Error 7254 with a FIND statement in a static class constructor

In some circumstances it is possible to receive error 7254:

Illegal FIND, FOR EACH or OPEN QUERY in User-defined function <function
name>. (7254)

when using a FIND statement in a constructor of a static class.  The
problem happens when a static class is referenced the first time in a
WHERE clause.  Ultimately the error is correct.  The situation is the same
as having a UDF in a WHERE clause that then tries to execute a FIND
statement.  Although the error message, in this case, is a very confusing
since it is not obvious that the static constructor is running.

Issue Number: OE00220757
     LOGICAL to CHARACTER runtime conversion raises errors 87 & 5729

LOGICAL to CHARACTER runtime parameter data conversion fails with errors
87 and 5729.  The same errors are not displayed for other data types, for
example Logical to Date.

Issue Number: OE00220794
     Trigger won't run after setting FORMAT attribute in a trigger

Setting a fill-in's FORMAT attribute during the execution of a trigger
that was fired as a result of the fill-in losing focus may cause the
trigger not to work on subsequent events. For example, setting a fill-in's
FORMAT attribute in the VALUE-CHANGED trigger of a browse widget will
cause this issue if the VALUE-CHANGED event occurs due to the user
clicking on the browse when focus was in the fill-in.

Issue Number: OE00220833
     READKEY and PROCESS EVENTS restricts character input

If you have a READKEY and a PROCESS EVENTS in an editing block, the user
is prevented from inputing more than one character into the field being
updated.  So you need an UPDATE statement with the EDITING option to
experience this problem.

Issue Number: OE00221328
     HKSCS Character can not be entered in OE102B05 on Win XP

When using HKSCS Characters on Windows XP using the MS HKSCS-2001 Support
supplement, HKSCS characters cannot be entered from a GUI session. This
problem affects only Windows Xp and earlier versions of Windows.

Issue Number: OE00221927
     LANDSCAPE printer orientation keyword ignored

The LANDSCAPE keyword in the following statement is ignored:


If the printer has a default page orientation of portrait, any text sent
to that printer is printed in portrait page orientation instead of
landscape as instructed.

Issue Number: OE00222010
     AppBuilder crashes adding Oracle AutoVue OCX to ABL window

AppBuilder crashes when attempting to add the AutoVue ActiveX Control
(v20.2) to an ABL window.

Issue Number: OE00222130
     Error 13817 when comp DEFINE which includes a STATIC method call

The following errors are produced when attempting to compile a class that
has a static method call appear within a DEFINE statement:

SYSTEM ERROR: Unable to get class element ^myStaticClass from Type
Manager. (13817)

** Unknown Field or Variable name - myStaticClass. (201)

**  Could not understand line 9. (196)

Issue Number: OE00222200
     **stget: out of storage. (6498) when receiving fatal signal

Error '**stget: out of storage. (6498)' is generated when the client
receives a fatal signal in OpenEdge 11, when the session has a transaction
open on a shared-memory connection and it needs to rollback the

Issue Number: OE00222226
     Runtime error stget out of storage

The following piece of code will cause a compile time error because of the
extra parenthesis on the right side.  (The error is that compile time
arguments cannot be passed to an internal procedure):

RUN pTest IN THIS-PROCEDURE ((2 * 2) + 4)).

This is the same in OE10 and OE11.

However, if you happen to put this code in a "persistent run" like this:





there is no compile time error.

The code will even run fine in OE10.  But in OE11, the session will crash
with error  "stget out of storage".

Issue Number: OE00222274
     AppBuilder crashes when compiling after db changes

When checking the syntax of a v8 smartviewer, after making on-line db
schema changes within a separate session, the session goes away silently,
with no errors.

Issue Number: OE00222323
     Crash after deleting super procedure on chain

The client may crash on Unix platforms if you add a procedure to the
super-procedures chain (with ADD-SUPER-PROCEDURE()) and delete it without
removing it from the chain first. It can happen when reading the
SUPER-PROCEDURES attribute on the SESSION or procedure handles, or when
trying to run a procedure or user-defined function.

Issue Number: OE00222588
     Error 12927 running procedure on a handle, with a class property

When running an external procedure on a handle derived from a class
property, ths results in error 12927 at compile time:

Could not locate element 'AppSrvHdl' in class 'TestClass'. (12927)

Issue Number: OE00222733
     TYPE-OF can throw a System.NullReferenceException

The TYPE-OF() function, when used on an ABL object that inherits from .NET
or implements a .NET interface, throws a .NET NullReferenceException when
the object and type being compared are not the same.

Issue Number: OE00222881
     WRITE-XML is not correctly encoding non-printable characters

If a temp-table contains non-printable strings (e.g. chr(1)), this
temp-table cannot not be written to an XML-document any longer. Error
"WRITE-XML encountered an error loading XML into an X-DOCUMENT or
X-NODEREF object: FATAL ERROR: file 'MEMPTR', line '4', column '0',
message 'invalid character 0x1'. (13195)"  is thrown at runtime.

Issue Number: OE00222908
     Long menu labels with accelarators can crash client

The ABL GUI client can crash displaying a window if menu items have labels
with more than 72 characters and long key sequences for accelerators (such

Issue Number: OE00222953
     Browse ADD-LIKE-COLUMN method may crash OE session

The AVM session may crash when the ADD-LIKE-COLUMN method is used to add
the first column to the browse.

Issue Number: OE00223037
     RETURN ERROR AppError from trigger invalidates error object

When using a "RETURN ERROR AppError." statement from within a database
schema trigger, the AppError object gets deleted when the trigger ends,
even if there are references left to it elsewhere in the session (for
example, because the trigger stores a reference in a temp-table maintained
outside the trigger).

Issue Number: OE00223210
     Fwd slashes to reference xml file in READ-XML method; error 1303

Using forward slashes to reference an XML file in the READ-XML method
results in the following errors:

Error reading XML file '<filename>'. (13035)

READ-XML encountered an error while parsing the XML Document:

FATAL ERROR: file '', line '0', column '0', message 'unable to open
primary document entity '<filename>''. (13064)

Issue Number: OE00223376
     READ-XML  truncates temp-table field names

READ-XML truncates dynamic temp-table field names if they are longer than
32 characters.

Issue Number: OE00223438
     Session crash when executing APPLY "WINDOW-RESIZED" to a window

Applying the WINDOW-RESIZED event to a window which hasn't been realized
causes the session to crash.

Issue Number: OE00223445
     MouseDoubleClick event on Tree node doesn't restore minimized .W

Setting the WINDOW-STATE attribute of a minimized window to WINDOW-NORMAL
(3) doesn't always restore the window when WINDOW-STATE is set in a
trigger for an UltraTree mouse double-click event.

Issue Number: OE00223775
     Multiple calls to X-Document:SAVE() terminates session abnormall

Invoking the X-Document:SAVE() method causes an attribute of the root
element to be deleted.

Invoking the X-Document:SAVE() method a second time against a document
whose root element has more than two attributes, terminates the session

Issue Number: OE00223870
     Windows Update (MS Sec. Bulletin MS12-060) replaces MSCOMCTL.OCX

Windows Update for 08/14/2012 pushed a new version of MSCOMCTL.OCX. The
update is described in Microsoft Security Bulletin MS12-060 - Critical at Controls in
this OCX used in OpenEdge GUI applications become unusable.

Issue Number: OE00223969
     Infinite loop in editable browse with VALUE-CHANGED trigger

An editable browse that has a VALUE-CHANGED trigger that applies ENTRY to
the browse causes an infinite loop upon entry of an editable cell.

Issue Number: OE00224001
     OE 11.1 client COPY-LOB corrupts XML

When using COPY-LOB to copy an XML file from a database CLOB to a file,
the resulting  XML file is corrupted.  A few characters are missing from
the beginning. This only occurs when a remote win32 client is connected to
a database server on a 64-bit platform.

Issue Number: OE00224019
     SYSTEM ERROR: Attempt to define too many indexes for area 6 data

SYSTEM ERROR: Attempt to define too many indexes for area 6 database

Issue Number: OE00224068
     Error (2881) compiling a large number of procedures

When a client runs a procedure that compiles a large number of procedures,
the rcdaxxxx file grows and the compiling procedure eventually fails with
the error:

SYSTEM ERROR: Corrupted run-time segment chain. (2881)

without compiling all the procedures.

Issue Number: OE00224179
     Unexpected "Default Beep" sound during interaction with a window

An unexpected "Default Beep" sound is produced when the user clicks on the
title bar of a window in an OpenEdge application.

Issue Number: OE00224669
     Identical LONGCHARS written with WRITE-XML/JSON not equal

Two identical LONGCHARs written with WRITE-XML or WRITE-JSON can fail an
equality test under the following circumstances:

- using -cpstream UTF-8

- the codepage of the LONGCHARs is fixed to UTF-8

Issue Number: OE00225218
     Client doesnt close with QUIT in OCX event and IOEverywhere 1

The Quit statement doesn't cause the application to exit when executed
from an OCX event handler.  However, any subsequent keystroke will close
the application.

Issue Number: OE00225371
     Wrong index key created if char field built with function calls.

When using a UTF-8 database, the wrong index keys can be created for
indexed character fields.

This occurs only when the result of calling an ABL date-time function is
to converted to character string and then that string is assigned to an
indexed character column in a database table.

Issue Number: OE00225418
     JsonObject:GetLongChar() gives error (12008) with UTF-8

The JsonObject:GetLongChar() method will generate the following error if
the AVM is started with -cpinternal UTF-8:

  Invalid character code found in data for codepage UTF-8 (12008)

Issue Number: OE00225426
     find-by-rowid gets error 7328 & 10041 when using named buffer

Using the method find-by-rowid on a named buffer results in error 7328 &

Issue Number: OE00225633
     WAIT-FOR Application:Run breaks ALT keys

When using a COM control that is implemented in .NET, then using the .NET
event loop (e.g. WAIT-FOR System.Windows.Forms.Application:Run()), ALT key
sequences on the numeric keypad might no longer generate the intended
non-ASCII characters in OE widgets. One example of such a key sequence is
the Euro symbol ALT-0128.

Issue Number: OE00225692
     2nd READ-XML into same dynamic dataset misses data

Using READ-XML to construct a single dynamic prodataset, if you load 2 XML
files with the same dataset name but different table names, for the second
READ-XML the tables are added to the existing dataset.

If the tables created by the second READ-XML() have fields that are being
renamed because the XML node name matchess an ABL keyword, those fields
are not populated when data is loaded from the XML into the table.

Issue Number: OE00225722
     65536: maximum number of sub-transactions

A savepoint counter overflows after 65535 assignments. As a result not
everything is being restored during rollback leading to various database

Issue Number: OE00225759
     LOAD-MOUSE-POINTER doesn't work for a browse

The LOAD-MOUSE-POINTER method doesn't work for a browse widget. The arrow
cursor is shown instead of the cursor set by LOAD-MOUSE-POINTER.

Issue Number: OE00226146
     Task Manager shows incorrect windows in the Applications tab

The Windows Task Manager may show one or more windows labeled "Progress"
which are not part of the application being run. These windows are not
meant to be visible and do not affect the execution of the application.

Issue Number: OE00226272
     Memory leak with DELETE OBJECT and object refs in a temp-table

There is a small memory leak which occurs if an object is deleted using
the DELETE OBJECT statement and there are references to the object in a
temp-table. For every reference to the object in a temp-table, a small
amount of memory is leaked when the object is deleted using the DELETE
OBJECT statement.

Issue Number: OE00226415
     FIND on global BUFFER in internal procedure can crash client

A program can use a global BUFFER for a table, and FIND on this BUFFER in
an internal procedure. There is a corner case where a long running
program, performing such a FIND on the BUFFER in a loop, can crash the
client. The following code demonstrates such a situation, run against the
sports2000 database:

RUN findcust.

PROCEDURE findcust:

  DO i = 1 TO 0x100000000:
      FIND FIRST customer WHERE
   customer.custnum = 1 NO-LOCK NO-ERROR.
MESSAGE "Completed".

This is more likely to occur in programs with few global BUFFERs and few
FIND statements.

Issue Number: OE00227527
     Clicking on a toggle-box may cause session to crash

Clicking on a toggle-box while the PROCESS EVENTS statement is executing
may cause the session to crash.

Issue Number: OE00227530
     COPY-LOB of CLOB to file not observing NO-CONVERT

When executing the COPY-LOB statement from a CLOB to file using
NO-CONVERT, the AVM will incorrectly convert the CLOB data to the
-cpstream codepage. COPY-LOB for a LONGCHAR to file with NO-CONVERT will
correctly leave the data in the LONGCHAR's codepage in the file.

Issue Number: OE00228986
     Alert box or system dialog box cancels dialog box modality

If an alert box (MESSAGE ... VIEW-AS ALERT-BOX) or system dialog box
(SYSTEM-DIALOG) is displayed while a dialog box is active, upon dismissing
the alert box or system dialog the dialog box will no longer be modal with
respect to the window which displayed it.

Issue Number: OE00229105
     Spurious pixels displayed after install of

After installing the hotfix and then starting the GUI client,
there is a pixelated area displayed in the top left hand side of the

Issue Number: OE00230746
     Client hang with STOP in OCX event and IOEverywhere 1

The client can hang when executing a STOP statement from a codejock choose
event. After the STOP the code appears to return out of the ocx correctly
until it gets to the last END PROCEDURE in the Execute procedure.  At this
point it appears to hang and does not restart the startup procedure.

ABL Internationalization
Issue Number: OE00124868
     Unable to convert to codepage IBM278 in OpenEdge 10.x

Conversions to codepage IBM278 fails with error 6063 in OpenEdge 10:

Code page conversion table for <codepage> to IBM278 was not found in
convmap.cp. (6063)

Issue Number: OE00223812
     COLUMN-LABEL with multi-byte chars have excessive width in UTF-8

When using -cpinternal UTF-8, if the COLUMN-LABEL of a field contains
multi-byte characters, the width allowed for the field in the frame in the
GUI client can be calculated much wider than necessary. This depends on
the number of multi-byte characters and where they are in the COLUMN-LABEL

ABL Web Services client
Issue Number: OE00215392
     Bprowsdldoc fails due to included schema with no targetNamespace

In some cases the WSDL Analyzer returns the following error due to
included schemas with no targetNamespace:

Error loading WSDL document somedocument.wsdl : Cannot resolve reference:
SomeType{[null]} for construct [null]{[null]} (11748)

ADE Tools and Runtime
Issue Number: OE00223387
     Data Admin/Dictionary showing old area for alternate buffer pool

Data Admin/Dictionary showing old area for alternate buffer pool

Issue Number: OE00223506
     Need to be able to compile and run GUI app on 64-bit OE license

Need to be able to compile and run GUI app on 64-bit OE license

Issue Number: OE00223958
     SDO viewObject procedure override does not execute

Code placed in an SDO (Smart Data Object) viewObject procedure override
does not execute when the application Window containing the SDO is

ADE Tools and Runtime Translation Manager
Issue Number: OE00110396
     Error 12272 when creating a zip file in Translation Manager

Error 12272 is raised when trying to create a zip file of a kit in the
TranMan - "A variable or array element passed as an INPUT or INPUT-OUTPUT
parameter to a DLL cannot contain the Unknown value. (12272)"

Issue Number: OE00204492
     AppServer broker vulnerable to potential DoS attack

AppServer broker is vulnerable to a denial of service attack that may
occur if a thrid-party client sends a specific sequence of packets over
time to the listening socket, using the AppServer communication protocol.

Issue Number: OE00229749
     Error 16506 incorrectly appears after wrong username/password

When an AppServer client passes incorrect credentials that are used to
connect to a database from within the Connect procedure and the connect
statement is in a transaction, this causes the AppServer agent to disallow
all future connections.  Whenever another user attempts to connect to the
AppServer from that point forward, the Connect procedure dies without ever
being loaded.

Issue Number: OE00133544
     Online backup displays incorrect estimate of media needed

Online backup displays incorrect estimate of media needed to perform the

Issue Number: OE00181281
     .df fails to load against a database with many extents on Linux

Linux platforms fail to process keys and socket events if a database with
too many extents is connected in self-service/single-user mode when a .df
is loaded or the debugger is initialized.

Issue Number: OE00195011
     Incorrect PID displayed in database log

On AIX In some circumstances a PID of broker or server process may be
displayed with an incorrect value.

Issue Number: OE00205473
     Probkup message from failed backup across network hangs process

Probkup message, from sending the backed up file across a network, where
the network has registered failed writes hangs the probkup process.  It
sees it as an end of file and response with Please enter the next
device/filename or type "quit" to exit. Need to have the backup end
whenever there is a failed network connection rather then waiting on some

Issue Number: OE00219468
     C/S connection fails 437 file with same name as DLC

If OE is install directory contains a space, eg: C:\Program Files\OpenEdge
And a file exists with the same name as the first word before the space
eg: C:\program
And the database is started under the AdminService
Then Client-Server connections will fail with error
Disconnected from server because database name was incorrect. (437)

Issue Number: OE00219703
     idxbuild hang or crash

idxbuild hang or crash when using 10.2B06 new performance tuning

Issue Number: OE00220955
     Getting buffer stack underflow running dbanalysis against DB

Getting buffer stack underflow running dbanalysis against DB which causes
database to crash.

Issue Number: OE00221434
     Memory leak for remote ABL client

Memory leak for _mproserv with ABL connect statement.

Issue Number: OE00221813
     Idxbuild does not properly exit when expected

Idxbuild does not properly exit when expected after issuing a negative
response to query y/n.

Issue Number: OE00221877
     the _mprosrv process leaks memory on 32-bits only

This is leak that happens for every new query.

Issue Number: OE00222002
     Abnormal database shutdown due to a manual kill -15

It is possible, but unlikely, that a database could shutdown abnormally if
a self-service client process is terminated using kill -15. The
appropriate way to terminate the client's connection to the database is
using promon.

Issue Number: OE00222318
     Online added AI files with fixed variable size over grow limit

Online added after image files do not switch at their fixed variable
They continue to grow and can cause disks to completely fill or reach
ulimit as opposed to their fixed varible size.

Issue Number: OE00223055
     idxbuild -TF >0 with mergethreads mis-reports memory usage

It has been determined that the message in the .lg file:

Max merge pool entries estimated at: 91841 w/memory usage: 1812987904

has an overflow bug in it.

Issue Number: OE00223147
     Database activity drops suddenly, clients stops responding

Database activity drops suddenly, clients stop responding, while waiting
for latches to be released.

Issue Number: OE00223299
     Proshut process does not return after immediate shutdown.

Proshut process does not return to calling process or script after and
immediate shutdown has been issued and the process was killed.

Issue Number: OE00223542
     _mprshut process assoc. with keyeventrdr goes runaway with CPU

_mprshut process assoc. with keyeventrdr goes runaway with CPU

Issue Number: OE00223567
     Error  _area record not on file(138) generating incremental DF

Error  _area record not on file(138) generating incremental DF

Issue Number: OE00223950
     Intermittently key event reader process doesn't shutdown

Intermittently the _mprshut key event reader process does not shutdown
after an emergency shutdown.

Issue Number: OE00224728
     db conv to OE 11 with multitenancy causes required credentials

After a database conversion from a database without any credentials
defined under 10.2B to version 11.0 or 11.1, and after Multi-tenancy is
enabled for that converted database credentials are then requested when
connecting to that database.

If a user is then created in that database (by logging in to the database
by pressing ESC and therefore bypassing entering a user and password) then
on future restarts of the database no access to that database is possible
anymore to the database. (all database data becomes unavailable to anyone)

Issue Number: OE00227173
     Temp sort file grow every time that a query is executed

When running a search that has any wildcard in a word-index, the search
will create an srt file on the db server. If the query returns a large of
number of rows (greater than 100,000) then space in the sort file is not
entirely re-used and the .srt can grow very large.

Issue Number: OE00227977
     Differences in OE11 schema after running conv1011

During conversion the utility (dbutil conv1011) adds the _File._category
column and sets its value to blank space instead of a string of one blank

Issue Number: OE00229505
     prefetchfactor can cause a hang with no-lock queries

Using prefetchfactor has been shown to cause a hang with no-lock queries.
The hang occurs when the network buffer is filled to exactly the
percentage specified in prefetchfactor after rounding.
This caused and issue with a "<=" vs "<" check in the networking code.

Issue Number: OE00230964
     conv1011 change the BI cluster size from 16Mb to 16kb

conv1011 change the BI cluster size from 16384 kb to 16 kb.

Database Failover Clusters
Issue Number: OE00220957
     Replication faiilover will fail if last transaction was undone

Replication failover will fail if at least one transaction had completed
successfully but the very last transaction was in the begin state and was

Database Shared Memory
Issue Number: OE00221539
     Slow checkpointing when using large -B on Windows 64-bit

Database checkpoints take longer and longer on Windows 2008 64-bit when
using large -B.

Issue Number: OE00216717
     Table definiton incorrect after warning raised during pro-to-ora

Warning during pro-to-ora could leave the dataserver schema table
definition as follows:

- No description or dump name
- fields and table names are uppercased
- labels and initial values are incorrect
- datetime field is converted into 2 fields

Issue Number: OE00219750
     MSSDS displays wrong err msg when row size exceeds buffer limit

Microsoft SQL Server DataServer displays confusing error message when row
size exceeds buffer limit.  The procedure editor also resets itself but
still connected to MS SQL Server which causes to lose the ABL code.

Issue Number: OE00222491
     For each query > "" <> TRUE fails on SQL table

A joint condition with a string evaluation in the ABL query results in a
corrupted SQL query

Issue Number: OE00222952
     Session crash loading MSS Dsrv delta.df

Data Administration session crashes when loading incremental delta .DF
files into schema holder for DataServer for MS SQL Server.

Issue Number: OE00223564
     OpenEdge 11.0 SQL DataServer 32-bit r-code crashes 64-bit client

When code that is to be executed by the DataServer engine is compiled with
a 32-bit version (resp. 64-bit) of OpenEdge 11.0 (or 11.1) it crashes
(producing a protrace) when run on a 64-bit (resp. 32-bit) version of
OpenEdge 11.0 (or 11.1).

Issue Number: OE00224297
     Client crash checking syntax against MSS DataServer

Client crashes when checking syntax a query in the format similar to the
following against DataServer for MS SQL Server:


     EACH b USE-INDEX y OF a:

Issue Number: OE00225208
     Table labels removed after Update / Add Table Definitions

Table label is set to '?' after performing Update / Add Table definitions
against an existing table.

Issue Number: OE00225776
     Rerun same ABL query with FIELDS() -> different SQL query

If the exact same ABL query is being run multiple times (= from the same
internal procedure, and with the same where clause) and that query has a
FIELDS() list, on the second run the Oracle dataserver with generate a new
SQL query with a different list of fields in the SELECT when it should
re-use query created during the first one.

In addition, the second SQL statement does not include the fields
specified in the ABL FIELDS() list, so the ABL code will not be able to
run as expected.

Issue Number: OE00226396
     Table parameters does not get created in sh holder with protomss

Table named "parameters" does not get created in schema holder with

Issue Number: OE00226418
     Open Query with outer-join might cause an SQL error

An Open Query with OUTER-JOIN causes one of the following SQL errors when
the two tables in the query contain multi-component primary or unique

37000: [Microsoft][SQL Server Native Client 10.0][SQL Server]The
correlation name 'T1' is specified multiple times in a FROM clause.

37000:[Micorsoft][SQL Server Native Client 10.0][SQL Server]Statement(s)
could not be prepared.

DataServers MS-SQL
Issue Number: OE00211239
     Client crashes executing query referencing sql view in ms sql

Client crashes when executing a query against a ms sql server database
that references a view.  The MS SQL Server db is created via protoMSS
using computed columns

Issue Number: OE00226541
     MATCHES returns false when variable is left side of the match

MATCHES returns false when variable is left side of the match running
against MS SQl Server DataServer

Issue Number: OE00225630
     Data Administration missing in 11.1 SL Dataserver Documentation.

The docs are missing references to Data Administration.

Documentation ABL
Issue Number: OE00216359
     References to certain attributes no longer require casting

Each of the following attributes references an instance of
Progress.Lang.OERequestInfo or Progress.Lang.OEVersionInfo:

attributes of the SESSION system handle

o REQUEST-INFO and RESPONSE-INFO attributes of the server object and
asynchronous request object handles

In previous releases, the object in each instance was stored as a
Progress.Lang.Object, which required a downward cast to access members of
the OERequestInfo or OEVersionInfo class. With release 11.2, these objects
are stored with the respective Progress.Lang.OERequestInfo or
Progress.Lang.OEVersionInfo class type, and therefore no longer require a
downward cast to access their members. However, note that any existing
code that includes this downward cast will continue to work.

Graphical User Interface
Issue Number: OE00221108
     Error 382 with SmartPanel pupdsav if query returns 0 rows

Using a SmartPanel to navigate/populate a SmartDataBrowse returns error
382 after performing the following sequence of actions: Add a record ->
Reset values -> Cancel action -> Add another record. This only occurs if
the SDO query returns zero rows.

Issue Number: OE00227038
     REFRESH() in ROW-LEAVE trigger loses characters in UTF-8 session

In a Unicode session (started with -cpinternal utf-8), calling the
REFRESH() method of a browse widget from within a ROW-LEAVE trigger on the
same browse widget a character field will truncated the data if it
contains extended characters (ASCII value higher than 127).

The number of characters remaining will be ( <length specified in field's
format> - <number of extended characters before the cutoff point>), with a
maximum of half the string being lost.

Issue Number: OE00223094
     If DLC is set as one of the system variables, install hangs

If DLC is set as one of the system variables, install hangs

Issue Number: OE00226967
     Password encryption utility bin/genpassword missing

Password encryption utility bin/genpassword is missing in database license

Installation Install
Issue Number: OE00222209
     11.1 silent install fails to install PDS

'm getting an error when doing a silent install of 11.1 Progress developer
studio.  If I run the install manually, it works. 
Steps to reproduce:
On a clean windows 7 64 bit OS with .net4.0 (and the ms document explorer)
already installed.
1) Install Progress 32bit manually and select the following options:
1.a) OE Enterprise RDBMS
1.b) OE Application Svr Ent
1.c) OE Studio
1.d) Progress Dev Studio OE
2) Selected c:\ProgressV11\OpenEdge and c:\ProgressV11\wrk_OpenEdge as the
installation folder/work folder.
3) Selected similar folders for the oemgmt folders (it defaulted nicely).
4) Did Complete installation
5) Unchecked Sonic ESB Adapter and WebSpeed Messager.  Left Progress
Dynamics Unchecked.  Kept OE Explorer/management checked.
6) Left program folder defaulted to Progress\OpenEdge 11.1
7) Left the default (Engish - American) and clicked next
8) Picked 1252 Basic Basic and clicked next.
9) Left the default info for the webservices adapter dialog and clicked
10) Left the default info for the admin server authorizations and clicked

When it finished installing, save the c:\Windows\oe_response.ini and the

Note that the oesetup.log indicates a successful install and that the PDS
install completed.

Now do a silent install on a clean OS with .net 4.0 and MS Document
Explorer already installed.
Create a C:\ProgressV11 folder and put the oe_response.ini from the manual
install there.
setup.exe -psc_s -psc_f1=c:\ProgressV11\oe_response.ini

When that finishes, the log file will show a failure witht he PDS install.

The same process works with OE 11.0.

Issue Number: OE00217196
     Background processes fail to start due to code page mismatch

When using OpenEdge Explorer for database configuration and there's a
difference in international settings for code page, collation table,
cpstream, etc between the database ( and the contents of
%DLC%\, the background processes (aiw, biw, apw, wdog) fail to

Issue Number: OE00217915
     fmconfig -enable fails on HP-UX

The fmconfig -enable command fails on HPUX with the following errors:

ERROR: Remote monitoring is not supported with this version of JAVA:
ERROR: Remote monitoring on this platform requires a newer version of
JAVA:  HP-UX 1.5.0

Issue Number: OE00220558
     OE Management reporting many errors regarding vst for trend db

OpenEdge Management is reporting many Data storage errors in the
admserv.log file on startup associated with recGetValues for fields in the

Issue Number: OE00221827
     OpenEdge Management defaults action set to none on Monitoring Pl

OpenEdge Management defaults action set to none on Monitoring Plans.

Issue Number: OE00222332
     10.2B container configuration Managed by 11.0 OOE are grayed out

Unable to edit 10.2B container configurations managed by 11.0 OOE

Issue Number: OE00225268
     Adjust timeout of remote adminservers

Adjust the timeout for remote adminservers losing connection with OEM.

Issue Number: OE00225272
     Adding compression to getstatistics and getschema calls

Adding compression to minimize the amount of data sent over the network to
reduce the possibility of container status timeouts.

Management Management
Issue Number: OE00220236
     Fathom Bookmark cant be switched off when using log file monitor

"Fathom Bookmark" is being written to the file monitored by OEM log file
monitor despite being disabled in the LFM resource properties.

Message Number Change
Issue Number: OE00216652
     Adminport not increment in OpenEdge 11.0 which should

Adminport not increment in OpenEdge 11.0 which should

Open Client
Issue Number: OE00212444
     DataSet Generation Differs for .NET 2.0

The strongly-typed classes generated for a static dataset differs with
.NET 2.0 versus .NET 1.1.  This causes problems during proxy generation.

Issue Number: OE00220200
     .NET OpenClient tracing logs cannot be read by other processes

When a .NET OpenClient application has tracing turned on, the generated
log files cannot be read by any other processes while the OpenClient
process is running. The OpenClient process needs to close the log or
terminate before other processes can read the logs.

Issue Number: OE00220559
     NullRef Error During Garbage Collection

It is possible during .NET garbagae collection for the .NET Open Client
runtime to throw a NullRef exception.

Issue Number: OE00220561
     .NET Open Client Throws Unhandled NullReferenceException

When reading messages from the network it is possible for .NET Open Client
to throw an unhandled NullReferenceException

Issue Number: OE00221554
     .Net client to be able to set readtime out to infinite

No provision to set the timeout value to be infinite for the socket read
in .Net client.  This causes a default value of 2000 ms for the timeout
which causes timeout on the long running application through ssl.

Issue Number: OE00223924
     Error 12324 occurs when passing .NET DSet to DSet-Handle

Retrieving a dataset (not via handle) from the AppServer, where the
dataset contains a temp-table with a non-unique index, will fail with
error 12324 when you pass the retrieved dataset back to the AppServer and
the input parameter is a dataset-handle.

ERROR condition: Remote mismatched fields or mismatched BEFORE-TABLE
attribute for temp-table parameter or dataset member parameter. (12324)

Issue Number: OE00224024
     .NET Open Client Cannot Connect Using IP Address

In OpenEdge 11.1, the .NET Open Client product cannot connect to an
AppServer using an IP address.

Issue Number: OE00226627
     WSACancelBlockingCall Exception in .NET Open Client

If the .NET Open Client sends a message out on the UDP socket but gets no
response and times out, the retry mechanism fails to catch this and .NET
ends up throwing a WSACancelBlockingCall exception.

OpenEdge GUI for .NET
Issue Number: OE00218060
     System.OutOfMemoryException using Combit List&Label

When generating a report with Combit List & Label, based on a ProDataSet
with 2 temp-tables with a defined relationship, where the first table
contains several thousand records, an exception occurs:

System.OutOfMemoryException: Exception of type
'System.OutOfMemoryException' was thrown.

Issue Number: OE00219233
     Focus lost in embedded ABL window after displaying modal dialog

If a dialog box or alert box is displayed while focus is in an ABL window
which is embedded in a .NET form, focus will not return to the embedded
window when the dialog box or alert box is dismissed. Focus may go to a
.NET control in the form or focus may appear to be lost.

Issue Number: OE00221901
     Non-GUI clients don't support -preloadCLR on Windows

OpenEdge 11.0 batch clients (_progres), AppServer agents and WebSpeed
agents generate error 1610 when attempting to use the -preloadCLR

-preloadCLR is not supported by this executable. (1610)

Issue Number: OE00222022
     -IOEverywhere 1 causes (13967) mixing .NET forms and smartWindow

If a .NET form is launched using a WAIT-FOR application:Run(), this form
runs a (non-embedded) SmartWindow persistently, and the SmartWindow
launches a second .NET Form using a WAIT-FOR ShowDialog(), the client will
throw a "You can only use a .NET-specific input-blocking statement
(WAIT-FOR x:y()) once any .NET forms are shown (other than to wait for an
ABL dialog box).  (13967)" when the dialog form is closed.

This issue is only seen if the -IOEverywhere 1 parameter is used.

Issue Number: OE00222175
     System.ComponentModel.IdataErrorInfo implementation issue

The System.ComponentModel.IdataErrorInfo implementation of the
ProBindingSource causes an error to be shown only on the selected row, not
on each row which contains an error, which is what it should do.

Issue Number: OE00222715
     Removing previousState property breaks existing applications

The previousState property is no longer public, so this breaks existing
applications that accessed it.

Issue Number: OE00222740
     Passing a .NET Exception to Progress.Lang.Error.causes 13448

Passing a .NET Exception object as a parameter to a routine expecting
Progress.Lang.Error fails with error 13448 (class incompatibility error)
in OpenEdge 11.1.

Issue Number: OE00223554
     GUI client hangs using Keep3DFillinBorder=yes

The GUI client can hang when using the Keep3DFillinBorder=yes setting in
the registry or ini file. Moving focus away from the application then back
again resolves the problem. Setting Keep3DFillinBorder=no works around the
problem, at the expense of the visual aesthetics of the fillins.

Issue Number: OE00224318
     Error assigning interface instance to obj defined as interface

Error 13448 (classes are incompatible) is raised when an object instance
that implements a .NET interface is assigned to a variable defined as that
interface type.  This only happens when the object instance was created
with a private constructor.

Issue Number: OE00225070
     Focus lost after dismissing MESSAGE VIEW-AS ALERT-BOX

If an alert box is displayed when focus is in an enabled browse cell in a
window which is embedded in a .NET form, focus will appear to be lost when
the alert box is dismissed.

Issue Number: OE00225229
     NullReferenceException in .NET Bridge when using ACTIVE-FORM

A NullReferenceException may occur when an application references the
ACTIVE-FORM system handle.

Issue Number: OE00228262
     AVM crash calling GetClass on object implementing .NET interface

An OOABL class can implement a .NET interface. If there is a call to the
GetClass() method on an object o this type, or the
Progress.Lang.Class:GetClass() method is used on the class, the AVM will

Issue Number: OE00228411
     Memory leak using .NET classes

When using .NET classes that override the GetHashCode() method, it is
possible that the AVM will maintain a reference to a .NET object, thus
causing a memory leak. This can happen when changing a property of .NET
object causes a different return value from GetHashCode(). An example of
this is the classes implementing the
Infragistics.Documents.Excel.IWorksheetCellFormat interface.

OpenEdge Replication
Issue Number: OE00225519
     Installing OE10.2B07 Service Pack breaks Replication

The replication server fails during startup when reading recovery file

Issue Number: OE00228024
     RPAGENT.EXE RPSERVER.EXE startup fails when spaces in directory

Replication Server and Agent fail to start when the installation directory
contains spaces eg: C:\PROGRAM FILES\OPENEDGE\DLC\BIN. Problem introduced
in 10.2B07 and 11.1.0, fixed in 10.2B08 and 11.2.0.

OpenEdge Replication Replication
Issue Number: OE00226985
     increase limit of -pica queue to 1000000

The -pica queue limit has been increased to 1000000.

OpenEdge Replication Utilities
Issue Number: OE00199297
     Autostart after transition can only start a primary broker

Replication is unable to autostart a secondary broker after transition.

Progress Developer Studio for OpenEdge
Issue Number: OE00222151
     PDSOE doesn't create include files during compilation

Progress Developer Studio for OpenEdge doesn't detect that files use
WSMETA NAME="wsoptions" CONTENT="include" in Speed Script and the
corresponding include file is not generated when html is compiled from
OpenEdge Editor.

Issue Number: OE00222519
     "Source not found" when stepping into a procedure in debug

ABL Debugger fails to step-in to any procedure files referred in main
procedure being debugged, if only name of procedure (without extension) is
used, for example "Run gp_proc2", instead of name with extension, for
example "Run gp_proc2.p".

Issue Number: OE00222582
     Buffer in method parameter crashes the debugger

Defining a buffer as a method parameter can crash the Progress Developer
Studio for OpenEdge debugger.

Issue Number: OE00222720
     Update Assembly References lists only Infragistics2 assemblies

The OpenEdge 11.1 Developer Studio "Update Assembly References" tool lists
only Infragistics2.* (CLR 2.0) assemblies in the "New Assembly Reference"

Issue Number: OE00222885
     PDS for OE help tooltip shows wrong help for method

When hovering with the mouse over a specific method (ie: buffer-copy),
it shows the help description of the statement with the same name instead.

Issue Number: OE00223352
     In OpenEdge 11.1 Studio, "Background" property of .NET objects i

ABL Source editor shows warning for case of ABL keywords based on
preference settings (Windows->Prferences->Progress OpenEdge->Editor).
In PDSOE 11.1, case warning is being shown for non-ABL keywords. For
example "oObject:Background", here "Background" is attribute of object
"oObject" , not a ABL keyword. So case warning should not appear for the

Issue Number: OE00223407
     Startup parameter "-assemblies" no relative path accepted

This is a regression issue, in OE 11.0 it works fine.

If you try to set a relative path to the startup parameter "-assemblies"
in the Project Properties in the startup parameters field, it gives error
"Please enter a valid directory path containing assemblies xml file".

If you set the absolute path it works fine.

Issue Number: OE00223655
     OEA 11.1 Visual Designer code generation/parsing not working as

OEA 11.1 Visual Designer code generation/parsing not working as expected
with German locale.

Issue Number: OE00225146
     Cannot import database configuration into a shared AVM

A database configuration from another workspace cannot be imported into a
project using a shared AVM.

Issue Number: OE00226094
     AppBuilder perspective fails to render window borders

In the PDS:OE AppBuilder perspective, if the AppBuilder is run in embedded
mode the window borders for the Object Pallette and the AppBuilder main
window are not rendered.

The pro*tools window is rendered as expected.

Note that the area for the window borders is there, and is functioning as
expected even though it's not drawn (clicking and dragging where the title
would be will move the window, clicking where the X button would be closes

Progress Developer Studio for OpenEdge AppBuilder Support
Issue Number: OE00217457
     Override button disabled for ADM1 objects in OEA AppBuilder

When the AppBuilder is run in Progress Developer Studio for OpenEdge, and
a new procedure is added to an ADM1 object, the Override radio set button
is disabled in the New Procedure dialog.

Progress Developer Studio for OpenEdge Editing
Issue Number: OE00148757
     Deleting multiple triggers in PDSOE leaves extra code

When editing a .w file in Progress Developer Studio for OpenEdge, if you
use the Outline view to select and delete all of multiple successive
triggers for the same widget, the following part of the trigger code is
not deleted: &Scoped-define SELF-NAME <widget-name>.

Progress Developer Studio for OpenEdge Visual Designer
Issue Number: OE00224173
     Unable to open designer if creating object with parameter mode.

Visual designer doesn't load the form if initialization component method
contains object creation with parameter mode (INPUT, OUTPUT or

Issue Number: OE00201897
     PROMSGS description of error 13216 should be modified

Description of the error 13216 should be modified to include entire error.
Not an abbreviation of the actual command.

Report Builder
Issue Number: OE00229704
     PRORE32 returns error 16395 in 11.1 using DataServer schema

Report Builder Runtime Engine (PRORE32.EXE) shipped with OpenEdge 11.1
returns error 16395 when attempting to display a report that was created
against a DataServer schema and the -U -P parameters are supplied in the
RB-DB-CONNECTION override parameter.

** -P and -U startup parameters require an authentication enabled domain

Issue Number: OE00216767
     SQL engine prepares query containing JOIN and UNION incorrectly

For SQL queries containing a JOIN and a UNION, the SQL engine may choose
an incorrect index when preparing the query. This may cause incorrect
results to be returned from the query.

Issue Number: OE00216909
     JDBC not working with service name

JDBC driver is not working with service name in connection URL in Windows
7 and Windows 2008.

Issue Number: OE00220314
     Encountered internal error in SQL ENGINE in sts_aggrun.cxx

Running a SQL-92 query with aggregation and huge number result rows will
produces the following error:

java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver][OpenEdge]
Encountered internal error in SQL ENGINE at 1200 in
Z:/vobs_sql/sql/src/sts/sts_aggrun.cxx. Contact Progress Technical Support

Issue Number: OE00220423
     Internal error when querying a table during multi db connection

When connected to 3 identical databases and running a SELECT statement
with WHERE clause against a table in the the second aux database, the
query fails with internal error.

Issue Number: OE00221587
     Internal error -2 upd a record w/view w/check opt after a col dr

Internal error -2 when drop a column from a middle of a table and then
updating a record using a newly created view  with check option.

Issue Number: OE00222266
     JDBC connection abort error when running sql with case stmt

JDBC "connection abort: recv failed" error when querying database using
select with parametrized case statement in it. The sqlsrv2 process
creates protace file.

Issue Number: OE00222732
     MultiComponent Index + before update trigger gives internal erro

Internal error -1214 happens when a wider range of index configurations
(using multi-component indexes) is used, and a particular pattern of index
key updates is done by the application's sql triggers. There is a good
probability that this type of situation would occur in a large-scale
application environment,

Issue Number: OE00223152
     SQL command is hanging after to migrate from 10.1A to 10.2B

SQL command is hanging after to migrate from 10.1A to 10.2B.
This can occur with a query involving the MINUS set operator where the
MINUS occurs in a derived table in the query and there is more than one
table on either side of the MINUS operator.
This could also occur with the INTERSECT set operator.

Issue Number: OE00223251
     Catalog name not found in OpenEdge 10.2B

Catalog name not found error thrown in OpenEdge 10.2B when create table as
select contains derived table.

Issue Number: OE00223727
     _sqlsrv2 process runs for ever when using multiple IN ( values )

While running a query which involved 17 tables join, correct join order is
not selected due to which query runs very slow. This problem is
independent of values in IN list.

Issue Number: OE00224063
     Strange characteres on column names using ODBC

When connected via ODBC driver and use column name alias that contains
special characters, these characters are not been displayed correctly.
This happens only on the label (title) of the column, not for the data

Issue Number: OE00225045
     SQLSCHEMA can fail if table name is a reserved word.

SQLSCHEMA can fail if table name is a reserved word and resulting .dfsql
is incomplete.

Issue Number: OE00225292
     SQLSCHEMA output does not preserve CRC

Tables created using SQLSCHEMA output does not preserve CRC, which causes
binary load to fail.

Issue Number: OE00225723
     SQL query slowdown after update index statistics

Prior to 11.2 release, a query that normally runs in 3 or 4 seconds
without updating statistics, it takes about 20 seconds after update them
involving some tables and joins. Following is the update statistics

Issue Number: OE00228218
     SQL92 - Updating field in SQL Trig assigns array flds to NULL

Updating a field in a table using a SQL Trigger causes all array fields in
the table to be set to NULL.

SQL Server
Issue Number: OE00135348
     The SQL Engine always treats a column named ROWID as a function

Beginning with Progress 9.1E, the SQL engine always treats a column named
"ROWID" (whether it is delimited or not) as a function.

Issue Number: OE00216746
     Getting Internal error when union-index-join is used

Queries with UNION and UNION ALL set operator will not report internal
error. Will return valid result set.

Issue Number: OE00223136
     Query with large WHERE IN clause crashes _SQLSRV2

Prior to 11.2 release, running SQL query with large number of constant
values in WHERE IN clause crashes SQL database server (sqlsrv2).

Issue Number: OE00209582
     Connection refused and timeout errors

Connection refused and timeout errors with multiple SQL connects. This
problem occurs when a secondary broker is used for OE sql connections, and
the -Ma startup parameter value for the secondary broker is different from
the -Ma paramater value for the primary broker.

Issue Number: OE00217412
     More than 13 "IN" in WHERE statement causes huge performance dro

When using WHERE IN statements in a complex SQL query for very large
tables (millions of rows) , if 13 or more IN values are present the
performance of the query execution drops. The time of execution goes from
a couple of seconds (with less than 13 IN) to 10+ minutes (when adding 13
or more IN).

If the same query is modified and the WHERE IN statement is replaced by
WHERE OR then you can add more than 13 values and the query executes in a
few seconds.

This problem can occur when one (or more) of the tables has associated
indexes which contain some index key values with  many, many duplicate
values and other index key values with many fewer key values. In other
words, this problem is related to skewed key value distribution.

Issue Number: OE00218460
     SQLSchema, SCHLDUMP and SQLLOAD utilities fail with blank passwo

SQLSchema, SCHLDUMP and SQLLOAD utilities fail to work with a blank

Issue Number: OE00220527
     Internal error -1214 (dsmret.h) when updating a row

When a field, which has index on it is updated as part of SQL Trigger
execution on a table, the next UPDATE statement on the same table for the
same field generates below error:

Internal error -1214 (see dsmret.h) in SQL from subsystem DSM SERVICES
function dsmKeyDelete called from ix_delete on <user>.<table> for
<user>.<index>. Save log for Progress technical support.
SQLState: HY000
ErrorCode: -219901

Issue Number: OE00223707
     All users can access the schema metadata

Access to the database schema metadata is accessible to all users and
cannot be revoked, in OpenEdge releases prior to 10.2B07. This occurs when
access is done using ODBC or JDBC catalog API's.

Issue Number: OE00225837
     Cannot binary dump and load non-PUB tables due to CRC errors

Cannot binary dump and load non-PUB tables from older version(pre 10)
database to new database due to CRC errors caused by schema difference in
the original database.

Issue Number: OE00228663
     Different error status for primary key  and unique key constrain

Three different error statuses for primary key, unique key constraint
failures, and unique index failure - current implementation of these
constraints are just implemented as unique indexes.

SQL Tools
Issue Number: OE00221262
     Sqlschema incomplete export definition table name contains hyfen

Sqlschema generate incomplete export definition for table name contains

Issue Number: OE00205185
     Error 782 after adding extents to a database

Error "Socket number<id> is too large;it cannot be greater than 1023
(782)" when session is connected to one or more single-user/self-service
databases with a large number of extents, and you try to connect to a
database in client/server mode.

Issue Number: OE00223625
     UTF-8 message truncated in MESSAGE UPDATE

The message displayed by the MESSAGE UPDATE statement may be truncated if
the message contains multi-byte UTF-8 characters.

Web Services Client
Issue Number: OE00220140
     Error receiving Web Service Response (11773) calling web service

Error receiving Web Service Response (11773) calling web service when
response file contains characters '&#13;'

Issue Number: OE00225021
     Error (11478) consuming a Webservice over HTTPS

Error loading WSDL document :internal error: Receive status (11748).

Issue Number: OE00223665
     poor performance of cgiip.exe on 10.1C and higher

poor web server performance under heavy load of cgiip.exe on 10.1C and

Issue Number: OE00225308
     WebSpeed agent crashes when updating to utf oracle db thro ODS

WebSpeed agent crashes updating a record through trigger in to the utf
oracle database.

The schema holder is also UTF-8.  The agent uses -cpinternal and cpstream

The gui client works fine.