cancel
Showing results for 
Search instead for 
Did you mean: 

DB 2 import - transaction log full

Former Member
0 Kudos

All,

Please help me to clarify this.

While performing the import, import monitor fails with transaction log full error and all the import stops.

I looked at db2diag.log file and could not find any error related to transaction log full. Log_dir has enough space. I had set it to max of 220 file and only 63 files used so far. No archiving enabled.

In notify log file, I saw "active log is full"

DB is db2 9.7 and OS is redhat linux 5

Any idea about this ?

Thanks!

Edited by: rkandy on Nov 25, 2009 3:53 PM

Accepted Solutions (1)

Accepted Solutions (1)

peter_dzurov
Contributor
0 Kudos

Hi,

I am not an DB2 expert, but little research is showing as follows:

"Either increase the number of logs, commit more regularly, or configure your system to rollback a single transaction from filling more than a specific number of logs (max_log parameter)."

You may find also following links helpful:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDS.doc_5.2/ldapin...

http://www.dbforums.com/db2/315772-transaction-log-full-db2.html#post1128549

Former Member
0 Kudos

I increased the size and number of primaryu log file and stopped and started the database and it worked fine.

Thanks!

former_member189725
Active Contributor
0 Kudos

Increasing the filesystem size /db2/<SID>/log_dir should resolve the issue.

Regrads

Ratnajit

Answers (0)