suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT26388 Status: Closed

ERRORS FROM SQLPRECOVERYLSN IN CREATING LOG AT BACKUP FILE CAN LEAVE A
TABLE SPACE UNABLE TO BE ROLLED FORWARD

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When an error with a table space is detected, under certain
circumstances the table space is taken offline and placed in
rollforward pending.  Examples of such circumstances can be:

1. rollforward fails to replay a create table space operation
due to a container issue
2. rollforward fails to replay an alter table space operation
due to a container issue
3. crash recovery or rollforward fails to start a table space
due to a container issue

When doing so the recovery starting point information is stored
in a log at backup file that normally is found under a directory
such as /db1/NODE0000/SQL00001/SQLOGAB.  This file is needed for
the ensuing table space rollforward and without it the
rollforward will not succeed.  A failure such as:

   FUNCTION: DB2 UDB, database utilities,
sqluBRLogAtBkpInfo::allocate, probe:107
   MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not
found."
                    DIA8411C A file "" could not be found.
   DATA #1 : String, 31 bytes
   BRLogAtBkp file does not exist!
     [1] 0x00007F1BB578C988
_ZN18sqluBRLogAtBkpInfo8allocateERiP13SQLO_MEM_POOLPK18sqluBRLog
AtBkpFile + 0xE8
     [2] 0x00007F1BB535C52B
_Z19sqlbGetPoolLogAtBkpP12SQLB_POOL_CBPP18sqluBRLogAtBkpInfoP12S
QLB_GLOBALS + 0xFB
     [3] 0x00007F1BB5FA0C0C
_Z21sqlpGetTablespacesMRTP8sqeAgentPmPj + 0x7AC
     [4] 0x00007F1BB5FA13A9
_Z11sqlpFindMRTP8sqeAgentP14sqlpMasterDbcbjPjPm + 0x459
     [5] 0x00007F1BB5F9B677
_Z23sqlpInitForwardRecoveryP8sqeAgentP14sqlpMasterDbcbP9SQLP_LSN
8PjPKc + 0x187
     [6] 0x00007F1BB5FA0428
_Z19sqlpForwardRecoveryP8sqeAgenttPKcPiPjt + 0x1CD8

can be found in the db2diag.log.

In this case the table space cannot be rolled forward and a
table space restore and roll forward will be necessary.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to release inclusive of this fix. Refer to SYSROUTE  *
* APAR.                                                        *
****************************************************************
Local Fix:
Restore and roll forward table space.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT26391 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2018
23.09.2018
23.09.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)