Ansicht
Dokumentation
03781 - SQL 502: Cursor already open
PERFORM Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
SQL 502: Cursor already open
Hi Mike,We starting received sql502 just after applying SF66039 or SF66309; sorry I'm at
teched so I can't take a look at our systems to get the exact pft
This "cursor already open" only occurs on 1 program in our environment; it is a
bdc session process.
I feel it has to do with XDA code (IBM)
We opened a pmr with IBM a couple of weeks ago; but I have not aggressively
pushed the issue.
If you open a pmr, that would be great....it will then help IBM to resolve
Doreen
-----Original Message-----
From: Mike Martin, IS-NA, AOSOLA
To: 'Gueldenpfennig, Volker'
Cc: Sap400 (E-mail)
Sent: 11/6/01 11:25 AM
Subject: RE: SQL 502: Cursor already open
Thanks for the reply, Volker, and we are on 4.5B and V4R4. The strange
this is that since we have been in the middle of a large project, we
haven't changed our environment for some time (we installed kernel patch
573 and latest DBSL 560 many months ago). We have the latest CUM and DB
group PTFs, and all applicable hipers have been applied. Our
environment has been running so smoothly (outside this one problem) that
I am reluctant to upgrade the executables.
This program runs daily and had been completing fine for some time (1.5+
years). Only the past week have we noticed this problem, fairly
consistently. At one point, I simply regenerated the program and was
able to process a BDC session on our application server without errors.
Then, when the user tried again the next day, the dumps started again.
Moreover, I have since tried regeneration without success.
I wonder if there is a way to view or manage the cursors to help trap
the error and determine the cause. Also, is there any general
information you can provide regarding cursors? I think I will open an
OSS message, however, I have had no luck recently with their level of
service. This list seems to provide answers days before OSS even reads
a message!
Thanks,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Gueldenpfennig, Volker [ mailto:volker.gueldenpfennigZs...
<mailto:volker.gueldenpfennigZs...> ]
Sent: Tuesday, November 06, 2001 12:09 AM
To: 'MMartinZa...'
Cc: Sap400 (E-mail)
Subject: RE: SQL 502: Cursor already open
Hello Mike,
I don't know your release, but as of 4.5A the kernel and the DBSL
(database
system layer) are to be patched seperately. So you have to install the
patch
for KERNEL and for LIB_DBSL. You should go to the latest patches and
retry.
It's really interesting, that it work s 2-tier and fails 3-tier. The
name of
the cursor is created in the DBSL and is "quite normal". When the
SQL0502
occurs, either the DBSL made an error or the DB2/400 made an error. That
is
mostly hard to detect. As your problem seems to be reproducible
(hopefully
not only after hours or days running!), you should open an OSS ticket
when
it still persists with the latest pateches on the SAP site and the PTFs
on
the IBM site. Then we would have to analyze whether realy 2 cursors of
this
name were opened within the same commit boundary or they if they were
opened
with "with hold" in order to survive a commit (=> SAP error) or if this
was
not the case (=>IBM-error).
Regards
Volker
Durban Tours - Südafrika Safari
ABAP Short Reference CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 4415 Date: 20240425 Time: 001537 sap01-206 ( 4 ms )
