While archiving data from WDSO getting error Data area archived is empty

[surendra_p]

Hi Folks,

We are implementing SAP HANA Near line storage concept to archive data from SAP BW Info providers.

When i am trying archive data from WDSO i am getting the error Data area archived is empty.

but there is data present is the provider and archiveing in continuos manner only.

Please help me on this issue and thanks in advance.

Regards

Surendra

[anilsuryavansi · Accepted solution]

hi Surendra, WODSO works little differently then standard dso or cube when it comes to archival.

You will get generally this error if you are using a time slice dimension other other request id creation date or request id load date.

Take an example if you are archiving based on document date; and your first request loaded is having document date 01.01.2016 then you did a history loads to DSO and loaded 2015 data in second request onward.

Now if you start you archival of data with document date older than 31.12.2015; system will check that the very first request that needs to be archived first has data greater than 31.12.2015; it won't archive any data from write optimized DSO.

Basically all the requests are required to be archived in same sequence as these are loaded.

Hope this will help.

Regards,

Anil

[surendra_p · Accepted solution]

Hi Anil,

I understand what you said is correct . i am trying to archive data based on Request creation date only but also i am getting this error.

Upto few request the data archiving done then after i am getting Error "Data area archived empty"

For reference see below screenshot.

Here till the Tick Mark Requests the data archiving done successfully then after i am unable archive.

Please help me and provide few steps to archive data for this type situations as early as possible.

Regards

Surendra

[anilsuryavansi · Accepted solution]

Hi Surendra,

If you have Request creation date based archival then there should not be issue with archiving. What exactly the job log says.

I don't have any system as of now with NLS so i quickly checked on ADK log and can see below information in job log. Please see job log that shows selections passed during archival.

Regards,

Anil

[surendra_p · Accepted solution]

Hi Anil,

I have created DAP with Request based only but i am facing same issue still.

Following is for reference please help me as early as possible .

if you dont have any problem can share you contact details on my mail id -(Surendrap595@gmail.com ) i will contact, Please help me i am facing in Golive.

Regards

Surendra

[anilsuryavansi · Accepted solution]

Hi Surendra, can you check what is the selection getting passed to request__req_cdate field that i highlighted in my screen shot. or can you attach complete log?

Regards,

Anil

[surendra_p · Accepted solution]

Hi Anil,

This is the errror i am facing

Job log overview for job:    BI_ARCH-Z0CPAO51-CREATE / 06593100

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

|Date      |Time |Message text |Message class|Message no.|Message type|

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

|15.08.2016|06:59:31|Job started |     00 |    516    | S      |

|15.08.2016|06:59:31|Step 001 started (program RSDA_REQUEST_EXECUTE, variant &0000000000476, |     00 |    550    | S      |

|15.08.2016|06:59:31|REQUEST_INVALIDATION = |    RSDA     | 003    |     S |

|15.08.2016|06:59:31|New archiving request created for data archiving process

| RSDA     |    134 |     S      |

|15.08.2016|06:59:31|Processing is in production mode |    RSDA     | 135    |     S |

|15.08.2016|06:59:31|User has authorization to archive InfoProvider Z0CPAO51 |    RSDA     | 129    |     S |

|15.08.2016|06:59:32|Status transition from '10' to '10' performed for request 2,398,549 |    RSDA     | 251    |     S |

|15.08.2016|06:59:32|Request 2,398,549 created successfully |    RSDA |    224    | S      |

|15.08.2016|06:59:32|Selection conditions of request 2,398,549 are: |    RSDA     | 225    |     S |

|15.08.2016|06:59:32|REQUEST__REQ_CDATE <= '20091231' |    RSDA     | 147    |     I |

|15.08.2016|06:59:32| has authorization to archive

|    RSDA |    129    | S      |

|15.08.2016|06:59:32|Lock set for request 2,398,549 in mode E |    RSDA     | 222    |     S |

|15.08.2016|06:59:32|SQL: 15.08.2016 06:59:32 |    DBMAN    | 099    |     I |

|15.08.2016|06:59:32| LOCK TABLE "TESTDATRNRPARTX" IN EXCLUSIVE MOD |    DBMAN    |    099    | I      |

|15.08.2016|06:59:32|SQL-END: 15.08.2016 06:59:32 00:00:00 |    DBMAN |    099    | I      |

|15.08.2016|06:59:32|SQL: 15.08.2016 06:59:32 |    DBMAN    | 099    |     I |

|15.08.2016|06:59:32|DELETE FROM "TESTDATRNRPARTX" |    DBMAN    | 099    |     I |

|15.08.2016|06:59:32|SQL-END: 15.08.2016 06:59:32 00:00:00                                                                                    |    DBMAN |    099    | I      |

|15.08.2016|06:59:32|SQL: 15.08.2016 06:59:32 |    DBMAN    | 099    |     I |

|15.08.2016|06:59:32| LOCK TABLE "TESTDATRNRPARTX" IN EXCLUSIVE MOD |    DBMAN    | 099    |     I |

|    DBMAN |    099    | I      |

|15.08.2016|06:59:34|End of check and update for status control control |    RSM1 |    544    | S      |

|15.08.2016|06:59:34|Lock deleted for request 2,398,549 in mode E |    RSDA     | 223    |     S |

|15.08.2016|06:59:34|Data area to be archived is empty                                                                                        |    RSDA |    247    | I      |

|15.08.2016|06:59:34|Exception  occurred in line 112 of include CL_RSDA_ARCHIVING_REQUEST=====CM01E (program CL_RSDA_ARCHIVING_REQUEST=====CP)|    RSDA     | 140    |     I |

|15.08.2016|06:59:34|General error in BW archiving (-> see long text) |    RSDA     | 001    |     I |

|15.08.2016|06:59:34|Exception  occurred in line 56 of include CL_RSDA_ARCHIVING_REQUEST=====CM00S (program CL_RSDA_ARCHIVING_REQUEST=====CP) |    RSDA     | 140    |     I |

  |15.08.2016|06:59:34|Processing of data archiving process xxxxx canceled                                                                  

Regards

Surendra

[anilsuryavansi · Accepted solution]

Weird since i see data in manage tab older to your selected date i.e. 20091231. Is it possible to try once archiving data older than 20080630 and see if those 2 requests are getting archived?

Regards,

Anil

[surendra_p · Accepted solution]

when ever we pass request date range it will collect all the request id's below under that range and archive it.

but here upto few requests the data getting archiving but after that it's throwing error .

i am unable to find what is the cause.

Regards

Surendra

[anilsuryavansi · Accepted solution]

Ok so does it mean if you enter 20080630 - those requests got archived? If yes then I would advise go ahead and archive data in smaller pieces now and raise with SAP via oss note if there is any limitation on requests / days or records for on process.

Regards,

Anil

[surendra_p · Accepted solution]

Here after what ever the request above mentioned date as small like one week or one day the archival process getting failed.

Any way thanks for you suggestions. i will try my best.

Regards

Surendra

[anilsuryavansi · Accepted solution]

Ohh ok so even if you select the days of archival selection period older then 30.06.2008 only; then also those two requests are not getting archived.

See below one error I had received once. For this job I was trying to archive data older than 31.12.2014 and job keeping cancelled. Then I changed the days and archived data older than 30.06.2015 and all the requests till June 2015 were archived.

See if you have privilege to try archiving data till 31.12.2010; if so give it a try and see if gets archived.

All the best!!!

[anilsuryavansi · Accepted solution]

Hi Surendra,

I encountered one scenario today with archival of wodso and is pretty interesting and useful.

I have one wodso that loads into two different cubes. Till 06.02.2015 all the requests were loaded in both the targets and after that we discontinued to use Cube1 and only Cube2 is being loaded.

All the requests after 06.02.2015 are not getting archived though I select just one day 07.02.2015 for archival or give 0 days older for archival.

Then I did a data mart from wodso to cube1 without transferring data; and that's it - it solved my issue. Now requests from 07.20.2015 are also getting archived.

So my learning is - data mart for all the targets should be completed to archive any requests.

I see your post is still open so thought of sharing. See if you have similar situation.

Happy learning and sharing. Let me know if this is useful.

Regards,

Anil

[surendra_p · Accepted solution]

Hi Anil,

Thanks for your Information.

Yes ,which is the target i am trying to archive data From this target data is flowing further to next level target to around 4 to 5 DSO's.

As per your analysis to solve this issue we need to create DMART right.

Ok i will try with this.

Regards

Surendra

[surendra_p · Accepted solution]

Hi Anil,

Thanks lot for your investigation on this issue and finally the issue got Resolved.

But I have one doubt how the data mart will affect this issue and how it solving because we are not transferring data just we are creating Data mart with out data transfer.

Can you please share me if you have information.

Regards

Surendra

[anilsuryavansi · Accepted solution]

Hi Surendra,

The archival process is defined in such a way that if you have started delta load from one target to another target; then the delta should be completed before archiving. It does not matter whether data is transferred or not.

Regards,

Anil

[surendra_p · Accepted solution]

Hi Anil,

I tried with your solution it's worked fine for object which has no loads currently running.

But we have two more objects which contains daily loads(Now Also) but we have to archive data till 2013 for this object i am getting same issue.

I understand that there is no loads running objects we can archive means that the object already stopped using.

Is it correct or not....?

Regards

Surendra

[anilsuryavansi · Accepted solution]

We archive during the weekend with loads stopped. I never tried archiving when load is running and won't recommend.

Regards,

Anil

[surendra_p · Accepted solution]

No ,we are not archiving currently loading data and we are also not preferring to archive data while loads running.

But the object which we are trying to archive have daily loads but we are archiving only 3 years old data.

The solution which you shared working fine for object which is not presently in use and having no daily loads.