ODS --> ODS 4 last request reload error

[Former Member]

Hello BW Experts,

Scenario:

ODS1 --> ODS2

daily load

last 5 days deltas error due to database problem.

corrected the db problem

now trying to reload

this is the procedure done for reloading

1) ODS2: delete the last 5 days errored requests

2) ODS1: datamart deleted for 5 requests.

3) delta run from ODS1 --> ODS2

4) data loaded okay

5) activation error:

-

---

Request REQU_41NHWWM46CP6BD7KZTAE5S65M(87,919) has not or not correctly been updated; Please edit

Message no. RSM096

Diagnosis

Request REQU_41NHWWM46CP6BD7KZTAE5S65M (87,919) for DataSource 8ZADDSFIN from source system BW1CLNT100 has the status (green) and a smaller SID (is thus older) than the request that you currently want to update into the ODS object.

System response

This is not possible since the sequence of the requests must be kept when wanting to update them into an ODS object. Delta- and init. requests must be updated into the ODS in the request sequence.

Procedure

First update request REQU_41NHWWM46CP6BD7KZTAE5S65M(87,919) for DataSource 8ZADDSFIN from source system BW1CLNT100 from the PSA into ODS object.

If you do not need the data in request REQU_41NHWWM46CP6BD7KZTAE5S65M (87,919) in the ODS object, you can also set the total status for this request to (red) in the Monitor, on theStatus tab page. When checking for completeness, the system then ignores the request.

-

---

Q1) what does this error mean.?

Q2) Please suggest a procedure to correct the error and reload / activate the data.

Thanks,

BWer

[edwin_harpino]

hi BWer,

we had similar situation and oss suggested note 521522-P9:P25:SDL:PSA request cannot be posted to the ODS

Symptom

A PSA request cannot be updated to an ODS (with the scheduler in the PSA tree) even though the request does not yet exist in the ODS and all prerequisistes (active update rules ...) have been fulfilled.

(The ODS is not even offered as a possible updating data target in the scheduler in the PSA tree).

This happens if the request SID of the new request to be updated is smaller than the largest activation SID in the ODS which was already updated to the data targets behind.

This check is incorrect and should be checked against the largest request SID of this activation request, which was already updated, rather than the activation request SID.

Other terms

Updating the request from PSA to ODS; activation request SID;

DMEXIST; PROCESSED_ONE; RSM1529; RSM1 529

Reason and Prerequisites

This is caused by a program error. --

Solution

Depending on your BW system release, this problem is eliminated as follows:

You can book the request beforehand as well by running through the following procedure:

1. Turn off the automatic update (or an update started some other way) on the ODS! - No-one may extract data from the ODS or otherwise change, reset etc. the delta administration.

2. Note the contents of the field Processed_one in the table rsbodslogstate (se16) and replace the contents by those in the field Processed_all for the ODS object into which you want to update the request. This must make the value smaller than the SID of the request you want to update in the ODS. You get these SIDs by double-clicking on the request number for this request in the monitor.

3. Start the workbench again and call the ODS administrator, the last request now no longer seems to be updated.

4. Subsequently post the request from the PSA into the ODS.

5. Set the contents of the processed_one field back to its previous value again.

6. Activate the request.

7. It is VITAL that you bear in mind that no data should be extracted from this ODS during this action, as otherwise the resetting of the delta administration (table rsbodslogstate) will cause incorrect or already extracted data to be extracted again, or the delta administration might be destroyed.

Using the patches below, you can then book the PSA requests without changing the rsbodslogstate table.

[Former Member]

Hi ediwn,

I am having the same problem but for some reason i cant update table RSBODSLOGSTATE. Also, in editing processed_all should i put the request no. which is not present in the ods (and which is causing the trouble) or the one which I want to load (which is higher than the one causing the trouble) or something else.

Thanks a lot.

[former_member188975]

Hi BWer,

To verify what request REQU_41NHWWM46CP6BD7KZTAE5S65M is, you can look it up in transaction RSRQ. This will take you to the monitor of this request and you can check the data target and InfoSource, and the details tab for errors if any. You can also manually post it to the ODS and then try to activate the ODS data.

Hope this helps...

[Former Member]

After running transaction RSRQ, it was able to change the status of a request, even if the request does not appear visible in the Datasource, PSA or DSO. It really help me to treat invisible requests, and after that make available the activation of my DSO . Thanks Bhanu!