|
Problem IC63222
|
Status: Closed |
AUTOCONFIGURE DOES NOT RETURN CURRENT/RECOMMENDED CFG VALUES WHEN DB2_COMPATIBILITY_VECTOR=ORA IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
AUTOCONFIGURE command does not return output for
current/recommended configuration parameter values when
DB2_COMPATIBILITY_VECTOR=ORA is set
db2set DB2_COMPATIBILITY_VECTOR=ORA
db2stop
db2start
db2 "create database ORA"
db2 "connect to ORA"
db2 "autoconfigure using mem_percent 50 workload_type mixed
tpm 500 admin_priority both num_local_apps 10 num_remote_apps
200 isolation RS bp_resizeable yes APPLY DB ONLY"
DB210203I AUTOCONFIGURE completed successfully. Database
manager or database configuration values may have been changed
if you chose to apply changes. The instance must be restarted
before any such applied changes come into effect.
You may also want to rebind your packages after the new
configuration parameters take effect so that the new values
willbe used.
--> no output for current/recommended db/dbm cfg values is
returned. The actual change of autoconfigure command will still
be applied. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 V9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* AUTOCONFIGURE command does not return output for *
* current/recommended configuration parameter values when *
* DB2_COMPATIBILITY_VECTOR=ORA is set *
* *
* db2set DB2_COMPATIBILITY_VECTOR=ORA *
* db2stop *
* db2start *
* db2 "create database ORA" *
* db2 "connect to ORA" *
* db2 "autoconfigure using mem_percent 50 workload_type mixed *
* tpm 500 admin_priority both num_local_apps 10 *
* num_remote_apps 200 isolation RS bp_resizeable yes APPLY DB *
* ONLY" *
* *
* *
* DB210203I AUTOCONFIGURE completed successfully. Database *
* manager or database *
* configuration values may have been changed if you chose to *
* apply changes. The *
* instance must be restarted before any such applied changes *
* come into effect. *
* You may also want to rebind your packages after the new *
* configuration *
* parameters take effect so that the new values will be used. *
* *
* --> no output for current/recommended db/dbm cfg values is *
* returned. The actual change of autoconfigure command will *
* still be applied. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FP1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The fix is available in DB2 v9.7 FP1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.09.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
