well, you can do two things:
1. Make sure you commit your changes frequently
2. Increase the size of the database log files or number of log files
db2 update db cfg for dbname using logprimary NN
dollar
Quote:
Originally posted by shrek lee
hi:
I face a error message in DB2 UDB 7.1, when I executed sql statement "drop" or "create" the DB2 appear follow message:
DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
SQL0964C The transaction log for the database is full. SQLSTATE=57011
How can I solve it ?
|