Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...
Database Forum / DB2 Topics / February 2006

Tip: Looking for answers? Try searching our database.

Strange Errors in db2diag.log

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Praveen_db2 - 23 Feb 2006 12:49 GMT
Hi All
I am getting strange errors in my db2diag.log can any one tell me what
these errors mean??
Following is the code from my db2diag.log
*********************************************************************************************
2006-02-23-17.53.12.253000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:1   Database:DEVM_DB

Error in agent servicing application with coor_node:
0x1BD7A612 : 0x0000                                     ..

2006-02-23-17.53.12.253001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:2   Database:DEVM_DB

Error in agent servicing application with coor_agent_index:
0x1BD7A610 : 0x0161                                     a.

2006-02-23-17.53.12.268000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:3   Database:DEVM_DB

Error in agent servicing application with CLIENT PID:
0x1BD7A5F0 : 0x34323033                                 3024

2006-02-23-17.53.12.268001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:4   Database:DEVM_DB

Error in agent servicing application with INBOUND APPLICATION ID:
0x189DC224 : 4143 3130 4530 3130 2E4A 3730 412E 3030    AC10E010.J70A.00
0x189DC234 : 4538 3833 3132 3232 3530                   E883122250

2006-02-23-17.53.12.268002   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:5   Database:DEVM_DB

Error in agent servicing application with INBOUND SEQUENCE NUMBER:
0x189DC1CE : 0x0003                                     ..

2006-02-23-17.53.12.268003   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:6   Database:DEVM_DB

Error in agent servicing application with OUTBOUND APPLICATION ID:

2006-02-23-17.53.12.268004   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:7   Database:DEVM_DB

Error in agent servicing application with OUTBOUND SEQUENCE NUMBER:

2006-02-23-17.53.12.268005   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:8   Database:DEVM_DB

Error in agent servicing application with AUTHORIZATION ID:
0x189DC0E5 : 5753 4143 4553 2020 0000 0000 0000 0000    DB_USER  ........
0x189DC0F5 : 0000 0000 0000 0000 0000 0000 0000 00      ...............

2006-02-23-17.53.12.284000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:9   Database:DEVM_DB

Error in agent servicing application with PRODUCT SIGNATURE:
0x189DC290 : 0x32313038304C5153                         SQL08012

2006-02-23-17.53.12.284001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleagnt_sigsegvh Probe:10   Database:DEVM_DB

Error in agent servicing application with APPLICATION NAME:
0x189DC266 : 6465 7665 6E76 2E65 7865                   devenv.exe

2006-02-23-17.53.12.300000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
DRDA Application Server  sqljsSignalHandler Probe:10   Database:DEVM_DB

DIA0505I Execution of a component signal handling function has begun.

2006-02-23-17.53.12.315000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
DRDA Application Server  sqljsSignalHandler Probe:911   Database:DEVM_DB

Source Type not DRDA AS. SourceType =
0x025B82A0 : 0x00000004                                 ....

2006-02-23-17.53.12.315001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
DRDA Application Server  sqljsSignalHandler Probe:20   Database:DEVM_DB

DIA0506I Execution of a component signal handling function is complete.

2006-02-23-17.53.12.315002   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
relation data serv  sqlrr_signal_handler Probe:50   Database:DEVM_DB

DIA0505I Execution of a component signal handling function has begun.

PID:1600 TID:440 Node:000 Title: RDS AGENT CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLCA
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS UCINTFC
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS UCINTFC: pCurrentPID =
0x1BD7A3D8 : 0x3C090F60                                 `.    <

PID:1600 TID:440 Node:000 Title: RDS UCINTFC:
pCurrentPID->pkgnamcsn.rdbcolid =
0x3C090F82 : 0x2020534543415357                         DB_USER  

PID:1600 TID:440 Node:000 Title: RDS UCINTFC: pCurrentPID->rdbcolidLen =
0x3C090F64 : 0x0008                                     ..

PID:1600 TID:440 Node:000 Title: RDS UCINTFC: pCurrentPID->rdbname =
0x3C090F70 : 4143 4553 5044 4D20 2020 2020 2020 2020    DEVM_DB        
0x3C090F80 : 2020                                        

PID:1600 TID:440 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgname =
0x3C090F94 : 5037 3531 3232 3839 2020 2020 2020 2020    P7512289        
0x3C090FA4 : 2020                                        

PID:1600 TID:440 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgcnstkn =
0x3C090FA6 : 0x574358527A574263                         cBWzRXCW

PID:1600 TID:440 Node:000 Title: RDS UCINTFC: pCurrentPID->pkgsn =
0x3C090FAE : 0x0002                                     ..

Trap c0000005 detected in db2diag call from [0,0,0] trapfile created

PID:1600 TID:440 Node:000 Title: RDS APPL CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS NESTED APPL CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS SP REGISTERS CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS TRAN CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS NESTED TRAN CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS COORD CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS NESTED CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: RDS INVOCATION CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

2006-02-23-17.53.12.409000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
relation data serv  sqlrr_dump_ffdc Probe:20   Database:DEVM_DB

DIA8516C A severe internal processing error has occurred.
ZRC=0x87120007

PID:1600 TID:440 Node:000 Title: SQLCA
sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 0   sqlerrml: 0
sqlerrmc:
sqlerrp : SQL08013
sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
          (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)    
          (7)      (8)      (9)      (10)        (11)    
sqlstate:      

PID:1600 TID:440 Node:000 Title: SQLCA
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: CREATOR
0x1D69198C : 0x2020534543415357                         DB_USER  

PID:1600 TID:440 Node:000 Title: PACKAGE
0x1D6919AA : 0x3938323231353750                         P7512289

PID:1600 TID:440 Node:000 Title: CREATOR
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: PACKAGE
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: REQUEST TYPE
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: APM COMMON INFO
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: PACKAGE ENTRY
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: CACHED PACKAGE ENTRY
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: Recursive dump_sect
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SECTION NUMBER
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SECTION ENTRY
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SECTION CURSOR INFO
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SIBLING ENTRY
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

2006-02-23-17.53.12.518000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
relation data serv  sqlrr_dump_ffdc Probe:902   Database:DEVM_DB

DIA8516C A severe internal processing error has occurred.
ZRC=0x87120007

2006-02-23-17.53.12.518001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
relation data serv  sqlrr_dump_ffdc Probe:902   Database:DEVM_DB

PID:1600 TID:440 Node:000 Title: SQLE_DBCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_DBCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_AGENT_CB Pointer:
0x1BD7A380 : 0x18DD0080                                 €.Ý.

PID:1600 TID:440 Node:000 Title: SQLD_AGENT_CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_TRAN_CB Pointer
0x1BD7A388 : 0x18ADC3F0                                 ðí.

PID:1600 TID:440 Node:000 Title: SQLD_TRAN_CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_APP_CB Pointer
0x1BD7A384 : 0x18ADC200                                 .­.

PID:1600 TID:440 Node:000 Title: SQLD_APP_CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: >> Begin CURSOR dump:
OPEN PERM CURSORS: >>

PID:1600 TID:440 Node:000 Title: << End CURSOR dump:
OPEN PERM CURSORS: <<

PID:1600 TID:440 Node:000 Title: >> Begin CURSOR dump:
OPEN TEMP CURSORS: >>

PID:1600 TID:440 Node:000 Title: << End CURSOR dump:
OPEN TEMP CURSORS: <<

PID:1600 TID:440 Node:000 Title: >> Begin CURSOR dump:
CLOSED CURSORS:  >>

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=0, obj(FID)=11, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=0, obj(FID)=24, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=0, obj(FID)=81, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=0, obj(FID)=30, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=415, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=417, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=421, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=424, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=146, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=203, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLD_CCB:
pool(TID)=2, obj(FID)=15, indexid(IID)=0, class=0

PID:1600 TID:440 Node:000 Title: SQLD_CCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: << End CURSOR dump:
CLOSED CURSORS: <<

PID:1600 TID:440 Node:000 Title: SQLI_CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLE_AGENT_PRIVATECB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLE_APP_CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLE_TRAN_CB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLP_LFPB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLP_ACB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLP_DBCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLP_TENTRY
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: locklist
Check C:\PROGRA~1\IBM\SQLLIB\DB2\l0174.000 for additional data.

PID:1600 TID:440 Node:000 Title: NLSWA:DatabaseApp
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: NLSWA:DatabaseDatabase
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: nlsacb
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: dbNLSAppCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: UnicodeNLSAppCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

2006-02-23-17.53.12.722001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
access plan manager  sqlra_sqlC_dump Probe:25   Database:DEVM_DB

Context info dumped! Check C:\PROGRA~1\IBM\SQLLIB\DB2\a1600440.000 for
additional data.

2006-02-23-17.53.12.737000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
access plan manager  sqlra_sqlW_raw_dump Probe:25   Database:DEVM_DB

Private workspace info dumped! Check
C:\PROGRA~1\IBM\SQLLIB\DB2\a1600440.000 for additional data.

2006-02-23-17.53.12.753000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
access plan manager  sqlra_sqlW_raw_dump Probe:25   Database:DEVM_DB

Shared workspace info dumped! Check
C:\PROGRA~1\IBM\SQLLIB\DB2\a1600440.000 for additional data.

2006-02-23-17.53.12.768000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
relation data serv  sqlrr_signal_handler Probe:20   Database:DEVM_DB

DIA0506I Execution of a component signal handling function is complete.

PID:1600 TID:440 Node:000 Title: SQLE_AGENT_PRIVATECB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

PID:1600 TID:440 Node:000 Title: SQLE_AGENTCB
Dump File:C:\PROGRA~1\IBM\SQLLIB\DB2\1600440.000

2006-02-23-17.53.13.815000   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
base sys utilities  sqleCleanupResources Probe:5   Database:DEVM_DB

DiagData
0x1BD7FE0C : 0x00000000                                 ....

2006-02-23-17.53.13.815001   Instance:DB2   Node:000
PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
routine_infrastructure  sqlerKillAllFmps Probe:5   Database:DEVM_DB

Bringing down all db2fmp processes as part of db2stop
0x1BD7FCD8 : 0x00000000                                 ....

2006-02-23-17.57.18.597000   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:2284   Appid:none
base sys utilities  LicCheckProcessors Probe:20

SQL8017W  The number of processors on this machine exceeds the defined
entitlement of "1" for the product "DB2 Enterprise Server Edition".  The
number of processors on this machine is "2".  You should purchase
additional
processor based entitlements from your IBM representative or authorized
dealer
and update your license using the License Center or the db2licm command
line
utility. For more information on updating processor based licenses, refer
to
the Quick Beginnings manual for your platform.  For more information on
the
db2licm utility, refer to the DB2 Command Reference.

2006-02-23-17.57.19.675000   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:2284   Appid:none
base sys utilities  startdbm Probe:911

ADM7513W  Database manager has started.

2006-02-23-17.57.51.800000   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:440   Appid:AC10E00F.ED04.00A7C3122751
base sys utilities  sqledint Probe:30

Crash Recovery is needed.

2006-02-23-17.57.52.003000   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:440   Appid:AC10E00F.ED04.00A7C3122751
recovery manager  sqlpresr Probe:410   Database:DEVM_DB

Crash recovery started. LowtranLSN 000000005BDC44EE MinbuffLSN
000000005BDBD1E8

2006-02-23-17.57.52.003002   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:440   Appid:AC10E00F.ED04.00A7C3122751
recovery manager  sqlprecm Probe:125   Database:DEVM_DB

Using parallel recovery with 5 agents 11 QSets 77 queues and 2 chunks

2006-02-23-17.57.52.018000   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:440   Appid:AC10E00F.ED04.00A7C3122751
recovery manager  sqlprecm Probe:400   Database:DEVM_DB

DIA2051W Forward phase of crash recovery has completed.  Next LSN is
"000000005BDC44EE".

2006-02-23-17.57.52.034001   Instance:DB2   Node:000
PID:2296(db2syscs.exe)   TID:440   Appid:AC10E00F.ED04.00A7C3122751
recovery manager  sqlpresr Probe:3170   Database:DEVM_DB

Crash recovery completed. Next LSN is 000000005BDC44EE
*********************************************************************************************

Regards
Praveen
Reply to this Message
mike_li - 23 Feb 2006 15:00 GMT
It looks like license issue involved here. You can use db2licm -l to
see what product you installed and what kind license you current have.
If you use more processors for your
product, you need to contact IBM to buy additional license.

> Hi All
> I am getting strange errors in my db2diag.log can any one tell me what
[quoted text clipped - 481 lines]
> Regards
> Praveen
Reply to this Message
Praveen_db2 - 24 Feb 2006 05:08 GMT
Hi Mike
Thanks for the reply.
Yes you are correct .We have 2 processors.But I found that I can update
the no. of processors successfully using
db2licm -n "Product Password" No._of_processors

What happens if I use this command?

Praveen

Reply to this Message
Knut Stolze - 24 Feb 2006 10:48 GMT
> It looks like license issue involved here. You can use db2licm -l to
> see what product you installed and what kind license you current have.
> If you use more processors for your
> product, you need to contact IBM to buy additional license.

No, this is not a licensing issue.  Why do you think so?

Signature

Knut Stolze
DB2 Information Integration Development
IBM Germany

Reply to this Message
Knut Stolze - 24 Feb 2006 10:47 GMT
> Hi All
> I am getting strange errors in my db2diag.log can any one tell me what
> these errors mean??
> Following is the code from my db2diag.log

*********************************************************************************************
> 2006-02-23-17.53.12.253000   Instance:DB2   Node:000
> PID:1600(db2syscs.exe)   TID:440   Appid:AC10E010.J70A.00E883122250
> base sys utilities  sqleagnt_sigsegvh Probe:1   Database:DEVM_DB

This is a segmentation violation that DB2 encountered.

Either this is a defect/bug in DB2, or you were running external routines
(C/C++ functions/procedures).  In the first case, it is a DB2 problem that
needs to be fixed.  Please call IBM support in that case.  If you are
running external routines, you might want to consider switching those to
FENCED routines so that they cannot simply bring down the DB2 engine when
they crash.

Signature

Knut Stolze
DB2 Information Integration Development
IBM Germany

Reply to this Message
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.