Symptom
- While running database backup the following errors can be seen in the db2diag.log.
2015-06-30-18.00.07.210481-300 E18847103A811 LEVEL: Severe
PID : ****** TID : 1 PROC : ****
INSTANCE: db2*** NODE : 000
HOSTNAME: *********
EDUID : 1
FUNCTION: DB2 UDB, database utilities, sqlubConnectDatabase, probe:1285
MESSAGE : SQL2406N The BACKUP cannot be performed because the database needs
to be rolled forward.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2406 sqlerrml: 0
sqlerrmc:
sqlerrp : sqlubCon
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 57019
2015-06-30-18.00.11.366303-300 I18848582A630 LEVEL: Error
PID : ******** TID : **** PROC : db2sysc 0
INSTANCE: db2*** NODE : 000 DB : ***
APPHDL : 0-54 APPID: *LOCAL.db2***.****
AUTHID : DB2*** HOSTNAME: *********
EDUID : 4370 EDUNAME: db2agent (PRD) 0
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:5247
MESSAGE : ZRC=0xFFFFFBA3=-1117
SQL1117N A connection to or activation of database "" cannot be made
because of ROLL-FORWARD PENDING
Read more...
Environment
- Database : DB6 10.1, 10.5, 11.1
- Operating System : Linux/Unix/AIX/Solaris
Product
SAP ERP 6.0
Keywords
Db2diag.log, backup, restore, missing log, SQL1276N , 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.