SQL error "-601" occurred when accessing table "SMEN_BUFFC

[Former Member]

Hi Guys

I am getting the above error at tiem when i am logging on.

The actual error message in the st22 dump is

Database error text........: "SMEN_BUFH5 in R3EPT32000 type *SQLPKG already

exists. Job=018343/EPT01/WP00"

The termination occurred in the ABAP/4 program "SAPLSMTR_NAVIGATION_MODULES "

in

"SMTR_STRU_PROCESS_STRUCTURE".

The main program was "SAPLSMTR_NAVIGATION ".

This seems to happen when some users log on to the system and then tries to change their password. If I stop sap and start it again, the rror goes away.

I have actually deleted the sql package with the command

DLTSQLPKG R3EPT32000\SMEN_BUFH5.

This seem to work but after a while the erro comes back again

[christian_bartels]

This is most likely the problem that is described in SAP Note 1027476. If you are at 7.00, a patch is already available. If you are at an older release, you can temporarily work around that problem by commenting out the entry for DLTOLDPKGS in the start profile.

Kind regards, Christian Bartels.

[Former Member]

dear all,

we have a 4.6c version and we get same error:

SQL error "-601" occurred when accessing table "SMEN_BUFFC

Do you have any hint? It seems it started to occur without a clear reason.

Thanks,

ciao

Giuseppe

[christian_bartels]

The theory is the same for all cases: For some reasons SQL packages are deleted even though they are still in use by an active SAP instance.

There were a couple of cases where DLTOLDPKGS would delete more packages than it should - SAP Note 894442 explains another case. The difficulty is, that in some cases the DLTOLPKPGS could belong to another SAP system than the one that is seeing the SQL error -601, so it is not enough to patch just that one, but you need to patch all programs in all kernel libraries on that system (in that partition).

If in doubt, you can use audit journaling (system value QAUDLVL *DELETE) to find out who is deleting the SQL package that later causes problems.

Kind regards,

Christian Bartels.

[Former Member]

Dear Christian,

at the moment in our Productive system we have hundreds of Dumps: nearly at every log on user get a DUMP with the well known message.

Analyzing develoepr trace we find following information:

C Wed Mar 14 09:54:35 2007

C Concurrent prepare happened for SIPID

C Library name: R3S1132000

C Package name: SMEN_BUFH5

C Statement name: "QL1YQAAAAAFC"

C SQL Error: -601

C *** ERROR => Error -601 in function prep_cached_op [dbsldb4.cpp 7057]

C Library name: R3S1132000

C Package name: SMEN_BUFH5

C Statement name: "QL1YQAAAAAFC"

C Failing statement is:

C , SELECT * FROM R3S11DATA/"SMEN_BUFFC" WHERE "MANDT" = ? AND "UNAME" = ? WITH UR

B ***LOG BY4=> sql error -601 performing PRE on table SMEN_BUFFC [dbtran 7009 ]

B ***LOG BY0=> SMEN_BUFH5 in R3S1132000 tipo *SQLPKG esiste gi{. Job=251690/S1100/WP12 [dbtran 7009 ]

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'

B FHDR: {tab='SMEN_BUFFC ',

fcode=53, mode=2, bpb=0, dbcnt=0, crsr=1,

B hold=0, keep=1, xfer=2, pkg=0, upto=0, init:b=0,

B init:p=0000000000000000, init:#=278, wa:p=0000000000000000, wa:#=278}

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'

B STMT:

B CRSR: {tab='SMEN_BUFFC ', id=-1, hold=0, prop=0x10000, max.in@0=1, fae:blk=10,

B con:nm='R/3', con:id=0, con:vndr=2, val=2,

B key:1=0, key:#=6, xfer=2, xin:#=0, xout:#=0, upto=0,

B wa:p=000000800440C380, init:p=00000090D4CF4DF8, init:#=15, init:b=0}

Additionaly we also tried to delete only mentioned SQL package (while system was running), but without succes.

What do you think?

Giuseppe

[christian_bartels]

Deleting an SQL package while the system is up and running will make things worse. You can try to work around the problem by stopping the system, delete all SAP packages for that system, and restarting it.

Kind regards,

Christian Bartels.

[Former Member]

Dear all,

good solution (suggested by OSS - SAP) was to:

- comment in the start profile of the SAP system:

"Start_Program_01 = host $(DIR_EXECUTABLE)/DLTOLDPKGS SYS

- restart the system.

Reason of error is still not clear. But at least with mentioned solution we didn't get additional dumps. Any idea ?

ciao

Giuseppe

[Former Member]

Hello Morga,

From your other postings, the system were just installed. Are the PTF level (CumPack, DB group fix, etc) and SAP kernel level (DW, LIB_DBSL, etc) current?

The installation guide and relevant notes contain the recommendation for configurations of SAP and i5/OS.

If everything looks ok, open an OSS message?

Best regards,

Victor