Issues fixed in OpenEdge 12.2.1
- Last Updated: September 9, 2024
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
The following table lists issues fixed in this release:
| Components | Item | Details | Knowledge Base |
|---|---|---|---|
| ABLTOOLS | OCTA-22493/PSC00360755 | Adding an additional startup parameter to the ABLUnit Run Configuration prevents the configuration from running. There are no errors, but the output result.xml isn't complete. | Click for more information |
| ADE | ADAS-24071 | Since upgrading to 11.7.5, can no longer see the field definitions of metaschema tables in Data Dictionary. Receive message "The entered name does not match any table name in this database". | Click for more information |
| DB | OCTA-2584/PSC00217061 | The Replication Server process cannot be terminated with the dsrutil utility if the Database Service Manager Queue (PICA queue) is full. | Click for more information |
| DB | OCTA-13066 | Remote clients are not able to connect to database servers and the error "Rejecting login – too many users for this server (1334)” occurs when there are indeed available connections. | Click for more information |
| DB | OCTA-13278 | The promon utilities reporting of currently connected users for a database with remote clients can be different with regards to the actual number of users connected to the database. | Click for more information |
| DB | OCTA-13882 | SQL queries can fail against a Replication target database with a Table/View/Synonym not found (7519) error because a database schema change on the Replication source database is not fully replicated to the target database. | Click for more information |
| DB | OCTA-18370 | Multi-Threaded Index Rebuild can create index keys that are too large. | Click for more information |
| DB | OCTA-19414 | PROSHUT with or without the -F option can hang when a locked USR Latch is left behind by a disconnected user. | Click for more information |
| DB | OCTA-20279 | prostrct add fails with error 7125 when trying to add an extent and the path of the extent is already used by a different database. The other database crashes with error 8540. This is a windows only issue. | Click for more information |
| DB | ADAS-21325 | A cancelled prostrct add online of AI extents where the area is created but the physical extent is not can cause a query of the _dbstatus VST to error with an empty record. | Click for more information |
| DB | ADAS-22517 | When there are many objects in the same Type II storage area (300+ for 4K DBs and 600 for 8K dbs) PROSTRCT STATISTICS may fail with error (210) (14684) when attempting to scan the object blocks for their statistical information. This can be identified by running dbanalys for an area and if the reported _object list block(s) is greater than 1_, prostrct statistics will fail. | Click for more information |
| Generic JMS Adapter | ADAS-24146 | OE Adapter for SonicMQ is reading two messages from the server instead of one. | Click for more information |
| Install | ADAS-14739/PSC00365609 | Unable to restore/rollback to the previous OpenEdge Service Pack version as the Setup utility failing to take backup of existing OpenEdge files. | Click for more information |
| Lang | OCTA-3299/PSC00343962 | When compiling a class with the XREF-XML compiler option, if the class defines a dataset with more than one PARENT-ID-RELATION, the compiler issues the error: Error in DataSet relations information during XREF-XML. | Click for more information |
| Lang | OCTA-3772/PSC00360327 | The RadGridView populates records from the parent table, but does not show any child records even though they exist when used with an ABL ProBindingSource and setting the RadGridView:AutoGenerateHierachy property to true. | Click for more information |
| Lang | OCTA-20072 | In 12.1.0, an ABL client session using join queries may crash. Specifically, if there is a record in memory and within a sub-transaction that same record is read again as part of the result list for the children of a join, the crash may occur. | Click for more information |
| Lang | OCTA-20945 | A character-mode ABL program which hides and subsequently redisplays a browse widget may crash. | Click for more information |
| Lang | OCTA-20960 | An ABL window which contains one or more OCX controls may flicker when it's displayed. CPU usage may be high when such a window is displayed. | Click for more information |
| Lang | OCTA-21257 | When using the JsonObject WRITE method with character data types there is a memory leak in the client session. | Click for more information |
| Lang | OCTA-21276 | Java open client application performance may be impacted by theamount of garbage collection caused when processing a response that contains a temp-table or dataset with a large number of fields. | Click for more information |
| Lang | OCTA-21580 | When using the double colon notation to refer to a buffer field in a FOR or FIND statement, if the buffer being referred to resides in a database using the previous major OpenEdge release, these statements raise the STOP condition. | Click for more information |
| Lang | OCTA-22223 | ABL clients crash when connecting client/server to a read-only, audit-enabled database within a transaction. | Click for more information |
| Lang | OCTA-22620 | A FOR EACH query with NO-LOCK and NO-PREFETCH specified on some but not all levels of the join returns incorrect data. | Click for more information |
| OEM | ADAS-18632 | PASOE instance does not autostart when AdminServer service started or restarted. It requires a manual intervention to start PASOE instance despite of the setting “autostart=true” in pasmgr.properties file for respective PASOE instance. | Click for more information |
| PASOE | ADAS-22626 | PASOE operation system command "wc -c " on AIX/Linux takes long time to execute | Click for more information |
| PASOE | ADAS-23649 | PASOE agent disconnects the database and shuts down if a bound apsv session-managed connect procedure returns an error after binding the connection. | Click for more information |
| PASOE | ADAS-23862 | Output datasets sent over Soap are not mapped correctly when their name is different than what the WSDL document specifies. | Click for more information |