Error while Activating DSO Data

Hello
I am having a problem, I am getting an Error while activating DSO Data, Data is loaded in DSO succefully but can not be activated with this error
"Activation of M records from DataStore object 0FIAR_O03 terminated"
Thanks

Hi,
The activation would have failed due to varies reasons..
It would be a short dump,check in ST22.
check the job log in SM37 for better understanding of the issue.
Have you loaded the respective master data?
if it is a transaction data load,then the SID is checked at the time of activation and not during loading.
So if the master data is not loaded then the activation would fail.
It can also be due to the system performance at that moment.
Even if the data volume is huge ,there are chances of the activation failing..
Try repeating the activation once again.it might succeed..
Else check the logs to understand the actual issue.

Similar Messages

DBIF_DSQL2_DEFAULT_CR_ERROR while activating DSO data

Hello Friends,
While activating DSO data i am getting 'DBIF_DSQL2_DEFAULT_CR_ERROR' . please suggest me a solution .
Regards
Nilesh

Hi Nilesh,
Try to check the following link:
/message/5657425#5657425 [original link is broken]
And moreover this error occurs during COMMIT or ROLLBACK to "DEFAULT" database connection.
Regards,
Srinivas.

Hexadecimal Error while activating DSO

Hello Experts,
I'm getting following error while activating DSO. I tried ALL_CAPITAL, ALL_CAPITAL_HEXADECIMAL in RSKC. still i'm facing this problem anyone can suggest anything. Iam using BW3.x flow
Value "CC-5012 TRYPSIN/EDTA SOLUTION 100ML" (HEX 430043002D0035003000310032000A00540052005900500053) of characteristic 0CRM_ITDESC contains an error at position 8
Message no. BRAIN290
Diagnosis
Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 8 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.
Thanks
Ajay.D

Hi Ajay,
There are invalid characters at the specified position. Now you ahve 2 options:
1. Either edit the PSA manually and replace this invalid character
2. Use the Funvtion Module 'RSKC_CHAVL_CHECK' . Pass the data to it & get the invalid char replace it with space. This can be called in the filed level routine if the effected info object is identified .
Check out these threads:
Re: Problem with Characters that have a hexadecimal display between HEX00
Re: Invalid Characters issue
Regards
Raj

Error while activating DSO

Hi,
I am getting an error while activating the DSO. I am able to load the data but this occurs when I try to activate the data. I get the follwing error message
"Value "09020751987.44 " from characteristic 0REF_DOC_NO contains an error at position 15
Message no. BRAIN290
Diagnosis
Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 15 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."
Any thoughts how I should correct/

Hi Tanu,
this is an error in the data loaded. If you have used PSA, then try searching for the packet containing this record using the change log table, by request id. (This step is to precisely find the position of the record in PSA).
Now delete the request from the DSO and correct the data in PSA. The issue could be a tab or a space in the reference document feild and then save the data. Reconstruct this packet from PSA and then try activating.
Subsequently let the data team/ user know about the correction in the source system as well, in order to avoid any future failures.
This should correct the issue.
regards,
Naveen.A

Error while Activating ODS data

Hi Experts,
I am getting following error while Activating ODS Request.
Job started
Step 001 started (program RSODSACT1, variant &0000000000142, user ID lsingh
Activation is running: Data target ZINV_MAT, from 7,883 to 7,883
Data to be activated successfully checked against archiving objects
SQL: 10/17/2005 21:04:17 lsingh
ANALYZE TABLE "/BIC/AZINV_MAT40" DELETE
STATISTICS
SQL-END: 10/17/2005 21:04:17 00:00:00
SQL: 10/17/2005 21:04:17 GOELA
BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
'SAPIBD', TABNAME => '"/BIC/AZINV_MAT40"',
ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
GRANULARITY => 'ALL', CASCADE => TRUE ); END;
SQL-END: 10/17/2005 21:04:17 00:00:00
ABAP/4 processor: DBIF_RSQL_INVALID_RSQL
Job cancelled
It's giving DBIF_RSQL_INVALID_RSQL error.
I am loading full upload to the ODS first time.
Any answer will be greatly appreciated.
Regards,
LS

hi LS,
yes contact basis is the right way
try to double click the DBIF_RSQL_INVALID_RSQL if you interest with more detail error info, by viewing the short dump (transaction st22 can be used), transaction sm21 may also helpful, if authorization is granted.

Error While Activating the Data Source in RSA5 T-Code

Hi,
When i tried to inactive the data source in 2lis_11_vahdr it shows "Data Source does not exists errror".
So i went to RSA5 T-Code and tried to activate the data source but there it is throwing the error like "Event with errors Extract in Data Source 2LIS_11_VAHDR".
I have checked the above thing with all the data sources every one are throwing the same errors. Can any one please suggest me how to solve the issue.
Or Is this issue related to Basis People?.
Regards,
Kumar.

Hi Ravi,
1.When i tried to inactive the data source in LBWE T-Code the error is "Data Source 2lis_11_vahdr does not exists ".
2. In RSA5 T-Code while activating the data source the error is "Event with errors Extract in Data Source 2LIS_11_VAHDR".
Regards,
Kumar.

Error while activating Transactional data source

I am facing the below error while activating the transactional data source.
Field Revenue ( Position 7 ): Amount Field in Internal Format, Check Settings.
Can nyone plz let me know.

Hi Reddy,
You might have created the Revenue field Currency as "Fixed Currency" like INR or USD.
In the Datasouce Def - Fields tab you have Internal format for a field then you should have the reference field to specify the external format like 0currency.
In your case you have not taken any reference field 0currency. So you should n't specify the revenue field in Internal format,
As Shashank said, Please change it to External format and Activate the DS.
Thanks
Sreekanth.

Error while activating DSO after loading from another DSO..Production issue

Hello Gurus,
I got an error while activating DSO2 after loading from another DSO1.
DSO1 load and activation was sucessful but while loading from DSO1 to DSO2 load was fine but got error while activating...
>Error when assigning SID: Action VAL_SID_CONVERT table ZWEEK_NUM
>Value u201809u2019 of characteristic ZWEEK_NUM is not a number with 000004 spaces
this theard was posted after searching for related post in SDN.
and i tried Function Module RSODS_CHECK_RSODSACTUPDTYPE but it is not available .. but I used this in BW 3.10u2026..
is their any similar Function Module in BI 7.0 please advice.
We are using SAP NetWeaver BI 7.0
Release- 700 Service level- 017
Thanks in advance
Sandy

sloved the issue......
it was due to wrong data for the related field...
it must be "0009 "
Thanks for ur support. closing the ticket
Regards
Sandy

Error - While activation of Data in DSO

Hi Experts,
I'm facing following error message when tried to activate the data in DSO - The data went through fine in PSA and when triggered DTP to load data in DSO; the monitor showed green but when activated in DSO it's giving following error message. I transfered the global settings but facing the same following error message:
Diagnosis
     An exception wrong_date was raised while executing function module
     RST_TOBJ_TO_DERIVED_TOBJ .
System Response
     Processing the corresponding record has been terminated.
Procedure
     To analyze the cause, set a break point in the program of the
     transformation at the call point of function module
     RST_TOBJ_TO_DERIVED_TOBJ . Simulate the data transfer process to
     investigate the cause.
Procedure for System Administration
Any idea that why it's generating this error message while activating data in DSO. I checked those records in error stack and seems to be a date issue but I checked the factory calendar and check the validity and that's fine and is within the factory calendar data range.
Thanks in advance - you response will be really appreciated.

hi,
as you said the global settings were done,
try the global settings once again then delete the PSA(if records were less) nd load from source and then load to target.
this may solve if all settings were fine.
if records were huge in PSA, try correcting the records in error stack after allowing the good records to the target.
Ramesh

SQL error while activating DSO and loading Mater Data

Hello Experts,
we are having process chains which include process activating DSO and loading to Master data,
while executing achai, we are getting error:
An error occurred during confirmation of process 000008. See long text
Message no. RSODSO_PROCESSING024
Diagnosis
Note the detailed system message:
An SQL error occurred when executing Native SQL.
when i go to T-Code: ST22
the diagnosis is below:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          20.05.2010 22:18:02
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Could you please help me out how can i deal with this issue, .
Regards
Sinu Reddy

it seems that the target you're loading to is already locked by another load...if it concerns a master data is also possible that the master data is locked by a change run. check your scheduling and make sure you don't load the same target at the same moment...
M.

Error while activating DSO ....date is not possible....

Hi all,
While activating the DSO ,I am getting the following error: Value '20022009' of characteristic 0DATE is not possible
In FEB 20/02/2009 is possible ...but why system giveing this message...?
Any suggessions...on this..
Thanks....Bk
Edited by: BK BI on Feb 24, 2009 9:39 AM

Hi BK,
Looks like in your case 20 is being considered as month which is obviously invalid hence no SID could be generated for 0calday and hence the DSO fails when activation.
Now as Daya and anil mention you could change the date to format yyyymmdd and try reloading the file.
The general principle would be go to menu settings ---> status and check the logged on date ...the format being shown to you is the format you can try loading in.
Or go to System --- > User profile -
> Own data --->defaults tab .... check the data format there and enter the value in that format in your file..
Hope it helps,
Regards,
Sunmit.

Error while activating the data source.

Dear all,
We are using the BI version 7.00 - i have a problem i.e., while creating the infopackage for the data source
0PM_OM_OPA_2 the following error is displayed.
"No active transfer rule for DS 0PM_OM_OPA_2 and ....source system CLNTDEV400; create first..."
Moreover the data source is found to be in version "M" - while activating the same when in click on the display/change icon , the following error is popped up.
"You can only edit 3.x DataSources using transfer rule
maintenance Do you want to create the transfer rules now?"
What could be the reason for this error. What are the things that are to be done to replicate the data and pull data?
Valid experts comment is expected in this regard.
Regards,
M.M

Hi Magesh,
Replicate your data source in BW and then right click onit and choose Assign Info source, it may take you to BC wherein you may need to install the Transfer Rules and related info objects etc.... Once you maintain this data source in the source system then you can create an info pack withput any extra effort.
Hope it helps..

Error While activating master data

Dear All,
I am getting an error while updating the master data.
Attributefrom characteristic A0SUBBRD not (actively) available
Attribute A4INNOCAT from characteristic A0BRD not (actively) available
Attribute A0BRD from characteristic A1MATR3 not (actively) available
Help me about to solve this issue
Thank you

Hi,
You are getting this error bcoz the mentioned info objects in the log are not active in the BW system.
make sure the characteristics are active and available in BW system before updating master data.
In which system are you facing this issue 9 DEV or QA or PROD)?
Have you collected all the objects while transporting? Try to retransport the objects it will work fine.
Regards
KP

Process Chain Error while activating DSO

Hello.
1st, let me say that I'm pretty new to BI so I apologize for the stupid question :-S
I have a process chain (Warehouse Mangement) that failed this morning at the DSO data activation step. It's simply because some entries have lowercase value in a field that should not. I know how easy this is to fix in the transformation but my problem is more on how to fix the actual fail of the process chain. Can I edit the "non-activated" data in the DSO (only 2-3 records that I need to put in uppercase) and "repair" my process chain or should I proceed another way?
Thanks for your help.

Hi John.
If guess your Process Chain process ended in "Red color". Once you fix the error you can try to make "right-click" on the process with error and select "Repair". If this operation is "supported" by the activation process you won't have error.
But I really believe that you'll have to erase the request and launch the complete process (o set of related processes) once again. It's possible that the data you want its already in the NEW-DATA table of your ODS.
This tables is the following. /BIC/A<your ods tech-name>40
Hope it helps
gdmon.-

Error while activating the Data in DSO

Hello,
We moved huge amount of FI data from datasource to DSO. After moving all the data, we tried to activate the data. But the mistake we did is we activated all the requests at one go. (my assumption) It turned all the request to Red. The job log says SQL error.
Is there any way of solving this issue without deleting the data. Data load will take too much time and we would like to avoid it if possible.
Waiting for inputs!!!
Regards,
Abhishek

yes a Dump was triggered.
Database error text........: "ORA-12801: error signaled in parallel query
server P007#ORA-01652: unable to extend temp segment by 2560 in tablespace
PSAPTEMP"
Internal call code.........: "[RSQL/FTCH//BIC/AYEPSPFI140 ]"
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_RSODSO_ACTIVATE_REQUESTS===CP" or "CL_RSODSO_ACTIVATE_REQUESTS===CM00D"
"ACTIVATE_DATA_FROM_QUEUE"
Edited by: Abhishek Nishis on Oct 12, 2009 10:54 PM

Error while Activating DSO Data

Similar Messages

Maybe you are looking for