ODS Activation error

Hi All
In BI 7.0, I am facing an error while activating the ODS. The data has been loaded successfully by the DTP. But its turning RED in the activation. When i checked the log,
the error is under SID Generation.
In data Pkt 2 : "No data can be loaded for which no masterd data exists. No SID found for value 'xx' of char 0soursystem."
In data Pkt 3 : "No data can be loaded for which no masterd data exists. No SID found for value 'xxxx' of char Zcustomer."
When i checked the data, everything looks fine. I see the master data too. So why this error comes ?
2) Why SIDs are created on activation ?
3) Is it pre-requisite to have the master data ready in the MD tables, before loading the data into ODS ? otherwise, will it fail ?
4) when can i remove the option for BEX reporting for my ODS. In BI, I dont see that option in ODS.
Any help pls ?
thx
venkat

Hi..............
First when we load a ODS...........first it goes to activation queue.........when we activate the ODS then only it goes to active table................DUe to this SID issue always come in time of activatio..............during data load notjing will happen...............In case of a Infocube load will fail...............
Now SID...........While creating a master data.........in the MASter data/Text tab..........if you make it master data enable...............then automatically it will linled with four tables..........
Attribute
Text
Hierarchy
SID.....................
So when we are loadind Master data SID will generate............
Here this error came because...........SID does'nt exist for that particular value...............
So first you load the master data.........if possible do full upload..........
If then also load fails............
Then go to source system..........copy the datasource of the master data IP...........go to RSA3 in the source system................Check the data source for that particuler value.........whether value exist in the source system or not..........
Hope this helps you.........
Regards,
Debjani........

Similar Messages

ODS Activation Error:characteristic 0CALMONTH is not plausible

HI,All:
i have upload data from flat file to ODS successfully,but i am get following error when i try to activation data in this ODS.
- Error getting SID for ODS object ODS_DX01
- Value '000120' of characteristic 0CALMONTH is not plausible
- Error when assigning SID (details in long text)
- Activation of data records from ODS object ODS_DX01 terminated
How should i get rid of this error. Any idea would be appreciated.
Regards
Jerry

Hi Sandeep,
Appreciate if u dont copy other posts..and use it as ur own..!
ODS Activation Error
(u can freely post a link to other's posts..with due credit to the author)
Vishvesh
Message was edited by:
Vishvesh Bahirat

ODS ACTIVATION ERROR IN BI 7.0

Hi,
Iam Facing the problem in activation of ODS....
When i loaded the data in ODS manually..The data was succesful and activation also ran well...
But when see the same in the processs chain ....Activation of ods is in red...
I repeated it...but still stays in the same red status...and gives the message
ODS ACTIVATION FOR 'ODS NEME' TERMINATE.
This is in BI 7.0...
Can anyone p[lease guide me what is the actual problem...
Thanks,
Shashikanth.

Hi Shashi,
What's error mesg shows?
Probably, this is becos of RFC connection failed.
Regards
Sanjiv

ODS activation error after system copy

Hi all,
we are getting error on activation of request in ODS. I ran RSRV tests on the ODS "Check How Up-To-Date the Generated Programs of an ODS Object Are "
Result was :
Activation program is not current
Difference in line: 1469
Lines in temporary program: i_logsys = 'BWS300'
Lines in active program: i_logsys = 'BD2300'
Activation program has to be generated again
I had clicked Correct Error in RSRV and the problem was resolved.
I have also done the following steps as mentioned in sap note 518426, but did not solve my problem
Execute transaction "RSSGPCLA".
Set the status of the programs belonging to program classes
"RSDRO_ACTIVATE", "RSDRO_UPDATE" and "RSDRO_EXTRACT" to "Generation required".
To do this, select the program class and then activate the "Set
statuses" button. Important: Reset the three named program classes
only.
I have this issue with all ODS objects. It is very time consuming to run the above RSRV task for all ODS objects.
Is there any program that I can run to regenerate activation program for all ODS objects?
Thanks,
Naveen
Edited by: Naveen Ketha on Mar 1, 2008 10:36 AM

Hi Naveen,
Not very sure it would resolved the issue ,but have a look at note# 886102.
Summary
Symptom
The source system is hard-coded in the generated program for the
DataSource. This leads to problems after the logical name of the source
system (BDLS) is converted.
More Terms
Transaction BDLS
Cause and Prerequisites
This problem is caused by a program error.
Regards
Mr Kapadia
Edited by: Mr Kapadia on Apr 4, 2008 3:07 PM

Process chain - ODS Activation error

Hello All,
I have a process chain which has the following data load sequences:
Load data to ODS
Activate ODS
Load data to ODS2
Activate data ODS2
Load data to ODS3
Activate ODS3.
Used the Program to RSPC_SYNCHRONOUS_RUN to schedule the process chain in Background.
When the process chain is executed in background it loads the data to ODS1 and Activation process is not happening. It registers short dump like shown below at the end. But when i execute the same process chain in RSPC, Schedule option with Start variant set to immediate, it is activating the ODS Data and completes the process chain Succesfully.
Help me to solve this problem.
ABAP Short dump information:
Invalid interruption of a database selection.
t happened?
Error in ABAP application program.
The current ABAP program "GP4BRKGANFKJY5K2A3ACVGAPTN4" had to be terminated
because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Unable to perform database selection fully.
record.
t can you do?
If the error occurs in debugging mode, you should first run the process
without debugging activated.
If the error persists outside debugging, you must check the application
program more closely.
No error requiring recovery has occurred.
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletiondate.
is especially useful if you want to keep a particular message
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
     neither
    caught nor passed along using a RAISING clause, in the procedure "ACTIVATE_ODS"
     "(FORM)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    One of the database selections included a database commit.
    The selection was then supposed to continue. Before a
    database commit, however, all outstanding database selections must be
    concluded.
    Possible causes in the application program:
    Within a loop (SELECT/LOOP/EXEC SQL), one of the following
    statements is used:
    - MESSAGE (apart from MESSAGE S...)
    - COMMIT WORK
    - ROLLBACK WORK
    - CALL SCREEN
    - CALL DIALOG
    - CALL TRANSACTION
    - SUBMIT
    - BREAK-POINT
    - WAIT
    In debugging mode, a program sometimes triggers
    a "COMMIT WORK" during the database selection. As a result
    this termination may also occur in debugging mode with a correct
    program.
A "COMMIT WORK" during debugging may be due to the following reasons:
1. A program or screen was regenerated
    and updated in the database.
2. Each user needs a private process in debugging mode, but
    the number of available processes is restricted. If this
    limit is exceeded, each debugging step then requires a
    "COMMIT WORK".
The error occurred in a statement that accesses the table "/BIC/AZXOQMATR40 ".
Thanks in Advance.
Points will be assigned.
Regards
M.A

Hi,
If it is a daily process chain u define it on a periodic basis in the variant and it'll run successfully.
I guess the DUMP may be due to less processes at the time u run...It is gving the same in the dump also..
So when u run the chain immediate in the BKGD the ODS will be automatically getting the required processes dailog and bkgd to run according to ur settings and it was successful..
U try to execute the chain using FM: RSPC_API_CHAIN_START and give the tecnical name of the chain under I_CHAIN filed and conitinue...It'll scedule the chain in the BKGD only and if it is a periodic one the chain will be automatically ready for the next run also...
rgds,

ODS activation error after the structure change

Hi all,
      I am getting a short dump with " "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC " error when I am trying to activate an ODS after changing its structure. Do I need to change any setting before loading the data in to the ODS after adding few more fields to it. Exact error says
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"ACTIVATE_SIDS" "(FORM)"
Thanks

The above-described symptom is due to a program error during the transfer of error messages. The problem can occur, for example, if a hierarchy is activated during the activation of an ODS object.
If the indicator 'BEx Reporting' is set for the ODS object, entries are created in the SID tables of characteristics involved during the activation of requests for this ODS object. Newly-created SID values must then be inserted into hierarchy tables. This is not possible for reasons of consistency if a hierarchy is activated at this time. The RRHI_CHAVLS_REQUEST_TO_HIERA function module is used for inserting newly-created SID values in hierarchies.
To simplify the search for the cause of the problem, additional error messages are now displayed in the monitor. If the problem is triggered, for example, by the simultaneous activation of a hierarchy, the error message RH 14 is issued. As described in note 717967, this error message contains the name of the affected hierarchy. If the activation of an ODS object is cancelled due to a serious error, this now also causes additional entries in the log of transaction SM21 (Syslog). These entries start with the character string '> RSDRO':.
Solution
BW 3.0B
           Import Support Package 21 for 3.0B (BW3.0B Patch21 or SAPKW30B21) into your BW system. The Support Package is available whennote 0679665 with the short text "SAPBWNews BW3.0B Support Package 21", which describes this Support Package in more detail, is released for customers.
BW 3.10 Content
           Import Support Package 15 for 3.10 (BW3. 10 Patch15 or SAPKW31015) into your BW system. The Support Package is available when note 0601055 with the short text "SAPBWNews BW 3.1 Content Support Package 15" is released for customers.
BW3.50
           Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available when note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, is released for customers.

ODS activation error( The creation of the export DataSource failed

Hi Friends,
i have a problem activating the ODS. after defining the ODS, when i try to activate the following error is occured
1.The creation of the export DataSource failed
2.RFC connection to source system BWD100 is damaged ==> no Metadata upload
3.Error when creating the export DataSource and dependent Objects
Any help would be appreciated
Thanks

Seems that there are one or more characteristics in the ODS for which one or more attributes may be new or inactive.
Please see SAP Note 597326..Pasting the content below..Solution steps are also given..
Symptom
When you activate or transport ODS objects, the following errors appear in the log:
"The creation of the export DataSource failed". Message number RSBM 035
"Error &1 in function module &2". Message number RSBM 006
"Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
"Error when activating the ODS object &1". Message number RSDODSO 168
Other terms
RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
Reason and Prerequisites
A characteristic involved is active but it is using new or inactive attributes.
Characteristics involved are all characteristics used in the ODS object.
Solution
Check all characteristics involved as described in the following:
Check the Compounding and Attributes tabs in the characteristics maintenance.
All characteristics here must be active. This is displayed by a green icon.
If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again.
cheers,
Vishvesh

ODS activation error"Activation of data records from ODS object terminated"

Hi All,
While activating ODS request I am getting following error
"Activation of data records from ODS object KFI02O50 terminated ".
data load is suceesful for ODS but during activation of the request it is giving error.
I tried to change the status to green manually & then activated the request but still same problem.
Also I tried to delete request & loaded again from PSA & then activated the request but still same problem
If anybody has some solution please let me know.
Thanks in advance
Regards
Sonal

Hi Sonal,
Sometimes when there is erroeneous records that time while activating the Request request get fails.To check this go to manage tab of the ODS there under log u can see the log icon click on that and check y activation got failed..
Assign points if its helpful
Regards,
vid.

Urgent--Strange--ODS Activation Error!

I have DSO Object, When I am loading it get loaded..
While activating I am getting errors.. which is very diff..
say like..
"Process 00004 returned with errors"
"Process BCTL_4AFYBA4.....could not be terminated.Terminate manually"
"Exceptions in substep:With Write Data Package"
"Request set to 'incorrect' in a parallel mode"
Thanx
BI learner

Hai as already said by people use rsodso_settings Tcode
use background option for activation ,also change the parameter of parallel process to 2 and try
should work ...
If still problem persits check whats is the timelimit your basis have set for background jobs ask them to increase to 3600.
Also small suggestion check how many background processes are running and make the workprocess availabe as required..
Goodluck.

Error in ODS Activation

Hi Friends,
I got error when the ODS activating in Process Chain.
The Error Messages are
1. Inconsistent aggregation behavior - activation will be terminated.
2 Activation of M records from DataStore object 0PUR_DS03 terminated
in the data target (ODS) the request are in Red but activated as it is showing Request For Reporting Available flag having Query symbol..means the requests are available for reporting.
What should be the possible reason
How should i rectify it.
Thanks&Regards
Anand

hi,
I have activated ODS manually yesterday. the chain ran today.
But today i got the below error while data is loading into ODS.
Error Message Below.
Runtime Errors         RAISE_EXCEPTION
Date and Time          07.04.2009 03:43:06
Short text
     Exception condition "NOT_EXIST" raised.
What happened?
     The current ABAP/4 program encountered an unexpected
     situation.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     A RAISE statement in the program "SAPLRSSM" raised the exception
     condition "NOT_EXIST".
     Since the exception was not intercepted by a superior
     program, processing was terminated.
     Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Please sugeest to resolve the problem
Regards
Anand

Dump error when doing ODS activation

Hi,
When doing to the ODS activation, out of 500 data packets 1 data packet is not updated its highlighting Red traffic light. After that i selected that incorrect data packet i given manual update sytem is gives ABAP runtime errror MESSAGE_TYPE_X. i checked in SM21 as well as ST22 also it was MESSAGE_TYPE_X.
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 143857 ccdbwprd BIADMIN " generated
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 144123 ccdbwprd BIADMIN " generated
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 144435 ccdbwprd BIADMIN " generated
Transaction Canceled BT 510 ( )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150322 ccdbwprd BIADMIN " generated
Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20090413150322ccdbwprd BIADMIN 0051 )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150639 ccdbwprd BIADMIN " generated
Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20090413150639ccdbwprd BIADMIN 0051 )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150837 ccdbwprd BIADMIN " generated
please give ur suggestion to solve this issue.
Thanks & Regards
Khamesh

please verify the note 852443

ODS activation process random error in process chain

Dear All,
In my process chains, the process of ODS activation is sometimes in error. It is a random error, it is not always the same ODS and process chain.
The message error is DBIF_RSQL_SQL_ERROR.
I noticed that, on right-clic -> Change variant to the process of ODS activation, I have the following message:
"Not all infoobjects can be read".
For information, in the processes of activation of the ODS, the unique parameter is the name of the ODS to be activated.
Thank you very much for your help,
Arnaud

Hi......
Check SAP Note : 631668......
According to this note :
Symptom
This note applies only to BW systems under ORACLE.
Loading data into InfoCubes terminates with an error: ORA 60, "deadlock detected". The monitor log displays the entry "CALLER 70 missing" and the request is flagged as red.
Other terms
Caller 70, DEADLOCK, ora0060, bitmap, indexes, DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
Reason and Prerequisites
In SAP BW, there are two fact tables for including transaction data for Basis InfoCubes: The F and the E fact table.
Unlike the E fact table, the F fact table contains the information about the request from where the transaction data originates.
Therefore, transaction data is always written to the F fact table and the package dimension contains the request to which the loaded data belongs.
Using 'Request compression', the system reads the data of a request from the F fact table and writes it to the E fact table without request ID and compresses.
For good reporting performance, you must keep only the data of a few requests in the F fact table since the F fact table is partitioned according to the key of the package dimension and the data of all requests is always read. Therefore, you should compress the request if you are sure that the loaded data is correct and that you no longer have to delete the request.
When you install BW on an ORACLE database, BITMAP indexes are created on the fact tables to improve the reporting performance of the system.
These have a negative effect on the performance when loading data and the deadlock mentioned above (ORA 60) may occur as a result. The DEADLOCKs occur during parallel insert operations because ORACLE does not support a blocking concept for BITMAP indexes at data record level.
Solution
Before loading movement data, delete secondary indexes from the F fact table and create them again after the loading process. If the F fact table is small, no performance problems occur.
Alternatively, you can also load requests serially into InfoCubes by first loading the data only into the Persistent Staging Area (PSA) and then serially into the InfoCube. If you use the data transfer process (DTP) for loading in BW 7.0, this option is no longer available.
NOTE
This avoids the deadlock problem. However, you should note that after some loading processes, it is necessary to reorganize the BITMAP indexes because they degenerate very heavily and, therefore, the read and writing performance deteriorates dramatically.
Hope this helps you.....
Thanks==Points as per SDN.........
Regards,
Debjani..........
Edited by: Debjani Mukherjee on Sep 29, 2008 3:14 PM

Activation Error in ODS - Record mode 0 unknown (data record REQU_4DPGJKCKN

I created a generic extractor in R3 with a generic delta. In BW, my delta init loads with no errors but when I activate the data in the ODS, I get the activation error.
"Record mode 0 unknown (data record REQU_4DPQ31IK7WM9OTK26S5JMJ6LM/000001/"
I searched SDN but didn't found anything, and I searched help but only found general information about 0recordmode.
Can someone provide a solution and/or some more detailed information about the error message?
Thanks

Hello,
When you have created the InfoSource for the generic datasource, have you added field 0RECORDMODE to the InfoSource? When loading data to a ODS, 0RECORDMODE is essential.
The InfoObject is usually mapped to ROCANCEL (Indicator: Cancel Data Record) field of the extractor. This field is usually present in Standard extractors. But even if the field is not present in your extractor, add it to InfoSource Communication structure and leave it unmapped in transfer rules.
I think this might solve the problem.
Regards,
Pankaj

Error in ODS activation due to # character

For last two days I have been getting the error in the process chain. The process chain stops at ODS activation because the data contains '#'. I have gone SAP Note 173241, which says that # value is allowed in data. Is there any way to remove # from the data. Thanks in advance

It could be hexadecimal char in the load it would display as '#' but actually it would be some hexa char.
Either you can track it based on the log and edit in PSA and see if you can correct it in R3 as well.
We do have some of those come in our various desc fields, just modified a simple FM to strip our the not allowable char that are not in RSKC.
let me know if u need the FM i'm using to strip out hexa
Mayil

Error in ODS activation/export datasource

Hello Gurus,
When I am activating an ODS 0CFM_O01, it gives the foll error. can u pls guide. thanks in advance
DataSource 80CFM_O01 does not exist in source system BWCLNT700 of version A
Error when creating the export DataSource and dependent
Error when activating ODS Object 0CFM_O01
rgds

hi,
take a look oss note 597326-Activating ODS: Error when creating the export DataSource.
base on that note, the activation error coz dependent object(s)-infoobjects not active, to eliminate the error we have to first have all the objects active. you may try in business content installation, collection mode 'manual', put 0CFM_O01, grouping 'only necessary objects', right click 0CFM_O01 and choose 'install all below' then 'install'. hope this helps.
note 597326
Activating ODS: Error when creating the export DataSource
Symptom
When you activate or transport ODS objects, the following errors appear in the log:
"The creation of the export DataSource failed". Message number RSBM 035
"Error &1 in function module &2". Message number RSBM 006
"Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
"Error when activating the ODS object &1". Message number RSDODSO 168
Other terms
RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
Reason and Prerequisites
A characteristic involved is active but it is using new or inactive attributes.
Characteristics involved are all characteristics used in the ODS object.
Solution
Check all characteristics involved as described in the following:
Check the Compounding and Attributes tabs in the characteristics maintenance.
All characteristics here must be active. This is displayed by a green icon.
If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again.

ODS Activation error

Similar Messages

Maybe you are looking for