What could be the reason if data load from PSA to ODS runs forever?

[Former Member]

I developed an enhancement to populate a custom field which is a company code and used for our data selection. The data to PSA successfully gets the custom field (company code) filled in. But then I load the data from PSA to ODS, the monitor always show yellow status without a finish. I check the content of the ODS, even if the package is there with green color, but it contains no data.

Some hints:

I created the custom field (company code) as an InfoObject without the checkbox "With master data" and "With texts" checked. This InfoObject was added into the Data Fields section of the ODS and also it's added to communication structure and match it with R3 custom field in transfer rule, in update rule, this InfoObject is populated with the same source field. Everything get activated.

Why the data can't get into ODS from PSA successfully?

Desperate !!!!

Thanks!!!

[Former Member · Accepted solution]

Hi Kevin,

First Check: Has the job for loading got cancelled in sm37. Also look out for any short dumps in st22.

Also let us know what you see in the "details" tab of the monitor.

Bye

Dinesh

[Former Member · Accepted solution]

hey Dinesh,

I checked in sm37, find 7 cancelled jobs, look at for short dumps in st22, get 7 short dumps too! Checked table space by db02, double click Tablespaces page, the last column called TS State show all rows are normal.

One of the 7 short dumps msg is as below (in between two dashed lines):

-

---

Runtime Error DBIF_RSQL_INVALID_RSQL

Except. CX_SY_OPEN_SQL_DB

Date and Time 12/13/2005 02:13:05

ShrtText

Error in RSQL module of database interface.

What happened?

Error in ABAP application program.

The current ABAP program "GP3ZRG01CLI27OAABABMUCUXLTH" 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.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

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

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

"GP3ZRG01CLI27OAABABMUCUXLTH" or "GP3ZRG01CLI27OAABABMUCUXLTH"

"ACTIVATE_SIDS"

-

---

If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)".

2. A suitable printout of the system log

To obtain this, call the system log through transaction SM21.

Limit the time interval to 10 minutes before and 5 minutes

after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, select the Editor function "Further Utilities->

Upload/Download->Download".

4. Details regarding the conditions under which the error occurred

or which actions and input led to 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:

ystem environment

SAP Release.............. "640"

Application server....... "qd1sbwdb"

Network address.......... "9.56.218.181"

Operating system......... "AIX"

Release.................. "5.2"

Hardware type............ "002F34AF4C00"

Character length......... 16 Bits

Pointer length........... 64 Bits

Work process number...... 25

Short dump setting....... "full"

Database server.......... "qd1sbwdb"

Database type............ "DB6"

Database name............ "QDW"

Database owner........... "SAPQDW"

Character set............ "C"

SAP kernel............... "640"

Created on............... "Nov 6 2005 20:48:23"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "DB6_81 "

Patch level.............. "99"

Patch text............... " "

Supported environment....

Database................. "DB6 08.*"

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"

Memory usage.............

Roll..................... 16192

EM....................... 12569568

Heap..................... 0

Page..................... 24576

MM Used.................. 4002288

MM Free.................. 184976

SAP Release.............. "640"

Information on where terminated

The termination occurred in the ABAP program "GP3ZRG01CLI27OAABABMUCUXLTH" in

"ACTIVATE_SIDS".

The main program was "RSODSACT1 ".

The termination occurred in line 13511 of the source code of the (Include)

program "GP3ZRG01CLI27OAABABMUCUXLTH"

of the source code of program "GP3ZRG01CLI27OAABABMUCUXLTH" (when calling the

editor 135110).

The program "GP3ZRG01CLI27OAABABMUCUXLTH" was started as a background job.

Job name........ "BI_ODSA403ITDWTRY0GQ4C0G0XYCEP4L"

Job initiator... "USC-2PT2"

Job number...... 02125101

Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in

the

procedure "ACTIVATE_SIDS" "(FORM)" but was not handled locally, not declared in

the

RAISING clause of the procedure.

The procedure is in the program "GP3ZRG01CLI27OAABABMUCUXLTH ". Its source code

starts in line 13448

of the (Include) program "GP3ZRG01CLI27OAABABMUCUXLTH ".

Source Code Extract

Line SourceCde

13481 l_err_count = i_err_count.

13482 l_single_convert = rs_c_true.

13483 ENDIF.

13484

13485 * empty tables

13486 PERFORM clear_sid USING SPACE.

13487

13488 *** SP7

13489 * initialise activation task-handling

13490 IF i_serialize = rs_c_false.

13491 PERFORM rsadmina_get_values.

13492 PERFORM init_activate_taskhandler.

13493 ENDIF.

13494

13495 * create WHERE condition based on the requests in I_T_REQUEST

13496 PERFORM generate_where_requests(saplrsdro)

13497 USING i_t_request 'U' CHANGING l_t_where.

13498

13499 * same SELECT-statement used multiple times

13500 PERFORM open_cursor_with_hold

13501 USING l_t_where

13502 *INSERTAS 13082002 P12/05 <541698>

13503 * rs_c_true "sorting means smaller hash-tables??

13504 rs_c_false"not sorted

13505 rs_c_false"not sorted by keyfields of AQ

13506 g_max_tasks

13507 *ENDINSERTAS

13508 CHANGING l_cursor.

13509 DO.

13510 ADD 1 TO l_count.

>>>>> FETCH NEXT CURSOR l_cursor INTO l_s_upddata.

13512 IF sy-subrc <> 0.

13513

13514 PERFORM register_sids

13515 USING l_s_upddata rs_c_true rs_c_true.

13516

13517 CLOSE CURSOR l_cursor.

13518 EXIT.

13519

13520 ELSE.

13521

13522 PERFORM register_sids

13523 USING l_s_upddata rs_c_true rs_c_true.

13524

13525 IF l_count >= c_check_intervall. "don't check all the time!

13526 l_count = 0.

13527 l_new_sids_possible = rs_c_false.

13528 IF g_req_BBP_APPROV_cnt >= c_max_sid_hashtab.

13529 *** SP7

13530 refresh l_t_msg.

Contents of system fields

Name Val.

SY-SUBRC 0

SY-INDEX 1

SY-TABIX 64

SY-DBCNT 0

SY-FDPOS 0

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY

SY-UCOMM

SY-TITLE Activating M->A in ODS

SY-MSGTY I

SY-MSGID RSDRO

SY-MSGNO 308

SY-MSGV1 02:13:03

SY-MSGV2 20,051,213,071,303

SY-MSGV3

SY-MSGV4

Active Calls/Events

No. Ty. Program Include Line

Name

4 FORM GP3ZRG01CLI27OAABABMUCUXLTH GP3ZRG01CLI27OAABABMUCUXLTH 13511

ACTIVATE_SIDS

3 FUNCTION SAPLRSDRO LRSDROU16 149

RSDRO_ACTIVATE_SID_ODS

2 FUNCTION SAPLRSSM_PROCESS LRSSM_PROCESSU30 948

RSSM_PROCESS_ODSACTIVATE

1 EVENT RSODSACT1 RSODSACT1 224

START-OF-SELECTION

Chosen variables

Name

Val.

No. 4 Ty. FORM

Name ACTIVATE_SIDS

CL_RSO_MSG=>IF_RSO_APPLICATION_LOG_CONST~PROBCLASS_NONE

???

??????

??????

SYST-REPID

GP3ZRG01CLI27OAABABMUCUXLTH

and bla bla bla ....

-

---

As I said, there is new custom field I inserted into the ODS, Communication Strut./InfoSource/Update Rule and etc. When defining the InfoObj, the checkbox "With master data" is checked, but the checkbox "With texts" is not check. I am not sure these two checkboxes settings are right or not. Another thing for this InfoObj. maybe should use ALPHA convertion and also I need to check the "Conversion" checkbox in the Transfer Rule? From the short dump, it sounds that's the reason that I should use ALPHA conversion, right?

Thanks

[Former Member · Accepted solution]

Hallo

can you to transaction RSRV and check the activation program for the ODS? if get Red, then correc it and try the activation again. as far as I understood the issue is during the activation of data not during the loading.

RSRV - all elementary Test, Check status of ODS Program. drop on the right, inset you ODS techincal name, press execute. if error occurs, then press correct error.

then repeat the acitvation of the reuqest/s.

Mike

[Former Member · Accepted solution]

Hi,

It is some what temporary table(memory) issue. So,discuss with Basis people to use automatic extention of roll back segments in BW .

Try to initialize delta with disjoint selections ,instead of doing it at a time.And also use 'For all entries' wherever it is recommandable in the user exit.

With rgds,

Anil Kumar Sharma .P

Message was edited by: Anil Kumar Sharma

[Former Member · Accepted solution]

hey Mike,

After following your note, do get red errors and these red errors are:

"Varying numbers of lines"

"No. of lines, temporary program: 11707. No. of lines, active program: 11371"

"Activation program has to be generated again".

Then I pushed the button "Correct error", you say "then repeat the acitvation of the reuqest/s", how to do that?

Thanks

[Former Member]

Hi Kevin,

What is the color of the request. If it is yellow make to red and then try to "processs manually" (what I had said in my earlier thread).

Bye

Dinesh

[Former Member]

hey Dinesh,

I am not sure where is the request you mentioned. Could you give me details?

Thanks

[Former Member]

Hallo

if you correc the error, then go to RSA1, select the ODS, manage, then acitvate the request.

onc eyou correct the error in RSRV, can you repeat the check? you should get green. and if this is green, then activate as mentioned above.

by the way: if you have a tablespace issue, in ST22 you see the message: unable to extend table space by XXXXX byte. i do not see that in your mesaage log.(maybe i missed it)

Regards

Mike

[Former Member]

It's eventually fixed by either Mike's RSRV fix or my ALPHA conversion. Now I can get the data into ODS without any error and pretty quick now.

Now I've got another issue, I am trying to use Formula in the update rule to restrict the data ranging from company code X300 to X3RT.

I tried formula with Company Code >= 'X300' AND Company Code <= 'X3RT'. I tried 'X300'/'X3RT' with string, number, and constants, but none of them works! Any idea?

Thank you all!

[Former Member]

Hallo

Why Formula? with formula you can set up a value. if Iunderstood correctly you want to only have the data for Company X300 to X3RT. use this selections in the infopackage. you just load what you need.

are you doing a full load or Delta loading?

if delta, then make an init based on the selections. automatically the delta will be based on the init selections

Mike

[Former Member]

Hi Kevin,

DBIF_RSQL_INVALID_RSQL - mostly indicates it is a tabelspace or memory issue.

Goto the details tab of the monitor and select the package in red(error one) -> right clieck and select "process manually".

Hope this helps.

Bye

Dinesh

[Former Member]

hey Dinesh,

There is no any red color error, only these yellow color texts there in the details tab of monitor.

Thanks

[Former Member]

Hi,

From the dump, we can say it is not the problem with Master data and AlPHA . It is geting fail at Filling internal table l_s_upddata. I hope, internal table use teporary memory(even not Disk space, so it is not problem with table space) .So try to use auto refresh(free) of roll back segments.

With rgds,

Anil Kumar Sharma .P

[Former Member]

Hi Kevin,

From the error messages it looks like a tablespace issue. Maybe now there is enough tablespace. So first try to move the data again. In case you still get the same problem then contact your BASIS and ask to extend the tablespace. Then move the data from your PSA to ODS.

Bye

Dinesh

[Former Member]

hey Dinesh,

How would you guess it's table space issue from the short dump? I check the table space by db02, the last column "TS State" shows normal for each row.

I also tried checked ALPHA conversion, still no help. One hint, this InfoObj. is kind of company code field, even if I use 0Comp_Code as a template when creating this custom InfoObj., but I didn't check the checkbox "With master data" and "With texts", then the attributes used to be attached to 0Comp_Code are gone for this custom InfoObj., another reason?

The yellow color texts in the details tab of Mointor are:

"3028 Records sent ( 3028 Records received )"

"Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished "

"Missing message: Subseq. processing completed"

"ODS activation (change-log) : not yet activated"

Thanks

[Former Member]

Hi Kevin,

Another reason would be a tablespace issue. Check the tablespace in DB02. If the tablespace is full then contact the BASIS.

Bye

Dinesh

[Former Member]

Hi,I think the job is still running in the background thats why it is showing yellow col. wait for some time to complete the job. even if the job is completed and status is yellow then try to activate the ods.

regs,

mahantesh