on 12-04-2007 10:19 PM
Hi Guys,
We have many dumps when run a program in our system R/3 4.6C over V5R3M0.
The many dumps is:
DBIF_RSQL_SQL_ERROR
SQL error "-904" occurred when accessing table "A073 ".
OSS SAP say that i have to delete SQLPKG when the error appear.
I execute this deletion all weekend with DLTR3PKG; but the packages overflow quickly and i can close the system only the sunday.
Any suggestions? i try delete the A073 SQLPKG with the command:
WRKOBJ OBJ(ALL/A073) OBJTYPE(SQLPKG) on-line the last week; and we have many errors after this delete (all process with access to this table not run).
I increase the SQLPKG´s size to 1 GB (note 306823), but the problem persist.
Best Regards,
Ernesto Castro.
Hi,
I also facing the similar kind of issue can some one please help me out. please look at the below runtime errors i am getting when trying to delete the user thru Su01 transaction.
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 19.02.2008 01:01:42
Short text
SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
Program SAPLSUU1
Include LSUU1U09
Row 1
Module type (FUNCTION)
Module Name SUSR_USER_BUFFERS_TO_DB
Trigger Location of Exception
Program SAPLSUU1
Include LSUU1U09
Row 249
Module type (FUNCTION)
Module Name SUSR_USER_BUFFERS_TO_DB
Source Code Extract
Line SourceCde
219 CALL FUNCTION 'RSAU_WRITE_USER_AUDIT_LOG'
220 EXPORTING
221 userid = usrxx_delete-bname
222 deleted = 'X'
223 EXCEPTIONS
224 parameter_error = 0
225 OTHERS = 0.
226 ENDLOOP.
227 ENDIF.
228
229 DELETE usr21 FROM TABLE usrxx_delete.
230 DELETE usr07 FROM TABLE usrxx_delete.
231 DELETE usr30 FROM TABLE usrxx_delete.
232 DELETE usrefus FROM TABLE usrxx_delete.
233 DELETE usrbf3 FROM TABLE usrxx_delete.
234
235 * Tabellen mit längerem Schlüssel als mandant und bname
236 LOOP AT usrxx_delete.
237 DELETE FROM usrbf2 WHERE bname = usrxx_delete-bname.
238 DELETE FROM usr05 WHERE bname = usrxx_delete-bname.
239 DELETE FROM usr08 WHERE bname = usrxx_delete-bname.
240 DELETE FROM usr09 WHERE bname = usrxx_delete-bname.
241 DELETE FROM usgrp_user
242 WHERE bname = usrxx_delete-bname. "note 0210496
243 DELETE FROM usracl WHERE bname = usrxx_delete-bname.
244 * Einträge für Matchcode-objekte löschen.
245 DELETE FROM mcdefid WHERE syuser = usrxx_delete-bname.
246 ENDLOOP.
247
248 LOOP AT usrxx_delete.
>>>>> DELETE FROM ususer_sys
250 WHERE reluser = usrxx_delete-bname AND
251 reltype_u = c_typ_user. " note 309535
252
253 DELETE FROM ususer_agr
254 WHERE reluser = usrxx_delete-bname AND
255 reltype_u = c_typ_user. " note 309535
250 WHERE reluser = usrxx_delete-bname AND
251 reltype_u = c_typ_user. " note 309535
252
253 DELETE FROM ususer_agr
254 WHERE reluser = usrxx_delete-bname AND
255 reltype_u = c_typ_user. " note 309535
256
257 *<<< 542675
258 DELETE FROM usgrp_user
259 WHERE BNAME = usrxx_delete-bname.
260 *>>> 542675
261
262 DELETE FROM usapplref WHERE bname = usrxx_delete-bname.
263
264 *...Zuordnung HR löschen
265 * -> No application calls during upgrade
266 DATA ev_shadow LIKE gsugi_pa-w_istatus.
267 CALL FUNCTION 'UPG_IS_SHADOW_SYSTEM'
268 IMPORTING
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Emesto and Deli,
Both of you facing same type of problem..This problem is very simple..in your database library R3<SID>DATA some object(*FILE) is missing or file partially restored.
Kindly check and restore properly.
First please check with dev_w0 log..In that log may have the package name or file name or table name if you found any please restore in particular object...Both of your problem will solve 100%.
Before starting SAP instance pls delete SQLPKG.
Thanks
Jibin.
Edited by: jibin singh on Feb 19, 2008 11:39 AM
Hi Ernesto Castro,
We also getting the same type of dump for MARA and MARC table.
Could you please provide the solution/which commands to be run?
ategory | Installation Errors |
untime Errors | DBIF_RSQL_SQL_ERROR |
xcept. | CX_SY_OPEN_SQL_DB |
ate and Time | 10/21/2013 07:14:59 |
Short text
SQL error "-904" when accessing table "MARC". |
What happened?
Error Text of the Database: "Resource limit exceeded. MSGID= | |
Job=261609/ECQADM/WP02" Regards, Sudarshan |
Hello Sudarshan,
the problem is well described in this SAP note:
Note 54028 - IBM i: SQL0 904 reason code 7, overflow in SQL package
Solution: SQL Packages have to be deleted -> this can only be done when the system is stopped
.
“If the overflow occurs because many similar SQL statements exist for a table in an SQL package,
you may be able to use the Auto SingleExecution for Package Overflow procedure described in Note 1109573 to solve the problem“:
Note 1109573 - DB4: Auto SingleExecution for Package Overflow
Also please let your developers check self-programmed transactions (if this is the case):
(from note 1109573) “Solutions to the SQL0904 for Release 640+:
Note: We intentionally decided not provide the 46D automatic overflow mechanism in 640+ due to the fact that package overflow errors often indicate a software design issue, or a database error; neither of which we want to inadvertently mask.”
Just last week I had a similar case where only ONE table was affected:
In addition, as only one table (LTAP) is affected
I have created this instance profile parameter that will become active after the system restart as well:
dbs/db4/dbsl_tablehint0 = Table = 'LTAP' & NoSTMTID = true ? PackageDispersion = 3
(see SAP note 1536572 for details)
Hope this helps,
Rüdiger
Greetings,
After identifying the ABAP code as Volker suggested, an alternative to "rewriting" the ABAP code significantly would be to use the SINGLE_EXECUTION hint described in note 485420.
If you are encountering a new error based on existing ABAP code, there may be a problem in the packaging handling of the database. If you suspect this may be the case, please open an OSS ticket. After analysis, we may suggest that you also open a PMR with IBM.
By the way, another alternative for 6.40+ users is to use the conditional hint mechanism described in note 1109771. With this technique it wouldn't be necessary to modify ABAP code at all.
... Eric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eresto,
in my eyes, you have to fix the root cause:
You are having programs written - most likely yourself - that do access this table in a way where millions of different SQLs are generated.
You should hunt for these programs and modify them. I know, it might be a bit complicated - but that is the only true solution ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
your problem is solved only by deleting SQLPKG,
<b>don't perform this operatation online</b>, you need to shutdown the sap server and delete SQLPKG and restart SAP Server solve your problem,
also look at note 306823 to increase SQLPKG Size to 1 GB,
regards,
kaushal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.