Load Failure’s
BW Error 1
2
3
Failure occurred When delta Update is going on from one data target to another data target.
Maestro job abended with error code or PR1 batch job did not run or get delayed.
Database errors: Enable to extend Table, enable to extend the Index. For example. Database error text. "ORA-01653: unable to extend table SAPR3./BIC/AZUSPYDO10 0 by 8192 in tablespace PSAPODS2D"
PBI-Wipro Confidential
Possible Causes 1.TRFC error 2. Data is incorrect (error records). 3. Locked by ALEREMOTE or user.
This can be due to some upgrade issue or some changes are done in Maestro schedule.
This is due to lack of space available to put further data.
Solution In Monitor check the technical status of the request for red status and then, delete the request from the data target
Document if any
Failure1.doc
If its delta update, In the source datatarget reset the delta. Retrigger the infopackage to load data again. If it’s Full update, restart job again after deleting error request from the datatarget. Maestro jobs are handled by Production Services, if job is abended with a error code, ticket will be raised by SAP BASIS team looks at Maestro problems. If there is a issue with PR1 batch job, ticket is raised for SAP team. This is Database error. Short dump message indicates this error message. Ticket is raised for DBA Elizabeth Mayfield who provides the space required. If the update mode is delta, technical status of job is changed to red and request is deleted from the datatarget. Infopackage for Delta update is triggered again to get delta from R/3 back. If its full update, request is deleted from the datatarget and Infopackage is
Failure2.doc
Failure3.doc
Page 1 of 6
Load Failure’s
``4
Dead Lock
5
Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RSQL/INSR//BIC/FZPUR_ VNDR ]" Please check the entries in the system log (Transaction SM21). Time Stamp errors :
6
7
This can happen when SMON is running or any DBA process is running.
This can happen when there is some changes done on datasource and datasource is not replicated.
Error log in PSA- Error occurred while writing to PSA.
This is because of corrupt data or data is not in acceptable format to BW.
Duplicate data error in Master data upload:
This can happen if there are duplicate records from
PBI-Wipro Confidential
triggered again to get full update. Contact the DB People Ticket is raised for DBA who can adjust the schedules for SMON process.
Execute T code SE38 in BW give programme name as RS_Transtrucuture_acti vate and execute the programme. Give Info source and Source System and activate. This will replicate the data source and its status is changed to active. Once this is done, delete the request by changing technical status to red and trigger Infopackage to get delta back from source system. Check the cause of the error in Monitor in detail tabsrip.This gives the record number and Infoobject having format issue. Compare the data with correct values and determine the cause of failure. Change the QM status of request in datatarget to red and delete the request. Correct the incorrect data in PSA and then upload data into data target from PSA. If it’s a delta update, change the technical status in the monitor to red and delete the request from the
Failure4.doc
Failure5.doc
Failure6.doc
Failure7.doc
Page 2 of 6
Load Failure’s
8
9
10
11
Error occurred in the data selection:
Processing (data packet): No data:
Process Chain failed.
Errors occurred in (IDocs and TRFC) here only one Data package arrived in BW that’s also with error: Non Updated IIDOCs found in the source system.
PBI-Wipro Confidential
the source system. BW do not allow duplicate data records.
datatarget.If its full upload delete the request. Delete the request. Schedule again with the option in the Infopackage, “without duplicate data” for master data upload.
This can occur due to either bug in the infopackage or incorrect data selection. In the infopackage. This can be because of some bug in Infopackage, rescheduling with another Infopackage corrects the problem. Errors occurred in one of the job in the process chain
Data selection checked in the infopackage and job is started again after changing the technical status to red and deleting the error request from the data target.
This can happen when in source system job is terminated or source system or BW is not available for whole period of data upload. This can also happen if resources are not sufficient in source
This type of problem we can solve with copy the Info package and reschedule the data.
Attend failure manually and go to process chain log for today and right click on the next job and select Repeat Option. This will execute all remaining jobs in process chain. IIDOC’s need to be processed manually either in OLTP or in BW depending on the failure. Error message in monitor in status tabstrip will take you to either BW or OLTP wherever there is a problem. Process IDOC’s, this will start the left over packets and will finish the load. This situation we have to check the Idocs so we have to check Idoc in WE05 and know the
Failure8.doc
Failure9.doc
Failure10.doc
Failure11.doc
Page 3 of 6
Load Failure’s system.
12
13
14
15
16
Processing (data packet): Errors occurred-Update ( 0 new / 0 changed ) : Errors occurred-Error records written to application log. Process Chains: Errors occurred in Daily Master Data
Errors occurred-Transfer rules ( 0 Records ) :
Missing messages -Processing end: Missing messages
Other (messages): Errors occurred in data selection
PBI-Wipro Confidential
This can be because of data not acceptable to datatarget although data reached PSA. This occurs when Transaction data is loaded before Master data. These errors happen when the transfer rules are not active and mapping the data fields is not correct. This can be because of incorrect PSA data, transfer structure, transfer rules, update rules and ODS. The 'valid from' date is smaller than the mimimum date, The 'valid from' date is smaller than the mimimum date, Error in node time interval with the ID 00000011. Details in next message, The
status these are WE51, WE52, WE53 may be and next goto WE 19 there we have to execute the exist Idoc with successfully loaded Idoc. Data checked in PSA for correctness and after changing the bad data data uploaded back into datatarget from PSA. Ensure to load Master data before Transaction data. Reload data depending on update mode(Delta/Full Update) Check for transfer rules, make relevant changes and load data again.
Check PSA data, Transfer structure, transfer rules, Update rules or datatarget definition.
Failure12.doc
Failure13.doc
Failure14.doc
Failure15.doc
Change the selection option and reload data. Failure16.doc
Page 4 of 6
Load Failure’s 'valid from' date is smaller than the mimimum date. 17
18
19
20
21
Activation of ODS failed
Source System not available
Caller 70 missing
This happens when data is not acceptable to ODS definition. Data need to be corrected in PSA. This can happen when request IDOC is sent source system, but the source system for some reason is not available. IDOC’s not processed completely.
Object corrupted- Delta Management of Master data lost but allows Full update. “ Update Mode R not supported. “
This happened during mass failures due to database space issue.
Error while opening file from the source system.
This happens when either file is open or file is not deposited on
PBI-Wipro Confidential
Check for Infoobject which has caused this problem in the monitor details tabstrip. Delete request from datatarget after changing QM status to red. Correct data in PSA and update data back to datatarget from PSA. Ensure that source system is available. Change technical status of request to red and delete request from datatarget. Trigger Infopackage again to get data from source system. Idoc Problem, Either wait till time out & process Idoc from detail monitor screen, or go to BD87 & process Idoc with status = YELLOW ( be careful while processing IDOCS from BD87, choose only relevant Idocs Reinitialization or there is one program for repair of Info object. During reinitialization ensure to use option of Only PSA, avoid duplicate data and subsequently into datatargets. Go to Transaction code RSRV to check consistency of Infoobject. Arrange for file, delete error request from datatarget and trigger Infopackage to load data from file.
Failure17.doc
Failure18.doc
Failure19.doc
Failure20.doc
Failure21.doc
Page 5 of 6
Load Failure’s
22
23
24
Object locked by user
While load is going on in R/3 table is locked
Change run already started by ALEREMOTE
PBI-Wipro Confidential
server or not available. This can happen when user or ALEREMOTE is accessing the same table.
This happens when some datasource is accessing R/3 transparent table and some transaction takes place in R/3 This can happen due to overlapping of same request to Program.
Change the technical status of job to red, delete request from datatarget and trigger Infopackage again. If its delta update it will ask for repeat delta, Click on Yes button. Change the technical status of job to red in the monitor and retrigger the job again from R/3.
Go to Transaction Code RSATTR, see if it’s running. Once it’s finished, repeat the job.
Failure22.doc
Failure23.doc
Failure24.doc
Page 6 of 6
