DB2 - Problem description
Problem IC63723 | Status: Closed |
AN ERROR IN SQLOGETNUMPHYSDISKS WHILE CREATING A DATABASE IN SOLARIS ZONE ENVIRONMENT. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
An error similar to following may appear, when creating a database in Solaris zone environment, or when running db2support command. The key string to match is "sqloGetNumPhysDisks, probe:5" 2009-01-14-01.18.07.981428-300 E2810E432 LEVEL: Error (OS) PID : 16276 TID : 1 PROC : db2fmp (108) 0 INSTANCE: db2inst NODE : 000 EDUID : 1 EDUNAME: db2fmp (108) 0 FUNCTION: DB2 UDB, oper system services, sqloGetNumPhysDisks, probe:5 MESSAGE : ZRC=0x8300000A=-2097151990 CALLED : OS, -, unspecified_system_function OSERR : ECHILD (10) "No child processes" The error indicates that DB2 is unable to determine the number of disks installed in the server, because Solaris hides the hardware details within a local zone. This error message is expected in such case, and does not affect any functionalities of DB2. Since a concern was raised that this message may wrongfully alarm users, the message level will be lowered to WARNING. Currently, it's shown as ERROR, as seen in the message above. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Those running DB2 in Solaris Zone environment * **************************************************************** * PROBLEM DESCRIPTION: * * Same as ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Ignore the message, as it doesn't affect any DB2 features. * **************************************************************** | |
Local Fix: | |
Ignore this message. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 9.5 Fix pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.10.2009 05.02.2010 05.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |