Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

DUMP MESSAGE

Former Member
0 Likes
684

Using the BAPI ISM_CONTRACTDEMAND_SET' it gave a dump SNAP_NO_NEW_ENTRY. Kindly help on this

4 REPLIES 4
Read only

Former Member
0 Likes
638

Hi,

Please refer the SAP OSS note 17537.

Thanks,

Sriram Ponna.

Read only

0 Likes
638

Thanks

Read only

Former Member
0 Likes
638

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.

Read only

0 Likes
638

Thanks Imran i am facing same Dump and now my dump is resolve using your solution thanks again