Topic
  • 2 replies
  • Latest Post - ‏2009-11-24T10:35:23Z by sakumar9
DB2 PK DBA
DB2 PK DBA
3 Posts

Pinned topic DIA8309C Log file was full?

‏2009-11-16T20:41:06Z |
Hi All

Please Note there was no bulk insert/update/delete. no export/import
We have shifted traffic to new servers.

We noticed that DB2 log shows following error i have already increased db log size to 10000:

2009-11-16-16.47.16.953000+300 E4602539H541 LEVEL: Error
PID : 6828 TID : 6156 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : JCRDB
APPHDL : 0-338 APPID: 66.219.30.210.35853.09111608520
AUTHID : DB2ADMIN
FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, probe:2860
MESSAGE : ADM1823E The active log is full and is held by application handle
"434". Terminate this application by COMMIT, ROLLBACK or FORCE
APPLICATION.

2009-11-16-16.47.16.953000+300 I4603082H505 LEVEL: Error
PID : 6828 TID : 6156 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : JCRDB
APPHDL : 0-338 APPID: 66.219.30.210.35853.09111608520
AUTHID : DB2ADMIN
FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:6680
RETCODE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.
Thnx in adv:
  • DB2 PK DBA
    DB2 PK DBA
    3 Posts

    Re: DIA8309C Log file was full?

    ‏2009-11-18T14:37:02Z  
    Very much disappointed from this forum as got 0 response.
    I had derived solution my self
    just increase value LOGFILESIZE, LOGPRIMARY and LOGSECONDARY to resolve this error.
    if doing bulk import of data or bulk Insert / update / delete. then try to commit more frequently. use commitcount.

    Thanks
  • sakumar9
    sakumar9
    79 Posts

    Re: DIA8309C Log file was full?

    ‏2009-11-24T10:35:23Z  
    Very much disappointed from this forum as got 0 response.
    I had derived solution my self
    just increase value LOGFILESIZE, LOGPRIMARY and LOGSECONDARY to resolve this error.
    if doing bulk import of data or bulk Insert / update / delete. then try to commit more frequently. use commitcount.

    Thanks
    Once you increase the log size, you will have to restart the instance.