Error SNAP_NO_NEW_ENTRY or DBIF_RSQL_SQL_ERROR

Hi,
I get Error SNAP_NO_NEW_ENTRY or DBIF_RSQL_SQL_ERROR.
Need help
Points willl be rewarded.
Thanks
Vinayak

Hi
I would guess that your transaction log is full.
SNAP table is used to store shortdumps and this error means the table cannot be written to.
N.P.C

Similar Messages

ABAP runtime errors SNAP_NO_NEW_ENTRY

The following errors occured just after login, can anyone tell me how to handle it?
ABAP runtime errors SNAP_NO_NEW_ENTRY
Occurred on 0000.00.00 at 13:47:44
Runtime error: Unable to write short dump.
What happened?
The current ABAP/4 program " " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Unfortunately, the original cause of the error cannot be determined
because there is no suitable short dump in the table SNAP (which
records information about the point of termination).
termination).
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
Error analysis
Unfortunately, the original cause of the error cannot be
determined, since there is no suitable short dump in table SNAP.
The table SNAP probably already contains a number of short dumps
and cannot accept any more. Please check the situation using the
system log.
The table SNAP contains all the short dumps for the last 7 days.
How to correct the error
Check the system log for each cause of error.
More space probably needs to be provided for table SNAP
using database means.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:

补充两句：
1. SNAP表的Reorganization应该在后台通过定期的（每天）job执行，参看Note 16083。
2. 如果登录系统即发生Dump，怀疑是否SNAP的table space是导致这个Dump的原因，考虑可能有其它致命错误。如果登录后还可以执行transaction，尝试执行SM21，DB02检查。

ABAP runtime error: snap_no_new_entry

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

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

ABAP/4 runtime error SNAP_NO_NEW_ENTRY

Hi All,
I am unable to login in to my SAP server, after entering user id and password, the below ABAP Dump is displayed
ABAP/4 runtime error SNAP_NO_NEW_ENTRY
I have checked the SAP notes, but no luck
Please advise
SAPXPT

Hello,
SAP note 17537 describes the following :
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.
Probably it is the last one, maybe a connection problem to the DB, archiver stuck, ...
Can you still connect to the database with the command : R3trans -d
Merry Christmas,
Wim Van den Wyngaert

SNAP_NO_NEW_ENTRY Error

Hi, i have a report wich launches a batch-input process.
The thing is that i've got this SNAP_NO_NEW_ENTRY dump, when i run this report in background.
I've got no idea why the program is reporting this dump, and i have no idea what's the meaning of it.
Thanks in advance.

My first instinct would be to check whether your abend log data table, SNAP, is full -> there are some other SDN postings on this topic too e.g.
Re: Error SNAP_NO_NEW_ENTRY or DBIF_RSQL_SQL_ERROR
Basis can empty data from this table (which is referenced by ST22) - I think they use RSNAPREO but check with your team first. Google has some other references as well.

Error DBIF_RSQL_SQL_ERROR and DBIF_REPO_SQL_ERROR while running DTP

Hi to all,
I am loading the data from PSA to DSO, while running DTP, after some records load a run time error coming DBIF_RSQL_SQL_ERROR or DBIF_REPO_SQL_ERROR .
Also i tried the Number of Processes reduce from 3 to 1 in DTP, but still same error .
i have searched the SDN and found that it is due to table space problem.
if it is due to table space , how i will find it and how to correct it.
Please can any one tell we why it is coming and what is the solution for that.
i shall be thankful to you for this.
Regards
Pavneet Rana

Thanks for reply,
i have checked ST22 . and found the error text for 2 runtime error .
first for DBIF_RSQL_SQL_ERROR
second for DBIF_REPO_SQL_ERROR
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 14.03.2011 22:00:21
Short text
 SQL error in the database when accessing a table.
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrator
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
How to correct the error
 Database error text........: "SQL30081N A communication error has been
 detected. Communication protocol being used: "TCP/IP". Communication API being
 used: "SOCKETS". Location where the error was detected: "200.1.1.66".
 Communication function detecting the error: "recv". Protoco"
 Internal call code.........: "[RSQL/FTCH/RSBMONMESS ]"
 Please check the entries in the system log (Transaction SM21).
 If the error occures in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
 "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
 "CL_RSBM_LOG_REQUEST_ROOT======CP" or "CL_RSBM_LOG_REQUEST_ROOT======CM00F"
 "GET_STATIC_BUFFER"
 If you cannot solve the problem yourself and want to send an error
 notification to SAP, include the following information:
 1. The description of the current problem (short dump)
 To save the description, choose "System->List->Save->Local File
 (Unconverted)".
 2. Corresponding system log
 Display the system log by calling transaction SM21.
 Restrict the time interval to 10 minutes before and five minutes
 after the short dump. Then choose "System->List->Save->Local File
 (Unconverted)".
 3. If the problem occurs in a problem of your own or a modified SAP
 program: The source code of the program
 In the editor, choose "Utilities->More
 Utilities->Upload/Download->Download".
 4. Details about the conditions under which the error occurred or which
 actions and input led to the error.
 The exception must either be prevented, caught within proedure
 "GET_STATIC_BUFFER" "(METHOD)", or its possible occurrence must be declared in
 the
 RAISING clause of the procedure.
 To prevent the exception, note the following:
Information on where terminated
 Termination occurred in the ABAP program "CL_RSBM_LOG_REQUEST_ROOT======CP" -
 in "GET_STATIC_BUFFER".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 29
 of the (Include) program "CL_RSBM_LOG_REQUEST_ROOT======CM00F".
 The program "CL_RSBM_LOG_REQUEST_ROOT======CP" was started as a background job.
 Job Name....... "BIDTPR_2256_1"
 Job Initiator.. " a"
 Job Number..... 18254200
 The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
 procedure "GET_STATIC_BUFFER" "(METHOD)", but it was neither handled locally
 nor declared
 in the RAISING clause of its signature.
 The procedure is in program "CL_RSBM_LOG_REQUEST_ROOT======CP "; its source
 code begins in line
 1 of the (Include program "CL_RSBM_LOG_REQUEST_ROOT======CM00F ".
Source Code Extract
Line SourceCde
 1 method get_static_buffer.
 2 data l_s_storage type rsbm_s_storage.
 3 l_s_storage = get_s_storage( ).
 4 check l_s_storage-type = rsbm_c_storagetype-database..
 5 delete o_th_nodes_static where logid = n_logid.
 6 delete o_t_msg_static where logid = n_logid.
 7 delete o_t_logpar_static where logid = n_logid.
 8 select *
 9 from rsbmnodes connection (l_s_storage-id)
 10 appending corresponding fields of table o_th_nodes_static
 11 where logid = n_logid.
 12
 13 data l_count_monmess type sytabix.
 14 select count( * ) from rsbmonmess
 15 into l_count_monmess
 16 where logid = n_logid.
 17 if l_count_monmess > 50000.
 18 select * from rsbmonmess up to 50000 rows connection (l_s
 19 appending corresponding fields of table o_t_msg_static
 20 where logid = n_logid
 21 and posit < 50
 22 order by node posit.
 23 else.
 24 select * from rsbmonmess connection (l_s_storage-id)
 25 appending corresponding fields of table o_t_msg_static
 26 where logid = n_logid
 27 order by node posit.
 28 endif.
>>>>> select * from rsbmlogpar
 30 appending corresponding fields of table o_t_logpar_static
 31 where logid = n_logid.
 32 field-symbols: <l_s_nodes> type rsbmnodes,
 33 <l_s_log> type s_log.
 34 read table o_th_log assigning <l_s_log>
 35 with table key logid = n_logid.
 36 if sy-subrc <> 0.
 37 break hoeferf. "
 38 endif.
 39 loop at o_th_nodes_static assigning <l_s_nodes>.
 40 if <l_s_nodes>-node > <l_s_log>-maxnode.
 41 <l_s_log>-maxnode = <l_s_nodes>-node.
 42 endif.
43 endloop.
44 * --- set datapackage buffer
45 cl_rsbk_dp_state=>free_buffer( n_requid ).
46 cl_rsbk_dp_state=>fill_buffer( n_requid ).
47 endmethod.
Runtime Errors DBIF_REPO_SQL_ERROR
Date and Time 14.03.2011 15:34:32
Short text
 SQL error "-99999" occurred when accessing program
What can you do?
 Note which actions and input led to the error.
 For further help in handling the problem, contact your SAP administrato
 You can use the ABAP dump analysis transaction ST22 to view and manage
 termination messages, in particular for long term reference.
How to correct the error
 Database error text........: "CLI0108E Communication link failure.
 SQLSTATE=40003"
 Triggering SQL statement...: "CX_SY_NATIVE_SQL_ERROR========CP "
 Internal call code.........: "[REPO/*/43/LOAD/CX_SY_NATIVE_SQL_ERROR===
 Please check the entries in the system log (Transaction SM21).
 If the error occures in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
 "DBIF_REPO_SQL_ERROR" " "
 "SAPLSYDB" or "LSYDBU27"
 "DB_COMMIT"
 If you cannot solve the problem yourself and want to send an error
 notification to SAP, include the following information:
 1. The description of the current problem (short dump)
 To save the description, choose "System->List->Save->Local File
 (Unconverted)".
 2. Corresponding system log
 Display the system log by calling transaction SM21.
 Restrict the time interval to 10 minutes before and five minutes
 after the short dump. Then choose "System->List->Save->Local File
 (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
 In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
 Termination occurred in the ABAP program "SAPLSYDB" - in "DB_COMMIT".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 7
 of the (Include) program "LSYDBU27".
 The program "SAPLSYDB" was started as a background job.
 Job Name....... "BIDTPR_2252_1"
 Job Initiator.. "A"
 Job Number..... 12541100
Source Code Extract
Line SourceCde
 1 FUNCTION DB_COMMIT.
 2 *"----------------------------------------------------------------------
 3 *"*"Lokale Schnittstelle:
 4 *"----------------------------------------------------------------------
 5
 6 EXEC SQL.
>>>>> COMMIT WORK
 8 ENDEXEC.
 9
 10 ENDFUNCTION
please can any one tell me cause for runtime error.
i shall be thankful to you for this.
regards
pavneet rana
Edited by: pavneet rana on Mar 15, 2011 1:29 PM

Backup to remote stage failed due to RFC error

Hello!
Recently I have problem to execute a successful online Backup to the external source.
If I start backup from DB13 and analyse the work processes (Tcode SM50) I found the following:
The responsible BGD-WP:
status: On hold , reason: RFC, report: SAPLSSXP
The dev_w8 trace retrieves the following error:
Source RSCROSS10 Line 112.
Error Code DBIF_RSQL_SQL_ERROR.
Module $Id: //bas/700_REL/src/krn/runt/absapsql.c#6 $ SAP.
Function HandleRsqlErrors Line 761.
The DB13-protocol retrieves the following information:
BR0278E Command output of 'F:\usr\sap\DEV\SYS\exe\uc\NTAMD64\sapftp.exe -v -n -i 192.168.200.3 -u H:\oracle\DEV\sapbackup\.bdwkhbgq.ftp -b -c put E:\ORACLE\DEV\SAPDATA1\SR3_3\SR3.DATA3 /sap/DEVB/bdwkhbgq/SR3.DATA3':
Connected to 192.168.200.3 Port 21.
220-FTP server ready. 220 This is a private system - No anonymous login 331 User sapbackup OK. Password required 230-User sapbackup has group access to: administrator 230-This server supports FXP transfers 230-OK. Current restricted directory is / 230-************************************************ 230-* Use SITE command to change client codepage: * 230-* ie, site codepage [client codepage] * 230 ************************************************ 200 TYPE is now 8-bit binary 200 PORT command successful 150 Connecting to port 2734 NiWrite error: -6, bytes to send: 32767 bytes written: 0
BR0280I BRBACKUP time stamp: 2007-10-20 03.08.23
BR0279E Return code from 'F:\usr\sap\DEV\SYS\exe\uc\NTAMD64\sapftp.exe -v -n -i 192.168.200.3 -u H:\oracle\DEV\sapbackup\.bdwkhbgq.ftp -b -c put E:\ORACLE\DEV\SAPDATA1\SR3_3\SR3.DATA3 /sap/DEVB/bdwkhbgq/SR3.DATA3': 1
BR0222E Copying E:\ORACLE\DEV\SAPDATA1\SR3_3\SR3.DATA3 to/from /sap/DEVB/bdwkhbgq/SR3.DATA3 failed due to previous errors.
Can some one help me with this issue?
Thank you very much!
regards
Thom

Hello Eric,
unfortunately it is not possible to do it, because I have only remote access to the SAP system.
Is it possible to analyse the problem with the log files?
If yes --> which logs should I post here?
I went through the monitors in RZ20 and found a lot of errors/warning:
Database:
DBIF_SETG_SQL_ERROR
ORA-03106: fatal two-task communication protocol error
DB error 24909 in FET
SQL error 3106: WP in reconnect status
Background:
Job SAP_COLLECT_FOR_PERMONITOR terminated
Utilisation:
100% > 95% Background work process load exceeds threshold
BackgroundService: SystemWideFree BPWP: 1 WPs > 2 WPs Current value over threshold value.
Abap ErrorInUpdate
Syslog : BasisSystem
Operating system call recv failed (error no. & >E5)
The log file dev_cp retrieves the following information after execution of DB Check:
Trace file of control program (trace level 3)
< Function: BtcTrcInit> Function: main SAPXPG 700
2007-10-23--14-42-27 : Before BtcXpgDetach
> Function: BtcXpgDetach < Function: BtcXpgDetach Accept RFC connection from R/3 system
2007-10-23--14-42-27 : Before RfcAccept
2007-10-23--14-42-27 : RfcAccept returned OK
security check switched OFF
Install RFC call SAPXPG_START_XPG
Install RFC call SAPXPG_START_XPG_LONG
Install RFC call SAPXPG_END_XPG
Wait for RFC call SAPXPG_START_XPG or SAPXPG_START_XPG_LONG
2007-10-23--14-42-27 : Before first call of RFCDispatch
> Function: BtcXpgStartXpgLong
2007-10-23--14-42-27 : Beginning of BtcXpgStartXpgLong
> Function: BtcXpgStartXpgImportLong > Function: BtcXpgParam < Function: BtcXpgParam > Function: BtcXpgParam
Line Text
<No StdOut/StdErr output reported>
Target log table is not identical to source
ItGetLine terminated with NULL
<Function: BtcXpgItTransfer > Function: BtcTrcReset < Function: BtcTrcReset Call mode: VIA RF
Input arguments of BtcXpgStartXpg:
My WP settings are:
rdsip/wp_no_dia = 6
rdsip/wp_no_btc = 3
rdsip/wp_no_vb = 1
rdsip/wp_no_vb2 = 1
rdsip/wp_no_spo = 1
Thank you!
Thom

ABAP runtime errors    SNAP_NO_NEW_ENTR

The following errors occured just after login, can anyone tell me how to handle it?
ABAP runtime errors    SNAP_NO_NEW_ENTRY
       Occurred on     0000.00.00 at 13:47:44
Runtime error: Unable to write short dump.
What happened?
The current ABAP/4 program " " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Unfortunately, the original cause of the error cannot be determined
because there is no suitable short dump in the table SNAP (which
records information about the point of termination).
termination).
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
Error analysis
Unfortunately, the original cause of the error cannot be
determined, since there is no suitable short dump in table SNAP.
The table SNAP probably already contains a number of short dumps
and cannot accept any more. Please check the situation using the
system log.
The table SNAP contains all the short dumps for the last 7 days.
How to correct the error
Check the system log for each cause of error.
More space probably needs to be provided for table SNAP
using database means.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:

hello,
Check these:
Note 495297 - DB6: Monitoring transaction log
Re: Question. usage of transaction log
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f03d5fb8-b619-2b10-c383-c6d56872829e&overridelayout=true
Ideally, db2diag.log should tell you this information.
Hope it helps.
thanks,
Prasanna

Bw problem/error when trying to load data

hi experts i suddenly have this issue when trying to load data anywhere in my bw system (psa,ods,infocubes) i get the following abap runtime error:
SNAP_NO_NEW_ENTRY
runntime error,short dump could not be written
and bellow that it generally says that SNAP is full and i need to create more free space
any suggestions what i should do?
ps.i ve tried the re-organize option and no luck, i need to take more drastic measures
thanks

check the below thread...
[SNAP_NO_NEW_ENTRY;

Update terminated, DBIF_RSQL_SQL_ERROR

Dear all,
      Updatation terminated and error generated was DBIF_RSQL_SQL_ERROR. The details are:
Details
Recording at local and central time........................ 02.10.2006 10:21:13
Task................ 04452 / V1 Update Task No. 10
Transaction code....
Program name........ RSM13000
Problem class....... K    SAP Web AS Problem
Development class... SBAC
Module name......... dbtran
Line................ 7275
SQL function........ SEL
Table name.......... MDVL
SQL code............ 0
Technical details
File................ 000005
Position............ 0000263520
Entry type.......... g      ( Database SQL Error             )
Message ID.......... BY 4
Variable parts...... 0     SELMDVL                                       dbtran 7275
Pls help me to solve this problem. Thanks in advance.
rgds....
Art

Dear Art,
Please check sql server log.
Regards
Matt

Inbound-Queue SYSFAIL: SQL error in the database when accessing a table

Hi,
we send around 80 IDoc simultaneously, there 15 are stuck.
They all have SYSFAIL in SMQ2 with message: SQL error in the database when accessing a table
I already unlocked the queues and try to resend. Nothing happend!
I ran RSQIWKEX for the single queus but now there are new queues in Status SYSFAIL.
I already checked some entries in forum and blogs, but nothing worked out yet!
Can someone help?! it's urgent!!
br

Hi, well as mentioned i searched and found this already.
But in ST22 i got error concerning
Laufzeitfehler DBIF_RSQL_SQL_ERROR
Ausnahme CX_SY_OPEN_SQL_DB
So i guess it's something more serious.
Any more ideas?!
Can i simply delete the stucked queues and reporcess them?!
br

RSBKCHECKBUFFER job scheduled twice and both canceling suddenly with two er

Hello,
This job RSBKCHECKBUFFER is scheduled to run two times in production system starting at same time 12:00 pm and it was running fine till 12.04.11 but both the jobs started failing suddenly since 12.05.11 with two different sql errors at times
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
1. Database error text........: "SQL1224N The database manager is not able to
accept new requests, has terminated all requests in progress, or has
terminated the specified request because of an error or a forced interrupt.
SQLSTATE=55032 row=1"
2. Database error text........: "SQL0911N The current transaction has been rolled
back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1"
Also both the job is scheduled to run with two different parameters
Parameters
&0000000000001
&0000000000000
Can anyone let me know what could be the reason of sudden failure since 12.05.11.
Also if I schedule the job to run only once in the system will it solve the problem ?

Hello Shradha,
1. Database error text........: "SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt.
SQLSTATE=55032 row=1"
- As far as I know this is serious problem in production environment. Looks like your DB was being restarted at that time. Please have your DBA team to review db2diag.log for error details.
2. Database error text........: "SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001 row=1" .
- Looks like second job was overlapped with first one. Please try to run the job once in a day or change of schedule of both jobs to ensure no overlap.
Thanks,
Siva Kumar

Loads using DTP - manual update possible?

Hi,
I have a question regarding loads done using DTP in BW 7.0.
In 3.X loads using infopackages, sometimes a data package will get runtime errors such as DBIF_RSQL_SQL_ERROR (deadlocks). Usually, we would change the status to red and do a manual update of the affected data package in the data load monitor.
However, I cannot find this option for DTP and I have to reload the whole request even only 1 data package has failed because of the SQL error. Does anyone know how to repair this in a DTP load?
Any help will be appreciated, thanks in advance!

Hi CK,
Not found a way of doing this at current but I know where you are coming from, you're thinking of the old set manual status or even try a sm58 and trigger the idocs. If a DTP fails you might have the option of using the error stack but only if this has been configured. A failed load will prompt you to do this. Other ways of trying to fix the SQL errors are to check what the SQL problems are, most of our problems have been tablespace issues, etc.
Daily monitoring by basis/bw admin should sort these.
Cheers,
Pom

Solution Manager having serious issue

Hello All,
When I am trying to log on to my SolMan system it is giving me an error called Runtime error:
SNAP_NO_NEW_ENTRY.
Due to this I am not able to run any t-code.Not even I can run st22.In the error analysis it is saying that Table SNAP already contains so many short dumps that it cannot take on any more.My database is SQL server 2005 & os win 2003.
I also found that the transaction log directory is almost full. I have tried to folllow note 1224089 to shrink the logfiles.
But failed to do so. I have tried to shrink using windows authentictaion but nothing happened. But in the note mentioned
Connect to the server (use user 'SA' and Password where the file to be shrunk is located).
What is the password of user SA ???
Please guide me.
Regards,
Partha

I guess you are looking right note for SQL transaction log shrink.
You might be aware that this occurs if you leaves the databases in full recovery mode.
As you have asked
What is the password of user SA ???
This is what you specify at the time of SQL Database installation when selecting "Authentication Mode"
Check SAP installation docu. for SQL db , at this stage it says
Select Mixed Mode (Windows Authentication and SQL Server Authentication).
This mode is required for a Java or ABAPJava system.+
If you choose this mode, you have to set the password for the sa login.
Possibility of setting this password same as master password for may cases....
try logging in using this ID as per note and follow the same to shrink ....
Check Note [37916|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=37916] for more details on SA password policy ...
Just in case if you have forgot the password... Follow Note 864220
Better not to go for 2nd option... Deletion of transaction log. As per this [Link|http://support.microsoft.com/kb/873235]
Microsoft Suggest: The transaction logs are very important to maintain the transactional integrity of the database. Therefore, you must not delete the transaction log files even after you make a backup of your database and the transaction logs.
Lets us know your progress.

ALV with pushbutton

Hi all,
When I create a ALV output with grid(using REUSE_ALV_GRID_DISPLAY), during output display I want a pushbutton to be displayed BEFORE each row.The row should not be editable.When I select the button, the whole row should be selected.
What extra code should I add in my program?
Thanks,
Shivaa......

hi Vijay,
I have added the code as you suggested.Isee the output as I wanted.But, when I click 'BACK' pushbutton,
I get following runtime error--> SNAP_NO_NEW_ENTRY...
I am enclosing the code here..Let me know if I have done any mistake.
REPORT ZALV.
initialization.
tables: lfa1.
type-pools: slis.
data: itab like lfa1 occurs 3,
 fcat type slis_t_fieldcat_alv,
 layo type slis_layout_alv,
 pnam type sy-repid.
layo-colwidth_optimize = 'X'.
layo-zebra = 'X'.
layo-detail_popup = 'X'.
layo-box_fieldname = 'BOX_FIELD'.
start-of-selection.
pnam = sy-repid.
select * up to 20 rows from lfa1 into table itab.
perform calcat.
perform gridout.
form calcat.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
 I_PROGRAM_NAME = pnam
 I_INTERNAL_TABNAME = 'ITAB'
 I_STRUCTURE_NAME =
 I_CLIENT_NEVER_DISPLAY = 'X'
 I_INCLNAME = pnam
 I_BYPASSING_BUFFER =
 I_BUFFER_ACTIVE =
 CHANGING
 CT_FIELDCAT = fcat
EXCEPTIONS
 INCONSISTENT_INTERFACE = 1
 PROGRAM_ERROR = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.
form gridout.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 I_INTERFACE_CHECK = ' '
 I_BYPASSING_BUFFER = ' '
 I_BUFFER_ACTIVE = ' '
 I_CALLBACK_PROGRAM = pnam
 I_CALLBACK_PF_STATUS_SET = ' '
 I_CALLBACK_USER_COMMAND = ' '
 I_CALLBACK_TOP_OF_PAGE = ' '
 I_CALLBACK_HTML_TOP_OF_PAGE = ' '
 I_CALLBACK_HTML_END_OF_LIST = ' '
 I_STRUCTURE_NAME =
 I_BACKGROUND_ID = ' '
 I_GRID_TITLE = 'Vendor Master Information'
 I_GRID_SETTINGS =
 IS_LAYOUT = layo
 IT_FIELDCAT = fcat
 IT_EXCLUDING =
 IT_SPECIAL_GROUPS =
 IT_SORT =
 IT_FILTER =
 IS_SEL_HIDE =
 I_DEFAULT = 'X'
 I_SAVE = ' '
 IS_VARIANT =
 IT_EVENTS =
 IT_EVENT_EXIT =
 IS_PRINT =
 IS_REPREP_ID =
 I_SCREEN_START_COLUMN = 0
 I_SCREEN_START_LINE = 0
 I_SCREEN_END_COLUMN = 0
 I_SCREEN_END_LINE = 0
 IT_ALV_GRAPHICS =
 IT_HYPERLINK =
 IT_ADD_FIELDCAT =
 IT_EXCEPT_QINFO =
 I_HTML_HEIGHT_TOP =
 I_HTML_HEIGHT_END =
IMPORTING
 E_EXIT_CAUSED_BY_CALLER =
 ES_EXIT_CAUSED_BY_USER =
 TABLES
 T_OUTTAB = itab
EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Error SNAP_NO_NEW_ENTRY or DBIF_RSQL_SQL_ERROR

Similar Messages

Maybe you are looking for