Monitor for DSO Activation

Hello friends ...
I need to monitor the activation of a DSO object. the load of the DSO is complete, the activation process is running, but not many take for complete activation.
thanks everyone!

HI Cesar,
I would think that the activation of the DSO request would depend upon the things like
1.No:of free processess
2.Current load on the system
3.Activation of requests in parallel
As a first go please check the background job for activation and check for the log ,it would have a begin time and end time.
I would also suggest you to do the following.
1. Please check the package size, usually a constant package size is used for all loads.
2. for a previous load in the DSO check the actiavtion log of a successful request and then you can have a fair idea as to what time a request for activation takes.Activation log is the icon next to monitor icon in the manage screen of DSO.
Note: The time shown in the manage is the time for extraction and loading into new table before activation.
Also I would suggest you to check table RSODSACT, this gives some information on activation of requests.But not sure if the data is correct..
Regards,
James Harold.

Similar Messages

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

Requested End Deadline monitoring for Background Activity Step

Hi All,
Workflow for MSS Position change has been implemented in the system.
When a request was created thru Portal the Workflow was triggered but it got stuck.
I found that in a background activity step there is a requested end deadline monitoring which was reached.
Since it is a background activity there is no agent assigned, then what could be the reason that the deadline was reached ?
Can anyone tell me when is the Requested End deadline triggered ?
Regards,
Radhika.

Hello,
Yes, if it's workitem creation time + 1 minute then it means the deadline (any deadline - Latest End, Requested End, Requested Start etc, they're all the same, they just have different names) gets triggered.
What happens next depends on how that deadline has been defined - it may just send a message to someone and do nothing else (ie it leaves the background process running). Or it may be a modeled deadline set up to end the process. Have a look in the Requested End tab to see what it does.
regards
Rick Bakker
Hanabi Technology

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

DSO activation issue

hi gurus,
we have started facing problem in bw system suddenly for dso activation.
earlier it was running fine for 2 million records it used to take ard 3600 sec to complete but now its running for 10-11000 sec and getting failed.even for dso whwre its 20000 records its failing wit message "bi_bctl failed due to missing confirmation"
and it is happening very frequently.we have maintained settings as 3600 sec -max wait time in RSODSO_SETTINGS.
But nthng is wrkng and now problems seems to be more complex as even dtp loads are running for long time to load data to cube
can anyone guide us as when we check in SM50 BGD process are also free so not able to find root cause as several dumps are also cmng in ST22.what can we ask basis team to check ?any parametrs.setitng.etc
Any quick help appreciated
thanks
nilesh

Hi
Check how many parallel processes(child jobs) you have for this DSO activation step. this will happen due to non availability of background processes.
Check you have enough background processes and try to decrease the number of child jobs.
if you are running DSO activation PC, make sure you have not selected option "automatic activate the data upon loading" in DSO.
check below blog
DSO activation job log and settings explained
Regards,
Venkatesh

Disable monitoring for the Interface

Hello,
In the Cisco Prime 2.1 I want to disable monitoring for the active interface in the device (router, switch, Nexus device), but the interface must stay in active state. How to do this? Thank you and best regards, Darko

This is a bit surprising, since the logical disk discovery only runs once a day, plus it's not supposed to discover network and removable drives.
That means that your disks are mounted when the discovery runs and that they appear as "real" logical disks...
Unfortunately there is no "sync time" parameter for this discovery, which would have allowed you to specify the time of the day at which the discovery runs; thus allowing you to set a time at which you know the drives are not mounted.
Is there any other parameter that could help identifying these specific disks, besides their letter, so you could add them to a dynamic group?
Otherwise, what you could maybe try is to create your own logical disk discovery based on the native one, but with specific settings that would exclude your drives and then disable the native discovery.
But this again implies that you have something that would let you identify specifically your mounted drives... Also the native discovery is a quite complex VBS, I wouldn't actually recommend disabling/modifiying it.
Maybe I could have another idea with more details about your environment...

DSO Activation - Monitoring Status

Hi,
I would want to monitor the status of DSO activation of M-->A, just like the data load as each package of records once it gets update to the DSO we could see in the request monitor, is there any way where i could monitor activation of records likewise.
Thanks,
Mani

Hi Mani,
There are 3 ways:
In the manage tab of the DSO, There is a button called "LOGS" beside the monitor button.
Click that button, where you can get the total log for the ACTIVATION of the DSO.
And also if you want you can check in SM37 by giving the name as: BI_ODSA*
and one more option is you can check in t-code SLG1 by providing the input as:
1. Object: RSSM
2. Subobject: MON
3. EXTERNAL ID: -ODSAC-"ODS NAME"
Give user id, time.
Select all logs.
and then you can get the log for the activation.
Regards,
Ravi Kanth

DSO activation in Production

Hi Experts:
I added two new fields in DSO in dev and my transports are moving in production. As a cut-over activity I have to delete data in DSO and the the PC will run to load data in DSO. My question is:
In production do I need to activate the DSO request manually after the DTP monitor is green as we do it in Dev and in Quality?
Please reply.
thanks!

Hi,
As you know that standard DSO is having 3 tables 1, New table 2, Active table and 3. Changle log table.
After executing DTP data will be moved to new table. At the time of activation data will be moved to other 2 tables.
In your case
1, If you are loading the data manually then you need to activate the DSO request manually to move the data from New table to Active table/Change log table.
or
2, If you are using this loading step in process chain then Activate DSO will be autmatially selected with the DTP step for DSO. So no need to include do it manually. If the activation step fails then you can activate the DSO request manually or you can directly repeat the load step after fixing the error.
Hope this will helpful.
Please suggest me if i'm wrong.
Regards
AG

DSO activation step has been failing if i activate from process chain

Hello Frnds,
one of the DSO activation step is failing from process chain.
Problem : if i do the activation from PC then only it is failing
If i do the DSO activation manually then it is fine .
Kindly provide your suggestions on this issue.
Thanks & regards
Ravi

Hello Lavanya,
below are the logs for ur reference & process monitor is not genereated
log from Process Tab:
Cannot activate request 0000015877(REQU_4E3YPXSZ5F73H6ZNFZJYWMVJH) of DataStore object ZXXXX
Activation of M records from DataStore object ZOGSDRCA terminated
Job log:
Job started
Step 001 started (program RSPROCESS, variant &0000000015318, user ID ALEREMOTE)
Cannot activate request 0000015877(REQU_4E3YPXSZ5F73H6ZNFZJYWMVJH) of DataStore object ZOGSDRCA
Activation of M records from DataStore object ZOGSDRCA terminated
Cannot activate request 0000015877(REQU_4E3YPXSZ5F73H6ZNFZJYWMVJH) of DataStore object ZOGSDRCA
Activation of M records from DataStore object ZOGSDRCA terminated
Entire chain now has status 'A'
Process Activate DataStore Object Data, variant Activate Data ZOGSDREC has status Undefined (instance )
Process Generate Index, variant Generated from DROPINDEX ZDELETEREC_CAUSE_INDEX has status Undefined (instance )
Process Generate Index, variant Generated from DROPINDEX DELETE_INDEX_ZCGSDREC has status Undefined (instance )
Process Data Transfer Process, variant ZOGSDREC -> ZCGSDREC has status Undefined (instance )
Process Data Transfer Process, variant ZOGSDRCA -> ZCGSDRCA has status Undefined (instance )
Process Delete Index, variant Delete Reclamation causes' index has status Undefined (instance )
Process Delete Index, variant Delete index of ZCGSDREC Reclamations has status Undefined (instance )
Process Start Process, variant Start Reclamation delta load has status Completed (instance 4EQ978RV7JE1BU3MT2YB20A3X)
Process Execute InfoPackage, variant 2LIS_05_Q0NOTIF Delta has status Successfully completed (instance REQU_4EQTTCCMY2XEEPL99XGE9EECT)
Process Execute InfoPackage, variant 2LIS_05_Q0CAUSE Delta has status Successfully completed (instance REQU_4EQG4DHZ6JD3K5UZCR5WP16P9)
Process Data Transfer Process, variant 2LIS_05_Q0NOTIF / EQ2CLNT210 -> ZOGSDREC has status Undefined (instance DTPR_4EQ97CM4OU8SN3TPQ44G2ZMZX)
Process Generate Index, variant Generated from LOADING ZPAK_4BFDG83ZVZM4MDUC6L71H1 has status Successfully completed (instance INDX_4EQ97IDIWSIXM0EU3NVNMGOBX)
Process Activate DataStore Object Data, variant Generated from LOADING ZPAK_4BFDG83ZVZM4MDUC6L71H1 has status Ended with errors (instance ODSA_4EQG4KJGK99HMTOSPBB5WU0BX)
Job finished
Here i am giving process types sequence :
Infopackage -> Create index-> DSO activation.
does this create index is generating any issues ?
Regards
Ravi
Edited by: BIuser on Aug 10, 2009 1:13 PM
Edited by: BIuser on Aug 10, 2009 1:13 PM

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

Error while creating transformation for DSO in SAP BI

While creating a transformation for DSO in SAP BI, I got an error "Data source xxx (FS_xxx) does not exist in version A". I would like to know what this error is all about and how to resolve this issue.
Thanks.
Bhusan

Hi Bhusan,
You have to activate your datasoure to make it as an ACTIVE version.
SO in RSA1>Modelling>Datasouces--> find your datasource name and activate it first.
Then create your transformation and continue with other steps.
Hop it helps
Regards,
Arun.M.D

Monitor for DSO Activation

Similar Messages

Maybe you are looking for