Problem:
On September 8th or 9th, 2001 (i.e., 21:46:40 Sept 8 EST (Toronto time) or 01:46:40 Sept 9 GMT), the 32-bit time value gains a digit to go from 999999999 to 1000000000. The exact time of the failure will depend on which timezone the machine operates under. The result is that DB2 will not pass the fifth parameter, the MODE or sequence #, to the BACKUP USEREXIT. As a result of this, after this date/time database backups on OS/2 via a USEREXIT for a database alias of 8 characters will no longer work and as such a backup will not be taken.
The error or message seen will depend on how the USEREXIT is coded. If you are using the default USEREXIT, you will see an invalid parameter error being reported by the USEREXIT.
DB2 Products affected:
This problem is only related to the OS/2 platform and does not affect other USEREXITs (eg. LOG) or backups taken without USEREXITs.
Impact:
Inability to perform DB2 UDB backups on OS/2 via a USEREXIT as of September 8th or 9th, 2001 (i.e., 01:46:40 Sept 9 GMT, or 21:46:40 Sept 8 EST).
Resolution: Apply DB2 UDB for OS/2 APAR JR16294 or use the suggested workaround.
Fix Availability:
Fix Status for releases currently in service:
The fix for this problem has been uploaded to the DB2 UDB FIXPAK FTP site in the OS/2 directory for each release currently in service and we are developing a fix for V5 (out of service). The patched DLLs are stored in the archive file JR16294.zip. All national language versions use the same patch. A readme in the same directory (English only) is available to outline the problem/workaround/patch installation (JR16294.TXT).
Location of FIX for V 6.1 FixPak 8:
ftp://ftp.software.ibm.com/ps/products/db2/fixes/english/db2os2v61/FP8_WR21255/
Location of FIX for V 7.1 FixPak 3:
ftp://ftp.software.ibm.com/ps/products/db2/fixes/english/db2os2v7/FP3_WR21251/
Note that this fix can only be applied to specified FIXPAK levels (FixPak 3 for V7.1 and FixPak 8 for V 6.1) and will not correct the problem for customers on special/private builds. They will either need to upgrade to one of these levels before applying the patch or will need to use the workaround until the next FixPak is made available.
Fix Status for releases which are not in service (V5 only) where customers may have a service extension:
Location of FIX for V 5.2 FixPak 16:
A fix is being developed and will be uploaded to
ftp://ftp.software.ibm.com/ps/products/db2/fixes/english/db2os2v5/FP16_WR21262/
location. The fix will be in a file called "db22v5_JR16294.zip" and a
readme in the same directory (English only) will also be available to
outline the problem/workaround/patch installation (JR16294.TXT). We are
expecting to have this fix developed and uploaded by end of day Friday,
September 7, 2001, Toronto time.
Note that this fix could only be applied to V5.2 FixPak level 16 and will not correct the problem for customers on special/private builds. They will need to use the workaround.
TCO Customers can use one of the following options:
Workaround:
Catalog another database alias to your database using 7 characters or less and use this database alias for performing your backups. You must ensure that the restores are performed using the same database alias as was used for the backup. By cataloging a separate alias, you avoid having to reconfigure all your remote database clients, making it transparent to your users.
Questions:
Use the standard 24X7 BAU service and escalation procedure to contact your local support organization.
If you are using the DummyKey Ring provided by IBM with WebSphere, and you have enabled security, you run the risk of stopping WebSphere on July 19, 2001. Read on for more information on how to deal with this potential problem.
If you are not using the IBM-provided DummyKey Ring and/or do not have security enabled, or if you are using WebSphere Application Server for OS/390, please disregard this notice.
THE PROBLEM: The IBM-provided DummyKey Ring in certain releases of WebSphere Application Server has a certificate expiration date of July 19, 2001. WebSphere Application Server releases prior to 3.5.3 or 3.02.4 on all platforms except OS/390 are likely affected. All communications to/from the server will halt when the certificate expires, if security has been enabled. If multiple servers are tied together for communications, all servers must have the same level of unexpired certificates in order to continue functioning.
IDENTIFICATION: The Dummy KeyRing sample certificate expiration on July 19, 2001, will affect you only if ALL of the following conditions are true:
1. Running WebSphere Application Server Version 3.0, 3.0.1, 3.0.2, 3.0.2.1, 3.0.2.2, 3.0.2.3, 3.5, 3.5.1, or 3.5.2.
==> Verify by looking in the ...\properties\com\ibm\websphere directory.
Look inside the product.properties (3.0.x) or product.xml (3.5.x) file.
2. eFix PQ47370 is NOT applied.
==> Verify by looking in the ...\bin\admin.config file. PQ47370 is not applied if there is no reference to a PQ47370.jar file. (PQ47370 contains an updated sample certificate.)
3. The DummyKeyring sample certificate is being used (rather than using your own secure keyring).
==> Verify by looking in the ...\properties\sas.server.props file. This IBM-provided sample certificate is not being used if there's no reference to the DummyKeyring.
RESOLUTION: Create your own dummy keyring, as explained in the WebSphere
InfoCenter in Section 5.5.6.1.5:
"Example: Generating and Using Test Certificates."
Other temporary resolutions are possible by installing IBM's updated sample keyring (which has an expiration date of January 19, 2004).
For more information on IBM WebSphere Application Server support, please visit:
http://www.ibm.com/software/webservers/appserv/support.html
NOTE: The sample Dummy Keyring is provided in all WebSphere Application Server releases as a convenience only, for setting up SSL communications on an initial, temporary basis. As documented, use of this sample keyring could compromise security and is not recommended for other than test, development, or internal usage.
IBM encourages customers running WebSphere Application Server for OS/2 Warp to participate in online forums to exchange information on this and other technical support issues. Please feel free to report your experiences with this information to other users in the appropriate newsgroups.
It is distributed as a single file that you should download to a directory and then execute. Once expanded, review the README2 file for the list of fixes (also available on the FixPak Repository under the "Netscape Communicator for OS/2 V461, XR_461A"). See the READ.ME for install details.
The Refresh is stored on a site that checks your IP address to verify that it is a valid IP address to secure a copy due to export restrictions on the code. To secure the Refresh, please either use the FixPak Repository to access the site, or you may use this link: http://www6.software.ibm.com/dl/netscape4/nc461os2w-p. Select the English-US or National Language Version required.
Versions Released:
07/06/2001 - English-US, Spanish, German