1,126
edits
Difference between revisions of "ARS1107E"
Jump to navigation
Jump to search
Added more troubleshooting for IBM CMOD ARS1107E.
(Initial edit - IBM CMOD ARS1107E - An error occurred.) |
(Added more troubleshooting for IBM CMOD ARS1107E.) |
||
| Line 26: | Line 26: | ||
For example, this error message was logged 5 seconds before the ARS1107E message in the System Log, and indicates that the DB2 transaction logs have run out of space for new transactions: | For example, this error message was logged 5 seconds before the ARS1107E message in the System Log, and indicates that the DB2 transaction logs have run out of space for new transactions: | ||
[[ARS0013E]] DB Error: [IBM][CLI Driver][DB2/AIX64] SQL0964C The transaction log for the database is full. SQLSTATE=57011 | [[ARS0013E]] DB Error: [IBM][CLI Driver][DB2/AIX64] SQL0964C The transaction log for the database is full. SQLSTATE=57011 | ||
Some recommended fixes for this issue are: | |||
* Update the LOGPRIMARY parameter in the DB2 configuration to increase the number of transaction logs that DB2 creates at start-up. | |||
* Increase the size of each individual transaction log - larger, busier systems will benefit from larger transaction logs. | |||
* Increase the size of the filesystem containing the transaction logs (arsdb_primarylog) appropriately. | |||
* Turn on transaction log compression with the LOGARCHCOMPR1 parameter in DB2. | |||
* Increase the number or archive logs with the LOGSECOND parameter in DB2. | |||
* Increase the size of the archive log filesystem to store more of the transaction logs that 'overflow' into it. | |||
* Implement transaction log archiving with Tivoli Storage Manager to help reduce the headaches caused by managing database transaction logs. | |||
== Articles Related to this message == | == Articles Related to this message == | ||
Check the [[Troubleshooting Content Manager OnDemand]] article for more instructions on finding the source of the issue. | Check the [[Troubleshooting Content Manager OnDemand]] article for more instructions on finding the source of the issue. | ||