DB2 - Problem description
| Problem IT04021 | Status: Closed |
REDIRECT RESTORE WITH REBUILD OPTION RETURNS SUCCESS EVEN THOUGH FAILS TO ALLOCATE SPACE FOR TEMP SPACES | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
During redirect restore with rebuild option, restore fails to
allocate space for temp spaces and fails returning SQL290N error
in db2diag.log however, restore's return code itself to end user
is a success. After this, the tablespaces restored are left in
restore pending state, however it makes user to believe the
restore was fine.
These are the db2diag.log messages:
2014-07-29-09.59.11.558632-240 E3096250A1407 LEVEL: Error
(OS)
PID : 45154494 TID : 21608 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 21608 EDUNAME: db2pfchr (SAMPLE) 0
FUNCTION: DB2 UDB, oper system services,
sqloFilePreallocationOnFSWithFastExtend, probe:70
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
CALLED : OS, -, ioctl
OSERR : ENOSPC (28) "No space left on device"
DATA #1 : signed integer, 4 bytes
0
DATA #2 : signed integer, 4 bytes
28
DATA #3 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes
File Handle = 84
File System Block Size = 4096 bytes
File System Type = jfs2
File Handle Flags :
Require Sector Align = No
DIO/CIO Mode = Yes
Raw Block Device = No
Reserved Handle = No
Flush On Close = Yes
Thread-Level Lock = No
Write-through Mode = No
File Not Tracked = No
DATA #4 : File size, 8 bytes
1024
DATA #5 : unsigned integer, 8 bytes
4096
DATA #6 : Logical page size, PD_TYPE_MEM_PAGE_SIZE, 4 bytes
4096
DATA #7 : unsigned integer, 8 bytes
693107712
DATA #8 : unsigned integer, 8 bytes
169215
DATA #9 : unsigned integer, 8 bytes
1
DATA #10: String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
2014-07-29-09.59.11.559296-240 I3097658A2745 LEVEL: Error
(OS)
PID : 45154494 TID : 21608 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 21608 EDUNAME: db2pfchr (SAMPLE) 0
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100
CALLED : OS, -, ioctl
OSERR : ENOSPC (28) "No space left on device"
DATA #1 : String, 131 bytes
A total of 4 analysis will be performed :
- User info
- ulimit info
- Target file info
- File system
Target file handle = 84
DATA #2 : String, 194 bytes
Real user ID of current process = 123932
Effective user ID of current process = 123932
Real group ID of current process = 13123
Effective group ID of current process = 13123
DATA #3 : String, 379 bytes
Current process limits (unit in bytes except for nofiles) :
mem (S/H) = unlimited / unlimited
core (S/H) = unlimited / unlimited
cpu (S/H) = unlimited / unlimited
data (S/H) = unlimited / unlimited
fsize (S/H) = unlimited / unlimited
nofiles (S/H) = unlimited / unlimited
stack (S/H) = unlimited / unlimited
rss (S/H) = unlimited / unlimited
DATA #4 : String, 41 bytes
current sbrk(0) value: 0x000000011b2d3ac0
DATA #5 : String, 266 bytes
Target File Information :
Size = 64344064
Link = No
Reference path = N/A
Type = 0x8000
Permissions = rw-------
UID = 123932
GID = 13123
Last modified time = 1406642351
DATA #6 : String, 363 bytes
File System Information of the target file :
Block size = 4096 bytes
Total size = 67108864 bytes
Free size = 0 bytes
Total # of inodes = 2688
FS name = N/A
Mount point = /db2udb
FSID (major,minor)= 10, 21
FS type name = jfs2
DIO/CIO mount opt = None
Device type = N/A
FS type = 0x6
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x0900000009DE1468 pdOSSeLoggingCallback + 0x34
[1] 0x090000000842CE44 oss_log__FP9OSSLogFacUiN32UlN26iPPc +
0x1C4
[2] 0x090000000842D320 ossLogSysRC + 0xA0
[3] 0x090000000844BF4C
ossErrorIOAnalysis__FCPC21OSSErrorAnalysisParam + 0xC8C
[4] 0x090000000844DFE8 ossErrorAnalysis@AF12_1 + 0x48
[5] 0x090000000A7B3AF4 sqloSystemErrorHandler + 0x3E4
[6] 0x090000000B60A604
@78@sqloFilePreallocationOnFSWithFastExtend__FCP12SQLO_FHANDLECL
CPL + 0x84C
[7] 0x090000000B609698
@78@sqlo_file_ext_and_commit__FCP12SQLO_FHANDLECLT2 + 0x2F8
[8] 0x0900000009C14FEC sqloSetFileSize + 0x1F4
[9] 0x090000000C1600EC
sqlbServiceAddDMSContainerRequest__FP14SQLB_pfParIoCbP12SQLB_POO
L_CBP16SQLB_POOLCONT_CBP12SQLB_GLOBALS + 0x21C
2014-07-29-09.59.11.559664-240 I3100404A462 LEVEL: Error
PID : 45154494 TID : 21608 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 21608 EDUNAME: db2pfchr (SAMPLE) 0
FUNCTION: DB2 UDB, oper system services,
sqloFilePreallocationOnFSWithFastExtend, probe:200
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
DATA #1 : Codepath, 8 bytes
5:7:8:10:25:26
2014-07-29-09.59.11.587205-240 I3100867A645 LEVEL: Severe
PID : 45154494 TID : 90404 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-271 APPID:
*LOCAL.db2inst1.140729135906
AUTHID : db2inst1
EDUID : 90404 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbSetPoolCont,
probe:1360
MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full."
DIA8312C Disk was full.
DATA #1 : <preformatted>
A severe error was encountered while trying to set new
table space containers for table space DB2TSTEMPSORT4K (3)
2014-07-29-09.59.11.620005-240 E3101513A598 LEVEL: Error
PID : 45154494 TID : 90404 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-271 APPID:
*LOCAL.db2inst1.140729135906
AUTHID : db2inst1
EDUID : 90404 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlbStartPoolRestore,
probe:3
MESSAGE : ADM6025I The table space "DB2TSTEMPSORT4K" (ID "3")
is in state
0x"2001100"). "RESTORE" is not possible. Refer to the
documentation
for SQLCODE -290.
The output for the corresponding restore commands from command
line look as follows:
RESTORE DATABASE SAMPLE REBUILD WITH tablespace
(SYSCATSPACE,TBSPACE1) FROM '/db2/backups/01/sample02'
,'/db2/backups/02/sample02' ,'/db2/backups/03/sample02'
,'/db2/backups/04/sample02' TAKEN AT 20140719210031 INTO SAMPLE
LOGTARGET '/db2/backups/04/sample02/overflowlogs' REPLACE
EXISTING REDIRECT
SQL1277W A redirected restore operation is being performed.
Table space
configuration can now be viewed and table spaces that do not use
automatic
storage can have their containers reconfigured.
DB20000I The RESTORE DATABASE command completed successfully.
SET TABLESPACE CONTAINERS FOR 0 USING ( FILE '<PATH>'
1215904 )
DB20000I The SET TABLESPACE CONTAINERS command completed
successfully.
SET TABLESPACE CONTAINERS FOR 14 USING ( FILE '<PATH>'
798310 , FILE '<PATH>' 798310 , FILE '<PATH>'
798310 , FILE '<PATH>' 798310 )
DB20000I The SET TABLESPACE CONTAINERS command completed
successfully.
RESTORE DB SAMPLE CONTINUE
SQL1277W A redirected restore operation is being performed.
Table space
configuration can now be viewed and table spaces that do not use
automatic
storage can have their containers reconfigured.
DB20000I The RESTORE DATABASE command completed successfully. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users on DB2 v101 FP4 and lower * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V101 FP5 * **************************************************************** | |
| Local Fix: | |
As a temporary workaround, define temp tablespaces explicitly during redirect restore by specifying a small size. | |
| Solution | |
First Fixed in DB2 V101 FP5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.08.2014 16.07.2015 16.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|