DUMP MESSAGE

Former Member — Sat, 12 Apr 2008 18:55:55 GMT

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

Re: DUMP MESSAGE

Former Member — Sat, 12 Apr 2008 19:09:21 GMT

Hi,

Please refer the SAP OSS note 17537.

Thanks,

Sriram Ponna.

Re: DUMP MESSAGE

Former Member — Thu, 24 Apr 2008 11:30:59 GMT

Thanks

Re: DUMP MESSAGE

Former Member — Tue, 27 Oct 2009 06:50:34 GMT

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.

Re: DUMP MESSAGE

rahul_kumar46 — Thu, 24 Oct 2013 04:30:06 GMT

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

topic DUMP MESSAGE in Application Development and Automation Discussions

DUMP MESSAGE

Re: DUMP MESSAGE

Re: DUMP MESSAGE

Re: DUMP MESSAGE

Re: DUMP MESSAGE