Redwood User Account error on Job

Question

Hi All,
We currently had all our BWP jobs fail with the following error:
JCS-00503: OS account SYSJCS does not exist or is disabled on BRSAPPRDBWPV2
JCS-00315: job must run under OS equivalent of Oracle account SYSJCS
We run our oracle database on a Windows 2003 environment and also our Redwood/SAP servers are on a Windows 2003 server.
The job itself users "USER" account.
The only way we could get the jobs to start was by restarting the BWP Redwood services, and this worked fine.
Also want to state the we had the following issue at the sametime which was flagged up to us in "messages":
resubmit.update_job:
ORA-04061: existing state of package body "SYSJCS.CHAIN" has been invalidated
ORA-04065: not executed, altered or dropped package body "SYSJCS.CHAIN"
ORA-06508: PL/SQL: could not find program unit being called: "SYSJCS.CHAIN"
All our BWP process chains are executed via the RUN BW CHAIN script, which is copied and renamed for the process chain.
We have tried to replicate the error in our dev environment but it worked fine. RFC points nothing at all.. Any help would be much appreciated. OSS note has been raised...
Thank You
Jazz

Answer 1

Hi Jazz,
The SYSJCS.CHAIN package is not used for BI Process Chains, only for CPS Chains. So the invalidation must have come from another source.
When this error occurs, as long as there are sessions started before the package has been re-validated (state reinitialized), you can continue to run into this error until all sessions have been restarted. The extend of the error depends on the package being reinitialized (how often it is used and the dependencies it has) and the session that needs to call it.
I think the error may already have been there before you did the chain import and just happened to surface shortly after the import.
Regarding your other questions:
1. RSI_IMPORT_BW_CHAINS or RSI_IMPORT_BW_CHAIN_DEFINITIONS:
the second one is only needed if you want to display the process chain definitions in the web interface before the chain is even running in CPS (in the job monitor you only see the processes that have started); if you do not use that, RSI_IMPORT_BW_CHAINS is enough
2. How would you go about maintaining BW process chains in Redwood (CPS)?
This is a question that every customer runs into at some point. First, you currently can not change a process chain definition in the BI system from CPS. Then there are cases where you probably want to leave the process chain structure intact (typically on the deepest level: drop index, do some work, recreate indexes). And there are other cases where it can be useful to bring some logic to CPS (typically on all levels where you have process chain within process chain in BI, ie. on all but the deepest levels).
For this last case, which is of course the most interesting for CPS, it can be very valuable to recreate the BI "meta-chain" structure in a CPS job chain.
So here you replace the BI "meta-chain" calling several BI process chains by a Cronacle job chain still calling some of the BI process chains (the ones on the deepest levels).
Now you can add all the CPS extras for error handling, retries, cross system dependencies, (external) events, alerting, etc. etc. on each and every point in the CPS job chain, so you get a lot more information, intervention and recovery points on your BI process than you would when running the entire thing in one big BI Process Chain (triggered from CPS or not does not matter).
Typically the customer's decision here mainly depends on the advantages that can be achieved, especially if there are service levels to be met on the reports that need to be delivered from BI and these deadlines tend to get tighter by the month.
By reducing the total runtime of the process or reducing the number of errors that occur or if they occur, the amount of work to fix it, you can save a lot of time, and thus money.
Hope this helps.
Regards,
Anton.