Question

Here is an example of failure : db2updv97 -d sample ... ... MESSAGE: Error creating system module : UTL_MAIL.UTL_MAIL_SEND MESSAGE: Rolling back work due to sqlcode: -727 on line 998. db2updv97 processing failed for database 'sample'. If you look closer in db2diag.log for corresponding error, you can see log file was full (SQL0964C) error leads to sqlcode: -727. 2016-04-19-16.40.47.456237-240 I133023A319 LEVEL: Warning PID : 821 TID : 2199061911168PROC : db2updv97 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, Common Trace API, sqlrl_db2updv, probe:587 DATA #1 : String, 54 bytes db2updv97 processing starting for database 'sample'. ... ... .... 2016-04-19-16.40.59.246057-240 E141054A592 LEVEL: Error PID : 836 TID : 2199383959888PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : sample APPHDL : 0-7 APPID: *LOCAL.db2inst1.160419204047 AUTHID : DB2INST1 EDUID : 21 EDUNAME: db2agent (sample) 0 FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, probe:2860 MESSAGE : ADM1823E The active log is full and is held by application handle "0-7". Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION. 2016-04-19-16.40.59.246742-240 I141647A556 LEVEL: Error PID : 836 TID : 2199383959888PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : sample APPHDL : 0-7 APPID: *LOCAL.db2inst1.160419204047 AUTHID : DB2INST1 EDUID : 21 EDUNAME: db2agent (sample) 0 FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:6680 MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE "Log File has reached its saturation point" DIA8309C Log file was full. 2016-04-19-16.40.59.263595-240 I146242A1041 LEVEL: Error PID : 836 TID : 2199383959888PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : sample APPHDL : 0-7 APPID: *LOCAL.db2inst1.160419204047 AUTHID : DB2INST1 EDUID : 21 EDUNAME: db2agent (sample) 0 FUNCTION: DB2 UDB, relation data serv, sqlrrUpdateInvalObj, probe:300 RETCODE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE "Log File has reached its saturation point" DIA8309C Log file was full. MESSAGE : SYSINVALIDOBJECTS update failed due to unexpected error DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -964 sqlerrml: 0 sqlerrmc: sqlerrp : SQLRL698 sqlerrd : (1) 0x85100009 (2) 0x00000009 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2016-04-19-16.40.59.263739-240 I147284A382 LEVEL: Warning PID : 821 TID : 2199061911168PROC : db2updv97 INSTANCE: db2inst1 NODE : 000 DB : sample APPID : *LOCAL.db2inst1.160419204047 FUNCTION: DB2 UDB, Common Trace API, sqlrl_db2updv, probe:1515 DATA #1 : String, 53 bytes Error creating system module : UTL_MAIL.UTL_MAIL_SEND 2016-04-19-16.40.59.263951-240 I147667A733 LEVEL: Warning PID : 821 TID : 2199061911168PROC : db2updv97 INSTANCE: db2inst1 NODE : 000 DB : sample APPID : *LOCAL.db2inst1.160419204047 FUNCTION: DB2 UDB, Common Trace API, sqlrl_db2updv, probe:1515 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCAL sqlcabc: 136 sqlcode: -727 sqlerrml: 13 sqlerrmc: 3 -964 57011 sqlerrp : SQLRR0AA sqlerrd : (1) 0x801A006D (2) 0x00000009 (3) 0x00000001 (4) 0x00000000 (5) 0xFFFFFB82 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 56098 2016-04-19-16.41.04.749022-240 I159909A318 LEVEL: Warning PID : 821 TID : 2199061911168PROC : db2updv97 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, Common Trace API, sqlrl_db2updv, probe:1098 DATA #1 : String, 52 bytes db2updv97 processing failed for database 'sample'. How to solve "SQL0964C Transaction log for database is full" https://www.ibm.com/developerworks/community/blogs/AllAboutData/entry/h…