A fix is available
APAR status
Closed as program error.
Error description
DESCRIPTION: When the user chooses not to set up DB2 extended security, by either setting the keyword DB2_EXTSECURITY to 'NO' in the response file or de-selecting "Enable operating system security" on an install GUI panel, the v8.2 ESE install on windows generates the following error message in the install log file: "Unable to find the string resource 3574:.......Failure". This message is generated by the configuration task:TaskUpdateDB2TEMPDIR, which does some work for setting up DB2 extended security. Thus, this task is not needed if the user does not want the extended security. However, based on an earlier decision, this task is always executed during a v8.2 DB2 install (up to v8.2.5) on Windows. Impact of this problem: No inpact. Since the failed task is a task that needs not to be executed, there is no impact for the DB2 product installed on the system, and its configuration. The only problem is it puts a "... Failure" message in the install log file, which might cause some confusion.
Local fix
Problem summary
When the user chooses not to set up DB2 extended security, by either setting the keyword DB2_EXTSECURITY to 'NO' in the response file or de-selecting "Enable operating system security" on an install GUI panel, the v8.2 ESE install on windows generates the following error message in the install log file: "Unable to find the string resource 3574:.......Failure". This message is generated by the configuration task:TaskUpdateDB2TEMPDIR, which does some work for setting up DB2 extended security. Thus, this task is not needed if the user does not want the extended security. However, based on an earlier decision, this task is always executed during a v8.2 DB2 install (up to v8.2.5) on Windows. Impact of this problem: No inpact. Since the failed task is a task that needs not to be executed, there is no impact for the DB2 product installed on the system, and its configuration. The only problem is it puts a "... Failure" message in the install log file, which might cause some confusion.
Problem conclusion
First fixed in DB2 UDB Version 8, FixPak 13
Temporary fix
Comments
APAR Information
APAR number
JR24010
Reported component name
DB2 UDB PE WIND
Reported component ID
5724B5501
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-05-24
Closed date
2006-10-03
Last modified date
2006-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB PE WIND
Fixed component ID
5724B5501
Applicable component levels
R810 PSN
UP
R820 PSN
UP
R910 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820"}]
Document Information
Modified date:
06 October 2021