Long ODS activation times for 0FI_GL_04 data source.

[Former Member]

Hello,

We had FULL loaded the ODS and enabled the deltas too. Our validation team determined that our deltas were not right and we stopped the deltas and resumed the full loads.

Now when we do the full loads the ODS activation aborts after running for 3 days!

Any suggestions on overcoming this ?

Thanks

Dorothy

[Former Member]

I have had problems with this object, and found the only way around the problem was to partition the data loads. Try uploading each fiscal year seperately, it may help.

Simon

[Former Member]

Checked 873525. We are on BW3.5 and R346C. So I do not think this note applies in our case.

Also, the error occurs when I do not use a RFC load balance group(RZ12) either.

[Former Member]

It seems you are facing System Resources issue . Have you checked that you have enough dialog processes minimum 4 for activation process ?

[Former Member]

1. I have a problem. This problem is related to ODS activation failed due to job cancellation.

2. This is Short dump runtime error "RAISE_EXCEPTION".

3. This is a full update and this error is occurred in Process chain.

4. In the Process chain data is loaded in ODS completed successfully, but while activating ODS this error is occurring frequently (every 3 days).

5. That time we are doing activation repeated manually and then activation completed successfully.

The job has cancelled due to lack of dialog processes (system resources) for activation of ODS object activation

Error: Short dump runtime error RAISE_EXCEPTION.

Error analysis: A RAISE statement in the program “SAPLSPBT” raised the exception condition “RESOURCE_FAILURE “

The termination occurred in the ABAP program “SAPLSPBT” of the include program “LSPBTU09” function SPBT_PARALLEL_PROCESSING. The program “SAPLSPBT” was stared as a background job.

CALL FUNCTION 'PARKING_ASYNCHRONOUS_RECEIVE'
EXPORTING
PARKING_OPTION = 'S' "Set park
EXCEPTIONS
PARKING_IMPOSSIBLE = 1
PARKING_OPTION_FAILED = 2
OTHERS = 3.

IF SY-SUBRC <> 0.

• MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

• WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

WAIT UP TO PRFC_DELAY SECONDS.

• Zurücksetzen der Parking-Position der asynchronen Antworten

CALL FUNCTION 'PARKING_ASYNCHRONOUS_RECEIVE'

EXPORTING

PARKING_OPTION = 'R' "Reset park

EXCEPTIONS

PARKING_IMPOSSIBLE = 1

PARKING_OPTION_FAILED = 2

OTHERS = 3.

IF SY-SUBRC <> 0.

• MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

• WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

ATTEMPT_COUNT = ATTEMPT_COUNT + 1.

ELSE.

EXIT.

ENDIF.

ELSE.

CURR_RESOURCES = 1.

EXIT.

ENDIF.

ENDDO.

IF CURR_RESOURCES = 0.

RAISE RESOURCE_FAILURE.

ENDIF.

ENDIF.

SERVER_NAME = SERVER_DEST.

ENDFUNCTION.

could you pls suggest any solution for this?

[Former Member]

Hi Dorothy,

Check this OSS Note:873525

Bye

Dinesh

[Former Member]

Thanks For the reply, Sat.

The dump says "Exception condition "RESOURCE_FAILURE" raised"

"RAISE_EXCEPTION" C

"SAPLSPBT" or "LSPBTU09"

"SPBT_PARALLEL_PROCESSING"

I think this is OK as the activation is running for a long time.

The real issue is why is it taking this long. I 'full' loaded 1 months data at time in the past and it took a bout 45 minutes to activate. Do you think this is happening because I de-activated the deltas and resumed full loads ? By the way the SM50 shows that the hold times are becuase of waits on RFC.

[Former Member]

Dorothy

Welcome to SDN

Generally Activation won't run such a long so definitely it shoulsd have been failed with in 7/8 hours but to update the log it took so long. Please see for any short dumps and post the error message over here.

Thnaks

Sat