2008 Apr 12 7:55 PM
Using the BAPI ISM_CONTRACTDEMAND_SET' it gave a dump SNAP_NO_NEW_ENTRY. Kindly help on this
The problem is basically because of the Transaction log for Database is full, we need to do the following steps and restart the server from OS level. If require a proper memory tuning needs to be done.
Problem: SQL0964C Transaction log for database is full (snap_no_new_entry)
Resolution:
Use the following procedure to increase the size of the DB2 transaction log (logfilsiz):
1. Determine the current log file size setting by issuing the command:
su - <db2instance>
db2 list db directory # to list the database name
db2 connect to <databaseName>
db2 get db config for <databaseName> | grep -i logfilsiz
Example:
su - ldapdb2
db2 connect to amdb
db2 get db config for amdb | grep -i logfilsiz
2. Increase the size of the log file size setting by issuing the command:
db2 UPDATE db cfg for <databaseName> using LOGFILSIZ <new_value>
Example:
db2 UPDATE db cfg for amdb using LOGFILSIZ 5000
3. Stop the ibmslapd process.
4. Issue the commands:
db2 force applications all
db2stop force
5. Restart ibmslapd process.
2008 Apr 12 8:09 PM
2008 Apr 24 12:30 PM
2009 Oct 27 6:50 AM
The problem is basically because of the Transaction log for Database is full, we need to do the following steps and restart the server from OS level. If require a proper memory tuning needs to be done.
Problem: SQL0964C Transaction log for database is full (snap_no_new_entry)
Resolution:
Use the following procedure to increase the size of the DB2 transaction log (logfilsiz):
1. Determine the current log file size setting by issuing the command:
su - <db2instance>
db2 list db directory # to list the database name
db2 connect to <databaseName>
db2 get db config for <databaseName> | grep -i logfilsiz
Example:
su - ldapdb2
db2 connect to amdb
db2 get db config for amdb | grep -i logfilsiz
2. Increase the size of the log file size setting by issuing the command:
db2 UPDATE db cfg for <databaseName> using LOGFILSIZ <new_value>
Example:
db2 UPDATE db cfg for amdb using LOGFILSIZ 5000
3. Stop the ibmslapd process.
4. Issue the commands:
db2 force applications all
db2stop force
5. Restart ibmslapd process.
2013 Oct 24 5:30 AM
Thanks Imran i am facing same Dump and now my dump is resolve using your solution thanks again
| User | Count |
|---|---|
| 6 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |