This action might not be possible to undo. Are you sure you want to continue?
14, 2008 12:18 AM in Enterprise Data Warehousing/Business Warehouse
Subscribe Print Permalink Share
Hello Friends My Best Wishes to everyone for this New Year. I'm new baby in blog world. I entered the forum world last year. This is my first blog. Whole idea of this blog is to cover different process chain errors we come across:
Different Process Chain Errors: Process Chain Error: Created process chain to load data into an ODS and further updates it to an Infocube, activate process chain, schedule the process chain to start immediate. "Job BI_PROCESS_DROPINDEX could not be scheduled. Termination with returncode 8" - Message no. RSPC065 or "Job BI_PROCESS_LOADING could not be scheduled. Termination with returncode 8" Message no. RSPC065 The diagnosis revealed the following: Diagnosis Program RSPROCESS is to be scheduled as job BI_PROCESS_LOADING under user BWREMOTE. System response Scheduling terminated with return code 8. The meanings of the return codes are as follows: SY-SUBRC = 4: Scheduling terminated by user
Note 23538: Problems due to inconsistent host name notation..SY-SUBRC = 8: Error when scheduling job (JOB_SUBMIT) SY-SUBRC = 12: Error in internal number assignment Procedure Check the system log for more detailed information. But it is not proceeding further after getting errors. When executing Transaction RSPCM and when clicking a process chain log view "Request Status Change" window pops up.cannot start background jobs... Implement these notes to solve the problem: . To fix the problem check following OSS Notes: Note 947690: "Process Chain: Termination with Return code 8". Basically system is not having backend user. In transaction SU01 create a backend user like ALEREMOTE or something similar and give authorization SAPALL to run background jobs and click on "Logon Data" Tab Page and look for User Type and change the User Type from Communication to System User Type Communication: User type for communication between systems. User Type System: User type for background processing and communication within a system Process Chain Error: Process Chain stops at intermediate point and does not execute further Process Chain stops in the middle and does not execute further and status of step is Red but process indicator is set that process chain should proceed further even in errors.. Note 511475: "Scheduling jobs with BW background users".. Execute Function If look at the system log it will say that user .. Reason for this error is User (Which in this case is BWREMOTE). Note 150315: BW-Authorizations for remote user in BW and OLTP.
. the system does not suggest.5.Do not suggest process As a result. NoteS 1003941. generate or insert automatically any processes into the chain..0.No check on missing instance for "hold" Note 1005481 .Confirmation error during repair Notes 1003941 and 1005481 are relevant to BW 3. but there is no instance Note 1008038 . Process Chain Error: In Process Chain load data to ODS and after loading data. You ran a process chain mostly it is in green.Default Chains . System is suggesting while activation that the "Further Update" process type should proceed activation of ODS. 1005481 and 1008038 will work for BI 7... If you want no corresponding processes to be inserted automatically please flag option to remove system suggesting you process go to transaction RSPC . one is in yellow error If you selected option of system suggesting you process then in the warning message system will suggest you process like: " There must be a type "Update ODS Object Data (Further Update) process behind process "Activate ODS Object Data" var. System generates "Further Update"step. If there are no further update process in your process chain then you can add the process type otherwise you can ignore these warnings if process chain is meeting the requirement.ODS_0_customer name in the chain".Note 1003941 .in the chain. activate ODS data and using Infopackage to load further object.Process successful. Use Transaction Code SNOTE to download Notes and implement it.Your Process Chain Settings . "Update ODS Object Data (Further Update) process has to follow process" Activate ODS Object Data var. Once the ODS is activated and Further Update should be added for updating the other data target. .ZPAK.
even though one or more processes may be successful. If on higher Support Pack than SPS10 and still having the same issue and if still not able to activate the process chains for BI Admin Cockpit.. the process chain log may not contain any instances. In the ABAP Editor... Errors may occur after you import the support package. Note 885918 . Note 994007 .Object Infopackage not found in RSOR "The InfoPackages mentioned are shadow InfoPackages and the message is unnecessary because there should not have been a search for the package at all. Above notes will help in resolving the problem.Process Chain Error: Activating the content for BI Admin Cockpit. transaction SE38 execute the program RSSM_SHIPDVERS_CLEANUP which will solve the problem Scenario: When Process chain is not starting subsequent job even though the previous job completes successfully and the process is green. of type ‘Infopackage' is not available in version ‘D' Based on OSS Note 966131 . you can display and repair inconsistent InfoPackages if necessary. but there is no instance and Note 1003941 . When activating the process chains. Using the RSSM_SHIPDVERS_CLEANUP report. the chain does not continue after the successful process. . Check Note 1005481 ..P27:SDL: Inconsistencies in shadow Infopacks and RSSHIPDVERS.0 BI Support Package 11.Correction: Process successful. get a "red" error message: Object .Correction : No check on missing instance for "hold".Corrections: Deadlock with external status query causes this error..... Note 844739 ...." and we should apply the correction (as part of SPS10) for this purpose.. Check OSS Note 914305 SAPBINews NetWeaver 7.. As a result... In very quick parallel asynchronous processes..P29:P6: InfoPackage shadow creation in Content System....
The RSBTCDEL2 Program. Initial chain sometime fails on the step where it calls the main process chain. No batch process available. Error Message: Resource error. Enter your Data Store Object In Change Actions Select "Change Runtime Parameters" and Press Execute Action.DTP . It fails at Activate DSO Data.0 Transaction RSCUSTA2 is obsolete. Process Chain executes fine till last step Activate DSO Data. Scheduled batch job calls initial process chain and then initial chain then calls main master data chain. The main process chain will not start when this happens then need to run it manually. Initial chain contains a start process with setting "Start using meta chain or API and then a process to call the main process chain.Job count cannot be created and also check Note 784969 . .Scenario: You might have nightly load in your production system. In Parameters for Activation. Change Process Params and set to DIALOG with the server group = "Parallel_Generators".0 loading data to DSO. Change Process Params and set to DIALOG with the server group = "Parallel_Generators". No return of the split processes Activation of M records from DataStore object terminated In SAP NW 7.Activate DSO Data. Process Chain Error: Activation of DSO thru Process Chain gets failed In BI 7. Use Transaction RSODSO_SETTINGS (Maintenance of Runtime parameters) In transaction RSODSO_SETTINGS. In the process flow Execute Infopackage . Schedule the RSBTCDEL2 job to delete old finishing jobs to fix a problem as per Note 728947 . In Parameters for SID Generation. Process terminated Time limit exceeded. DSO is getting activated manually but with process chain it fails to activate.
Change it there to dialog.Incorrect reading of runtime parameter for Data Stores Object Process Chain Error . It should take it from the default in RSODSO_SETTINGS. Check this Notes: Note 1118205 . the system highlights every level of the process chain where the number of processes is too high. Note 994689 .Remove the option in "Parallel Processing" for background and with number of processes to 2 each for activation and SID. These settings override the RSODSO_SETTINGS settings. The invalid character can be seen in the error message of the ODS activation. Note that even when you create an new variant. Save the variant and execute the process chain.RSODSO_SETTINGS Maintain runtime parameter of DataStore obj. In transaction RSKC. And when you click it. You'll have to change them all. Special background jobs run to facilitate the execution of the process chain. If the number of parallel processes is greater than the number of available background processes. Check in the process chain variants for your activations.Invalid characters: If ODS activation fails because of invalid characters in that case first step would be to try to insert the new character in the allowed character set in BW. the system compares the result with the number of background processes on the selected server (or the total number of all available servers if no server is specified in the attributes of the process chain). After this is done activate the ODS object and it should go through sucessfully. or you could update directly in table RSBATCHPARALLEL if you have too many. Note your BTC process distribution and make sure that an extra BTC is free so the supporting background jobs can run. and produces a warning. . it will set it default to background. You will probably find that "Parallelism" is switched on at the bottom. System checks for the background processes available for a process chain : During the check. it's probably set to background. Change the settings of the Variant ODS activation process type (Parallel Process Settings) in each process chain for each ODS separately and change it to dialog with parallel generators with number of processes to 2 each for activation and SID. insert the character at the end and click on execute.
Process Chain Execution hangs. Note 1003360 .Number of required BTC processes for process chains Note 833168 . Note 192658 .Parameter rdisp/max wprun time.Process Chain activation returns 'Error in remote call of destination Note 906512 .BW fact tables: Deleting index from process chain terminates Note 754433 .Setting Parameters for BW systems.Process Chain run terminates with error RSPC007 Note 1024354 .Process Chain terminates when you reorganize master data.Please find list of other OSS Notes that might be helpful in resolving process chains errors: Note 947687 . Note 25528 .Activating process chains is very slow Note 621400 . .Template precalculation in a process chain terminates Note 1057875 .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.