DSO Activation

I have a standard DSO. In the settings, the only thing checked is "Set Quality Status to 'OK' Automatically", I have this loading using a process chain and in the chain, I have the Activate process included.
The DSO loads with no problem, but the Activate step fails with error message "No active PSA table".
Two things that seem weird:
1. Without doing anything, I go to the DSO > Manage and the DSO has been activated (so why does the process Activate in the process chain fail?)
2. If I Repeat the Activate step in the process chain, even though the process is active based on # 1 above, the Activate step turns green and completes the process chain.
I am having this problem for several DSOs in several different chains.
Thanks for any help. Keith J

PC- Display variant for DSO activation - click on Parallel processing - click DS Activ option -
   Background with "A"
   Num of Par proessing = 6
again Click on this time DS-SID GEN
Background with "C"
   Num of Par proessing = 3
Make sure you have the same settings for DSO activation which are failing?
Also refer Note: 1301094 - SP21:Error during activation of DSO in a Process Chain
Symptom
When you execute a DTP for loading a Datastore Object error happens in the activation of Datastore. This typically happens in a process chain. The error messages are as follows:
o RSDRO 103: "PSA update failed"
o RSAODS 003: "Error occurred while deciding partition number"
Solution
SAP NetWeaver BI 7.00
           Import Support Package 21 for SAP NetWeaver BI 7. 00(SAPKW70021) into your BI system. The Support Package will be available when note 1270629 with the short text "SAPBINews NW BI 7.0 ABAP SP21", describing this Support Package in more detail, is released for customers.
SAP NetWeaver BI 7.01 (SAP NW BI7.0 EnhP 1)
           Import Support Package 04 for SAP NetWeaver BI 7. 01 (SAPKW70104) into your BI system. The Support Package will be available when note 1227876 with the short text "SAPBINews NW7.01 BI ABAP SP04", describing this Support Package in more detail, is released for customers.
SAP NetWeaver BI 7.10
           Import Support Package 08 for SAP NetWeaver BI 7. 10 BI (SAPKW71008) into your BI system. The Support Package will be available when note 1260071 with the short text "SAPBINews NW 7.10 BI SP08", describing this Support Package in more detail, is released for customers.
SAP NetWeaver BI 7.11
           Import Support Package 02 for SAP NetWeaver BI 7. 11 (SAPKW71102) into your BI system. The Support Package will be available when note 1260072 with the short text "SAPBINews NW7.11 BI SP02", describing this Support Package in more detail, is released for customers.
In cases the correction instructions can be used.
Beforehand please definitely check the note 875986 for transaction SNOTE.
This note may already be available before the Support Package is released. However, the short text will still contain the words "preliminary version" in this case.
Edited by: Srinivas on Jul 29, 2010 4:30 PM

Similar Messages

DSO activation problem after creating the secondary indexes

Hi,
I am facing the problem with DSO activation after creating the secondary indexes.
Compared with Info Cubes there is no functionality available which allows dropping and recreating a secondary index before/after the data activation.
As a workaround I can write a simple report which drops and creates the indexes on database level.
By using a process chain, we can simply insert the drop index report before data activation and the create index report after the data activation process.
Can any body help me step by step procedure or Material to write the programs for delete index and create index reports on DSO object?..
Thanks in advance for your help.
Thanks & Regards,
Bala

hi,
in BI if you are using the dso for reporting then you can simply chk the settings of dso for SID generation.
no need to create the indexes or delete it.
if the dso is not used for report then no need to use indexes.
Ramesh

How to improve performance of DSO activation

Hi all,
We have created a DSO which is updated daily from another DSO. The extraction is from the Active table of the source DSO, so all records are extracted, in this case roughly 1,000,000 records. (we cannot use delta update for this particular DSO)
Because of the large number of records, the activation of the data in the target DSO is quite slow (ca 20 minutes).
My question: Is there any way that we can analize where exactly the time is lost during the activation and how we can improve the performance? Is it for example possible to deactivate the Change log?
Note that I am already familiar with RSODSO_SETTINGS, and also, we do not want to switch to write-optimized DSO.
Thank you in advance for your help.

Hi
DSO Activation can be improve by unchecking the "SIDs Generation upon Activation" check box in the DSO settings as it takes lot of time to create SIDs while activations. We can go ahead with this option only when we dont have any reports based on that DSO
Thanks & Regards
Rohit

Process Chain - Follow on dependencies to DSO Activation

Hi, I have a Data Load Process where the start routine is dependent on DSO data that was just previously activated. For some reason it looks like the the time before the load and the time after the DSO activation are close by just seconds.
The Data Load Routine will drop records if the activated DSO data is not available and this seems like what I am witnessing. I thought there was a way to configure the chain or job to wait until the previous is completely done. or did that go away with 7.0...
Is there a way to make sure the loading process doesn't start until the previous DSO activation is completed and the data is available?
Thanks!

Hi,
Interuppt concept :
If a process chain is only processed either in part or in its entirity if more than one start condition is filled, you use this process type to specify the additional conditions.
The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled. Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.
The interrupt process schedules an additional background job that starts based on the relevant condition. Therefore the interrupt process is not really active during the interrupt phase; it does not use any resources during this time.
If the interrupt processes are filled before the start process condition, the chain starts as soon as the start condition is filled; the interrupt process no longer interupts the chain because its condition has already been filled. If the interrupt process condition is is filled again before the start condition of the chain is filled, this does not influence the chain. It is not stopped by the interrupt process..
so basically your interrupt will wait for an event like ex:..YABAP_YGTRFCEVENTRAISE_0035 ... so you can raise that event eother by some job or some program..bUt for you i think adding the waiting timw will be better option ..
hope i cleared you ..
Regards,
Shikha

DSO activation in Process Chains - takes long time

Dear All,
We have included DSO activation in Process Chains. This process takes a long time to execute. We manually cancel the corresponding process in Process Overview and repeat it from chain. The chain runs daily and this issue also occurs on a daily basis.
Does anyone one of you have an idea of how to deal with this performance issue?
Regards.

Figure out in which class does your process fall in:
Class A- High Priority
Class B- Medium Priority
Class C- Least Priority
Background processes
Class A jobs
The number of work processes reserved for job class A is a subset of the number of background processes.
You should only reserve work processes for job class A if it makes sense within your system organization. Work processes reserved for class A jobs are no longer available for job classes B or C.
Set parallel processing for a specific BW process in the (variant) maintenance of the process
Call the function for setting the parallel processes.
You can call the function in the process variant maintenance of a process chain or in the process maintenance. The function call varies for the different BW processes.
For example, in the data transfer process you call the function with Goto--> Background Manager Settings.
The Settings for Parallel Processing dialog box appears
Under Number of Processes, define the maximum number of work processes that should be used to process the BW process.
If you enter 1, the BW process is processed serially.
If you enter a number greater than 1, the BW process is processed in parallel
In the Parallel Processing group frame, make the relevant settings for parallel processing in the background:
Enter a job class for defining the job priority.
The job priority defines how the jobs are distributed among the available background work processes
In the group frame Parallel Processing, you can define whether parallel processing should take place in dialog work processes or in background work processes for the processes ODSACTIVAT, ODSSID and ODSREQUDEL for the DataStore object
Transport:
The entries in tables RSBATCHPARALLEL and RSBATCHSERVER are written on a transport request of the Change and Transport System.
Edited by: ram.pch on Oct 7, 2011 9:55 PM

How to check if a DSO Active Table is being used in any look-up's?

Hi Gurus,
We have a DSO that is being loaded on a weekly basis. Now this DSO is being loaded right from the time our project went live. There are no reports built on top of this DSO and the DSO is not being used as a Data Mart i.e. it doesn't feed any other DSO's or InfoCube's. Also this DSO is not being used in any MultiProviders.
So the only sensible reason for using this DSO that we can think of is that the data from this DSO is being 'looked up' by some other DSO's or InfoCube at run-time. So Is it possible to check if the active data table of an DSO is being ;looked up' at run time by some other data loads? I already tried using an 'Where Used List' on the active data table of the DSO, but it didn't show any results.
Thanks
Arvind

Try the following:
Check the table RSAABAP in SE16, you can search the technical name of DSOs active table in field EDIC.
You get all Code-IDs, where this table is used in ABAP coding.
In RSAROUT you can check, which code-type it is.
Now you know, if the DSO is used in any routines.
Hope this helps.
Regards
Tobias

DSO Activation Error - While Installing BI Content

HI Friend,
    First, I deleted one sap source systems for BW1 ( My bw1 server BI is : BW1CLNT100 ), later ,I create the same sap source system, But active 0FIAP_O03 ods,
had error:
DataSource 80FIAP_O03 does not exist in source system BW1CLNT100 of version A
Error when creating the export DataSource and dependent Objects
Error when activating DataStore Object 0FIAP_O03
I go to BW1CLNT100 datasoucres ,I not finded 80FIAP_O03 datasoucre, But I goto bw prd BI datasoucre, I found   80FIAP_O03 datasoucre.
I think loss 80FIAP_O03 datasoucre for BW1CLNT100 source system, because I am't delete Roules on the 0FIAP_O03 infosoucre for delete sap soucre systems.
DSO Activation Error - While Installing BI Content
this problem no issue, So I create new thread.
Now, How could me create or load 80FIAP_O03 datasoucre for BW1CLNT100 source system?
Now, I Replicate Datascoure for BW1CLNT100 source system, Delete old datasocure....... I go home, I will try tomorrow .

Hello,
You should generate the export data source for 0FIAP_O03 again, if there is still a problem please goto
RSA1 > SOURCE SYSTEMS > and right click on the relevant source system, find the datamart application component and
right click on this to replicate the datasource.
Best Regards,
Des

Infoset based Query creating locks on DSO Activations

Hello Experts,
We are current on SAP NetWeaver 7.3 on ORACLE data base version 11.2.0.3.0.
We have a query thats built on top of an infoset ( Based on left outer join on 0material and 0mat_plant) when user executes the query its causing locks on DSO activations.
DSO activations are on hold due to locks on following table RSRNEWSIDS. when BASIS investigated this issue they came up with following reason
executing this infoset based query is causing the locks and if we kill this job the DSO Activations run fine.
The design is as follows
Infoset(0material --Lefter outer Join -- 0mat_plant) ---> MP ---> BEx Query.
Question 1) Is it possible for a query to create locks and cause holds on DSO Activations? if so what would be the reason?
Question 2) Any solution or any of you faced similar issue?
any solution is highly appreciated and rewarded.
Regards,
Vamsi.

Question 1) Is it possible for a query to create locks and cause holds on DSO Activations? if so what would be the reason?
It all comes down to SID if a query needs an association between fact and dimensions it will use SID and if you doing an activation it readjusts the SIDS so needs to be locked for the most up to date data.
Question 2) Any solution or any of you faced similar issue?
Do your query execution before or after DSO activation.
Cheers!
Suyash

New Feature in BW 7.3 for DSO activation - Performance Data in DB2 environ

In BW 7.3 SAP is introducing a new feature - Activation is changed from single lookups to package fetch of active table. I also understand that it is database dependent.
Can anyone who has knowledge in DB2 environment highlight the necessary dependencies to maximize the DSO activation improvement and what is the maximum improvement expected in terms of percentage.
Thanks.

Hi Valerie,
Unfortunately i didn't find the answer yet. For the moment we have kept the old connection types to our DS environment.
Good luck!
Best regards,
F. Geldof

Errors found by DSO activation

Hi gurus,
i got the following errors after checking the logs of the DSO activation. Any suggestions??
Thanks. points will be given,
SD
Value " " from characteristic ZM_RMTEXT contains an error at position 1
Message no. BRAIN290
Diagnosis
Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 1 is one of these characters. The value is therefore not permitted.
Note that these characters cannot be displayed and are therefore displayed as '#'. The actual character '#' has the hexadecimal display HEX23.
Procedure
Check the origin of the characteristic value. If possible, change the characteristic value in the source.
Incorrect source text in update routines and transfer routines can also cause this problem.
============================================================================
Value 'B2 1234567 Kabelsatz' (hex. '4232203132333435363720204B6162656C7361747A') of characteristic ZM_MATTAU contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic values by default:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Furthermore, characteristic values that only consist of the character # or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal representation 4232203132333435363720204B6162656C7361747A).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into the system, make the appropriate setting in BW Customizing. Refer to the documentation describing the requirements for special characters and the possible consequences.
For more information on the problems involved with valid and invalid characters, click here.

Hi,
You have invalid characters for the field ZM_MATTAU. Due to these your DSO activation is failing.
The way to resolve this is to write a cleansing routine for that field to strip away the bad characters and only permit the good characters to go through.
If you search the forum you'll get sample codes for the same.
Cheers,
Kedar

BI Dev client inactive & DSO activation problem

Hi SAP Experts,
Am facing some problems in DSO activation. Firstly the Business content DSO was not activating .So I had to activate the Datasources on the R/3. There were no errors in the job log but the DSO was still inactive. On trying to manually activate it , its stated that the BI Dev client was inactive. So I went to the Source Sytems tab, activated the BI client but it failed showing the following error messages:
1.EDI:Partner profile not available-> A partner profile could not be found with the following key:/IBDCLNT010/LS/
This involves the key fields of the table EDPP1: PARNUM.PARTYP
2.Entry in outbound table not found-> A partner profile could not be found with the following key:/IBDCLNT010/LS/RSRQST///
This involves the key fields of the table EDP13:RCVPRN,RCVPRN,RCVPFC
3.Entry in inbound table not found........LS/RSINFO :
4.Similar to error 3 :...../LS/RSSEND
5.Destination IBDCLNT010 has incorrect Unicode settings,adjust it to destination:
The unicode settings do not match the source systems.Conversion errors might occur during data transfer.Adjust the destination accordingly.
Has anybody seen this error log before. If so please do let me know your valuable suggestions.
Thanks for taking the time to read this technical concern
Edited by: Prathibha Pillai on Jul 29, 2008 7:58 AM

Hi,
As of 1-4 error messages.
You must define in partner profiles (ts WE20) the message type RSRQST as outbound on BI side and inbound on R/3 side, the message types RSINFO, RSSEND as inbound on BI side and outbound on R/3 side.
Regards,
Alexander

DSO Activation Fails after adding navigational attribute

hi Gurus
I have created a object A using Object B as reference and added Object A into Object C as navigation attribute.
Now my object D which is referenced to Object C also has this object A as attribute and i change to navigational attribute here.
When i try to turn on nav. attribute check box in DSO then DSO activation fails (Error - DS Object Object D__Object A (Master data check) does not exist} and therefore i cant add it as free char. in report. Though i am getting the data in report if i keep dnt turn on nav. attribute option in DSO and activate it.
Thanks
BIT

Hi
Make sure your object A has master data check box checked. For this your referenced object B should have master data check.
Regards,
Venkatesh

How to reduce Time taken by DSO Activation.

Hi
My Inventory Transaction DSO taking nearly 18min for 180,000 records to activate. It means it takes 1 min for every 10,000 records to activate. I think its too much.
Is there any way i can reduce DSO activation time... what are factors that increases the DSO activation Time.
Pls let me know if u have some idea this issue.
Thanks.....

Hi,
Some of the factors which affect DSO activation are
1) Data volume and size of DSO (if the volume and no of fields are more then it takes long time)
2) SID generation(uncheck this if the DSO is not used for reporting)
3) Secondary index (remove unwanted secondary index)
4) No of background jobs and packages siz allocated for activation (check the settings for ur DSO in tcode RSODSO_SETTINGS)
Apart from this it also depends on database performance and other factors
Regards,
Raghavendra.

Deadlock when deleting from rsstatmanpsa during DSO activation

We are experiencing intermittent Oracle deadlocks during DSO activation in our BI system. The deadlocks occur when the following SQL statement is executed:
      delete from rsstatmanpsa where
             partnr >= l_s_status-rnr_sid and
             psa     = l_s_status-dta.
This is at line 83 of the SET STATUS method of class CL_RSSM_STATMAN. (See below for runtime error details.)
When these errors occur the background job for the DSO activation is cancelled with the message ABAP/4 processor: DBIF_RSQL_SQL_ERROR. Strangely, when this occurs as part of a process chain, the status of the process variant does not get updated until/unless someone displays the process chain log, at which point the status changes and follow-on events are triggered. In other words, the process chain does not seem to be receiving word that the DSO activation process has abended, so we do not receive alerts that a problem has occurred.
Has anyone else experienced this issue?
Thanks,
Bob
P.S. We are running BI 7.0, Patch Level 15 on Oracle 10.2.0.4.0
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "SET_STATUS" "(METHOD)", nor was it propagated by a RAISING clause.
How to correct the error
Database error text........: "ORA-00060: deadlock detected while waiting for
resource"
Internal call code.........: "[RSQL/DELE/RSSTATMANPSA ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"CL_RSSM_STATMAN===============CP" or "CL_RSSM_STATMAN===============CM008"
"SET_STATUS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SET_STATUS" "(METHOD)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Information on where terminated
Termination occurred in the ABAP program "CL_RSSM_STATMAN===============CP" -
in "SET_STATUS".
The main program was "RSPROCESS ".
In the source code you have the termination point in line 83
of the (Include) program "CL_RSSM_STATMAN===============CM008".
The program "CL_RSSM_STATMAN===============CP" was started as a background job.
Job Name....... "BI_PROCESS_ODSACTIVAT"
Job Initiator.. "ALEREMOTE"
Job Number..... 05302800
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "SET_STATUS" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "CL_RSSM_STATMAN===============CP "; its source
code begins in line
1 of the (Include program "CL_RSSM_STATMAN===============CM008 ".
Source Code Extract
Line
SourceCde
53
if i_with_internal_check is initial.
54
l_s_status = i_s_status.
55
call function 'RSSM_GET_TIME'
56
importing
57
e_timestamps = l_s_status-ts_last_changed.
58
if l_s_status-ts_proc_started <= '10000101000000'.
59
l_s_status-ts_proc_started = l_s_status-ts_last_changed.
60
endif.
61
if l_s_status_exist is initial.
62
insert rsstatmanstatus from l_s_status.
63
if sy-subrc <> 0.
64
message x000.
65
endif.
66
else.
67
modify rsstatmanstatus from l_s_status.
68
if sy-subrc <> 0.
69
message x000.
70
endif.
71
endif.
72
delete from rsstatmanpart where
73
rnr      = l_s_status-rnr and
74
dta      = l_s_status-dta and
75
dta_type = l_s_status-dta_type.
76
select single * from rsstatmanpsa into l_s_psa where
77
rnr      = l_s_status-rnr and
78
psa      = l_s_status-dta.
79
if sy-subrc = 0.
80
delete from rsmdatastate_psa where
81
psa = l_s_status-dta and
82
type = l_s_status-dta_type.
>>>>>
delete from rsstatmanpsa where
84
partnr >= l_s_status-rnr_sid and
85
psa     = l_s_status-dta.
86
else.
87
select single * from rsmdatastate_psa into l_ds_psa where
88
psa = l_s_status-dta and
89
type = l_s_status-dta_type.
90
if sy-subrc = 0 and l_ds_psa-sid_checked > l_s_status-rnr_sid.
91
delete from rsmdatastate_psa where
92
psa = l_s_status-dta and
93
type = l_s_status-dta_type.
94
delete from rsstatmanpsa where
95
partnr >= l_s_status-rnr_sid and
96
psa     = l_s_status-dta.
97
endif.
98
endif.
99
if i_with_commit = 'X'.
100
call function 'DB_COMMIT'.
101
endif.
102
endif.

Walter,
Thanks for the suggestion. This is the same recommendation I just received from SAP.
We are currently in the midst of regression testing for a major release, so cannot implement these corrections immediately. I'll post again after we implement the corrections and let you know if they solve our problem.
Thanks again.
Bob

DSO Activation failed

HI,
Process step dso activation is failed due to Runtime error...I Checked in JOB Log it says ABAP/4 Processor : MESSAGE_TYPE_X and job is cancelled. So i went to ST@@ Tcode and released the dump. and again repeated the failed step.then it again failed due to same.Please tell me how to fix this issue.
Regards,
Swathi

Hi,
Please check the following threads, an SAP note has to be applied:
Loaded for 4 times same dump in BI system
DSO Activation Dump
Thanks,
Arminder

DSO Activation

Similar Messages

Maybe you are looking for