Error in DSO activation

HI Guys,
I ran a DTP to transfer data to a DSO (Data target) from R/3. The DTP works fine but when i try to activate the DSO, i get an error (red light). There is no error message or any clue. When i look in the monitor, it shows me all green lights. Where is my error? Is there any way I can debug the activation process?
Thanks & points will be given,
SD

Hi Sebastian,
did you check the application log? You can go there by managing the dso, clicking on activation and in that popup, there is a button for logs. Another way: slg1, object rssm, subobject mon and external identifier ODSAC<name of your dso>*.
Additionally a look at st22, sm37 and/or sm21 might also be of some help.
regards
Siggi

Similar Messages

No fiscal year variant specified - error upon DSO activation

In my DSO I need 2 fiscal periods - document day period and payment day period. For the first I use 0FISCPER IObj, for the second I've created CFISCPER (with a reference characteristic 0FISCPER).
CFISCPER has 0FISCVARNT as compounding.
There some occasions then I got payment date, but no document date (prepayment cases). As a result I got NULL value on 0FISCVARNT and error "No fiscal year variant specified" upon activation.
I've tried to create CFISVAR (with a 0FISCVARNT as reference characteristic) but BI doesn't let me switch 0FISCVARNT to CFISVAR in compounding for CFISCPER.
How can I deal this? Maybe there is some option in DSO?
thanx in advance. points will be awarded

Hello,
If you have create payment day period(CFISCPER) as a reference to 0FISCPER, then Fiscal year variant's infomation must be provided.
you can fixed the 0FISCVARNT for the case of no document date using a formula in the transformation,
eg. IF(0FISCVARNT<>'',0FISCVARNT,'K4')
hope it can help.
regards,
K

Getting Shor Dump while DSO Activation

Hi Experts,
I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest me.
Category               Internal Kernel Error
Runtime Errors         SYSTEM_CORE_DUMPED
Date and Time          25.02.2014 18:38:47
Short Text
     Process terminated by signal 10.
What happened?
     Error in the SAP kernel
     The current ABAP program "CL_RSODSO_DATASTORE=====
      terminated because the ABAP
     processor detected a system error.
Thanks
Sunil

Hi,
Take basis team help. error itself saying as related to internal kernel error.
recently any changes were applied on server? if yes then those might be causing.
please refer note - 517824.
Inform to basis team and sort it out.
Thanks

Getting Short Dump while DSO Activation

Hi,
I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest.
The kernel is latest version.
Also we had implemented a couple of SAP Notes while we searched on the SDN and service market place. But still no luck.
Category Internal Kernel Error
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 09.04.2014 16:14:13
Short Text
Process terminated by signal 10.
What happened?
Error in the SAP kernel
The current ABAP program
"CL_RSODSO_DATASTORE=====
terminated because the ABAP
processor detected a system error.
Thanks,
Sameer

Hi,
Yes this happens for a particular DSO only - 0FIAR_O03(DSO)
Also the kernel is the latest one.
I am from Basis. I have checked all the possibilities and have raised OSS message as well.
Thanks,
Sameer

Error occurs while activating a 'Write Optimized' DSO.

I am getting error " There is no PSA for infosource 'XXXX' and source system 'XXX' while activating a newly defined DSO object.
I am able to activate a Standard DSOs, however the error occurs while activating a 'Write Optimized' DSO

Hi,
For write optimised DSO, check if you have tick the uniqueness of the records. If you check that and if there are two same records coming from source in one go, then you will get error
From SAP help
You can specify that you do not want to run a check to ensure that the data is unique. If you do not check the uniqueness of the data, the DataStore object table may contain several records with the same key. If you do not set this indicator, and you do check the uniqueness of the data, the system generates a unique index in the semantic key of the InfoObject. This index has the technical name "KEY". Since write-optimized DataStore objects do not have a change log, the system does not create delta (in the sense of a before image and an after image). When you update data into the connected InfoProviders, the system only updates the requests that have not yet been posted.
Thanks
Srikanth

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

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

Write optimized dso activation error

The dictionary activation module could not activate all objects.
System Response
A statement is produced from the activation module log with warnings and error messages.
Enhancement category for include or subtype missing.....help me solve this issue....

Hi,
We had similar error during cube activation but we didn't change Enhancement catagory rather we have deleted additional indexes created on different dimension tables in SE11.
Go to se11 and check the number of indexes created, use Index button on tool bar. Delete unwanted indexes and then try to activate again.
Reards,
Durgesh.

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

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

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

Iam getting an Error [Error occured during activation process]

Hi ALL,
Iam trying to load the data in DSO from CSV file,I am facing an Error as [Error occured during activation process] please suggest
Thanks & Regards
Sameer Khan

Hi Sameer,
let us play the gussing game as there is no clear error statement...
Activation error: May be due to some special character (like # ! etc), you can include them in RSKC or correct that record from PSA.
SID Error: Load and Activate your Master Data.
There may be lot many situations...hope to have your exact error posted so that more elobrate help can be provided.

Error in DSO activation

Similar Messages

Maybe you are looking for