Ods activation Error

[Former Member]

Hello,

I've added an existing ODS a new infoObject. The extraction and the update of the data is working good but when i try to activate the ODS i get the short dump: DBIF_RSQL_INVALID_RSQL.

What can it be?

Thank you!

David

[Former Member · Accepted solution]

Dear David,

looks like some issue with..

1. mismatching of database structures.. may be we need to adjust the tables?

2. what values are going into that new object?

can you post the complete error message from ST22?

can we delete the data and reload the data is posible in your case?

regards,

Hari

[Former Member · Accepted solution]

Hi,

Here is the dump main parts:

Error in the module RSQL accessing the database interface.

What happened?

Error in ABAP application program.

The current ABAP program "GP15PI4RN983HQZFMLUTWJIQMAD" had to be terminated

because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Following a SELECT statement, the data read could not be placed in AN

the output area.

A conversion may have been intended that is not supported by the

system, or the output area may be too small.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was

neither

caught nor passed along using a RAISING clause, in the procedure

"ACTIVATE_SIDS" "(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The data read during a SELECT access could not be inserted into the

target field.

Either conversion is not supported for the target field's type or the

target field is too short to accept the value or the data are not in a

form that the target field can accept

How to correct the error

The exception must either be prevented, caught within the procedure

"ACTIVATE_SIDS"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Check the entries in the developer trace (Transaction ST11)

This contains details about the type and length of the database

field, and the field in ABAP in which the database field should

have been placed.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC

"GP15PI4RN983HQZFMLUTWJIQMAD" or "GP15PI4RN983HQZFMLUTWJIQMAD"

"ACTIVATE_SIDS"

-

---

[Former Member · Accepted solution]

Hi,

Take a look on the note: 634458 .

With rgds,

Anil Kumar Sharma .P

[Former Member · Accepted solution]

Hi Anil,

This not is not relevent because there were no deadlocks.

Thank you,

david

[Former Member · Accepted solution]

Would you like to run 'consistency' checks on this ODS and try correcting the error from there in the transaction RSRV?

regards,

Hari

[Former Member · Accepted solution]

Hi,

in ST22 are there any info's at: "Internal Notes" ?

/manfred

[Former Member · Accepted solution]

hi,

Here is the internal notes section:

Internal notes:

The termination occurred in the function "HandleRsqlErrors" of the SAP

Basis System, specifically in line 759 of the module

"//bas/640_REL/src/krn/runt/absapsql.c#16".

The internal operation just processed is "SQLS".

The internal session was started at 20060406132631.

Internal call code.........: "[RSQL/101//BIC/AZODS_ELE40 ]"

Internal call code.........: "[RSQL/101//BIC/AZODS_ELE40 ]"

[Former Member · Accepted solution]

Hi,

did you try to re-activate a 2nd time ? also try in maintenance screen of updtrules the checkbutton (Ctrl+F2)

/manfred

[Former Member · Accepted solution]

i tried it. it still doesnt work....

[Former Member · Accepted solution]

Hi,

next: let's have a closer look at the new infoobject you've added

/manfred

[Former Member · Accepted solution]

The new InfoObject is char 38 without conversion routine and the lowercase letters checkbox is empty. i enter into it only numbers.

I dont think that this is the problem because in the development system it worked great and in other system i tried exactly the same change and there it worked perfect.

[Former Member]

Hi,

have a look at OSS e.g. https://websmp103.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000678062003

or a closer look into the dump with ST22, sometimes there are more information related to the error.

/manfred

[Former Member]

Hi Manfred,

I'm in a higher Support Package than the one that was suggested by the note.

[Former Member]

Ok, than try to examin the dump with ST22

/manfred