finding error in db2diag.log

finding error in db2diag.log

Post by RP » Wed, 13 Sep 2000 02:24:22



I have a DB2 UDB 5.2 running on AIX spitting the following message on
the db2diag.log. Any ideas what they are :

2000-09-11-02.55.54.136839   Instance:instprd1   Node:000
PID:21036(db2agent (PRODMFG))   Appid:*LOCAL.instprd1.000911065103
base_sys_utilities    sqleflsr   Probe:2   Database:MFG002DB

RIDS/sqleflsr MS/DB_BAD_FAT PRCS/25351 4c43 4120 2020 0000 0088 ffff
fc28

2000-09-11-02.56.02.939481   Instance:instprd1   Node:000
PID:15374(db2loggr)   Appid:none
oper_system_services  sqlofmblk   Probe:20

DiagData
ffff a602                                     ....

2000-09-11-02.56.03.095154   Instance:instprd1   Node:000
PID:15374(db2loggr)   Appid:none
oper_system_services  sqloclose   Probe:36

errno: 0000 0009                                     ....

2000-09-11-00.50.12.386671   Instance:instprd1   Node:000
PID:21214(db2agent (PRODMFG))   Appid:*LOCAL.instprd1.000911041220
data_protection       sqlpALR_OpenExtent   Probe:30   Database:MFG002DB

Missing Extent Number: 0000
0060                                     ...`

                             ...`

2000-09-10-20.23.52.253838   Instance:instprd1   Node:000
PID:19916(db2cart)   Appid:none
data_protection       sqlpgart   Probe:40
DIA3605C Memory allocation failure occurred.

ZRC=FFFFD605

Any help is greatly appreciated

Thanks

RP

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

finding error in db2diag.log

Post by Andrew McLauchla » Wed, 13 Sep 2000 08:31:16


Not sure about the FC28 error but the A602 is an invalid memory address
and the D605 is a memory allocation failure. Sounds like you have
problems
on AIX or the h/w.

The messsges can be found in the troubleshooting guide under
DB2 Internal Return Codes

You may want to call IBM Support re the FC28 code.

..Andrew


> I have a DB2 UDB 5.2 running on AIX spitting the following message on
> the db2diag.log. Any ideas what they are :

> 2000-09-11-02.55.54.136839   Instance:instprd1   Node:000
> PID:21036(db2agent (PRODMFG))   Appid:*LOCAL.instprd1.000911065103
> base_sys_utilities    sqleflsr   Probe:2   Database:MFG002DB

> RIDS/sqleflsr MS/DB_BAD_FAT PRCS/25351 4c43 4120 2020 0000 0088 ffff
> fc28

> 2000-09-11-02.56.02.939481   Instance:instprd1   Node:000
> PID:15374(db2loggr)   Appid:none
> oper_system_services  sqlofmblk   Probe:20

> DiagData
> ffff a602                                     ....

> 2000-09-11-02.56.03.095154   Instance:instprd1   Node:000
> PID:15374(db2loggr)   Appid:none
> oper_system_services  sqloclose   Probe:36

> errno: 0000 0009                                     ....

> 2000-09-11-00.50.12.386671   Instance:instprd1   Node:000
> PID:21214(db2agent (PRODMFG))   Appid:*LOCAL.instprd1.000911041220
> data_protection       sqlpALR_OpenExtent   Probe:30   Database:MFG002DB

> Missing Extent Number: 0000
> 0060                                     ...`

>                              ...`

> 2000-09-10-20.23.52.253838   Instance:instprd1   Node:000
> PID:19916(db2cart)   Appid:none
> data_protection       sqlpgart   Probe:40
> DIA3605C Memory allocation failure occurred.

> ZRC=FFFFD605

> Any help is greatly appreciated

> Thanks

> RP

> Sent via Deja.com http://www.deja.com/
> Before you buy.


 
 
 

finding error in db2diag.log

Post by Dorie Perfett » Thu, 14 Sep 2000 04:00:00


The fc28 is a severe internal error and should be reported to IBM Support.
Looks like may be h/w related.

> Not sure about the FC28 error but the A602 is an invalid memory address
> and the D605 is a memory allocation failure. Sounds like you have
> problems
> on AIX or the h/w.

> The messsges can be found in the troubleshooting guide under
> DB2 Internal Return Codes

> You may want to call IBM Support re the FC28 code.

> ..Andrew


> > I have a DB2 UDB 5.2 running on AIX spitting the following message on
> > the db2diag.log. Any ideas what they are :

> > 2000-09-11-02.55.54.136839   Instance:instprd1   Node:000
> > PID:21036(db2agent (PRODMFG))   Appid:*LOCAL.instprd1.000911065103
> > base_sys_utilities    sqleflsr   Probe:2   Database:MFG002DB

> > RIDS/sqleflsr MS/DB_BAD_FAT PRCS/25351 4c43 4120 2020 0000 0088 ffff
> > fc28

> > 2000-09-11-02.56.02.939481   Instance:instprd1   Node:000
> > PID:15374(db2loggr)   Appid:none
> > oper_system_services  sqlofmblk   Probe:20

> > DiagData
> > ffff a602                                     ....

> > 2000-09-11-02.56.03.095154   Instance:instprd1   Node:000
> > PID:15374(db2loggr)   Appid:none
> > oper_system_services  sqloclose   Probe:36

> > errno: 0000 0009                                     ....

> > 2000-09-11-00.50.12.386671   Instance:instprd1   Node:000
> > PID:21214(db2agent (PRODMFG))   Appid:*LOCAL.instprd1.000911041220
> > data_protection       sqlpALR_OpenExtent   Probe:30   Database:MFG002DB

> > Missing Extent Number: 0000
> > 0060                                     ...`

> >                              ...`

> > 2000-09-10-20.23.52.253838   Instance:instprd1   Node:000
> > PID:19916(db2cart)   Appid:none
> > data_protection       sqlpgart   Probe:40
> > DIA3605C Memory allocation failure occurred.

> > ZRC=FFFFD605

> > Any help is greatly appreciated

> > Thanks

> > RP

> > Sent via Deja.com http://www.deja.com/
> > Before you buy.

 
 
 

1. Where can I find db2diag.log?

Hi,
  I am having trouble finding the db2diag.log file in Windows NT4.0
environment. However the previos dba has left the diagpath parameter
blank.

Txs,
Ramya.

Sent via Deja.com http://www.deja.com/
Before you buy.

2. Two Forms and One Recordset

3. db2diag.log error

4. help with msflexgrid

5. REPOST: Re: db2 error in db2diag.log and LDAP crash

6. SQL 7.0, Windows 98 & Access 97

7. Error in db2diag.log

8. Newbie Database Encryption Question

9. db2 error in db2diag.log and LDAP crash

10. how to disable particular error codes in db2diag.log

11. how to interpret errors in db2diag.log

12. Errors in db2diag.log

13. db2diag.log error message