|
Problem IC69367
|
Status: Closed |
db2pd commands may fail on Linux/Solaris platforms due to internal memory conflicts |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Running the db2pd command with application-side private memory
set encounetered the following error msg:
bash-3.00$ db2 LIST ACTIVE DATABASES
Active Databases
Database name = TOOLSDB3
Applications connected currently = 1
Database path =
/product/raid1dsk1/db2/db2inst2/db2inst2/NODE0000/SQL00002/
bash-3.00$ db2 connect to toolsdb3
Database Connection Information
Database server = DB2/SUN64 9.5.5
SQL authorization ID = DB2INST2
Local database alias = TOOLSDB3
bash-3.00$ db2pd -memsets -db TOOLSDB3
Database TOOLSDB3 not activated on database partition 0.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Too many signals. Exiting program.
- same error for memb and mempools.
bash-3.00$ db2pd -memb -db toolsdb3
Database TOOLSDB3 not activated on database partition 0.
All memory blocks in Database set.
bash-3.00$ db2 activate db toolsdb3
SQL1490W Activate database is successful, however, the database
already been activated on one or more nodes.
bash-3.00$ db2pd -mempools -db toolsdb3
Database TOOLSDB3 not activated on database partition 0.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Changing data structure forced command termination.
Too many signals. Exiting program.
bash-3.00$ |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* SUNOS *
****************************************************************
* PROBLEM DESCRIPTION: *
* Running the db2pd command with application-side private *
* memory *
* set encounetered the following error msg: *
* *
* *
* *
* *
* *
* bash-3.00$ db2 LIST ACTIVE DATABASES *
* *
* *
* *
* Active Databases *
* *
* *
* *
* Database name = TOOLSDB3 *
* *
* Applications connected currently = 1 *
* *
* Database path = *
* *
* /product/raid1dsk1/db2/db2inst2/db2inst2/NODE0000/SQL00002/ *
* *
* *
* *
* bash-3.00$ db2 connect to toolsdb3 *
* *
* *
* *
* Database Connection Information *
* *
* *
* *
* Database server = DB2/SUN64 9.5.5 *
* *
* SQL authorization ID = DB2INST2 *
* *
* Local database alias = TOOLSDB3 *
* *
* *
* *
* bash-3.00$ db2pd -memsets -db TOOLSDB3 *
* *
* *
* *
* Database TOOLSDB3 not activated on database partition 0. *
* *
* *
* *
* Changing data structure forced command termination. *
* ... *
* Too many signals. Exiting program. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.7 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2010
24.05.2011
24.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
