Solution: Check the cause of the error in Monitor in detail tabsrip.This gives the record number and Infoobject having format issue. Possible Causes: This is because of corrupt data or data is not in acceptable format to BW. Go to SE38 and execute program RS_Transtrucuture_activate ,mention source and name of the Infosource.ĭelete request from the datatarget and trigger Infopackage again.to get either delta or full data.Ħ) BW Error: Error log in PSA- Error occurred while writing to PSA.: Replicate datasource as shown in the screen shot below. Once this is done, delete the request by changing technical status to red and trigger InfoPackage to get delta back from source system. This will replicate the datasource and its status is changed to active. Give InfoSource and Source System and activate. Solution: Execute T code SE38 in BW give programme name as RS_Transtrucuture_activate and execute the programme. Possible Causes : This can happen when there is some changes done on datasource and datasource is not replicated. If its full update,request is deleted from the datatarget and Infopackage is triggered again to get full update. Infopackage for Delta update is triggered again to get delta from R/3 back. If the update mode is delta, technical status of job is changed to red and request is deleted from the datatarget. Solution: Contact the DB People Ticket is raised for DBA who can adjust the schedules for SMON process. Possible Causes: This can happen when SMON is running or any DBA Once DBA confirms that space issue is corrected, job is rerun to get data from source again. We can navigate to relevant short dump from monitor or execute transaction ST22. If its full update, request is deleted from the data target and InfoPackage is triggered again to get full update. InfoPackage for Delta update is triggered again to get delta from R/3 back. If the update mode is delta, technical status of job is changed to red and request is deleted from the data target. Ticket is raised for DBA Elizabeth Mayfield who provides the space required. Short dump message indicates this error message. Possible Causes: This is due to lack of space available to put further data. SAPR3./BIC/AZUSPYDO100 by 8192 in table space PSAPODS2D” If Job is an issue, SAP support team investigates it.ģ) BW Error: Database Errors: Enable to extend Table, enable to extend the Index.ĭatabase error text: “ORA-01653: unable to extend table Solution: Maestro jobs are handled by Production Services, if job is abended with an error code, BASIS team looks at Maestro problems. Possible Causes: This can be because of changes to Maestro or some changes to job. If it’s Full update, restart job again after deleting error request from the data target.Ģ) BW Error: Master job abended with error code or PR1 batch job did not run or get delayed. Retrigger the Info Package to load data again. If its delta update, in the source data target reset the delta. Solution: In Monitor check the technical status of the request for red status and then, delete the request from the data target. In my case, the Apache instance is shared between a number of applications/developers and I guess an upgrade or reconfiguration of the sever which I was not aware of has introduced these issues.SAP BI/BW Data Load Errors and Solutions for a support Project:ġ) BW Error: Failure occurred when delta Update is going on from one data target to another data target. Turning-off compression in the confluence web application solved the problem for me, as described here. I came across these instructions on testing for (and disabling) mod_deflate. This caused that the content was compressed twice which cannot be handled by the client.Īpache2 was using mod_deflate to compress content sent from the server to to the client. issuing the request directly on the machine where tomcat/confluence was running using a SOCKS proxy over ssh).įinally, I found out that the problem was caused by double compression performed by confluence and apache2. I also discovered that I can view all pages when I bypass the proxy (eg. The subtle problem was that some of the pages (like the login screen) could be viewed, while I lost the connection when viewing other pages. When I tried to view the confluence wiki pages, I received following error messages: I had similar problems when running a confluence instance (within a tomcat server) behind apache2 using either mod_jk or mod_proxy.
0 Comments
Leave a Reply. |