Databridge 6.2 Service Pack 2 Update 1 is available to maintained customers and applies to an existing installation of Databridge 6.2. This technical note describes fixes included in this release.
Databridge components and utilities that have been updated since version 6.2 are listed below with their current version number.
All host programs have been recompiled with MCP Level 55.1 software.
||Service Pack 2 Update 1
||Service Pack 2 Hotfix 4
||Service Pack 2 Hotfix 4
Obtaining the Hotfix
Maintained customers are eligible to download the latest product releases from https://download.attachmate.com/Upgrades/.
This update uses the same directory structure as the installation image of the original release to help you locate the appropriate update file for each product.
Please note the following:
- This version uses a single patch that 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.2 release software and install the 64-bit 6.2 release software before updating it with the 64-bit patch.
Before you install the update, 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.
We also recommend that you update the Client Console if you're updating the Client software, particularly if you use the Client Configurator. This will ensure that your data is interpreted correctly.
- On the MCP Server, upload DB62Update.con using binary or image file transfer.
put DB62Update.con DB62UPDATE
- Log on to the Databridge usercode on the host and go to CANDE.
- To unwrap encapsulated files in the DB62UPDATE file, use the following command:
WFL UNWRAP *= AS = OUTOF DB62UPDATE TO DISK (RESTRICTED=FALSE)
Databridge Client, Client Console, and Enterprise Server
- On Windows, open the Windows32 or Windows64 folder of the update and double-click the file databridge.62xxxx.Wnn.exe. All installed components such as the Client, the Console, or Enterprise Server will be updated.
- On UNIX, upload the appropriate tar files for the Client and Console from the update 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 Service Pack 2 Update 1
In addition to the previous Issues Resolved by Service Pack 2 Hotfix 5, this update resolves the following issues:
- In rare cases, certain updates are not sent to the client. This only occurs when all of the following conditions are true:
- The Engine is setup to read the active (current) audit file and the Databridge client has use_dbwait set to true.
- The Engine has reached the logical end of the audit file.
- The last block ends with a SAM, SAC or SAD record.
- The actual update (DSM, DSC, DSD) has not yet been written into the next block.
- The Engine is in a position to commit the transaction group.
- UNIX daemon gets an "address in use error" when binding the listen port for the second time. The solution is to bind once using IPV6, which allows both IPV4 and IPV6 to work.
Issues Resolved by Service Pack 2 Hotfix 5
In addition to the previous issues resolved by SP2 Hotfix 4, as described in KB 7021923, this update resolves the following issues:
- Remaps in DBTwin logical database cause structure number errors.
- DBGetInfo now returns the setting of the COMMIT DURING IDLE DATABASE in response to the new Info_SourceCommitDuringIdleDB.
- Allow the new Info_SourceCommitDuringIdleDB info option.
- DBEnterprise now uses the COMMIT DURING IDLE DATABASE setting from the DBEngine parameter file.
- DBSupport gets a syntax error if extremely long WHERE clause.
- Modified the recovery from a duplicate record, while attempting to mark a record as deleted for MISER database customers. Instead of giving up immediately and deleting the record, we now fudge the time and try again for a number of times before giving up and deleting the record.
- Added protection against rogue runs that send less than 4 characters and hang the service. We now close the connection when we get less than 4 characters when reading the length of the first message.
- Implemented a session initialization timeout to protect against rogue connections to the service that tie up resources. A normal console or BCNOTIFY session immediately sends an RC_Initialize RPC. We now time this out and close the connection when we get no input within the timeout period.
- The clone command fails with an RCI_GetDataSets error.
- The parser insists on having "with option x" as part of a clone command, even though this is optional.
- The clone command fails with large databases as the bconsole buffer does not dynamically expand.
Additional technical resources are available at https://support.microfocus.com/product/?prod=DB.