suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT25956 Status: Geschlossen

AUTOMATIC RESTORE FEATURE CAN PROVIDE AN INCORRECT SYNTAX IN THECOMMAND
PASSED TO DB2

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
In some cases where there are parallel backup entries in the
history file, empty directories can be passed through the
commands generated by DB2's automatic restore algorithm.  This
can result in a crash of the instance that may include a similar
entry in the db2diag.log:

2018-07-26-05.31.20.792782+000 E912821E1020 LEVEL: Critical

PID : 46789 TID : 140686326228736 PROC : db2sysc 0

INSTANCE: db2inst1 NODE : 000 DB : TEST1

APPHDL : 0-55 APPID: *N0.db2inst1.180726053224

AUTHID : db2inst1 HOSTNAME: db2test1.ibm.com

EDUID : 138 EDUNAME: db2agent (db2test) 0

FUNCTION: DB2 UDB, SQO Memory Management,
sqloDiagnoseFreeBlockFailure, probe:10

MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic".

The instance may have been shutdown as a result. "Automatic"
FODC

(First Occurrence Data Capture) has been invoked and diagnostic

information has been recorded in directory
"/db2test/db2dump/NODE0000/FODC_Panic_2018-07-26-05.31.20".

Please look in this directory for detailed evidence about what
happened and contact IBM support if necessary to diagnose the
problem.

A trap similar to this may be produced:


-----FUNC-ADDR---- ------FUNCTION + OFFSET------
ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 0x0356
ossDumpStackTraceV98 + 0x002b
OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00d7
sqlo_trce + 0x03c7
sqloEDUCodeTrapHandler + 0x03b1
gsignal + 0x0037
abort + 0x0148
sqloExitEDU + 0x0174
sqle_panici + 0x06a4
SQLO_MEM_POOL32diagnoseMemoryCorruptionAndCrashEmPKcb + 0x028e
sqlofmblkEx + 0x079e
sqludautControllerbPcjPiP12SQLU_BAPP_CBP26sqlu_tablespace_bkrst_
listP15sqlu_media_listbP5sqlca + 0x1d91
sqludrsa_route_inP5sqldaS0_P5sqlca + 0x0ebe
sqlerKnownProcedureiPcPiP5sqldaS2_P13sqlerFmpTableP8sqeAgentP5sq
lca + 0x0eae
sqlerCallDLP14db2UCinterfaceP9UCstpInfo + 0x1397
sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject + 0x0618
sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint
erface + 0x010b
sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x054e
sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0x011f
sqeAgent6RunEDUEv + 0x0de3
sqzEDUObj9EDUDriverEv + 0x0116
clone + 0x006d
Problem-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local-Fix:
Consider avoiding parallel backups or move to fix pack that
includes fix.
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.08.2018
27.11.2018
27.11.2018
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version