Home   |   Register   |   Rules   |   Calendar   |   Get Daily   |     |  
 


If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Incomprenhensible Error-Messages

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-05-10, 02:29
michael.mest michael.mest is offline
Registered User
  
Join Date: Jun 2009
Posts: 8
Question Incomprenhensible Error-Messages
Hi,

we use DB/2 Version 9.7 FP2
on a 64-Bit PowerBlade and we get some suspect error messages in db2diag-file:

Code:
2010-07-05-08.26.08.931463+120 I1027905A254       LEVEL: Error
PID     : 8562                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:45
RETCODE : ZRC=0xFFFFEC46=-5050

2010-07-05-08.26.08.931790+120 I1028160A371       LEVEL: Error
PID     : 8562                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : bytesr
DATA #1 : Hexdump, 8 bytes
0x00000FFFFF7F7148 : 0000 0000 0000 1000                        ........

2010-07-05-08.26.08.931904+120 I1028532A371       LEVEL: Error
PID     : 8562                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : ptr->release
DATA #1 : Hexdump, 2 bytes
0x0000040001FDB8C8 : 0D00                                       ..

2010-07-05-08.26.08.931987+120 I1028904A372       LEVEL: Error
PID     : 8562                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : ptr->chksum
DATA #1 : Hexdump, 4 bytes
0x0000040001FDB8B8 : 0000 6AE6                                  ..j.

2010-07-05-08.26.08.932070+120 I1029277A379       LEVEL: Error
PID     : 8562                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : ptr->dbm_cfg_version
DATA #1 : Hexdump, 2 bytes
0x0000040001FDB8CC : 25E4                                       %.

2010-07-05-08.26.08.932154+120 I1029657A359       LEVEL: Error
PID     : 8562                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : dbm config
DATA #1 : failed to open dump file
/db2home/iobasis/aux/db2dump/8562.0.000.dump.bin

2010-07-05-08.26.08.954531+120 I1030941A254       LEVEL: Error
PID     : 8568                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:45
RETCODE : ZRC=0xFFFFEC46=-5050

2010-07-05-08.26.08.954787+120 I1031196A371       LEVEL: Error
PID     : 8568                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : bytesr
DATA #1 : Hexdump, 8 bytes
0x00000FFFFFF87148 : 0000 0000 0000 1000                        ........

2010-07-05-08.26.08.954896+120 I1031568A371       LEVEL: Error
PID     : 8568                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : ptr->release
DATA #1 : Hexdump, 2 bytes
0x0000040001FDB8C8 : 0D00                                       ..

2010-07-05-08.26.08.954979+120 I1031940A372       LEVEL: Error
PID     : 8568                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : ptr->chksum
DATA #1 : Hexdump, 4 bytes
0x0000040001FDB8B8 : 0000 6AE6                                  ..j.

2010-07-05-08.26.08.955294+120 I1032313A379       LEVEL: Error
PID     : 8568                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : ptr->dbm_cfg_version
DATA #1 : Hexdump, 2 bytes
0x0000040001FDB8CC : 25E4                                       %.

2010-07-05-08.26.08.955415+120 I1032693A359       LEVEL: Error
PID     : 8568                 TID  : 4398057022560PROC : db2fm
INSTANCE: iobasis              NODE : 000
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0
MESSAGE : dbm config
DATA #1 : failed to open dump file
/db2home/iobasis/aux/db2dump/8568.0.000.dump.bin
This Messages repeat and repeat and blow up the diag-file.

Can anyone tell me, what it means and what we can do?

Thanks
Michael
Reply With Quote
  #2 (permalink)  
Old 07-05-10, 04:10
nvk@vhv nvk@vhv is offline
Registered User
  
Join Date: Jan 2010
Posts: 294
Try
db2diag -rc 0xFFFFEC46

Cheers
nvk
Reply With Quote
  #3 (permalink)  
Old 07-06-10, 00:42
michael.mest michael.mest is offline
Registered User
  
Join Date: Jun 2009
Posts: 8
Thx for your answer.

The result is the following:

Code:
Input ECF string '0xFFFFEC46' parsed as 0xFFFFEC46 (-5050).
ERROR: /view/db2_v97fp2_linuxppc64_s100514/vbs/engn/pd/../sqz/sqlzwhatisrc.C:
	Input ZRC 0xFFFFEC46 (-5050) cannot be identified as a V7 or V6 ZRC value
Reply With Quote
  #4 (permalink)  
Old 07-06-10, 11:02
stolze stolze is offline
Registered User
  
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
-5050 looks suspiciously like a SQLCODE to me. So I would try what the message suggests:
Quote:
$ db2 "? sql5050"


SQL5050C The content of the database manager configuration file is not
valid.

Explanation:

The database manager configuration file is not valid. The file may have
been altered by a text editor or a program other than the database
manager.

The command cannot be processed.

User response:

Reinstall the database manager.
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
  #5 (permalink)  
Old 08-10-10, 13:45
JamesTJr JamesTJr is offline
Registered User
  
Join Date: Nov 2009
Location: Harrisburg, PA
Posts: 5
I am also getting this error running db2 9.7 fp 2 on AIX. Have you figured out what is causing it?
Reply With Quote
  #6 (permalink)  
Old 08-10-10, 15:03
n_i n_i is offline
:-)
  
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
Quote:
Originally Posted by JamesTJr View Post
Have you figured out what is causing it?
Quote:
Explanation:

The database manager configuration file is not valid. The file may have
been altered by a text editor or a program other than the database
manager.
..........
Reply With Quote
Reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 
 
 
Home  |   Register  |   Get New  |   FAQ's  |   Sitemap

Powered by vBulletin
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.