Other Resolved Issues

This section lists the issues that were resolved in each release but were not part of the fixes listed in the previous section. A release is listed in this section only if changes occurred in that release.

Release 10.11

  • WDA-1742

    Added support for ReAuthenticateUser to reauthenticate and reauthorize the user for DBC using Kerberos authenticated database.

  • WPE-4830

    With webMethods Process Engine, deadlock errors occurred.

    With MySQL database, storage cleaner procedure caused deadlocks in database.

    The issue is resolved.

  • OBE-11884

    In the Define Environments page of Optimize, you cannot delete an environment that uses a PostgreSQL database. Also, when you open the Edit Environment page of such an environment, you cannot use the Map All function more than once.

    The issue is resolved.

  • OTN-21863

    When TN nodes in the cluster are restarted simultaneously, there are multiple cluster notifications between nodes to refresh document types that caused the ORA-01555 Snapshot Too Old error.

    The issue is resolved by increasing the PCTVersion value on the TypeData column of the BizDocTypeDef table.

  • PIE-56872

    A java.sql.SQLSyntaxErrorException exception occurred during OAuth initialization after migrating to Integration Server 10.3. This issue occurred as some migration paths do not add the SCOPE_DESCRIPTION column to the IS_OAUTH_SCOPE table.

    The issue is resolved, and the fix adds the SCOPE_DESCRIPTION column to the IS_OAUTH_SCOPE table.

  • WDA-1777 (DC_10.3_DCC_Fix8)

    The error *java.lang.NumberFormatException: For input string: "XRF"*appears during database migration from 912 - V103.

    The issue is resolved.

  • WDA-1727

    Space between product code issue fixed for command central.

  • WPE-4542

    With webMethods Process Engine, the storage cleaner encountered a deadlock.

    The issue is resolved.

  • WMN-7185

    With webMethods Monitor, services took a longer time to retrieve data. This issue occurred because the SQL query used by the pub.monitor.process.instance:getInstanceList service tool a longer time.

    The issue is resolved by migrating the Process Audit database component to version 81.5.

Release 10.7

  • WDA-1469

    The Error: Could not find or load main class com.softwareag.dcc.gui.Main message appears when you try to start the DCC GUI. When you try to start the DCC GUI by running the dbConfiguratorUI script, you receive the error Error: Could not find or load main class com.softwareag.dcc.gui.Main.

    The issue is resolved.

Release 10.3

  • PIE-52250

    Migration fails on Common DB Configurator.

    Migration fails on Common DB Configurator due to changes introduced in the DB script for an earlier version of Integration Server as part of PIE-52084.

    The issue is resolved.

  • OBE-10316

    When you use webMethods Database Component Configurator to migrate the CentralConfiguration component from version 9.12 to the latest version, an error occurs and the migration fails.

    The issue is resolved.

  • OBE-10432

    After migrating Optimize, the schema objects of the BAM_DIM_JOIN_TMP table might be different from the schema objects after a fresh installation. The issue occurs for Optimize environments that are configured to use a MySQL database.

    The issue is resolved.

  • OTN-18293

    There was a performance degradation when an update was made to a Trading Partner Agreement that was in use. With this fix, the partner table is optimized by including a Database index.

    The issue is resolved.

  • OTN-18452

    When using MySQL as an external database, importing a client certificate fails with an expiry date beyond 2038-01-19 UTC. This is because the datatype "Timestamp" associated with the MySQL table column of certificate expiry has an upper limit set to 2038-01-19 UTC. The issue is now resolved because the datatype for the column is changed to "DateTime" which has an upper expiry limit of year 9999.

    The issue is resolved.

Release 10.1

  • WDA-1031

    Command Central bootstrapper installs Database Configurator 10.0 but the program group item displays 9.12.

    The issue is resolved.

  • WDA-1026

    Desktop shortcut incorrectly displays the version as Database Component Configurator 9.12.

    The issue is resolved.

  • WDA-979

    DCC 10.0 displays incorrect copyright year and version in the console.

    The issue is resolved.

  • WDA-918

    In the Database Component Configurator, when a product is selected and then the mouse cursor is pointed to the radio button component, the selection is set back to “All”. Moving the mouse cursor without clicking the button should not change the selection.

    The issue is resolved.

  • WDA-976

    Database Component Configurator version shows 9.12 instead of 10.0 in the Windows Start menu.

    The issue is resolved.

  • WDA-844

    Incorrect Copyright year in the DCC “About” window.

    The Copyright year in the DCC “About” window shows 2006 – 2015. It should be 2006 – 2016.

    The issue is resolved.

Release 9.12

  • WDA-844

    Incorrect Copyright year in the DCC “About” window.

    The Copyright year in the DCC “About” window shows 2006 – 2015. It should be 2006 – 2016.

    The issue is resolved.