31 ODS Activation Failed.
31.1 Why does the error occur?
• During data load in ODS, It may happen sometimes that the data gets extracted and loaded
completely, but then at the time of the ODS activation it may fail giving status 9 error.
• Or due to lack of resources, or cause of an existing failed request in the ODS. For Master Data it is
fine if we have an existing failed request.
• This happens as there are Roll back Segment errors in Oracle Database and gives an error ORA-
00060. When activation of data takes place data is read in Active data table and then either Inserted
or Updated. While doing this there are system dead locks and Oracle is unable to extend the extents.
31.2 What happens when this error occur?
• The exact error message would be like “Request REQU_3ZGI6LEA5MSAHIROA4QUTCOP8, data
package 000012 incorrect with status 9 in RSODSACTREQ”. Some times it may accompany with
“Communication error (RFC call) occurred” error. It is actually due to some system error.
• The message appears in the Job Overview in RSMO, or in “Display Message” option of the Process
in the PC.
• The exact error message is “ODS Activation Failed”.
31.3 What can be the possible actions to be carried out?
• Whenever such error occurs the data is may or may not be completely loaded. It is only while
activation it fails. Hence when we see the details of the job, we can actually see which data package
failed during activation.
• We can once again try to manually Activate the ODS, here do not change the QM status as in
Monitor its green but within the Data Target it red. Once the data is activated QM status turns into
Green .
• For successful activation of the failed request, click on the “Activate” button at the bottom, which will
open another window which will only have the request which is/are not activated. Select the request
and then check the corresponding options on the bottom. And then Click on “Start”
• This will set a background job for activation of the selected request.
• Monitor the load for successful completion, and complete the further loads if any in the Process
Chain.
• In case the above does not work out, we check the size of the Data Package specified in the
InfoPackage. In InfoPackage -> Scheduler -> DataS. Default Data Transfer. Here we can set the size
of the Data Package. Here we need to “reduce” the maximum size of the data package. So that
activation takes place successfully.
• Once the size of the Data Package is reduced we again re trigger the load and reload the complete
data again.
• Before starting the manual activation, it is very important to check if there was an existing failed
“Red” Request. If so make sure you delete the same before starting the manual activation.
• This error is encountered at the first place and then rectified as at that point in time system is not
able to process the activation process via 4 different Parallel processes. This parameter is set in
RSCUSTA2 transaction. Later on the resources are free so the activation completes successfully.
31.1 Why does the error occur?
• During data load in ODS, It may happen sometimes that the data gets extracted and loaded
completely, but then at the time of the ODS activation it may fail giving status 9 error.
• Or due to lack of resources, or cause of an existing failed request in the ODS. For Master Data it is
fine if we have an existing failed request.
• This happens as there are Roll back Segment errors in Oracle Database and gives an error ORA-
00060. When activation of data takes place data is read in Active data table and then either Inserted
or Updated. While doing this there are system dead locks and Oracle is unable to extend the extents.
31.2 What happens when this error occur?
• The exact error message would be like “Request REQU_3ZGI6LEA5MSAHIROA4QUTCOP8, data
package 000012 incorrect with status 9 in RSODSACTREQ”. Some times it may accompany with
“Communication error (RFC call) occurred” error. It is actually due to some system error.
• The message appears in the Job Overview in RSMO, or in “Display Message” option of the Process
in the PC.
• The exact error message is “ODS Activation Failed”.
31.3 What can be the possible actions to be carried out?
• Whenever such error occurs the data is may or may not be completely loaded. It is only while
activation it fails. Hence when we see the details of the job, we can actually see which data package
failed during activation.
• We can once again try to manually Activate the ODS, here do not change the QM status as in
Monitor its green but within the Data Target it red. Once the data is activated QM status turns into
Green .
• For successful activation of the failed request, click on the “Activate” button at the bottom, which will
open another window which will only have the request which is/are not activated. Select the request
and then check the corresponding options on the bottom. And then Click on “Start”
• This will set a background job for activation of the selected request.
• Monitor the load for successful completion, and complete the further loads if any in the Process
Chain.
• In case the above does not work out, we check the size of the Data Package specified in the
InfoPackage. In InfoPackage -> Scheduler -> DataS. Default Data Transfer. Here we can set the size
of the Data Package. Here we need to “reduce” the maximum size of the data package. So that
activation takes place successfully.
• Once the size of the Data Package is reduced we again re trigger the load and reload the complete
data again.
• Before starting the manual activation, it is very important to check if there was an existing failed
“Red” Request. If so make sure you delete the same before starting the manual activation.
• This error is encountered at the first place and then rectified as at that point in time system is not
able to process the activation process via 4 different Parallel processes. This parameter is set in
RSCUSTA2 transaction. Later on the resources are free so the activation completes successfully.
By: sarat | 19 Apr 2011
8. Safety Intervals are used in Generic Data Source to make sure that no data records are missed, even if those are not stored in the DB table when the extraction took place. Time stamps got created during extraction and which is in turn used for delta extraction.
1) 0CALDAY => If we setup delta on base of calday we can run delta only once per day that too at the end of the clock to minimize the missing records.
2) Numeric Pointer => This type of delta is suitable only when we are axtracting data from a table which supports only creation of new records, but not change of existing records. Ex: CATSDB(HR time management table)
3) Time Stamp => Using time stamp we can run delta multiple per day but we need to use safety lower limit and safety upper limit with minimum of 5 minutes (300 seconds to be given)
1) 0CALDAY => If we setup delta on base of calday we can run delta only once per day that too at the end of the clock to minimize the missing records.
2) Numeric Pointer => This type of delta is suitable only when we are axtracting data from a table which supports only creation of new records, but not change of existing records. Ex: CATSDB(HR time management table)
3) Time Stamp => Using time stamp we can run delta multiple per day but we need to use safety lower limit and safety upper limit with minimum of 5 minutes (300 seconds to be given)
By: sarat | 19 Apr 2011
