SAP Knowledge Base Article - Preview

2838804 - DB2 does not stop successfully after db2stop issued

Symptom

  • Db2stop fails with the following error and stop does not succeed.

    2019-01-01-00.00.00 I720607A1381 LEVEL: Event
    PID : 000000000 TID : 1 PROC : db2stop
    INSTANCE: db2sid NODE : 000
    HOSTNAME: Host
    EDUID : 1
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:10980
    MESSAGE : ZRC=0xFFFFE86B=-6037
    SQL6037N START or STOP DATABASE MANAGER timeout value was reached.

  • ps -elf output:
    ----------------------------------------------------------------
    F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
    *snip*
    4 S root 24200 1 0 99 19 - 300894 futex_ 3/21 ? 00:00:00 db2wdog
    0 [db2inst1]
    4 Z db2inst1 24204 24200 1 99 19 - 0 exit 3/21 ? 00:19:57
    [db2sysc] <defunct>
    5 S root 24219 24200 1 99 19 - 301534 msgrcv 3/21 ? 00:13:30
    db2ckpwd 0


Read more...

Environment

Db2 Linux, and Windows 10.5 and 11.1

Keywords

 ADM0503C, SQL6036N , KBA , BC-DB-DB6-DBA , Database Administration , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.