Recent history

This list is incomplete and is DB-focused; doesn't cover all of OE.  NeRF manuals are also a good source of info.

11.0

• Database multi-tenancy
• RC4 cipher support in OpenEdge TDE
• SHA-2 hashing in the ABL
• New OE Auditing events
• New option to make _User records SQL-only
• New OpenEdge license removal utility
• R-code is now portable again between 32-bit and 64-bit
• VST support for ABL temp-tables

 11.1

• OpenEdge installer now includes JDK
• New startup params, also added to 10.2B06 (see above)
• Promon enhancements, also added to 10.2B06 (see above)
• Updates to promon 6 and promon R&D 1|12 (startup param screens)
• Encrypted passwords
• New multi-tenant startup params: -nGovernor and –Lgovernor
• OE SQL multi-tenant enhancements
• New ODBC and JDBC drivers

 11.2

• proutil auditreconfig: reclaim space used by OE Auditing areas
• drops old audit tables and indexes, recreating them in new areas
• NOTE: truncates all audit data; use carefully!
  • maximum value for -pica (OE Replication buffers) increased from 8192 to 1,000,000
  • OE SQL:
  • more granular error messages for constraint violations
  • new query paging with OFFSET and FETCH
  • enhanced ORDER BY clause that supports column names and aliases in query expressions containing set operators
  • new param: -SQLQuotedRowid: specifies how the quoted string “rowid” is interpreted (column name or function)

 11.2.1

 ?

11.3

• bibackup active|all added to probkup; "active" is the default
• skips unused backup clusters
• NOTE: bibackup active, the default, should not be used prior to 11.5 due to a bug in prorest (PSC00317988); have to use "bibackup all" in 11.3.x and 11.4.x
  • rfutil -ailist allows roll forward of many AI extents with one command; easier and more efficient than rolling forward individual extents
  • also provides per-file completion status information
  • avoids doing a redo phase for each file
    • proutil dbrestrict qualifier: allow you to restrict access to a DB (e.g. a warm spare) so only certain clients or utilities can access it
    • prostrct create and proutil bigrow algorithms made more efficient (the latter can be reverted to old behaviour with undocumented –zextendSyncIO parameter)

11.3.1

 nothing

 11.3.2

 nothing

 11.3.3

 nothing

 11.4.0

• new Table Partitioning add-on product for Enterprise RDBMS (ABL, SQL, & utility support)
• change to proutil behaviour with UTF-8 databases
• new output option for analysis reports: proutil dbanalys -csoutput -csfileprefix -fieldsep -verbose

11.5.0

• new Advanced Enterprise Edition RDBMS product license
• bundles the Enterprise RDBMS product with the Multi-tenant Tables, OE Management, OE TDE, OE Replication Plus, and Table Partitioning add-on products)
  • improvements to table partitioning
  • logging and reporting of all DB broker startup parameters
  • all params are written to the log file at startup
  • new _DbParams VST with all primary broker startup params
  • all startup params are audited if OE Auditing is enabled
  • _Servers VST is enhanced with new fields for broker-specific startup params
  • promon changes to screens:
    • shared resources
    • R&D | status | startup parameters
    • VST changes are enabled with proutil enablenewvsttables qualifier
    • VST changes can be disabled for backward compatibility with pre-11.5 via proutil disablenewvsttables qualifier
    • status of new VSTs can be checked via proutil describe qualifier (feature 23)
    • prolog command now re-logs all the startup parameters to the beginning of the log, unless you specify -silent
      • it is no longer necessary to specify the -online switch when the DB is online

 11.5.1

• OE SQL:
• ADT (Authorized Data Ttruncation): enabled in one of two ways:
  • broker startup parameter (for life of broker): proserve –db <dbname> -S <port-number> -SQLTruncateTooLarge <on/off>
  • connection URL option (for life of session) : jdbc:datadirect:openedge://<ip>:<port>;databaseName=<dbname>;truncateTooLarge=<on/off>;
  • number of truncation events is logged to the DB log at the end of the SQL client session
  • server-wide and connection-specific logging is available; note that enabling logging may degrade performance
    • see SP release notes for details
    • TLS 1.0/1.1/1.2 support for client/server connections

 11.6.0

• custom install utility
• -Mm parameter no longer has to agree between client and server
• -enforceMm startup parameter: reverts to pre-11.6 behaviour for -Mm, requiring it to be set identically on client & server
• LOB support in dbanalys
• new "LOB SUMMARY" section follows "RECORD SUMMARY" section in the dbanalys report
• new *.lob.txt file is created when using the -csoutput parameter
  • new fields in _connect:
    • _Connect-PartitionId: displays the partition ID if the database is enabled for Table Partitioning and the wait type is REC or RGET
    • _Connect-Timestamp: displays the timestamp of the user's schema cache
    • _Connect-Wait2: displays additional info based on the value of _Connect-Wait1. If _Connect-Wait1 contains a ROWID, this field contains a table number. If _Connect-Wait1 contains a dbkey, this field contains an area number.
• OE Replication:
• replication agents can be restarted without restarting the target via: dsrutil restart agent
• new fields in _replagent, _replagentcontrol, _replserver
• new VSTs: _replagentactivity, _replagentcontrolactivity, _dbservicemanager, _dbservicemanagerobjects
  • OE SQL:
  • improvements to query performance after UPDATE STATISTICS
  • ASU (Autonomous Schema Update): helps resolve character width constraints by updating the SQL column width in schema automatically when Authorized Data Truncation (ADT) occurs for data in a column
    • enabled with -SQLWidthUpdate parameter

 11.6.1

• -crStatus startup parameter (documented but not enabled in 11.6.0)
• -crTXDisplay startup parameter (documented but not enabled in 11.6.0)

11.6.2

• Authentication gateway

11.6.0 OO ABL Reflection

I don't know what was added in 11.2.1 but I do know a major bug that was introduced. When doing a binary dump that only used one index no data would be dumped at all even though the log file said it had happily dumped the data. In other words 11.2.1 should not be installed if there is the choice of going to a later version! :)

11.2 was a major bad release for PDSOE. So it should definitively be avoided.

Outlook for Android herunterladen

Von: James Palmer
Gesendet: Dienstag, 5. Juli, 10:07
Betreff: RE: [Technical Users - OE General] Recent history
An: tu.oe.general@community.progress.com

Update from Progress Community

James Palmer

I don't know what was added in 11.2.1 but I do know a major bug that was introduced. When doing a binary dump that only used one index no data would be dumped at all even though the log file said it had happily dumped the data. In other words 11.2.1 should not be installed if there is the choice of going to a later version! :)

View online

You received this notification because you subscribed to the forum.  To unsubscribe from only this thread, go here.

Flag this post as spam/abuse.

11.6 has a rather large group of messages (# 18289 and higher) related to "the watchdog thread that monitors idle resources for the specified session pool" but I did not find such feature mentioned in documentation. It does not yet implemented, does it?