ABAP runtime error: snap_no_new_entry

[Former Member]

Hi All,

We got the above error.

We tried ST22 --> Go to --> Till here I can go only.....I am not able to Reorganize.

As well as I tried Reorganize again its Throw the DUMP.

Plz Suggest Other Answer.

Regards,

Rableen

[SreeniC · Accepted solution]

Hi Rableen,

Check SAP Note 17537 - ABAP/4 runtime error SNAP_NO_NEW_ENTRY.

Also check your transactional log, this error also occurs when transaction is full.

On which database are you ?

Regards,

Sreeni.

[Former Member · Accepted solution]

hi,

we are using MSSQL and in sm21 its showing the DATABASE ERROR 9002 EXE also.

[Former Member · Accepted solution]

Hi,

I am trying to do as it is giving in the sap note 17537...

But due to dump i am not able to open reorganize.

thanks,

rableen singh

[Former Member · Accepted solution]

Hello Rableen,

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.

So check if the SNAP table is full or if there is a general database problem.

maybe a connection problem to the DB,

Can you connect to the database with the command : R3trans -d

Regards,

Amit BArnawal

[former_member188883 · Accepted solution]

Hi Rableen,

ABAP runtime error: snap_no_new_entry. 

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 and it failed, 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.

2) Restart SAP and database.

3) Repeat the ST22 dump Re-organization process.

Hope this helps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Deepak,

I am new to Basis thats why I don,t know how to check for transaction log and how to truncate it....

Can you please tell me how to do this.

regards,

Rableen

[former_member188883 · Accepted solution]

Hi Rableen,

From MSSQL Enterprise manager connect to your database.

Select the database instance specific to your installation.

Check out the data files and log files definition for your SID. Right clik on the transaction log and there you can find option to shrink it.

In case your transaction log is full, you can go with the following options

1) Take transaction log backup

2) Add a new log directory using the step mentioned above.

Regards,

Deepak Kori

[Former Member]

Hi Rableen,

There could be many reasons for this dump. But I have faced this problem many time when /db2/SID/log_dir is full when archiving to TSM failed. In this case you can't even reorganize SNAP from ST22.

So I suggest you to check your MSSQL archiving status and filesystem usage.

Hope it helps.

Thanks,

Siva Kumar

Edited by: Siva Kumar Arivinti on Dec 30, 2011 11:15 AM