Databridge 6.3 Hotfix 2 is available to maintained customers and applies to an existing installation of Databridge 6.3. This technical note describes fixes included in this release.
Note: Version 6.3 Update 1 is available beginning in February 2016. For more information, see KB 7021927.
Obtaining the Hotfix
Maintained customers are eligible to download the latest product releases from https://download.attachmate.com/Upgrades/.
You will be prompted to login and accept the Software License Agreement before you can download a file. For more information on using the Downloads website, see KB 7021965.
Databridge components and utilities that have been updated since version 6.3 are listed below with their current version number.
All host programs have been recompiled with MCP Level 56.1 software.
This hotfix uses the same directory structure as the original release to help you locate the appropriate update file for each product.
Please note the following:
- This version uses a single patch which updates the Client, the Console and DBEnterprise Server.
- You cannot update a 32-bit install with a 64-bit patch or vice versa. Uninstall the 32-bit software 6.3 release software and install the 64-bit 6.3 release software before updating it with the 64-bit patch.
Before you install the hotfix, quit all Databridge applications including the Console, and then terminate the service/daemon. After the installation is complete, restart the service/daemon manually.
IMPORTANT: To avoid potential problems, we strongly recommend that you upgrade the Host and Enterprise Server software simultaneously.
If you're updating the Client software, we recommend that you update the Client Consoleâparticularly if you use the Client Configurator. This will ensure that your data is interpreted correctly.
- On the MCP Server, upload DB63HOTFIX.con using binary or image file transfer.
put DB63HOTFIX.con DB63HOTFIX
- Log on to the Databridge usercode on the host and go to CANDE.
- To unwrap encapsulated files in the DB63HOTFIX file, use the following command:
WFL UNWRAP *= AS = OUTOF DB63HOTFIX TO DISK (RESTRICTED=FALSE)
Databridge Client, Client Console and Enterprise Server
- Windows: Open the Windows32 or Windows64 folder of the hotfix and double-click the file databridge.D63xxxx.Wnn.exe. All installed components (such as the Client, the Console, or Enterprise Server) will be updated.
- UNIX: Upload the appropriate tar files for the Client and Console from the hotfix to the directories where these components are installed. (Optimally, the Client and Console are installed in separate directories to facilitate maintenance.) If you use Windows to process the extract of the tar file from the zip file, you must transfer the tar file to UNIX using binary FTP.
Then, use the following command:
tar -xvf <filename>
where <filename> is the full name of the tar file. This command replaces the files in the Databridge install directory with updated files from the tar file.
Note: To avoid accidentally deleting the Databridge applications, we recommend that you always keep the install directory and the working directory separate.
Issues Resolved by Hotfix 2
In addition to the previous Issues Resolved by Hotfix 1, this hotfix resolves the following issues:
- Processor utilization increases starting in DBEngine 62.004.0034 when replicating many overlapping transactions.
- The new MANUAL COMPILE option can be used to prevent DBEngine from automatically trying to compile DBSupport or DMSIISupport if they are incorrect. This is useful when the DMALGOL compiler is not resident on the system. Syntax:
MANUAL COMPILE [ [ = ] TRUE | FALSE ]
If the option is not specified the default is false, i.e. automatic compiles.
- DBTwin faults with string protect or returns the DMSII error "SOME REQUIRED ITEMS ARE NULL" if DBEngine compiled with $ PRIMARYFILTER.
- Using a Windows user name longer than 17 characters causes a SEG ARRAY ERROR @ (10807500) fault. Note that the MCP does not support user names longer than 17 characters in the REMOTEUSER declaration.
- DBEnterprise now passes the client user ID to DBServer for verification when using the AUTHORIZED USERCODE feature.
- " Filter routine failed" if data set contains FIELD (48) REQUIRED.
- The client now passes the Windows/UNIX userid to the server, for verification when using the AUTHORIZED USERCODE feature.
- The SQL Server client does not prevent the user from setting the configuration file parameter "bcp_delim" to the empty string, which causes the bcp to fail.
- The maximum number of script threads that can be configured was increased form 4 to 8.
Issues Resolved by Hotfix 1
In addition to the previous 6.3 updates (described in KB 7021921), this hotfix resolves the following issues:
- If the available audit ends with a halt/load recovery record, DBEngine updates the client audit location with a SEG of 0.
- DBTwin faults with a SEG ARRAY ERROR if a data set has an embedded data set.
- DBEngine waits on a NO FILE if AUDIT NO FILE is set and the audit file is moved to another family at the same time.
- DBEngine returns "missing section" for active audit file on alternate family when using DMAuditLib.
- The Extract worker task name has been changed to
when DYNAMIC NAMES = true.
- DBTwin encounters KEYCHANGED errors when using a tailored DBSupport.
- An embedded remap causes an INVALID INDEX when used with a non-tailored DBSupport and a 57.1 database.
- Twin gets a DUPLICATES error while tracking a COMPACT data set and the report shows "Record Not Found" errors when processing aborted transactions.
Also, if a Twin transaction contains more than 50,000 updates some could fail with NOTLOCKED errors.
- EXTRACT EMBEDDED = FALSE is ignored for a tailored DBSupport.
- Aborted COMPACT creates are sometimes sent to the caller.
- If the primary database has done a DASDL update, Twin returns the error
>>>  Missing DESCRIPTION file for Audit file update level
>>>  Database update level changed from <old> to <new> <<<
- AX QUIT on main server stack causes all Workers to return result code 7 (no more audit available) rather than 1015 (operator quit).
- The new AUTHORIZED CLIENT IP option restricts client connections to certain IP addresses. Syntax:
AUTHORIZED CLIENT IP "ipaddress1" [, "ipaddress2" ...]
AUTHORIZED CLIENT IP "192.168.0.99"
AUTHORIZED CLIENT IP "10.10.1.45", "172.27.172.9", "10.17.1.2"
If the option is omitted, clients can connect from an IP address (but are still subject to any CLIENT HOST ... restrictions specified for the particular source).
Changes to this option require DBServer to be restarted to take effect.
- DBTwin encounters KEYCHANGED errors when using a tailored DBSupport.
- The DMSII Client does a P-DS if the primary database contains an embedded data set. The log shows DUPLICATES errors.
If the database contains a manual subset, the status report shows this error message:
>>>  XDR error at line 59114000 <<<
Note: DMSII links are not supported in this release.
- The DMSII Client skips updates for the first data set in the list when using the DISABLE ALL EXCEPT ... construct.
- DMSIISupport compile fails with PROGRAM SEGMENT TOO LARGE when a large number of sets are declared for a data set.
- Copying files from the MCP to a Windows directory in the root of the drive results in incorrect "Permission denied" error. Copying files with "%" in the titles could cause DBE to fault when writing to the log.
- The recloning of data sets, that have resident history records and involve virtual data sets, results in the history data sets always being recloned.
Note: This bug was corrected in the 6.3 base release.
- The 64-bit SQL Server client does not use COUNT_BIG in the select statement used to get the row counts. This causes tables, that have more rows than a 32-bit integer can hold, to get an overflow error.
- An error in the editing of the row counts at the end of the data extraction of a data set results in a negative number when the count overflows a 32-bit integer.
- The error recovery from failed updates to COMPACT data sets with items that have OCCURS DEPENDING ON clauses fails when RSNs (or AA Values) are used as the source of the index. The SQL to do a delete fails to enclose the RSN (or AA Value) in quotes, when the data type is CHAR(12), resulting in a SQL error. A similar error occurs when using binary AA Values (or RSNs).
Additional technical resources are available from https://support.microfocus.com/product/?prod=DB.