ODS Activation Issue in Prod - Critical

We are in BI 7. We have a huge ods ZXYZ in Prod. It has more than 400 million records. BEx reporting - off.
Over the last weekend some data was added the requests were being activated and there was master data activity in parallel. The ODS activation failed with SYSTEM_EXCEPTION. Unfortunately not investigating the root cause, the ODS activation was resumed and it returned SYSTEM_CANCELED again as there was master data activity going on.
The problem is that request is now partially activated and it became in faulty status. When trying to activate, we get the following error message.
<i>Activation of M records from DataStore object ZXYZ terminated
'A' and 'U' entries exist in RSODSACTREQ for request REQU_CTAKWUIM6ZAWBQC1K6Q5TVL8M - termination</i>
When trying to delete that request which was partially activated, it fails complaining about Faulty status of the ODS.
The problem is we are not moving forward as the request cannot be deleted/activated due to this.
RSODSACTREQ table has Activation status 2  - Activate failed for this request.
Can you experts please advice.

Hi,
I see that your message was not answered and you may not have this issue any more. But for future reference you could refer to note 947481. You might be able to use step 1 from this note to clean the failed request and reload your data.
Hope it will help some day. It did work for us.
Sameer Gandhi

Similar Messages

  • ODS Activation Issue

    Hi All,
    I am getting the below error while activating the ODS.  I have searched in SDN but not able to find the solution for this.
    Error when inserting the data record for data package                                                   8
    Message no. RSODSO_PROCESSING002
    Diagnosis
    Failed to store data records persistently. Possible causes are:
    You tried to save a record that is already stored in the database.
    This error only occurs with DataStore objects with option "Unique Data Records".
    A unique index was created for the table of active data.
    You can check this in the Data Warehousing Workbench by choosing "Display" for the DataStore object and opening the "Indexes" folder.
    There is a technical problem on the database.
    But In DSO "Unique records" is unchecked and Nothing in Indexes folder to delete.
    This DSO is getting data from from 2 datasources which are flat files. I am able to load and activate data from second datasource but when I loading and activating the data its giving the above issue.
    So can anyone let me know the resolvation for this issue.
    Regards
    Sankar

    Hello Punitha,
    Thanks for your reply.  But I am not able to see any Char name in the log.
    Please find the below log.
    Error when inserting the data record for data package                                                 9
    Process 000009 returned with errors
    Error when inserting the data record for data package                                                10
    Process 000010 returned with errors
    Error when inserting the data record for data package                                                11
    Process 000011 returned with errors
    Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000002; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000003; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000004; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000005; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000006; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000007; Added records 1-; Changed records 0; Deleted records 0
    Data pkgs 000008; Added records 1-; Changed records 0; Deleted records 0
    Log for activation request ODSR_4H47N3DWSG0OESY8S7V9DDPA4 data package 000001...000008
    RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_INSTANCE_FOR_RNR       498 LINE 43
    RSS2_DTP_RNR_SUBSEQ_PROC_SET GET_TSTATE_FOR_RNR 7 LINE 330
    Status transition 7 / 7 to A / A completed successfully
    RSS2_DTP_RNR_SUBSEQ_PROC_SET SET_TSTATE_FURTHER_ERROR_OK LINE 367
    Errors occured when carrying out activation
    Please take a look and suggest me the better wayout to resolve this.
    Regards
    Sankar

  • Integration model activation issue - After Prod to Quality refresh of R/3

    Hi Guys,
    Our R/3 quality system refreshed from production. Hence all the integration models Logical system pointing APO production system. Mistakenly I deactivated all the integration model in R/3 Q system which having APO Production logical system.
    All the IM in R/3 quality system are inactive. When try send material getting error message "relavent location doesn't exist".
    For that try to move the Location getting error message "Location already exist in APO Quality" system.
    Now I want to active the all the Plant, material.etc integration models. Please let me know if any more information and help to overcome the issue.
    Thanks,
    Saravanan V

    Saravanan
    Make a table level change and set the integration model flag as active in the table CIF_IMOD. This will help you solve the issue .
    Go to transaction SE16 . Give table name as CIF_IMOD. Give the name of you integration model and execute . Now all versions of that integration model will be displayed ( this will happen if you have many inactive versions and do not have the RIMODDEL program to delete inactive IM's) . Choose the latest version and go to change mode  and set the value of "Entry is active"  (technical name ACTIVE) field to  I.
    You can take help from development team if you do not have authorization to SE16
    Thanks
    Saradha

  • ODS Activation is taking much time...

    Hi All,
    Some times ods activation is taking much time. Generally it takes 30 mins and some times it take 6 hours.
    If this activation is taking much, then if i check sm50 ...i can see that there is a piece of code is taking much time.
    SELECT
    COUNT(*) , "RECORDMODE"
    FROM
    "/BIC/B0000814000"
    WHERE
    "REQUEST" = :A0 AND "DATAPAKID" = :A1
    GROUP BY
    "RECORDMODE"#
    Could you please let me know what are the possiblites to solve this issue.
    thanks

    Hello,
    you have 2 options:
    1) as already mentioned, cleanup some old psa data or change log data from this psa table or
    2) create a addtional index for recordtype on this table via Tcode se11 -> indexes..
    Regards, Patrick Rieken.

  • ODS ACTIVATION FAILS

    hi gurus,
                  i am getting the data upto psa level.the infosource is feeding to one ods.but i am not getting the data in ods.strictly speaking i am getting the data in newdata of ods but i am not getting in active data table.can anyone resolve this issue highly appreciated.
    thanks and regards,
    nataraj.

    hi balaji amd pals,
                          i am getting that type of error(subsequent process).i am sending the error as follows
    Subseq. processing (messages) : Errors occurred
    Activation of data records from ODS object ZOPMOMCB terminated
    Communication error (RFC call) occurred
    Request REQU_40JA03VHZT6V9EAJTLHM7BW5H , data package 000001 incorrect with status 9
    Request REQU_40JA03VHZT6V9EAJTLHM7BW5H , data package 000001 not correct 
    Inserted records 1- ; Changed records 1- ; Deleted records 1-
    No confirmation for request ODSR_40JABQY2GD5XKWR0TKB86GF45 when activating the ODS object ZOPMOMCB
    ODS activation (change-log) : Errors occurred
    Other (messages): Errors occurred
    thanks and regards,
    nataraj.

  • ODS activation, short dump COMPUTE_INT_PLUS_OVERFLOW. How to solve?

    Hello Gurus,
    We are on BW 3.1.
    We have an issue - ODS activation failed due to a short dump.
    Runtime Error          COMPUTE_INT_PLUS_OVERFLOW
    Exception              CX_SY_ARITHMETIC_OVERFLOW
    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:
    In the current program "SAPLRSSM_PROCESS",
    using + or 'ADD' to add the values 2137304138 and 12410267 resulted in a
    value greater than 2147483647 or samller than -2147483648. This
    leads to a whole number overflow.
    Could you please guide me to solve this?
    Please let me know if you need more details.
    Thanks,
    raj

    This dump is happening because of the overflow of the size assigned for the variable.
    This dump can be avoided by changing the declaration of the variable definition.
    DATA: variable_name type p decimals 0.  
                              OR
    DATA: varibale_name(25) type n decimals 0
    Try this. This will resolve your dump.
    regards,
    brijesh

  • Problem with ODS activation -- Urgent

    Hi All,
    I have a problem with ODS activations, when I trying to activate ODS data automatically/ Manually. It is going to short dump.
    Could you anybody pls help me in this issue.
    Thanks in Advance
    Narendra

    Sorry for delay,
    I raised an OSS messsage and waiting from reply.
    The ODS fetch the data from 6 sources. all the 5 sources data is correctly updating in the ODS. I have ODS activation problem with only one soure data.
    The error is
    RSMO
    Inserted records 1-; Changed records 1-; Deleted records 1-
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 incorrect with status 4 in rsodsacstreq
    No confirmation for request ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9 when activating the ODS object ZPMPRCST
    Activation of data records from ODS object ZPMPRCST terminated
    SM37 Job log
    Error Message from Job log (SM37) (Highlights of the Job log)
    SIDs determined successfully for request REQU_49Y4VOQEDO6H73KDE354JNDB5 from ODS object ZPMPRCST
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 not correct
    Inserted records 1-; Changed records 1-; Deleted records 1-
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 not correct
    Inserted records 1-; Changed records 1-; Deleted records 1-
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 not correct
    Inserted records 1-; Changed records 1-; Deleted records 1-
    No confirmation for request ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9 when activating the ODS object ZPMPRCST
    SID assignment started at 07:41:12
    SID assignment finished at 07:42:22
    Activation started at 07:42:22
    Activation finished at 08:12:28
    Errors occured when carrying out activation
    Analyze errors and reactivate if necessary
    Activation of data records from ODS object ZPMPRCST terminated
    Activation is running: Data target ZPMPRCST, from 1.397.204 to 1.397.204
    Data to be activated successfully checked against archiving objects
    SIDs determined successfully for request REQU_49Y4VOQEDO6H73KDE354JNDB5 from ODS object ZPMPRCST
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 not correct
    Inserted records 1-; Changed records 1-; Deleted records 1-
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 not correct
    No confirmation for request ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9 when activating the ODS object ZPMPRCST
    SID assignment started at 07:41:12
    SID assignment finished at 07:42:22
    Activation started at 07:42:22
    Activation finished at 08:12:28
    Errors occured when carrying out activation
    Analyze errors and reactivate if necessary
    Activation of data records from ODS object ZPMPRCST terminated
    Activation is running: Data target ZPMPRCST, from 1.397.204 to 1.397.204
    Data to be activated successfully checked against archiving objects
    SIDs determined successfully for request REQU_49Y4VOQEDO6H73KDE354JNDB5 from ODS object ZPMPRCST
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 incorrect with status 4 in rsodsacstreq
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000002 not correct
    Inserted records 1-; Changed records 1-; Deleted records 1-
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000003 not correct
    Request REQU_49Y4VOQEDO6H73KDE354JNDB5, data package 000001 not correct
    No confirmation for request ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9 when activating the ODS object ZPMPRCST
    SID assignment started at 07:41:12
    SID assignment finished at 07:42:22
    Activation started at 07:42:22
    Activation finished at 08:12:28
    Errors occured when carrying out activation
    Analyze errors and reactivate if necessary
    Activation of data records from ODS object ZPMPRCST terminated
    Report RSODSACT1 ended with errors
    Job cancelled after system exception ERROR_MESSAGE
    RSODSACTREQ  Table Entries
    Table:          RSODSACTREQ                                                                               
    Displayed Fields:  10 of  10  Fixed Columns:                3  List Width 1000                                                                               
    InfoCube       Request ID                     Data packet number             Boolean    Boolean   Request ID                                                 ODS operation    Activ. status                                                                               
    ZPMPRCST     REQU_49Y4VOQEDO6H73KDE354JNDB5 000000             X       X             ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9     A                         0            
    ZPMPRCST     REQU_49Y4VOQEDO6H73KDE354JNDB5 000001             X                       ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9     A                        4            
    ZPMPRCST     REQU_49Y4VOQEDO6H73KDE354JNDB5 000002             X                       ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9     A                         4            
    ZPMPRCST     REQU_49Y4VOQEDO6H73KDE354JNDB5 000003             X                       ODSR_49Y5D1HMEA9OOGJD9VS1XTXY9     A                         4            

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

    Generally it is obesreved that the ODS activation failes with error something like 'SID cannot be determined'. Also many times we see that ODS activation goes on for 2-3 hours. In this case when we manuall activate the ods it gets completed successfully. However, can anyone tell me the reason for long activation time and the error mentioned above. It would further be helpful if you could tell me the possible preventive measures to avoid manual interventions...Thanks for help in advance

    Hi Lye
    First i will explain the reasons for long running ODS.
    1.This is probably because of too many parallel ODS activations running at the same time.
    2.some times some particular jobs running may lock your ODS activation which you can monitor in SM37 which results lock waits and dead locks.
    If you see the PID no for the job which is involved in lock waits,if you feel that particular job is not important at that point of time you can terminate the job(not ODS activation job) and repeat the job after the succesful completion of the ODS activation.
    If the ODS activation fails with SID error as you mentioned,i hope this solution may help you.
    1.Check the request for the infopackage which is loading the ODS in RSRQ
    2.give the request of the bearing infopackage or request ID and execute in RSRQ
    3.it shows whether that reqest is updated in to your target correctly or not.If its not loaded check the IP processing setting whether the reuested data is reaching in to targets are not.some times data load happens till PSA then push the data by doing process manually step.
    4.Now reapeat the ODS activation step.
    but if it is SID issue, then load the master data for that particular characteristic and repeat the ODS activation step.
    Hope may help you
    Regards,
    Venkata Lakshmikanth

  • ODS ACTIVATION Failure frequently......

    Hi,
    We r loading data from ods to cube , but ODS activation process for 3 ods is happening parallely.
    This ods activation failed sequence two times , but in logs error mesgs
    are "Activation of data records from ods object terminated,Qm status is in not green before ODS activation"…
    we are loading approx 10,000 records
    The chain is like this…
              START
    ODS1          ODS2          ODS3   à these 3 ODS are Parallel
    |          |          |     
    CUBE1     CUBE2     CUBE3
    Can anyone tell me what might be the reason…for failuring frequently.. this is a monthly chain
    -Shah

    Shah,
    1) I said "conflicting" because I thought you were loading all data to ONE ODS.. so I thought they might have some "locking" problem..But since u had confirmed me that 3 different ODSs.. this is out of scope for us..I am taking back my words..
    I do not see "technically" issue with Process chain design as all are 3 different tables now..
    It has a techincal issue, if you are loading 3 ODS parallely and Activating all 3 ODSs at a time..
    in the above scenario.. say ODS1 completed 1st and it tries to start the Activation node..( which tries to activate ODS2 and 3 also..) but still 2 and 3 are loading.. can lead to the mentioned error..
    generally.. if u schedule too many parallel jobs at a time it will occupy all available system resources and can lead to some ewrrors..
    regards,
    hari
    Message was edited by: Hari Kiran Y

  • ODS activation failures after new hardware installation..urgent

    Hi All,
    I am working in PRD.There are 10 process chains which i need to monitor daily.Daily ODS activation fails in 4 of the 10 chains.The error message for two of the failures are,
    Task 0040 during SID specification without confirmation     
    and for another process it is showing "DBIF_RSQL_SQL_ERROR" error.
    manually I am doing steps and the activation is successful.These type of errors we are getting after the new hardware installation.
    Could anyone let me know are there any patches to be applied inorder to avoid such type of errors.
    Please advice me what to do.
    Thanks,
    Manjula

    What is the patch your currently on at the moment.
    It could also be some of the settings in RZ11 have been changed. You need to work with your basis people to resolve this.
    DBIF_RSQL_SQL_ERROR is a common problem and usually due to not enough processor's available and the database gettings into a knot.
    Check SM21 and ST22 for the more information on the issue.

  • No msg from process chain on ODS activ failure

    All,
    We are loading and activating a CRM ODS (0CRM_PROH) in a process chain.  The process chain is set up to deliver a message if the ODS activation fails, but this is not happening reliably.
    For instance, yesterday a hex character came over from the source system causing ODS activation failure.  Strangely enough, the overall status of the request in the monitor was green.  Also, the activation step in the RSPC planning view was blue, not red as I would expect.  You could really only see the failure by switching to log view in RSPC, where it was clear the ODS activation had failed.
    Any thoughts on why the overall status of the request is green instead of red or yellow when the ODS activation fails?  Or, any thoughts on why no message is going out?  It's probably obvious that I'm new at interpreting the RSPC screens, so any general references on this topic would be helpful.
    Thanks,
    Bob
    P.S.  The ODS in question is set for automatic activation and automatic updating of data targets.  We are running BW 3.10.21, BI_CONT 3.30.16.

    Hello Diane
    We also had this issue, but with an older version (30B patch 7, works OK w/ patch 14).
    Anyway, to fix it:
    - create a new variant (let's call it V1 as an example) for the SAP program RSODSACT1
    - in your process chain, insert an ABAP call after the ODS load. Punch it RSODSACT1 as program and V1 for the variant
    It worked for us
    Good luck
    Ioan

  • DBIF_RSQL_SQL_ERROR which are related to BW ods Activation

    Hi friends,
    I dont know whether this is the right thread i am posting or not. But technical people can definately help me.
    Recently we have upgraded patch from  SP 22 to SP 25 for BI 7.0. From that time onwards i am facing issues like anything.
    Here is the impact.
    1. Data loads not triggering for process Chains as per schedules. we are running emegency chains manually. We have raised an issue to SAP, waiting for reply.
    Short Dumps:
    b)
    DBIF_REPO_SQL_ERROR
    Short text
        SQL error 3114 occurred when accessing program "SAPLRS_EXCEPTION " part "LOAD".
    What happened?
        The system is no longer linked to an ORACLE instance.
        No further operations can be performed on the database.
    Error analysis
        The system attempted to access an ORACLE instance to which
        it is no longer linked.
        This situation may arise because the ORACLE instance
        has been stopped due to an error or an external operation.
    How to correct the error
        Database error text........: "ORA-03114: not connected to ORACLE"
        Triggering SQL statement...: "SAPLRS_EXCEPTION "
        The current status of the ORACLE instance cannot be determined.
        It may be still inactive or the database administrator may have
        restarted it.
        In any case, all systems that have accessed the ORACLE instance
        must be restarted after the ORACLE instance has been restarted.
        If you were working on a central system, inform
        your system administrator.
        If you were working on an external local system, inform
        the person responsible for this system.
        If you were working on your own local system, restart
        the system yourself.
        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_REPO_SQL_ERROR" " "
        "SAPLRRMS" or "LRRMSU14"
        "RRMS_EXCEPTION_HANDLING"
    c)
    DBIF_RSQL_SQL_ERROR
    CX_SY_OPEN_SQL_DB
    How to correct the error
        Database error text........: "ORA-03135: connection lost contact"
        Internal call code.........: "[RSQL/RDUP/TADIR ]"
        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"
        "SAPLSDI0" or "LSDI0U01"
        "TRINT_TADIR_UPDATE"
    2. Especially ODS activation (through process chains) failing in every process Chain. if you run maual activation , then its ok.
    All Batch are got struck when accessing table TADIR. Dump C which is mensioned above impact is very high on the system.
    Anyone know about to resolve the above dumps, Please help me.
    If you want to analyze more detailed level, please let me know
    Thanks in Advance.
    Venkat

    Hi Mark,
    Please gothrough below details.
    Filename......: sqlnet.ora
    Created.......: created by SAP AG, R/3 Rel. >= 6.10 # Name..........:
    Date..........:
    @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#4 $ ################
    AUTOMATIC_IPC = ON
    TRACE_LEVEL_CLIENT = OFF
    NAMES.DEFAULT_DOMAIN = WORLD
    NAME.DEFAULT_ZONE = WORLD
    SQLNET.EXPIRE_TIME = 0
    TCP.NODELAY=YES
    TADIR file got struck during this stament:
    Last SQL statement
    SELECT
    /*+
      FIRST_ROWS (1)
    FROM
      "TADIR"
    WHERE
      "PGMID" = :A0 AND "OBJECT" = :A1 AND "OBJ_NAME" = :A2
    FOR UPDATE
    Database                         Number              Time (usec)         Recs.
    Direct Read                     1,017                   172,733                 232
    Sequential Read                 1,815                471729                10,454
    Insert                                   20                     31,223                 306
    Update                                25                       9,621                  17
    Delete                                  25             115,827                 291
    Sources                         3,069,427  (Bytes)
    RSQL                              2,265,032  (Bytes)
    Commit                                                  0
    DB Procedure Calls                  0                   0
    Thanks and reagards
    Venkat

  • ODS activation failure due to Time characteristic

    Hello Gurus,
    One of my ODS activation job is failing because of the following error:
    Error when assigning SID: Action VAL_SID_CONVERT table YSDENTTIM
    Value '0545' of characteristic 0TIME is not a number with 000006 spaces
    The Infoobject YSDENTTIM is created using 0TIME as a reference with data type TIMS and it is mapped to the R/3 field ERZET (VBFA table). The data format for this field is hh:mm:ss and hence I dont understand this message.
    I cannot correct the data in PSA too because my load has around 7-8 million records and hence it is difficult to locate this record in the PSA.
    Has anyone faced this issue before?
    Thanks,
    Rishi

    Hi,
    The definition of PSA is itself it allows the correct data as well as RAW data...
    So the data which entered into PSA is not accepted at ODS level means there is wrong/error data from the source....
    Now to find the erroneous record u have to go to PSA maintainence and chk all the packets and select filter button below....it'll give u in which fields/columns u have to filter...
    Now select tht concrened filed/column(in ur case it was time i suppose) and continue...
    In the next screen u enter the data packets from 1 to all in ur PSA take it the MAX value....
    Now in the another column/field value u enter ur error value there as 0545 and execute...if all the settings are right it'll take u take the rows/records which is having the incorrect time u have selected/filtered...
    Now to edit the records u have to delete the request from ur target DSO/CUBE and edit with correct entrie and save...and reload/reconstruct into DSO and activate ur request
    Hope so it won't throw the eror now...
    Note: Here the main concern is how u can find the eror records...
    rgds,

  • ODS Activation - Background Job in SM37 is still active

    Hello Gurus,
    When I try to activate an ODS Request, the START button is disabled. Then when I select JOBS button on the same screen, it shows the previous ODS activation job with ACTIVE status. But the previous job is already showing as ready for reporting with no problems. Is there any setting where the START button is enabled after the completion of the background job
    Thanks in advance

    Hi,
    There is no setting to enable to START button , it will be enabled automatically once the activation job is completed. Did you check if the activation job that was running was for the latest request? You can check this by looking into the job log where the request ID will be available. Sometimes even if the activation job is running in the background, the request in the ODS will still be in green status-not available for reporting and you tend to think that the activation has not started or the activation for the previous request is still running.
    First check the request ID in the job log to ensure which request is being activated and if the activation is completed. After this you can either stop the job or let it run based on the situation.
    Regards,
    Shilpa

Maybe you are looking for