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

Similar Messages

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

DSO activation failed due to creation of the export datasource failed

hi experts,
i am activating DSO, but failed. Cause is "The creation of the export DataSource failed"
there are many threads in the forum saying restoring the BI myself source system can address it, I tried many times, but failed.
I used program RSDG_ODSO_ACTIVATE to activate an already activated DSO, it returned same error and the original activated DSO turned into inactivated. So I guess there must be something wrong with the setting.
please advise, thanks!
attach error info:
The creation of the export DataSource failed
Message no. RSBM035
Diagnosis
The system could not create DataSource .
System Response
The metadata for a DataSource must be created while the export InfoSouce is being generated. An error occurred at that time.
Procedure
Consult the appropriate developer (function module: RSA1_OLTPSOURCE_GENERATE).
The delta process ODS does not exist
Error when creating the export DataSource and dependent Objects
Error when activating DataStore Object ZFIM_D09

Hi,
As I read the system RESTORE option should resolve your issue. From RSA1 try to restore your source system and try to active your DSO again.
Regards,
Durgesh.

DSO Activations failed due to No active export DS

Hi Expert,
The DSO loads with no problem, but the Activate step fails with error message "No active export DS (DS:**,LS:**) for DSO ***. Activity canceled"
We solved the issue by running this abap program RS_TRANSTRU_ACTIVATE_ALL..
But still missing the root cause for issue .
I am having this problem for several DSOs in several different chains.
Thanks,
Krish

Generating Export DataSources for InfoProviders
The export DataSource is needed to transfer data from a source BI system into a target BI system. The user can use the selected InfoProvider as a DataSource for another BI system.
1. In the Data Warehousing Workbench in the BI source system, choose Modeling and select the InfoProvider tree.
2. Generate the export DataSource using the context menu of the user InfoProvider.
To do this, choose Additional Functions -> Generate Export DataSource.
The technical name of the export DataSource is made up of the number 8 together with the name of the InfoProvider.
The export DataSource is needed to transfer data from a source BI system into a target BI system. The user can generate an export DataSource for master data, and thus for individual InfoObjects. By doing this, all the metadata is created that is required to extract master data (all attributes, texts, and hierarchies) from an InfoObject.

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

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

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 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

Dso activation is not happening

HI guru's,
I am loading the data to dso and manually activating the request ,it is taking long time and finally not activating
dso activation is always failing , Iam not able to figure out the problem , please help me out.
After some time the job is failed and showing the message
"Activation sid for datastore object changed from 0 to 68"

Hi,
There are a couple of places where you can see the activation progress.
1) To start with SM37 job log > (give BI_PROCESS_ODSACTIVAT or BI_ODSA*)
and it should give you the details about the activation job. If its active make sure that the job log is getting updated at frequent intervals. If its completed check the log for ODS activation.
2) For very huge number of records SM37 job log may not get update frequently. In that case you have a workaround.
Go to contents > Active Data table > No. of entries > This will keep on increasing at frequent intervals.
3) SM66 > Get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. See if its accessing/updating some tables or is not doing anything at all.
4) Go to Activate button in Target > Request tab. Inside you can see a job log button. It will also show some log regarding the last activation.
5) If the Reporting icon has appeared near the request id in ODS. If it appears that may indicate that request is available for reporting
6) Check the request status in these tables.
Table RSICCONT table contains the requests that are actually loaded in a target.
Table RSMONICDP contains the request id of the fact table.
Table RSODSACTREQ contains information if an ODS is available for reporting/deleting inactive requests also possible.
Table RSODSACTUPDTYPE.
Check and let us know.
Hope this helps.
Thanks,
JituK

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

Office 2013 pro plus activation fail on windows 8

hi guys
I have issue about getting Office 2013 pro plus activation fail on windows 8 via KMS server.
When I test using KMS server via nslookup -type=srv _vlmcs._tcp all looks good with corporate KMS server.
Activation fine with windows 7 environment
Any idea
This topic first appeared in the Spiceworks Community

Hi
We recommend you download it from the website and extract it again to make sure your source install is complete.
Run setup.exe as administrator then try the install.
If the issue persists, refer to the article on General troubleshooting for installing Office 2013 and Office 365:
http://support.microsoft.com/kb/2822317
Regards
Tylor Wang
TechNet Community Support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

DSO Activation failed

Similar Messages

Maybe you are looking for