Database selection invalid cursor

[Former Member]

Hi

We are loading data in BW using DBConnect and on each infopackage we are getting the following warning in SM21

'Database selection invalid cursor'.

I have raised this with SAP Support and they have stated that it is just a warning and should be ignored. However it occurs every 10mins in our system and fills up the Analysis logs, does anyone have any advice on whether we can supress this warning in SM21 so the logs don't fill so quickly or give some advice on how we can fix the problem.

Thanks in advance.

[Former Member · Accepted solution]

Hi Lorraine,

This problem mostly occurs between select - endselect statements. Could you check the note 401847 - DBIF_RSQL_INVALID_CURSOR during extraction

Additionally, could you provide the error on alert_<DBSID>.log and st22 (if it is exits) and SM21 output here

Best regards,

Orkun Gedik

[Former Member · Accepted solution]

Hi Ornuk

Thanks for the quick response. The note you referred to doesn't apply in this instance as we have made no customising changes to the table and have no entries. We don't have any relevant entries in ST22 and there are no errors in alert_<DBSID>.log

We get the following messages in SM22

-

---

Time

Type

Nr

Clt

User

TCode

Grp

N

Text

-

---

13:11:41

BTC

038

400

BWREMOTE

BY

7

Database selection with invalid cursor

-

---

Database selection with invalid cursor

Details

-

---

Task......

Process

User......

Terminal

Session

TCode

Program

Cl

Problem cl

Package

-

---

23921

Background Processor No. 038

BWREMOTE

1

RSBATCH1

K

SAP Web AS Problem

SBAC

-

---

-

---

Module nam

Line

Table Name

Field Name

-

---

dbacds

1462

-

---

-

---

Documentation for system log message BY 7 :

The database interface was called by a cursor (in a FETCH or CLOSE

cursor operation) that is not flagged as opened. This can occur if a

COMMIT or ROLLBACK was executed within a SELECT loop (which closes all

opened cursors), followed by another attempt to access the cursor (for

example, the next time the loop is executed).

-

---

Technical details

-

---

File

Offset

RecFm

System log type

Grp

N

variable message data

-

---

36

136080

h

Database Error (Non-SQL)

BY

7

dbacds 1462

-

---

Thanks

Lorraine

[stefan_koehler · Accepted solution]

Hello Lorraine,

did you already checked the work process trace file 38 for further information?

As the error occurs in "dbacds" there is mostly more information about that. If you can reproduce this error easily (as you mentioned it happened with every info package) - you can also enable a DBSL trace for a short period to get detailed information at which step this issue exactly occurs.

Regards

Stefan

[Former Member]

Hi Stefan

Thanks for the response. I have passed this information to our Basis chaps to review.

Thanks

Lorraine

[Former Member]

Hi Deepak

This thread does not resolve our issue as we don't have issues with the redo log file size.

Thanks

Lorraine

[former_member188883]

Hi,

Please increase the size of your redo log file. Probably system is not able to create appropriate checkpoints.

Similar issue was resolved in the thread below

Hope this helps.

Regards,

Deepak Kori