This is a discussion on Log file size within the DB2 forums, part of the Database Server Software category; --> Hi, when I execute a INSERT INTO xxx(...) SELECT (...) FROM yyy that should add approximately 8000 rows of ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, when I execute a INSERT INTO xxx(...) SELECT (...) FROM yyy that should add approximately 8000 rows of the table xxx to yyy I get the following error message: "SQL0964C The transaction log for the database is full" I have created the database using the default settings for the log files. How can I increase the space for the log files in order not to have this error? Thanks in advance! Diego |
| ||||
| "Gordon Gekko" <diegz@telvia.it> wrote in message news:cakdt8$q1s$1@fata.cs.interbusiness.it... > Hi, > > when I execute a > > INSERT INTO xxx(...) > SELECT (...) > FROM yyy > > that should add approximately 8000 rows of the table xxx to yyy I get > the following error message: > > "SQL0964C The transaction log for the database is full" > > I have created the database using the default settings for the log > files. How can I increase the space for the log files in order not to > have this error? > > Thanks in advance! > > Diego > Using the Control Center and database configuration, change the number of primary and secondary log files (double both of these). Increase the size of each log file (increase by a factor of 10). If you still get the errors, increase them again. You may have to restart the database after each change. You can also update these via the command line. See the Administration Guide: Performance for details. |