cancel
Showing results for 
Search instead for 
Did you mean: 

Error 'DBIF_RSQL_INVALID_CURSOR' encountered when executing DTP

former_member194977
Participant
0 Kudos

Hi

I encountered this error message 'DBIF_RSQL_INVALID_CURSOR' when I executed a DTP to load data from the PSA to a standard DSO.

Any idea why this happens and how to resolve it.

Please let me know.

Many thanks,

Anthony

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

As a part of sanity check

If you have implemented an entry in the table <b>ROIDOCPRMS</b> in the OLTPsystem (or in the Myself System, if you are using a generic extractor directly in the BW), the field <b>MAXPROCS</b> may not have the value '0'. Either do not make any settings in the table - in this case draw default values or, if you are already maintaining control parameters there, then enter a value that is not equal to 0 in the field 'Maximum number of parallel processes'.

Hope it Helps

Chetan

@CP..

former_member194977
Participant
0 Kudos

Hi Chetan

Thanks for your reply. I'm using generic extractors directly in BW. I've checked the table ROIDOCPRMS and the field MAXPROCS is currently showing a value 12. I've tried to execute the DTP to load data from PSA to standard DSO again and still received the error 'DBIF_RSQL_INVALID_CURSOR'. Strangely enough, I didn't get this error when I loaded PSA data into a write-optimised DSO (without data uniqueness check).

Do you know if there is an OSS note to fix this error ?

We're currently on support pack 8.

Thanks,

Anthony

Former Member
0 Kudos

Hi Anthony,

It looks like problem with Extractor. Check the extractors you will find some clue.

Regards

Nimesh

former_member194977
Participant
0 Kudos

Hi Nimesh

I have checked my generic datasource and extractor. Couldn't find anything wrong with them. I generated and replicated them again before executing the DTP to load PSA data into the standard DSO. No luck... I still received the 'DBIF_RSQL_INVALID_CURSOR' error. I've raised an OSS note to SAP.

Regards,

Anthony

Former Member
0 Kudos

Hi Anthony,

Is your problem solved? Here are few things you can check not sure if this helps or not..

1.check if there are any locks on the object that you are writing..

2.Check the table space of the database table.

3.Check if the partitions/DB stats for the data target are available at database level.

Regards

Manga

former_member194977
Participant
0 Kudos

Hi

I have successfully managed to load the PSA data into a standard DSO after applying BW support pack 9. One of the notes in SP9 must have fixed the bug.

Cheers,

Anthony ;o)

Former Member
0 Kudos

Thanks Anthony, for the update.

didnt get a achance to check your message to make sure that you are on SP-08,"most" of the DTP issues are solved with SP-09 or SP-10.

Chetan

@CP..