snap_no_new_entry ABAP dump coming while ST22 is reorganized regularily

[Former Member]

Dear Friends,

snap_no_new_entry ABAP dump comes and hamper all activities while ST22 is reorganized daily. After restarting the server, It is working fine for a day only. Can you suggest in this regard to fix this problem permanently?

System Environment : SAP ECC 6.0, AIX, DB2

Table spaces :

Tablespace   Name	TS Type	KB Total	Percent Used	KB Free	Page Size (KB)	High-Water Mark   (KB)	No. Containers	Contents	TS State	AUTORESIZE
PSAPTEMP16	SMS	64	100.00	0	16	0	4	Temporary objects	Normal	NO
SYSTOOLSTMPSPACE	SMS	64	100.00	0	16	0	4	Temporary objects	Normal	NO
ECP#BTABD	DMS	6422528	99.94	3680	16	6418720	4	Large objects	Normal	YES
ECP#ES702DX	DMS	35586048	99.94	21888	16	35564032	4	Large objects	Normal	YES
ECP#EL702DX	DMS	18972672	99.93	13632	16	18958912	4	Large objects	Normal	YES
SYSCATSPACE	DMS	2785280	99.67	9216	16	2775936	4	Regular data	Normal	YES
ECP#ES702IX	DMS	7471104	99.58	31456	16	7439520	4	Large objects	Normal	YES
ECP#STABD	DMS	3637248	99.58	15424	16	3621696	4	Large objects	Normal	YES
ECP#POOLD	DMS	6258688	99.54	28832	16	6252608	4	Large objects	Normal	YES
ECP#POOLI	DMS	3637248	99.47	19200	16	3617920	4	Large objects	Normal	YES
SAPTOOLS	DMS	3053056	99.14	25120	16	3027808	4	Large objects	Normal	YES
ECP#PROTD	DMS	851968	98.94	9056	16	842784	4	Large objects	Normal	YES
ECP#BTABI	DMS	2457600	98.81	29344	16	2428128	4	Large objects	Normal	YES
ECP#CLUD	DMS	491520	98.75	6144	16	485248	4	Large objects	Normal	YES
ECP#STABI	DMS	2424832	96.81	77280	16	2400160	4	Large objects	Normal	YES
ECP#SOURCED	DMS	458752	95.02	22848	16	435776	4	Large objects	Normal	YES
ECP#SOURCEI	DMS	458752	93.34	30528	16	428096	4	Large objects	Normal	YES
SYSTOOLSPACE	DMS	229376	92.70	16736	16	212512	4	Large objects	Normal	YES
ECP#EL702IX	DMS	98304	84.29	15424	16	82752	4	Large objects	Normal	YES
ECP#LOADD	DMS	131072	79.86	26368	16	104576	4	Large objects	Normal	YES
ECP#PROTI	DMS	131072	77.57	29376	16	101568	4	Large objects	Normal	YES
ECP#CLUI	DMS	65536	63.31	24000	16	41408	4	Large objects	Normal	YES
ECP#DDICI	DMS	1015808	63.13	374464	16	986816	4	Large objects	Normal	YES
ECP#DDICD	DMS	5439488	61.23	2108736	16	5436512	4	Large objects	Normal	YES
ECP#DOCUD	DMS	65536	51.91	31456	16	53024	4	Large objects	Normal	YES
ECP#LOADI	DMS	32768	48.53	16800	16	15840	4	Large objects	Normal	YES
ECP#DOCUI	DMS	65536	36.25	41696	16	35744	4	Large objects	Normal	YES
ECP#USER1D	DMS	32768	30.69	22624	16	10016	4	Large objects	Normal	YES
ECP#USER1I	DMS	32768	30.00	22848	16	9792	4	Large objects	Normal	YES
SAPEVENTMON	DMS	51200	28.38	36576	16	14496	4	Large objects	Normal	YES
ECP#DIMD	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#DIMI	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#EL702I	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#FACTD	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#FACTI	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#ODSD	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#ODSI	DMS	32768	25.29	24384	16	8256	4	Large objects	Normal	YES
ECP#ES702I	DMS	6651904	0.12	6643520	16	8256	4	Large objects	Normal	YES
ECP#EL702D	DMS	17334272	0.05	17325888	16	8256	4	Large objects	Normal	YES
ECP#ES702D	DMS	31391744	0.03	31383360	16	8256	4	Large objects	Normal	YES

[Former Member · Accepted solution]

Hi Dharmendra,

The error implies SNAP table is full in the SAP system and it cannot write new entries. Since you tried to perform reorganize using ST22 , I would request you to do the following

1) Check whether Transaction log is full. If yes, then either take backup of transaction log or shrink the same, you can check db2diag.log for more details.

Note : As per log if any process making the log to fill , kindly terminate it

2) Restart SAP and database.

3) Repeat the ST22 dump Re-organization process.

Hope it helps

BR Vaibhav

[Former Member]

Hi,

Reason and Prerequisites
This error means that the short dump could not be found in the database. The error may be caused by the following:
• Table SNAP is full,
• short dump was not written due to database problems,
• short dump has already been solved by reorganization.

Solution
1. Execute transaction code ST22.
2. At the initial screen, Goto -> Reorganize.

Regads,

[maria_shen]

Hello,

Normally it indicates the transaction log full issue.

As the first step, you can collect the database snapshot and application snapshot to check the log utilization status, and whether there is any long running application that holds the first active log.

Kind regards
Maria

[Former Member]

Hi,

Transactional backup is not happening on regular basis causing the File system full.

Kindly schedule the transactional backup periodically to avoid this dump.

Get in touch with DB team on this.

Regards,

Prithviraj