Procces Chain problem

Hi all
We are using NW2004s (BI & EP) for our company management reports.
Daily morning BI-Team will run process chain for the actual business
report as of latest status. Some time this process chain get failures
due to some wrong datas.
In failure situations of process chain ,BI-team re-scheduling the
process chain in working hours around 8am in the morning and it takes
3hrs to complete , due to running of process chain all work proces
(DIALOG & BACKGROUND) are fully occupied. So end user canu2019t able to
access and view the report they are waiting for execution.
Please guide us how to overcome from this issue.

Hi Lakshminarayana,
Assuming you are using  7.0 dataflow, you can use the last update option in DTPs (Valid Records Update, reporting possible - Request Green). Set the maximum number of errors per pack to a high number (say 999999). This way, even if some data is in error, it will be written to the error stack but, the error records will be written to error PSA. Then, the only task for your BI team will be to fix the bad records in the error PSA and run ERROR DTPs. This will be selective and so, the entire process chain is not stuck because of one failed load. This feature (writing to error PSA and making the request green) is also available in 3.x. Hope this helps.
Thanks and Regards
Subray Hegde

Similar Messages

  • Process chains problems : Working every day with error (red)

    Hi All,
    I have a next question, about process chains problem.
    When I start my process chains immediate, then working without errors,  but I want this process chains work every day and chainged properties, selected date/time and periodicaly (every day) but now it work with error.
    How to I find problems? What are yours offers?
    p.s. I see logs, but every day have diffence between errors.
    Regards,
    Mahir M. Quluzade

    HI,
    just check the time which you have given is OK or is overlappintg with some other job which is locking your table in process chain
    or is colliding with attribute change run
    or it fails because of lack of background processes.
    There could be numerious reasons and you need to analyze the log for this.
    But as you said the job is failing everday for different reasons..try to find the most common errors and try to remove it or mention that here.
    Thanks
    Ajeet

  • Servlet chaining problem..

    import java.io.*;
        import javax.servlet.*;
        import javax.servlet.http.*;
        public class Deblink extends HttpServlet {
          public void doGet(HttpServletRequest req, HttpServletResponse res)
                                       throws ServletException, IOException {
            String contentType = req.getContentType();  // get the incoming type
            if (contentType == null) return;  // nothing incoming, nothing to do
            res.setContentType(contentType);  // set outgoing type to be incoming type
            PrintWriter out = res.getWriter();
            BufferedReader in = req.getReader();
            String line = null;
            while ((line = in.readLine()) != null) {
              line = replace(line, "<BLINK>", "");
              line = replace(line, "</BLINK>", "");
              out.println(line);
          public void doPost(HttpServletRequest req, HttpServletResponse res)
                                        throws ServletException, IOException {
            doGet(req, res);
          private String replace(String line, String oldString, String newString) {
            int index = 0;
            while ((index = line.indexOf(oldString, index)) >= 0) {
              // Replace the old string with the new string (inefficiently)
              line = line.substring(0, index) +
                     newString +
                     line.substring(index + oldString.length());
              index += newString.length();
            return line;
    What is pre request fo above code to work.
    I had tried this many time but it is not working, what will be calling servlet look like

    And can you explain why your title is "Servlet chaining problem"?

  • Proces chain problem in production

    Hello friends,
    i have faced the process chain problem in the production as "Status change of process ZD_BDIT_ACTIVATE" save status and trigge event if appropiate ? . and displayed message is " ABAP/4 Processor :DBIF_DSQL2_DEFAULT_CR_ERROR" . i want help to solved this problem and what exactly the problem is?
    actually this problem came to activation and its indicated red but when i went to data target and then i show that activation is not started or not trigger. please give me what is exactly problem and what is the proper solution.
    please reply me as soon as possible.

    Quick Checks:
    1. Check the status of User in R/3 which you have used in the RFC destination i.e SM59 and IDOC Adapter ? if it is locked , then unlock it. If password is the problem, then try to change the password.
    Don't reset it ...
    2. Also check out the status in XI, SM59... what is the user used ? is it correct etc... by testing the connection
    3. I think the IDOC Metadata is having problem.. Go to IDX2 and reimport the metadata in XI.
    Also note that, it is prefer to use Service User in SM59, and IDOC adapter instead of dialog use in the Production environment. so that no problem of locking etc
    Hope this helps`
    Rgds Moorthy

  • Process chain problem...., its urgent

    Hi all
    in my process chain we are loading 4 loads into ODS. After 3 loads, 4th load didn't take place. its not yet started even 3rd one successfully ran. its not showing error also. what can i do. after 4th one ODS activation process is there.
    Please advice me. will i go for manual loading. if i do manual, what abt activation after 4th load. will i do activation also manual or else it will trigger automatically as part of process chain........../
    Advice me frnds..., its urgent
    Regards
    swetha

    Hi Swetha,
    Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
    You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
    Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
    In the opened popup click on the tab 'Chain'.
    In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
    1. copy the variant from the popup to the variante of table rspcprocesslog
    2. copy the instance from the popup to the instance of table rspcprocesslog
    3. copy the start date from the popup to the batchdate of table rspcprocesslog
    Press F8 to display the entries of table rspcprocesslog.
    Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
    Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
    1. rspcprocesslog-log_id -> i_logid
    2. rspcprocesslog-type -> i_type
    3. rspcprocesslog-variante -> i_variant
    4. rspcprocesslog-instance -> i_instance
    5. enter 'G' for parameter i_state (sets the status to green).
    Now press F8 to run the fm.
    Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
    Of course you can also set the state of a specific step in the chain to any other possible value like 'R' = ended with errors, 'F' = finished, 'X' = cancelled ....
    Check out the value help on field rspcprocesslog-state in transaction se16 for the possible values.
    Try this solution with your 3rd ODS..hope this will solve your problem for this instance. This is just a workaround.
    Before next scheduel of the process chain..remove the link between 3rd ODS and 4th ODS and then reconnect once again and activate the process chain and schedule it as per your schedule cycle. From next upload onwards everything works fine.
    Assign points if it is helpful.
    Regards,
    Sreedhar

  • Fw800 daisy chain problems - crashing MBP

    I just had two massive crashes on a 6-month old MCP with new external FW800 drives daisy-chained.  The first crash happened when I tried to hook and "old" (5 years) FW400 hard drive within the daisy-chain of newer FW800 hard drives.  The second happened when all 3 of my new (8-months old) FW800 drives were connected:  one of the drives just spun its wheels and never showed any data.  After shutdown / reboot it's ok - but there are 1.3TB of info on it.
    Questions:  How many FW800 drives can you daisy-chain out of the one FW800 bus on a MacBook Pro?
    Or is it a length of cable issue?  Or is hooking up the older FW400 into the chain the problem?
    I researched online and found multiple posts that said you can daisy-chain Sixty-Three hard drives.  This sounds impossible and unbelievable given what I have just experience with THREE hard drives.

    The problem is that this could be tough to troubleshoot if it is a power supply, as the offending drive will attempt to pull the juice it needs to keep running from the FireWire bus.

  • Process Chains Problem

    Hi,
    I’m facing a problem with the triggering to the Process Chains.
    When I’m creating a new process chain and scheduling it for immediate run using ‘Activate & Schedule’ (F8) the chains fails to start.
    In SM37 I can see the following status for
    BI_PROCESS_TRIGGER in the job log:
      Job started
      Step 001 started (program RSPROCESS, variant XXXXX,
      user ID ALEREMOTE)
    The RSPROCESS variant is correct with WAIT = 0 & TYPE = TRIGGER
    The status of BI_PROCESS_TRIGGER remains ACTIVE & it seems to continue to infinity. The process never seems to continue beyond this point.
    This problem happens only to the newly built chains, existing chains in the system are working fine.
    A similar problem exists with Meta chains.
    I’ve a existing chain to which I’ve attached a new chain as ‘Local Process Chain’. The main chain is scheduled for immediate run & the local chain as Start using Meta Chain or API’
    When I run the main chain (F8) it executes fine but as it enters the local chain it seems to hang. (The other branches of the main chain run to completion).
    SM37 shows the following status for the local chain:
    BI_PROCESS_CHAIN as Active 
    BI_PROCESS_TRIGGER as Active  (Job log shows 'Job Started' and no further info)
    The Job log for BI_PROCESS_CHAIN shows the following:
    Job started
    Step 001 started (program RSPROCESS, variant &0000000007829, user ID ALEREMOTE)
    Communication buffer deleted from previous run 3YD14KALESRSTNM5MHPQ9Z5OW (status X)
    Version 'M' of chain SP_VENDOR_EVAL_INIT was saved without checking
    Version 'A' of chain SP_VENDOR_EVAL_INIT was saved without checking
    The Chain Was Removed From Scheduling
    Program RSPROCESS successfully scheduled as job BI_PROCESS_DROPINDEX with ID 07460801
    Program RSPROCESS successfully scheduled as job BI_PROCESS_INDEX with ID 07460801
    Program RSPROCESS successfully scheduled as job BI_PROCESS_LOADING with ID 07460801
    Program RSPROCESS successfully scheduled as job BI_PROCESS_LOADING with ID 07460901
    Program RSPROCESS successfully scheduled as job BI_PROCESS_ODSACTIVAT with ID 07460901
    Chain  <local chain> Was Activated And Scheduled
    (The  <local chain> has variants for deleting & recreating InfoCube Indexes, loading data to Cube & ODS, and activating ODS )
    It seems the Trigger process of the local chain never completes and so the local chain never runs.
    Any help to solve this issue will be greatly appreciated. I closed & reopened the transaction & even logged out of saplogon & logged in again. But these steps don’t seem to help much! Except that in my second case mentioned above the status in SM37 showed only BI_PROCESS_CHAIN  as Active initially ( without the job BI_PROCESS_TRIGGER ) and after I did my logout & login the BI_PROCESS_TRIGGER  seems to have started. But nothing more than that so far!!
    Thanks in advance,
    Melwyn

    Hi All,
    The problem is resolved by deleting the lock in SM37.
    The following lock appears (and stays!) when the chain is triggered-
    ALEREMOTE <time> E RSPCLOGCHA <chain name> #########################
    The lock is released if you leave the RSPC transaction & the chain executes for a normal Process Chain.
    In the case of meta chains (as explained by me earlier) this lock appears as the execution of the local chain begins BUT even if you leave RSPC the lock remains for the local chain.
    In both these scenarios deletion of this lock kicks of the normal execution of the Process Chain.
    Thanks everyone for your inputs.
    Cheers,
    Melwyn

  • Process chains problem in bi 7.0

    Hi,
    I am creating process chain loading cube , but iam unable to find out delete request in info cube.
    finaly i found one option delete overlaping reuest in info cube is it correct?
    please help me onthis.
    Advance Thanks.

    Hi suman,
    Refer this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/f8/e5603801be792de10000009b38f842/frameset.htm
    one small request when you find some problem then 1st just go for finding SAP Forums, there are lots of Forums available on this Topic. It will save your Time.
    Regards,

  • Process Chain problem related to Update ODS Object Data (Further Update)

    In the process chain, the data is loaded to an ODS first then feed to an InfoCube by kind of data mart load.  But when checking the process chain, getting yellow warning msg:
    A type "Update ODS Object Data (Further Update)" process has to follow process "Activate ODS Object Data" var.our_infopackage_name in the chain
    Message no. RSMPC016
    If we add the variant "Update ODS Object Data (Further Update) after the activation of the ODS and before the InfoPackage to feed data to the cube, then another yellow warning shows up for the InfoPackage of loading data to the InfoCube that says the Update variant can not be before the loading to this Cube and etc.
    What should we do to have the problem resolved?
    Thanks

    hey Dinesh,
    How to have a wait time for the load to the cube?
    I've given you "Very helpful" rewarding points and after you give the answer to the above, I will give you the "Solve problem" rewarding points.
    Thanks

  • Process Chain Problem - RSPCPROCESSLOG

    Hi,
    we have just upgraded from BW3.5 to BI7(patch 11) and we are currently experiencing a sporadic problem when executing process chains. 
    In some loading chains, even though the previous infopackage has finished successfully, the next package does not start.  The entries for the previous processes in table RSPCPROCESSLOG have field ACTUAL_STATE = 'F' (Completed), whereas normally the completed loads have status = 'G'.  This causes our process chains to get stuck and we can waste quite a lot of loading time due to this.
    Does anyone know why these (apparently) successful loads would be stored in RSPCPROCESSLOG with status = 'F'?
    I noticed in another thread that there is a function module (RSPC_PROCESS_FINISH) which can change the status, but as our chains are not constantly monitored we can lose a considerable amount of time before this function module can be executed.
    Also, I found OSS note 1002791 which looks relevant, although when I look at the correction instructions, it refers to TYPE = DTP_LOAD in table RSPCPROCESSLOG, whereas our problem is occurring with TYPE = 'LOADING', because we have not yet migrated from BW3.5 functionality.
    Any suggestions would be greatfully received.
    Thanks.
    Trevor Cowan.

    Really don't know about when the status gets set.  Have to look at that a bit.
    I do know that some changes were made in 7.0 to some things like change runs and I think other processes to use background processes instead of dialog.  Not saying this is your problem, but still something to look at.  Sometimes if you look at jobs in SM37 and if you see that you had jobs with delays before they actually started, that can suggest insufficent background processes. 
    Can you adjust your chains or timings so that not as many chains try to run at the same time or reduce the number of subchains that are triggered at the same time.  There is an OSS Note that talks about how many background processes you need to have free for process chains to work proprely - try searching for that.

  • Process chain problems

    Hi guys
    yesterday I got problem with process chain(PC),....its master data loading into characteristic attribute with everyday deltas.....
    I have three infopackages
    1.first IP for deltas(used in process chain)
    2.second IP for full repair
    3.third IP for delta initialisation.
    Process chain(having IP for deltas) stopped yesterday and the errors are:
    Repeat delta mode not supported by extraction API
    pROBLEM in source system
    I got advice yesterday...to solve this problem like this
    1.check if your failed delta request has any records...if it donot have any...go to IP for initialisation and do Delta initialisation without datatransfer.....if failed delta request has any data....then do delta initialisation with data transfer.
    2.Select repeat in process chain.
    Today...I checked delta queue...there are no records  for my request...then went into IP for Initialisation and choose option 'Delta Initialisation without data transfer'....and tried to schedule it.....it shows message:
    Delta Initialisation already done...cannot be done again....
    how can I solve this problem.....
    thanx for your inputs
    NR

    Hi.....
    Today...I checked delta queue...there are no records for my request...then went into IP for Initialisation and choose option 'Delta Initialisation without data transfer'....and tried to schedule it.....it shows message:
    Delta Initialisation already done...cannot be done again....
    Your delta queue is showing 0 records......may be there is no new records.......whatever delta s was there you have already send it..............
    Why you want to do re-init again..........I did'nt get you......
    Anyways............before doing re-init...always you have to delete the init flag.........because init flag is like a pointer.........you are doing re-init means you are again setting the init flag...........when already init flag is set...........how can you set it again without deleting the previous one.............due to this you are getting this error message..........
    Regards,
    Debjani.......

  • Sp12 - process chain problem

    hi,
    we are on sp12, when I tested sp12, I found problem in process chain, when I create a new process chain and want to add a new infopackage to it, I cant find any infopackages thru the Execute InfoPackage process. Is there any solution for this problem, because I am not able to add any infopackage to process chain.
    thanx

    Hi,
    While creating the process chain after the start process step, after selecting the  Load step and drag down to the right side of the process chain screen then create the varient.
    Click on the infource button which is left side of the RSPC transaction.In this select find button.through find button search with infosource or Infopackage then you will get Infopackage with delete index and create index step.select and drag to the right side of the window.
    Hope your problem will work out.
    Best regards,
    srinivas

  • Thunderbolt daisy chain problem with display

    Hi to everybody,
    being a proud new user of a thunderbolt audio interface Apollo Quad since a couple of days i am struggling to set it up without trouble for my secondary display in my Thunderbolt daisy chain...
    My setup and connections
    MBP Late 2011 17" 16GB RAM running Mavericks and UAD SW 7.11, 1 Thunderbolt port
    Promise Pegasus R4 Thunderbolt RAID drive
    Apple TB display
    Second 26" display connected via DVI/Mini display port adapter
    Erverything worked like a charm prior to inserting the TB audio interface with a Thunderbolt 2 Card into the TB daisy chain. Order of TB connections: MPB -> Apple TB display -> TB Audio interface -> Ext. display via DVI to TB connector.
    Since putting the audio interface (Apollo) in the TB chain Apollo itself, TB display and Pegasus RAID run fine - but the last display behind Apollo only shows "invalid mode" blinking on the display. I tried changing the order of the devices, no change.
    Has anyone an idea what to do?? - I have not exceeded the max number of TB devices (6) allowed to run in sequence. I read here in the forum that an ext display behind Apollo should work and has proven to do so. It has the new option card for TB2 inserted... Does the left/right port matter, which is connected to the display?
    Thanks in advance for any help to get that sorted out!! The last option would be to go remove the TB card and run the Apollo per firewire as I need the second screen.. not the most convincing solution for me though.
    Regards
    Uli

    Hi Ilya,
    I am curious why it only happens for one particular Process Chain. Normally displaying a log has nothing to do with the client settings of SCC4 and/or system settings of SE06. My only guess is that it might be created in this system directly and that the system wants to modify anything here.
    I am quite sure that the system is "closed" and it's not a Development system, e.g. a Production System. Please confirm.
    Anyway, I have one suggestion and that is to check the Object Changeability in the Transport Connection. Go to t/code RSA1, choose the Transport Connection view and click on the push button Object Changeability.
    Here you can see a list of Object Types like RSPT (Process Chain Starter), RSPV (Process Variants), PSPC (Process Chain). If it is set to "Not Changeable", I suggest to change that in e.g. "Everything Changeable".
    Please try that with the above mentioned Object Types for Process Chain related Object Types and see if you are able to display the log w/o the pop-up.
    You can also refer to SAP Note 337950 - Queries (including objects) cannot be edited for more information.
    Thanks,
    Sander

  • FireWire 800 Daisy Chain Problem

    Hello everyone, I have three firewire drives. Two 2TB 3.5" drives and one 2.5" 1TB drive. All three are connected to my MacBook Pro 13" via the one firewire port in a daisy chain. I usually always have the 3.5" disk connected. When I add the portable drive to the daisy chain, it crashes the desktop drive, and I get the "do not disconnect drives without ejecting" message. Is this normal? I am thinking of purchasing the Thunderbolt to Firewire 800 adapter, only to avoid the crashes of the other drives in the Daisy chain.
    My Mac is an early 2011 13" MacBook Pro i5 2.3GHz with 16GB RAM.
    Thank you for your help in advance

    Sorry for my late answer.
    The disc has 2 FW800 and 1 USB2.
    If you buy a TB to FW800 you should give to the disc more power from the TB port.
    If you connect the disc with USB you could use a special cable with 2 plugs on one side and one smal USB plug on the other.  This cable is designed to give to one disc the pover grom 2 USB ports but one of the 2 can also be connected to an USB power supply, so ytou will give to the disc more power....   of copurse with USB you have a lower speed.
    If you have Thunderbolt you should try to use TB discs. I know they are expensive but there is a trick which I like to use... have a look here  http://www.youtube.com/watch?v=1Aa3BXmQVpc 

  • Simple exception chaining problem

    The problem is 'throw new ClientException(e.getMessage());' the error message kept stating to be in try/catch but it's already in try bracklet. I tried placing the exception in other bracklet but it defeats the purpose of showing the exception in this specific bracklet. I'm not sure what's the solution of this, I got the two solutions in netbeans - make a new try/catch or extending the exception. I looked at the book, I don't see this class extending anything.
    import java.sql.Connection;
    import java.sql.SQLException;
    public class ClientBO {
        private Connection con;
        /** Creates a new instance of ClientBO */
        public ClientBO() {
            con = TomcatDAOFactory.createConnection();
        public void addSheet(SheetsForm sheetsform) {
            Connection con = null;
            try {
                TomcatClientDAO tomcatclientdao = new TomcatClientDAO(con);
                tomcatclientdao.createTest(sheetsform);
                con.commit();
            } catch (Exception e) {
                try {
                    if (con != null) {
                        con.rollback();
                        throw new ClientException(e.getMessage());
                } catch (SQLException sqle) {
                    e.printStackTrace();
                    throw new RuntimeException("error.unexpected");
            } finally {
                try {
                    if (con != null) {
                        con.close();
                } catch (SQLException sqle) {
                    sqle.printStackTrace();
                    throw new RuntimeException("error.unexpected");
    }

    You declare this:
    private Connection con;
    and define it in this constructor.
    public ClientBO()
    Next you declare this:
    Connection con = null;
    every line below this statement uses this locally defined variable 'conn',
    not the class variable 'conn' declared in 'private Connection con' (got that?). So from that point on , conn is null.
    Also, see my example on:
    http://forum.java.sun.com/thread.jspa?threadID=5193839&messageID=9769059#9769059

Maybe you are looking for