Scheduling a BI job chain in Redwood

The problem I am having is we are trying to schedule a BI job chain via Redwood software and are not getting any response. Within Redwood, I have executed these jobs IMPORT_BW_CHAINS, IMPORT_BW_CHAIN_DEFINITION, IMPORT_BW_INFOPACKAGES using BI job chain  0fcsm_cm_10 which is defined in BI as a job chain. These jobs run to completion but nothing is moved into Redwood to schedule as you would see from a import of a CCMS job. When I run job RUN_BW_CHAIN using the same BI job chain ID I receive the below error.  Not sure what I’m missing or doing with the process to get to schedule the BI job chains with Redwood.
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "RSI.RSIEXEC", line 1638
ORA-06512: at "RSI.RSIEXEC", line 1759
ORA-06512: at "RSI.RSI_RUN_BW_CHAIN", line 21
ORA-06512: at "RSI.RSI_RUN_BW_CHAIN", line 80
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1200
ORA-06512: at "SYS.DBMS_SQL", line 323
ORA-06512: at "SYSJCS.DDL", line 1085
ORA-06512: at "SYSJCS.DDL", line 1118
ORA-06512: at "SYSJCS.DDL", line 1177
ORA-06512: at line 3
JCS-00215: in statement RSOJ_EXECUTE_JOB

I am also seeing the same issue 
anton the last information  you requested
The following products are installed in the Cronacle repository:
Product                                  Version    Status
Cronacle for SAP solutions               7.0.3      Production 
Cronacle Forecast Module                 7.0.3      Production 
Cronacle Reports Module                  7.0.3      Production 
Cronacle &module Module                  7.0.2      development
Cronacle Mail Module                     7.0.3      Production 
Cronacle Audit Module                    7.0.2 r2.2 Production 
Cronacle Process Manager for Web         7.0.3      Production 
Cronacle Module Installer                7.0.3      Production 
Cronacle Repository                      7.0.3.34   Production 
Cronacle Monitor Module                  7.0.3      Production

Similar Messages

  • Can we schedule steps in Job Chain to run at a particular time of the Day.

    Hi ,
    We have created a Job chain for 3 steps.our requirement is we want to step 1 to run as per the schedule of Job chain but we want  step2 to run on fri 2 gmt and step 3 to run on saturday 1 gmt.
    is ther any setting in Job chain so that we can schedule subsequent steps to run at a particular time.
    Regards
    Rajesh

    Hi,
    You can add a timewindow to the jobdefinitions that you call in step 2 and 3, to restrict the start times for these jobs to the desired time.
    Regards,
    Anton.

  • How to Schedule a Job Chain to start automatically on SAP CPS.

    Hi,
    I did a job chain and i want to run automatically on sap cps Tuesday thru Saturday at 6:00 a.m., i make a calendar on sap cps with this specific options but the job chain doesn't start running.  I don't know if i need to do something more, so if someone can give a little help with this i will apreciate a lot.
    Thanks,
    Omar

    It finished ok but on the operator message i got the following message:
    Unable to resubmit this job.
    Details:
    com.redwood.scheduler.api.exception.TimeWindowExpectedOpenWindowException: CalculateNextClose should only be called on an open time window
    at com.redwood.scheduler.model.method.impl.TimeWindowMethodImpl.calculateNextCloseIntersectionInt(TimeWindowMethodImpl.java:388)
    at com.redwood.scheduler.model.method.impl.TimeWindowMethodImpl.calculateNextCloseIntersectInt(TimeWindowMethodImpl.java:249)
    at com.redwood.scheduler.model.TimeWindowImpl.calculateNextCloseIntersectInt(TimeWindowImpl.java:212)
    at com.redwood.scheduler.model.method.impl.SubmitFrameMethodImpl.calculateNextInt(SubmitFrameMethodImpl.java:178)
    at com.redwood.scheduler.model.SubmitFrameImpl.calculateNext(SubmitFrameImpl.java:176)
    at com.redwood.scheduler.model.listeners.JobStatusChangePrepareListener.resubmitSubmitFrameJob(JobStatusChangePrepareListener.java:763)
    at com.redwood.scheduler.model.listeners.JobStatusChangePrepareListener.resubmitJob(JobStatusChangePrepareListener.java:637)
    at com.redwood.scheduler.model.listeners.JobStatusChangePrepareListener.processJobToFinalState(JobStatusChangePrepareListener.java:520)
    at com.redwood.scheduler.model.listeners.JobStatusChangePrepareListener.modelModified(JobStatusChangePrepareListener.java:233)
    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.informListeners(LowLevelPersistenceImpl.java:728)
    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectListRetry(LowLevelPersistenceImpl.java:207)
    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.access$000(LowLevelPersistenceImpl.java:38)
    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl$WriteDirtyObjectListUnitOfWork.execute(LowLevelPersistenceImpl.java:79)
    at com.redwood.scheduler.persistence.impl.PersistenceUnitOfWorkManager.execute(PersistenceUnitOfWorkManager.java:34)
    at com.redwood.scheduler.persistence.impl.LowLevelPersistenceImpl.writeDirtyObjectList(LowLevelPersistenceImpl.java:102)
    at com.redwood.scheduler.cluster.persistence.ClusteredLowLevelPersistence.writeDirtyObjectList(ClusteredLowLevelPersistence.java:59)
    at com.redwood.scheduler.model.SchedulerSessionImpl.writeDirtyListLocal(SchedulerSessionImpl.java:648)
    at com.redwood.scheduler.model.SchedulerSessionImpl.persist(SchedulerSessionImpl.java:626)
    at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:32)
    at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:13)
    at com.redwood.scheduler.jobchainservice.JobChainService.childJobFinalStatus(JobChainService.java:223)
    at com.redwood.scheduler.core.processserver.ProcessServerRuntime.childJobFinalStatus(ProcessServerRuntime.java:836)
    at com.redwood.scheduler.core.processserver.ProcessServerRuntime.onMessage(ProcessServerRuntime.java:248)
    at com.redwood.scheduler.infrastructure.work.MessageEnabledWork.run(MessageEnabledWork.java:104)
    at com.redwood.scheduler.infrastructure.work.WorkerImpl.run(WorkerImpl.java:109)
    at java.lang.Thread.run(Thread.java:534)

  • Error while scheduling the Email Alert JOB chain

    Hi All,
    I have defined a job chain in CPS and when i am going to schedule it then it is giving me error message.We have taken the trial version.
    Please find the log attached below.
    11:18:31 PM:
    JCS-111004: Queue ETD.sapetd00_Queue has no ProcessServer with the required JobDefinitionType/Service/Resource for Job 932 (submitted from ETD.Z_MONI_BATCH_DP copy from 2009/12/30 18:22:23,113 Australia/Sydney) (submitted from Job Definition ETD.Z_MONI_BATCH_DP (Copy from 2009/12/30 18:22:23,113 Australia/Sydney)): Job Definition Type CSH/Service PlatformAgentService/"Empty"
    JCS-102064: Job 934 (submitted from System_Mail_Send copy from 2009/12/29 17:54:16,608 Australia/Sydney) is global but refers (via Job) to an object in an isolation group
    JCS-102064: Job 934 (submitted from System_Mail_Send copy from 2009/12/29 17:54:16,608 Australia/Sydney) is global but refers (via Chain Step) to an object in an isolation group
    JCS-102064: Job 934 (submitted from System_Mail_Send copy from 2009/12/29 17:54:16,608 Australia/Sydney) is global but refers (via Parent Job) to an object in an isolation group Show error details
    Thanks
    Rishi Abrol

    Hi
    Are you logged into the correct isolation group ?
    Ensure the process server is also assigned to the queue.
    Regards

  • Error in redwood job chain for Infopackage

    Hi,
    We have recently installed redwood for handling sap jobs and are able to run all the job chains with job step in abap program successfully.
    However, for APO and BW job chains we have intermediate step for executing BW infopackage where the job is getting failed with the below error:
    SAP/BW Error Message: rfc call failed 089: Job BI_BTC<infopackage_name>has not (yet ?) been started        
    The preceding abap job steps are getting executed successfully. After the infopackage step is failed the consecutive steps all fails.
    This problem is common to all job chains with infopackage.
    Any help is greatly appreciated.
    Regards,
    Sandeep.

    Hello Anton,
    We are facing the same problem: Same log error message.
    The infopackage is correctly started and ended in BW.
    Here our versions:
    Redwood Explorer 7.0.4.2 SP2
    BW :   SAP_BASIS 70016
               SAP_BW 70018
    Do you think applying SAP CPS SP3 would solve the problem?
    Or can we solve it by modifying some specific parameters?
    Thanks in advance.
    Regards;
    Mathieu

  • Backing up Jobs, Chains and Programs in Oracle Job Scheduler

    What is the best way to back up Jobs, Chains and Programs created in the Oracle Job Scheduler via Enterprise Manager - and also the best way to get them from one database to another. I am creating quite a long chain which executes many programs in our test database and wish to back everything up along the way. I will also then need to migrate to the production database.
    Thanks for any advice,
    Susan

    Hi Susan,
    Unfortunately there are not too many options.
    To backup a job you can use dbms_scheduler.copy_job. I believe EM has a button called "create like" for jobs and programs but I am not sure about chains and this can be used to create backups as well.
    A more general purpose solution which should also cover chains is to do a schema-level export using expdp i.e. a dump of an entire schema.
    e.g.
    SQL> create directory dumpdir as '/tmp';
    SQL> grant all on directory dumpdir to public;
    # expdp scott/tiger DUMPFILE=scott_backup.dmp directory=dumpdir
    You can then import into a SQL text file e.g.
    # impdp scott/tiger DIRECTORY=dumpdir DUMPFILE=scott_backup SQLFILE=scott_backup.out
    or import into another database (and even another schema) e.g.
    # impdp scott/tiger DIRECTORY=dumpdir DUMPFILE=scott_backup
    Hope this helps,
    Ravi.

  • Process Chains in Redwood

    hi All,
    We need to schedule Process Chains in RedWood; I am looking for the code in SE38 then I know i need to create a custome job for it.
    Thanks,
    Venu.

    hi venu,
    check this link
    /people/debjani.das/blog/2009/04/05/scheduling-process-chain
    regards,
    raghu.

  • Job Chians in Redwood

    Hi All,
    Iam creating Jobchians in Redwood.
    How I'm doing is
    1.create a script by copying a standard Script RSI.ABAP_RUN.
    2.Schedule one job from this newly created  script.(or just putting the job in HOLD state)
    3.create other scripts in the same manner.
    4.Go to Jobchains>RSI>create a new job chain -->scecify a name --->go to job flow diagram and create steps and add scripts (cretaed in earlier steps) to those steps -->save Job chain.
    so far so good.
    Now when I'm submitting the job chain , It's asking for INSTANCE,CLIENT,ABAP PROGRAM AND VARIANT.
    Actually 4 partameters are created automatically from Job chain diagram.
    But as I read in Docs, In job chains we can fire one step in systemA and the second in system B also ,if required.
    So,why Jobchain asking for instance name and client name ...more over ABAP pgm name and Variant Name?
    While defining the scripts itself i have used the respective Pgms and variants in those scripts and those are called from the job chain.
    For a change, I deleted all the 4 parameters created by job chain diagram and now I am able to schedule the job chain but it always goes in to error state saying INSTANCE name not specified.
    Iam using Redwood OEM.
    Please let me know the wrong  thing I'm doing while scheduling Jobchains.
    Any help is very useful and highly appreciated.
    Thanks,
    Bapu

    Hi all,
    The logic for chain parameters is as follows when you add a script call via the diagram: for all required parameters of the added script that do not have a default value (ie. parameters that need a value otherwise you cannot submit the script), a corresponing parameter on chain level is used: if it does not exist yet, it is created, otherwise it is reused.
    So, to replay your example: you created different copies of RSI_ABAP_RUN, with required parameters instance, client, abap program etc.
    You added the first one to a chain: parameters at chain level were created.
    You added the second one to the chain: parameters at chain level were reused, because they existed already.
    You submitted the chain and entered parameter values: these values were used in both steps.
    There are different ways to achieve other behaviour.
    1. Specify the parameters in the chain definition.
    For this scenario, you do not actually need to create copies of RSI_ABAP_RUN, as that script can also be reused.
    You add the script RSI_ABAP_RUN multiple times to a chain (via the diagrammer or via the Edit dialog).
    Then, via the Edit dialog of the chain, you go through each call and specify the parameter values in the chain itself. For this you drill down in the tree on the left hand side on the steps and the call in the step, and finally to parameters, where you can specify the behaviour for each parameter.
    - for parameters like instance and client, which are likely to be the same throughout the chain or at multiple points in the chain, you can "create a job chain parameter" the first time, and for subsequent calls "use existing job chain parameter" to have all parameters use the same values; you can then specify these at submit time, and thus run the entire chain in multiple instances if necessary
    - for parameters like Abap program and variant, you can either specify the value to use directly (no need to specify it at submit time anymore), or "create job chain parameters" but then create different parameter names if you need different values (then you can specify them when submitting the chain)
    2. Specify the values as default value in copies of the script RSI_ABAP_RUN
    As you did before, you create copies of the script RSI_ABAP_RUN, and in these copies, you set the parameter default values to the values you want to use (at least instance, client, program, variant if needed, etc.).
    Then you create or modify a chain (via the diagram) and add these scripts to the chain.
    This way, because defaults are provided, the chain should not get any parameters at all and always run the scripts as they are defined.
    To get an idea how the first scenario works, import an existing multi-step job from your SAP system using RSI_IMPORT_CCMS_JOBS. This will create a chain along the lines of the first scenario, so you can then look at the definition of the chain to see how the parameters are passed.
    Also look at the "all parameter mappings" item in the Edit dialog of the chain.
    Hope this helps,
    Anton.

  • How to schedule infospokes in process chains..

    Hi All,
    I have a few infospokes to be scheduled in a process chain. In each infospoke, I have upto 10 jobs that are to be scheduled one after the other. At the end of these jobs I have to run a FTP script. I am new at creating the process chains. So can anybody help me out in letting me know:
    1. How to create a start process where I can select a given job by using its name
    2. How to run a FTP script as a follow up step on completion of a previous step.
    Thanks in advance
    John

    Hi John
    it a big task to explain all so I will try to give you the high level picture.
    1. process chain is easy to implement and learn.
       usually it is triggered either by a batch job or a
       batch job that fires an event.
    2. to call an OS (like Win or Unix) from the PC you can
       trigger an event from the end of the PC to call a
       ABAP program that will initiate an OS call.
       you use trx: SM69   - External Operating Sys Commands
       to set this call up.
    3. to implement an FTP you can do via a batch file with
       OS commands or by using free utilities (there are many of them).
    I hope it helps.
    Edan

  • Job Chain Restart Behaviour

    If a Job Chain with 3 steps fails in the second step - we would like the restart to resume execution with the second step, bypassing execution of the first step.   What are the correct settings to enable restarting the chain with the failed step? Thanks

    Hi Noel,
    For now, you could put an "on completed" "request restart" on the SendMessage step. If the SendMessage runs, there was an error so you would want to restart, but the restart options have some restrictions then because they don't take the step of the error but the SendMessage step as a reference now (you have the request restart on the send message step).
    Last but not least: if you already inform someone, you can also simply right click a step in the monitor and choose restart, this should restart the chain but from the step you selected. This is the same as submitting a new chain but specifying the step where it should start (on the same page in the submit wizard where you specify the queue).
    There also is an add-on available from Redwood called "active alerting" which allows you to do rule-based alerting (depending on source of the error send message to different teams) as well as escalation (if no reply within x minutes, send to next team) very easily.
    Regards,
    Anton.

  • SAP CS 8.0 - question to parallel tasks in one job chain

    Dear all,
    I have a question about job chains in SAP CPS/Redwood
    We have a job chain like this:
    Job 1
         Job 1.1
                   Job 1.1.1
                   Job 1.1.2
         Job 1.2
                    Job 1.2.1
    The Jobs 1.1.1 and 1.1.2 should start  when the Job 1.1 is compled and don't have to wait until Job 1.2 is complete.
    How could I release it in Redwood in one job chain? Should I use a precondition in the job definition of 1.1 and 1.2?
    Thank you for your help.
    Best regards,
    Hans

    Assumptions :
    Job 1.1.1 and Job 1.1.2 are running in parallel.
    Job 1.1, job 1.2 are also running in parallel.
    Chain A -
    Step 1 - Job 1.1
    Step 2 - Job 1.1.1, Job 1.1.2 (these both will start as soon as Job 1.1 completes)
    Chain B -
    Step 1 - Job 1.2
    Step 2 - Job 1.2.1
    Chain C
    Step 1 - Job 1
    Step 2 - Chain A, Chain B (Chain A and Chain B will start as soon as Job 1 completes).
    Submit Chain C.
    Preconditions are usually  used to check the timewindow, for example , if you want to execute a step in a job chain, only if it is a Friday.
    thanks
    Nanda

  • Need informations about dependency scenario with job chains

    Hi,
    I created several job chains containing one ora mor scripts.
    Now I want to create dependencies between this job chains. For example : job chain 2 must begin when job chain 1 is finished, job chain 3 must begin when job chain 2 is finished etc...
    So my first question : how can I do that ? (create dependencies between job chains)
    Second point : all this job chains have not the same time periods : example : job chain 1 must execute every day, job chain 2 every monday, job chain 3 every day...... so if i take the example of tuesday : job chain 1 must execute and when it is finished then job chain 3 must execute. On Monday : job chain1, then job chain 2 and for finish job chain 3. How can I do that ?
    Edited by: kennel yves on Aug 19, 2009 12:27 PM

    Hi Yves,
    If your chains are not dependent on each other, you should submit them as separate jobs.
    So if you have a chain that runs every workday at 18:00, and another chain that runs on Tuesday and Friday at 14:00, and there are no dependencies between the chains, then you should:
    - submit the first chain at 18:00, time window "Workdays", submit frame "EveryDay"
    - submit the second chain at 14:00, time window "TuesdaysAndFridays", submit frame "EveryDay" (it will skip the days that the time window is closed anyway)
    Same for the other independent chains with different schedules. If there are no dependencies, there is no need to combine chains together.
    The first reply was for the scenario where you have chain A and B, A starts at some time and B starts after A. Additionally, B only runs on Tuesdays, while A runs every workday. In that case there are dependencies between the two chains, and then a parent chain is very convenient:
    - chain "RunAandB", with two steps
    - step 1: call chain A
    - step 2: call chain B, with a precondition so that B only runs on Tuesdays.
    Regards,
    Anton Goselink.

  • Restart in Job chains and managing DST

    Hi,
    1) Given a 5 step job chain, if step 3 fails how is this handled in CPS? The following steps are chained but can the errored step be fixed and rerun to continue the job chain processing?
    2) How is day light saving handled for particular jobs. Is there anywhere this is captured in the detailed job request form solman?
    Regards,
    Esha

    Hi,
    1) Given a 5 step job chain, if step 3 fails how is this handled in CPS? The following steps are chained but can the errored step be fixed and rerun to continue the job chain processing?
       -- Yes, you can restart at any step of Job chain. (Not not at call level, remember one step might have multiple call inside it)
    2) How is day light saving handled for particular jobs. Is there anywhere this is captured in the detailed job request form solman?
    -- Use GMT timezone to submit jobs. There is nothing on redwood which can solve day light saving. It alwasy has to be at OS level. But redwood has all timezones availabe and you can submits job in any timezone.
    Regards,
    Sunil Rohit

  • Schedule PC after Job

    I scheduled PC after Job. It ran fine for only one day. I want to run PC daily after certain Job. How to achieve this?
    Thanks in advance

    Raj, I think you will need to change the Start variant of your Process Chain to start "After event".  When you do this, you will see the Periodic Flag check-box. 
    Then create an ABAP program to trigger the event.
    See this link:
    How-to trigger a process chain using ABAP?
    Next, in your job, add a step at the end to call this ABAP program so that when the job finishes, it will trigger your Process Chain will start.
    Hope this helps, and sorry for the confusion

  • Changing console job status in Redwood when BW processes are in error

    Hi,
    When BW jobs failed in error, the status of the job step in Redwood is console => waiting an operator action.
    How do we can have the step directly in status error as no action will be done in the night for those BW jobs, please ?
    Clement

    Hello,
    When you start the BW chain with parameter RESTARTABLE=N(o) it it will always go to an end status immediately.
    Regards Gerben

Maybe you are looking for