Problem in activation of ODS 0SD_O06 due to Archiving request.

Hi Experts,
I am having a problem in activating ODS 0SD_O06, it is giving below error message
1. 550 of 1.476.126 data records are in a locked area
2. 550 data records locked by archiving request 1.048.978
3. Error when checking data to be activated against archiving objects.
We have archived the ODS content based on Billing Date, Archiving Request 1.048.978 is for the Bill Date 01.01.2004 to 31.12.2004.
I checked in the new data table of ODS with the Bill Date 01.01.2004 to 31.12.2004, I got 550 Records.
It means the records which is already archived for Bill Date 01.01.2004 to 31.12.2004, got changed and again came into the request.
I am not able to find the solution for this, please help me in this, your help will be highly appreciated.
Thanks and Regards,
Ajay Kumar
9350006555

hi,
If the data has been archieved then there is no tool to get the archieve data back in BW. So I suggest to investigate further.
Thanks

Similar Messages

Problem in activation of ODS

I am unable to activate the ODS and showing the error as SID is not properly assigned. Do I need change the request of ODS to red.

Hi,
You cannot reactivate the ODS data unless you edit the data inside the PSA. The data in the PSA is not compatible... may be some special character has arrived in PSA which loads to ODS but, it will create problem during ODS activation. You need to delete the request in ODS... go to PSA and find out the error record and edit it and again load it from PSA. Error record can be traced in errorlog of ODS activation.
Thanks
Kishore Kusupati

Problem in activating the ODS

Hi experts,
while activating the data in the ODS , I am getting the following errors.
"System error ocurred(RFC Call)"
Activation of data records from ODS object XXX terminated
"Task 0031 for parallel SID assigment terminated with errors"
"Task 0021 for parallel SID assigment terminated with errors"
"Task 0009 for parallel SID assigment terminated with errors"
"System error ocurred(RFC Call)"
Task 004 2for parallel SID assignment terminated with errors.
When I saw the dump I found the following message
How to correct the error
"MESSAGE_TYPE_X" C
"SAPLRSATREE " or "LRSATREEF28 "
"RSATREE_START_ACTIVATION"
I
                                                                                Information on where termination occurred
The termination occurred in the ABAP program "SAPLRSATREE " in
"RSATREE_START_ACTIVATION".
The main program was "SAPMSSY1 ".
The termination occurred in line 536 of the source code of the (Include)
program "LRSATREEF28 "
of the source code of program "LRSATREEF28 " (when calling the editor 5360).

Hi Kris,
Do u have any red requests in ur ODS Manage. This error is caused when u have red requests and still u r trying to activate the data in the ODS.
Or Probably u have check the check box for bex reporting in setings of ods, Uncheck it and ur error will go.
Try these and let us know
Regards
Majeed

Error while activating the ODS

Dear Experts,
Please help me out,
I am facing one problem while activating the ODS of 0FIGL. Data is uploaded successfully into the ODS but while activeting the ODS, it gives the following error message :
Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0DOC_HD_TXT
Value 'SWITCH 24 PORT MANAGED -I' (hex. '00530057004900540043004800200032003400200050004F00') of characteristic 0DOC_HD_TXT
SID determination finished for InfoObject 0DOC_HD_TXT
I have also read out all the related post & also applied them in this but still the position is same.
also in RSKC, all the characters are allowed.
please suggest.
Thanks in advance
Neha
Process 000090 returned with errors

Hi,
Pliz go thru below article for restricting Invalid chars.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0afbb81-f219-2c10-4181-b20f6b10e373?quicklink=index&overridelayout=true
It might give u an idea or solve your issue.
Thanks,
Jitender.

Error while activation of ODS Object.

Hi,
I have loaded the data from R/3 to a ODS Object and the activation of ODS failed due to the following errors as shown below..
-Value '20060 ' of characteristic 0CALQUARTER is not plausible
-Error when assigning SID (details in long text)
-Activation of data records from ODS object ZODS_02 terminated
-Error getting SID for ODS object ZODS_02
I could see that Calendar Quarter as 20060 in table /BIC/AZINV_O0240. There is a calendarday mapped to quarter and year in update rules of ODS object. How the calendar quarter is populated in update table in BW. How should i get rid of this error. Any idea would be appreciated.
Regards,
Raj

don't post same issue twice. Bhanu working on your thread.
check this ...
Raj,
you are getting this calender qurter from SAP right... check in RSA3 fro the your Datasource. if you are getting same value like '20060'. you can do one thing... you can set 'No Update' in Transfer Rules. you can write a routine in Update Rules for populating the data for calender Week.
you can call some standard function modules or you can write a small routine. If you want to write a routine check this thread...Re: Date to Quarter
Possibilites:
1. updtae rules
2. if RSA3(PSA) shows the value of the Quarter as '20050', if it is custom extractor(Generic using FM) you can change this.
3. If it is Standard Extractor or Generic Extractor (using either view/table or Infoset) you can enhance this. you can do the same thing in SAP Side.
All the best.
Regards,
Nagesh Ganisetti.

Problem with activating ODS object.

Hi experts,
I've got a problem with the activation of an ODS object. I've transported this single object from T to A system. First I got an error because one InfoObject was not yet transported to A. After I succesfully transported this InfoObjec, I tried to transport the ODS object again. But now the ODS object is not activated. I cannot activate it by hand also.
The following messages appear when I try to transport/activate this ODS object:
"No active nametab exists for /BIC/AZODEFOP50>"
"Termination due to inconsistencies"
"BIC/ZODEFOP00 (statements could not be generated)"
"Tabel /BIC/AZODEFOP50 could not be activated"
Does anybody know what is wrong and how i can solve it? I've tried to transport this ODS object several times but always the same problem. Even if I try to create this ODS object in A system by hand under the same name: ZODEFOP, I get the same errors when I want to activate it.
Please help me!
Thanx in advance,
Rgds,
Richard
Message was edited by:
        Richard Groot

Hi,
Make sure that the self system is in active form in RSA1->Source system tree.
And also make sure the RFC destination to self system is in active form.
Some times self sytem inactive or wrong path in destinations to self one creates the problem in the activation of ODS.Becuse it has to create a DS on ODS.
With rgds,
Anil Kumar Sharma .P
Message was edited by:
        Anil Kumar Sharma

Problem in activating ODS

Hello Friends,
I have loaded data into New Table of ODS with out any Errors , When I tried to activate ODS,I am getting an error as below
ERROR :
Main Process :
Time limit exceeded. No return of the split processes
Resource error. No batch process available. Process terminated
SID Generation :
Resource error. No batch process available. Process terminated
Activation of M records from DataStore object ZDS_PR terminated
While activating ODS I checked out in SM50 where I find there is only one BGD process of mine running
and at the same time I checkd out in SM66 there was only one BTC process of mine running
when I cheked out in JOBs , my JOB got cancelled afte 500 seconds,
I also changed the process time and number of Packages .
what meight be the probelm ?????
Before activating the ODS, in the request I could not see Query symbol in 'Request for Reporting Available' , does it means the data has some error ??????
Can someone help me ..............

Hi Smitt.J,
From your mail, i am assuming that there is the problem with your back ground jobs. hope you have to increase your back grond jobs and dilog jobs.
You can do job settings via RZ04 and RZ11 transactions.
Pls try to activate ODS with below programs.
RSDG_ODSO_ACTIVATE
RSDSODSACTIVATE.
Hope this may resolve your issue.
Pls let me know if you want any other info...
Best Regards,
Maruthi

I have a problem activating the ODS

Hi all,
I have a problem activating the ODS. When I try activate I getting the following dump:
"UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
"CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
"UPDATE_STATS"
Any help would be appreciated.
Thanks.

Assuming that you are using BI 7.0 Please check the support package you are using in the status. If you are below Sp 10 then you need to import support package 10
Please go thru sap note Note 975948 - No update statistics for newly created tables.
The Support Package is available once Note 914304 "SAPBINews BI 7.0 Support Package 10.
Good Luck
Raj

Certificate issues Active Directory Certificate Services could not process request 3699 due to an error: The revocation function was unable to check revocation because the revocation server was offline. 0x80092013

Hi,
We have some problems with our Root CA. I can se a lot of failed requests. with the event id 22: in the logs. The description is: Active Directory Certificate Services could not process request 3686 due to an error: The revocation function was unable to
check revocation because the revocation server was offline. 0x80092013 (-2146885613). The request was for CN=xxxxx.ourdomain.com. Additional information: Error Verifying Request Signature or Signing Certificate
A couple of months ago we decomissioned one of our old 2003 DCs and it looks like this server might have had something to do with the CA structure but I am not sure whether this was in use or not since I could find the role but I wasn't able to see any existing
configuration.
Let's say that this server was previously responsible for the certificates and was the server that should have revoked the old certs, what can I do know to try and correct the problem?
Thank you for your help
//Cris

hello,
let me recap first:
you see these errors on a ROOT CA. so it seems like the ROOT CA is also operating as an ISSUING CA. Some clients try to issue a new certificate from the ROOT CA and this fails with your error mentioned.
do you say that you had a PREVIOUS CA which you decomissioned, and you now have a brand NEW CA, that was built as a clean install? When you decommissioned the PREVIOUS CA, that was your design decision to don't bother with the current certificates that it
issued and which are still valid, right?
The error says, that the REQUEST signature cannot be validated. REQUESTs are signed either by itself (self-signed) or if they are renewal requests, they would be signed with the previous certificate which the client tries to renew. The self-signed REQUESTs
do not contain CRL paths at all.
So this implies to me as these requests that are failing are renewal requests. Renewal requests would contain CRL paths of the previous certificates that are nearing their expiration.
As there are many such REQUEST and failures, it probably means that the clients use AUTOENROLLMENT, which tries to renew their current, but shortly expiring, certificates during (by default) their last 6 weeks of lifetime.
As you decommissioned your PREVIOUS CA, it does not issue CRL anymore and the current certificates cannot be checked for validity.
Thus, if the renewal tries to renew them by using the NEW CA, your NEW CA cannot validate CRL of the PREVIOUS CA and will not issue new certificates.
But it would not issue new certificates anyway even if it was able to verify the PREVIOUS CA's CRL, as it seems your NEW CA is completely brand new, without being restored from the PREVIOUS CA's database. Right?
So simply don't bother :-) As long as it was your design to decommission the PREVIOUS CA without bothering with its already issued certificates.
The current certificates which autoenrollment tries to renew cannot be checked for validity. They will also slowly expire over the next 6 weeks or so. After that, autoenrollment will ask your NEW CA to issue a brand new certificate without trying to renew.
Just a clean self-signed REQUEST.
That will succeed.
You can also verify this by trying to issue a certificate on an affected machine manually from Certificates MMC.
ondrej.

Activation of ODS fails

When manually activating ODS Data from the target the process is failing. This is confirmed in (SM37) and in ST22.
When we run the "Check how up to date the generated programs of an ODS are from (RSRV) the results (without the option of a correct button) is saying
> Activation program is not current,
> Difference in Line 12,
> Lines in temporary program :L_S_chgdata type /bic/b0002712000,
> Lines in active program L_S_chgdata type /bic/b0002714000,
> Activation program has to be generated again.
We have tried to force activation using (RSODSACT1) but get a similar reference to the messages in RSRV and have used (RSODSACRREQ) which shows our request has a status of 0 which is inferring the request has been activated??
In the end our request is green in the data target and the load monitor but remains inactive and is not available for reporting. Does anyone have any suggestions to help?
Thank you in advance
Helen

Thanks to all for your responses, we have solved the problem.
For completeness of the thread:-
Per my earlier posting the load status via manage the data target is green but the data is not available for reporting we can also see the new data in the ODS Table
The load monitor technical status is also green and indicates that the data requires manual activation
When we tried to manually activate the data in the target the process fails but the load remains green
(SM37) indicates that load activation was cancelled stating the reasons given in earlier postings.
Pankaj,
Thanks for your responses, yours was the most help.
Resolution:
We effectively added a new field to the ODS then checked, saved and activated the ODS; watching the system talk in the bottom left confirmed that the program stated in the error messages was regenerated. We were also lucky in that the problem was in or DEV client so we could empty the ODS, reload it and the regenerated program enabled the activation to complete with no errors. We removed the dummy field and checked, saved and activated it again before transporting it to QAS. Not perfect but it worked.

Activation of ODS fails: Change-Log Request ODSR_... does not exist in ODS

Hello Experts,
I have a problem loading in an ODS object in Release BW 3.5. This load is in parallel to loading in a Cube and InfoObjects from 10 different SAP sources monthly.
Everytime, I load data, Activation fails. The Error message is "Change-Log Request ODSR_... does not exist in ODS ..." These Requests (30 requests) are very old starting with the Go-Live date of the application in 2005. If I search for the first Request in Reconstruct, a request without a InfoPackage-Name is found and if I reconstruct the request, all other new loaded Request are activated and everything is fine. The next month, the same error appears, but without the one old request in the list reconstructed the month before of course.
A few months before I had to repair loading and deleted also requests in the ODS. Then I realized my mistake, that reconstruction is not possible, because the request was gone in the reconstruction list. So I searched for the PSA Request in the ODS reconstruction list, found the requests and reconstructed these. Could this be the reason for my current problem?
But how can I stop this error? Reconstructing all of the requests did not work, because one request says, no active update rules exist for this request. So I stopped reconstructing every request of the long list.
Please help me, I could not find any helpful information until now ...
Many thanks in advance,
Hannes

Hi,
For the old requests that you don't want and that are not valid, goto the monitor for those and mark them red. After that you won't face any problems while activating the new requests.
The reason this is happening is that during activation BW thinks that these old requests are valid as they are green and tries to activate them as they are in squence. When it dosen't find them then it gives the error. If you mark them red, they are ignored and the next request is taken into consideration.
Cheers,
Kedar

Error in delta load activation in ODS

Hello every one,
we have generated generic data source and assigned delta on Shipment number with lower limit 10.
when we loaded data through initial load it got all the records from R3 and scheduled delta (suppose to get 0 records because no data was generated ), Delta is bringing 6 records with it and getting error while activating in ODS due to duplicates.
1.How these 6 record came from with out generating data in R3..
2.while activating it is showing error by saying below message
System error occurred (RFC call)
Key value exists in duplicate (Not allowed by the ODS object type)
Activation of data records from ODS object ZODSNAME terminated
No confirmation for request ODSR_4APQX0IG5LKYJX8248G9QB314 when activating the ODS object ZODSNAME
Request REQU_4APPPJ630P70EWTMMY686TTSO , data package 000001 incorrect with status 5
Request REQU_4APPPJ630P70EWTMMY686TTSO , data package 000001 not correct
Inserted records 1- ; Changed records 1- ; Deleted records 1-
If i am not clear ..please ask i am ready to give required inputs
Please through some light so solve this issue and to load delta properly with out error.
Thanks in Advance
Sandy

Hello,
1. The records may be due to Safety delta interval you have maintained in your generic datasource. In RSA7, you can check STAT column for your data source. Click on the Pointer for Generic delta. you would see Shipment Number from which next delta would be pulled it.
2. Have you unchecked "Do Not Check Uniqueness of Data" in your DSO. This may be the cause for activation failure as same records are coming in as per the safety interval maintained.

Error in the Activation of ODS

Hi all,
I have problems activating one of my ODS, when I check the logs, I found the following errors:
Request REQU_3YSFDYNAS6C41WUPRJW74XGVD, data package 000144 not correct
No confirmation for request ODSR_3YSY3Q7MJONMWLYFQFCCABDM1 when activating the ODS object E_PCA3
Communication error (RFC call) occurred
Anyone had an idea what is wrong, and what I could do to activate this ODS. I have tried couple of times reloading and activating the ODS, but each, they have the same error when activating.
Thanks in advance.
Rgds,
CK

Hi Sriram,
Here are the long text for the error.
<i>Diagnosis
Request REQU_3YSW2M9BY9434CRX1XLOTELYH , data package 000092 contains errors with status 9 in                                                                                table 'RSODSACTREQ' but this data package is missing in the return                                                                           structure.
System response
The data package is entered in the return structure as incorrect.
                                                                          </i>
And here is the long text for the RFC error.
<i>Diagnosis
System response
ODS object: E_PCA3
Package: 77
Task: 0077
Message(RFC): An SQL error occurred when accessing a table.
</i>

Activation of ODS taking very long time

Hello friends,
I have a problem with activating ODS data . Data has been loaded into ODS , but Activation process is taking more than 1 week . This problem is since last week. We are using BW 3.5 version with SP level 18.
When I right click ODS and chose delete data , then It is saying a message 'Lock in the lock manager could not be set' Message no: RSENQ009.
Could you please help me with this.
Any advice greatly appreciated.
Thanks

Hi Manoj,
)Data Activation can be processed in parallel and distributed to server groups in the BW customizing (transaction RSCUSTA2) in BW 3.x. There are parameters for the maximum number of parallel activation dialog processes, minimum number of records per package, maximum wait time in seconds for ODS activation (if there is no response of the scheduled parallel activation processes within this time, the overall status is red) and a server group for the RFC calls when activating ODS data.
2)Do not set the BEx Reporting flag if you do not plan to Report on ODS objects in BEx or in Web. If your reporting requirements on ODS objects are very restricted (e.g., display only very few, selective records), use InfoSets on top of ODS objects and disable the BEx Reporting flag.
In BW 3.x, the SIDs are determined during activation, in BW 2.x during data load. ,hence increasing the Activation time
Also refer the below notes
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_whm/~form/handler
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_whm/~form/handler
Hope these helps
Regards
Karthik
Assign points if helpful

Problem in Activating Contract

Hi all,
I am creating Contract in REFX while creating contract I am activating the contract. It is showing the error "Activation is not possible due to warnings (Partner Assignment)"
Message no. RECN027
Can anybody help me in this?
Thanks in advance.
Shailendra

Hi all
Just had an upgrade and I am experiencing the same problem: Message no. RECN027
Activation is not possible due to warnings (Partner Assignment) when trying to activate the Contract in RECN.
Where in the Business Partner do I change the validation of the partner please
Thanks in advance
Gavin

Problem in activation of ODS 0SD_O06 due to Archiving request.

Similar Messages

Maybe you are looking for