cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

DB2 crash

Former Member

on ‎05-09-2013 6:38 AM

0 Kudos

Hi Techies,

I am new to SAP DB2, When restarted the SAP system the database is not coming up it shutting down with the below attached error.

found the below error but QAS and PRD with the same kernel version working fine.

Detected kernel  config that is incompatible with DB2 NUMA support

Regards,

Sandeep Singh

1db2diag.txt.zip
Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (5)

Answers (5)

kaus19d
Active Contributor
‎09-08-2016 11:17 AM
0 Kudos

I believe indulging IBM Support team would be the considered option here available for you

Show replies
Show replies
kaus19d
Active Contributor
‎09-06-2016 3:28 PM
0 Kudos

i believe the database was upgraded/changed recently. So as downgrade not a question here, could you check for the db2 license file? Completely stop n start the database, I am sure indexing issue is not the case here. The required kernel info & relates are can be found in below:-

IBM Knowledge Center

Thanks,

Kaushik

Show replies
Show replies
Former Member
‎05-16-2013 8:11 AM
0 Kudos

Hi peter,

I found the below error in db2<sid>.nfy

2013-05-16-14.28.30.382509   Instance:db2sid   Node:000

PID:19019(db2stop2)   TID:347080480   Appid:none

base sys utilities  DB2StopMain Probe:911

ADM7514W  Database manager has stopped.

2013-05-16-14.36.20.496310   Instance:db2sid   Node:000

PID:19609(db2star2)   TID:1577977632   Appid:none

base sys utilities  DB2StartMain Probe:911

ADM7513W  Database manager has started.

2013-05-16-14.37.04.897973   Instance:db2sid   Node:000

PID:19615(db2agent (sid) 0)   TID:2298472192   Appid:170.241.163.113.40405.130516063649

oper system services  sqloEDUCodeTrapHandler Probe:90   Database:sid

ADM14011C  A critical failure has caused the following type of error: "Trap".

The DB2 database manager cannot recover from the failure. First Occurrence Data

Capture (FODC) was invoked in the following mode: "Automatic". FODC diagnostic

information is located in the following directory:

"/db2/sid/db2dump/FODC_Trap_2013-05-16-14.36.49.495072_0000/".

2013-05-16-14.39.11.935634   Instance:db2sid   Node:000

PID:20166(db2star2)   TID:2994960160   Appid:none

base sys utilities  DB2StartMain Probe:911

ADM7513W  Database manager has started.

2013-05-16-14.40.10.142726   Instance:db2sid   Node:000

PID:20172(db2agent (sid) 0)   TID:922740480   Appid:*LOCAL.db2sid.130516064009

recovery manager  sqlpresr Probe:410   Database:sid

ADM1530E  Crash recovery has been initiated.

2013-05-16-14.40.10.257229   Instance:db2sid   Node:000

PID:20172(db2agent (sid) 0)   TID:922740480   Appid:*LOCAL.db2sid.130516064009

recovery manager  sqlpresr Probe:3170   Database:sid

ADM1531E  Crash recovery has completed successfully.

2013-05-16-14.44.19.267541   Instance:db2sid   Node:000

PID:20172(db2agent (sid) 0)   TID:872408832   Appid:*LOCAL.db2sid.130516064416

oper system services  sqloEDUCodeTrapHandler Probe:90   Database:sid

ADM14011C  A critical failure has caused the following type of error: "Trap".

The DB2 database manager cannot recover from the failure. First Occurrence Data

Capture (FODC) was invoked in the following mode: "Automatic". FODC diagnostic

information is located in the following directory:

"/db2/sid/db2dump/FODC_Trap_2013-05-16-14.44.13.178287_0000/".

2013-05-16-14.44.21.714991   Instance:db2sid   Node:000

PID:20170(db2wdog 0)   TID:1270867712   Appid:none

base sys utilities  sqleWatchDog Probe:20

ADM0503C  An unexpected internal processing error has occurred. All DB2

processes associated with this instance have been shutdown. Diagnostic

information has been recorded. Contact IBM Support for further assistance.

2013-05-16-14.46.32.035839   Instance:db2sid   Node:000

PID:20778(db2star2)   TID:534116128   Appid:none

base sys utilities  DB2StartMain Probe:911

ADM7513W  Database manager has started.

2013-05-16-14.50.01.853436   Instance:db2sid   Node:000

PID:20784(db2agent (sid) 0)   TID:876603136   Appid:*LOCAL.db2sid.130516065000

recovery manager  sqlpresr Probe:410   Database:sid

ADM1530E  Crash recovery has been initiated.

2013-05-16-14.50.01.932127   Instance:db2sid   Node:000

PID:20784(db2agent (sid) 0)   TID:876603136   Appid:*LOCAL.db2sid.130516065000

recovery manager  sqlpresr Probe:3170   Database:sid

ADM1531E  Crash recovery has completed successfully.

2013-05-16-14.56.38.702644   Instance:db2sid   Node:000

PID:20784(db2agent (sid) 0)   TID:822077184   Appid:*LOCAL.db2sid.130516065634

oper system services  sqloEDUCodeTrapHandler Probe:90   Database:sid

ADM14011C  A critical failure has caused the following type of error: "Trap".

The DB2 database manager cannot recover from the failure. First Occurrence Data

Capture (FODC) was invoked in the following mode: "Automatic". FODC diagnostic

information is located in the following directory:

"/db2/sid/db2dump/FODC_Trap_2013-05-16-14.56.32.623210_0000/".

2013-05-16-14.56.41.431899   Instance:db2sid   Node:000

PID:20782(db2wdog 0)   TID:1501554432   Appid:none

base sys utilities  sqleWatchDog Probe:20

ADM0503C  An unexpected internal processing error has occurred. All DB2

processes associated with this instance have been shutdown. Diagnostic

inf

please find the output for db2set -all:

db2sid> db2set -all

[e] DB2DBDFT=sid

[i] DB2_SKIP_VIEWRECREATE_SAP=TRUE [DB2_WORKLOAD]

[i] DB2_RESTORE_GRANT_ADMIN_AUTHORITIES=YES [DB2_WORKLOAD]

[i] DB2_BLOCKING_WITHHOLD_LOBLOCATOR=NO [DB2_WORKLOAD]

[i] DB2_AGENT_CACHING_FMP=OFF [DB2_WORKLOAD]

[i] DB2_TRUST_MDC_BLOCK_FULL_HINT=YES [DB2_WORKLOAD]

[i] DB2_CREATE_INDEX_COLLECT_STATS=YES [DB2_WORKLOAD]

[i] DB2_ATS_ENABLE=YES [DB2_WORKLOAD]

[i] DB2_RESTRICT_DDF=YES [DB2_WORKLOAD]

[i] DB2_DUMP_SECTION_ENV=YES [DB2_WORKLOAD]

[i] DB2_OPT_MAX_TEMP_SIZE=10240 [DB2_WORKLOAD]

[i] DB2_WORKLOAD=SAP

[i] DB2_TRUNCATE_REUSESTORAGE=IMPORT [DB2_WORKLOAD]

[i] DB2_MDC_ROLLOUT=DEFER [DB2_WORKLOAD]

[i] DB2AUTH=OSAUTHDB

[i] DB2_ATM_CMD_LINE_ARGS=-include-manual-tables [DB2_WORKLOAD]

[i] DB2_SKIPINSERTED=YES [DB2_WORKLOAD]

[i] DB2_VIEW_REOPT_VALUES=YES [DB2_WORKLOAD]

[i] DB2_OBJECT_TABLE_ENTRIES=65532 [DB2_WORKLOAD]

[i] DB2_OPTPROFILE=YES [DB2_WORKLOAD]

[i] DB2_IMPLICIT_UNICODE=YES [DB2_WORKLOAD]

[i] DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT [DB2_WORKLOAD]

[i] DB2STMM=APPLY_HEURISTICS:YES,GLOBAL_BENEFIT_SEGMENT_UNIQUE:YES [DB2_WORKLOAD]

[i] DB2_INLIST_TO_NLJN=YES [DB2_WORKLOAD]

[i] DB2_MINIMIZE_LISTPREFETCH=YES [DB2_WORKLOAD]

[i] DB2_REDUCED_OPTIMIZATION=4,INDEX,JOIN,NO_TQ_FACT,NO_HSJN_BUILD_FACT,STARJN_CARD_SKEW,NO_SORT_MGJOIN,CART OFF,CAP OFF [DB2_WORKLOAD]

[i] DB2NOTIFYVERBOSE=YES [DB2_WORKLOAD]

[i] DB2_INTERESTING_KEYS=YES [DB2_WORKLOAD]

[i] DB2_EVALUNCOMMITTED=YES [DB2_WORKLOAD]

[i] DB2_EXTENDED_OPTIMIZATION=NLJOIN_KEYCARD,IXOR,MULTIRG_BOUND [DB2_WORKLOAD]

[i] DB2_ANTIJOIN=EXTEND [DB2_WORKLOAD]

[i] DB2COMPOPT=327685,131776 [DB2_WORKLOAD]

[i] DB2ATLD_PORTS=60000:65000

[i] DB2ENVLIST=INSTHOME SAPSYSTEMNAME dbs_db6_schema DIR_LIBRARY LD_LIBRARY_PATH

[i] DB2COUNTRY=1

[i] DB2COMM=tcpip [O]

[g] DB2FCMCOMM=TCPIP4

[g] DB2SYSTEM=lsinm013db2e

[g] DB2INSTDEF=db2sid

Regards,

Sandeep

Show replies
Show replies
hugo_amo
Employee
Employee
‎05-09-2013 9:00 AM
0 Kudos

Hi Sandeep,

This message was added with IC80998. This message is just informational message and can be ignored. This defect is fixed in V9.7 FixPack 9.

Regards,

Hugo

Show replies
Show replies
Former Member
‎05-10-2013 4:08 AM
0 Kudos

Hi Hugo,

We are presently using V9.7 FixPack 9.

Regards,

Sandeep Singh

former_member189725
Active Contributor
‎05-10-2013 4:41 AM
0 Kudos

what is the operating system you are using and the version?

Can you paste the content of db2nodes.cfg file under /db2/db2<sid>/sqllib ?

Regards

Ratnajit

Former Member
‎05-10-2013 5:37 AM
0 Kudos

Hi Ratnajit,

We are using RHEl 6.2, please find the db2nodes.cfg information

db2<SID>> cat db2nodes.cfg
0 lsinm013db2e 0
regards,
Sandeep Singh

former_member189725
Active Contributor
‎05-10-2013 7:38 AM
0 Kudos

Can you check if you have DB2_RESOURCE_POLICY registry set ?

Also what is the fix pack level ? From db2diag.log it seems the system is using fixpack 6.

Have you upgraded the fixpack recently.

The issue is with the Lunix RHEL 6 kernel incompatibility.

Regards

Ratnajit

hugo_amo
Employee
Employee
‎05-10-2013 7:50 AM
0 Kudos

Hi Sandeep,

Are you sure? In the db2diag.log you attached it is said that you are using fp 6.

Informational tokens are "DB2 v9.7.0.6", "s120629", "IP23421", Fix Pack "6".

Regards,

Hugo

Former Member
‎05-10-2013 8:22 AM
0 Kudos

Hi Hugo,

Sorry, Its the Fix pack 6 we are using, will now apply FP9.

Hope for luck.

Regards,

Sandeep Singh

hugo_amo
Employee
Employee
‎05-10-2013 8:27 AM
0 Kudos

Let us know the outcome.

Regards,

Hugo

Former Member
‎05-10-2013 8:51 AM
0 Kudos

Hi Hugo,

I could see only FP7 in the market place,


51045163_2DB2 for LUW 9.7 FP7 Linux on x86_64 64bit

Regards,

Sandeep Singh

former_member189725
Active Contributor
‎05-10-2013 9:13 AM
0 Kudos

FP 8 and 9 is not certified yet for 9.7.

Refer this note Note 101809 - DB6: Supported Fix Packs DB2 for Linux, UNIX and Windows

Latest available in SAP SMP is DB2 9.7 FP 7.

Apply this and check.

Regards

Ratnajit

hugo_amo
Employee
Employee
‎05-10-2013 9:18 AM
0 Kudos

Hi Sandeep Singh,

Yes, you are right. It is not available in the SMP yet but as I said, this error will be fixed in fp 9. Sorry about that.

Regards,

Hugo

Former Member
‎05-15-2013 11:01 AM
0 Kudos

Hi Hugo,

The system has been started with below steps:

1. db2stop

2.Clean ipc

3.db2start

4.db2 active db SID

Regards,

Sandeep Singh

Former Member
‎05-15-2013 3:24 PM
0 Kudos

Hi Sandeep Singh,

could you please attach the output from db2set -all.

Regards,

Peter Rupp

former_member188883
Active Contributor
‎05-09-2013 7:42 AM
0 Kudos

Hi Sandeep,

Could you check this link

http://portal2portal.blogspot.sg/2013/03/detected-kernel-config-that-is.html

Regards,

Deepak Kori

Show replies
Show replies
Ask a Question