Error in Full and Delta CPACache refresh.

Hi Experts,
In our production environent we have a SOAP -> XI - > PROXY scenario [Synchronous].
The Consumer of the WebService has reported an error:
500_Internal_Server_Error = SOAP:Server_Server_Error_XIAdapter_ADAPTER.JAVA_EXC
When I checked there are no messages in SXMB_MONI , but when I checked the Cache Refresh History I found that
there was error in both Full and Delta Cache Refresh. But the restart of the XI(Production) server resolved the issue.
The error is as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.pxi.su0956</EngineName>
<RefreshMode>F</RefreshMode>
- <GlobalError>
<Message>Couldn't parse Configuration Data cache update XML string from Directory.</Message>
org.xml.sax.SAXException: JavaErrors Tag found in cache update XML. at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.startElement(DirectoryDataSAXHandler.java:157) at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java(Compiled Code)) at javax.xml.parsers.SAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:56) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:871) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:640) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.process(CacheRefresh.java:104) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.doGet(CacheRefresh.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Can anyone tell me what is the cause of this error and how restart of the XI server resolved the issue?
Thannks,

Guys,
I have deployed the below components and after this repository could not be started which gives the below error.
1000.7.11.10.18.20130529165100
SAP AG
sap.com
SAP_XIAF
1000.7.11.10.11.20130529165100
SAP AG
sap.com
SAP_XIESR
1000.7.11.10.15.20130529165100
SAP AG
sap.com
SAP_XITOOL
We have the same issue. Still the Restart did not solve ths issue.
Can anybody help? We are not able to start the XI Repository.
Our PI components are as below
com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.xi.repository; nested exception is: java.rmi.RemoteException: [ERROR
CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:
        com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xm
l|CacheRefreshMDB^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)^M
1000.7.11.10.6.20121015232500
SAP AG
sap.com
MESSAGING
Regards
Omkar

Similar Messages

Full and Delta DTP doubts

There was a ongoing delta load happening between DSO 1 to DSO 2.
I deleted all requests from DSO 2.
And then ran first Full DTP ( DSO 1* to DSO 2) and immediately after full DTP ran Delta DTP ( DSO 1 to *DSO 2).
In Full DTP : There were 10,000 Records added into DSO 2
In delta DTP : there were 2,000 records added into DSO 2
I was bit surprised when I saw some data added in delta since before ( just 5 mins back ) I had ran full DTP therefore my understanding was delta would not bring anything.
By looking at various thread , I came to know that Full DTP get data from Active table and delta DTP get data from change log table.
However what if , if same records present in Active table and change log , so same records will be pick up by Full DTP run and also while delta DTP run , assume target DSO is in addictive mode then in such scenario duplicate record will be added and final result would be diffrent 9( i.e data get double up ).
How do we avoid such situation ?.
Any thoughts ?.
Edited by: Prashant on Aug 12, 2010 2:24 PM

HI,
DTP FULL: if you have 1 request in psa today and your dtp extraction mode is full it will load the data into the target.
                  in the next day you have run the infopackage and you habve got another request wich means in totall you have got
                  2request in psa so what the full dtp does is it will try to load both of them and you will get error saying duplicate records.
DTP DELTA:   it will load only the the fresh request from the source.
howe ever we dont do any initialisation in dtp the full and delta are only the extraction modes of data from the source. and its the infopackage which will fetch the deltas once the intialisation is done.
hope it helps.
Thanks & Regards
krishna.y

Full and delta Data loads in SAP BI 7.0

Hi,
Kindly explain me the difference between full and delta data loads in cube and DSO.
When do we select change log or active table(with or without archive) with full/delta in DTP for DSO.
Please explain the differences in data load for above different combinations.
With thanks and regards,
Mukul

Please search the forums. This topic has already been discussed a lot of times.

Two Extractor logics for full and delta?

Hi,
I have a situation where in the logics for full upload and delta uploads are drastically dfifferent!
What is best way to deal it?
shuould i have two different extractors for full and delta ?
Raj

Hi Raj,
I hope that u are working with the Generic Extractors. If the volume of the posting is too high then u need to restrict the data definitely from R3 side interms of the performance. And u need to maintain the Delta Functionality for the same.
If u cannt maintain the Delta from the R3 side then atleast try to restrict the same from BW side at the infopack level where u can extract the data based on the changed on and created with the two different IP's and update the same to the ODS(here make sure all the objects are with the overwrite).... and then u can maintain the Delta load from ODS to the Cube easily..
If the volume of the data is pretty less then u can use Full load to the ODS and then Delta to the Cube.
Thanks
Hope this helps..

Issue regarding Full and Delta InfoSpoke

Hi Experts,
I have created 2 Infospokes Full and Delta to extract data from DSO to SQL server, the settings in both the InfoSpokes are identical except for the extraction mode. However, the delta InfoSpoke is pulling the correct number of records from the DSO (360 records), but the full InfoSpoke is extracting only 196 records. I also tried loading the DSO using both Full/delta Infopackage and Full/Delta DTPs but still the results were same. Can anyone tell how this issue can be resolved.
Thanks,
Rajan

Dear Rajan,
I'd try to help you about your question,
Your case it's curious, did you check the filter in both InfoPackage?, try to delete and create them again (it is very important check whole filter). Otherwise, I suggest use Open Hub Destination which BI 2004s have the same functional (export data)
I hope this suggestion can help you,
Luis

Full and delta inventory

Hi all,
I'm studing the new "System planning Deployment and BP Guide" of 10.3 beta.
I see that in a "Daily use test" they schedule "One full and three delta inventory scans per devices".
I did not know that in ZCM10 there were two types of inventory. Is it a new functionality? Anybody can explain to me some info?
Thank you

mauro,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Filling of set up tables for Full and Delta updates

Dear Gurus,
How do I go about filling the set up tables if I want to load historical data to BW using LO **** pit when set up table is running on delta ?
I want to know how many set up tables will be there for each data source, Because if set up table is running on delta and using the same table I want to load historical data also then will I have to delete and fill set up tables or there will be a separate set up table for full upload and delta ?
If we have multiple set up tables for one data source then in the T-code OLI*Bw, where * -> App logistics num, so to fill I just say OLI6BW, then which set up table it is going to refer.
Clarify my doubt and get rewarded with plenty of points.
Regards
Mohan

Hi,
Filling up the set up tables depends on the datasource.
there are different T-codes for the respective extract structures
OLIIBW transaction PM data
OLI1BW INVCO Stat. Setup: Material Movemts
OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
OLI3BW Reorg.PURCHIS BW Extract Structures
OLI4BW Reorg. PPIS Extract Structures
OLI7BW Reorg. of VIS Extr. Struct.: Order
OLI8BW Reorg. VIS Extr. Str.: Delivery
OLI9BW Reorg. VIS Extr. Str.: Invoices
OLIABW Setup: BW agency business
OLIFBW Reorg. Rep. Manuf. Extr. Structs
OLIIBW Reorg. of PM Info System for BW
OLIQBW QM Infosystem Reorganization for BW
OLISBW Reorg. of CS Info System for BW
OLIZBW INVCO Setup: Invoice Verification
OLI7BW is the tcode for Sales Order.
Hope this solves Ur issue....
Assign points if helpful..
Rgs,
I.R.K

Interfaces- full and delta

Hi everybody,
I have a question on Interfaces-full file and delta file...Like is there a way to find out(either by looking at the program or the job, related to that pgm) as to wht exactly the outputof that particular interface, gives u(like the full file or a changes file only)? Or is there ny other method to find it out in SAP R/3 environment? As far as my knowledge goes, I think in BW we can find out using the Infopackages, am I right?
Thank You,
Appreciated a quick response,
Kaya.

Please search the forums. This topic has already been discussed a lot of times.

Full and delta loads

Hi,
Is there any procedure (program or table) to find out list of fullloads and delta loads in BW system?
Regards
Jaya
Edited by: Jayalakshmi Busetty on Feb 19, 2010 6:04 AM

Hi Jayalakshmi,
Your can find in datatarges in Manage Button.
Thanks & Regards,
Venkat.

Error in query and delta load

Hi people , i have a problem.
In my society ther's a document that was revocated from r3. Now when i successively load the delta , on bw the document still be active. How i can do? Where is the error?
Thanks

Hi,
When you say revocation is it the status "Reason or rejection" being set for that sales order.
If you want that to reflect in BW then you should check the status of the field.This will defenately appear in the BW as a delta.
If it about cancellation then you will have a record with cacellation indicator with in the BW delta.If you are loading it in the ODS with records mode mapped to ROCANCEl then cancelled records will be delted automatically from the BW and you will not be able to see those records.You can see the records with flag "reason for rejection".
Hope it helps
Thanks

Mixed Full and Delta from ODS to Cube

Hi,
we're facing the following problem:
We're loading data from an ODS to a Cube via Delta, every night. Due to reporting needs it's
nessesary we have to write some Infoobject-attributes to the cube.
This attributes will change sometimes. To display the current truth, we have to delete the old
assignments from the cube and update them with the new attribute values.
My idea was the following:
1. Identify the lines in the cube with the old attributes
2. Delete them via "selective deleting"
3. Load the lines with the new attributes from the ODS to the Cube
4. Proceed with delta upload from the ODS.
Is it a possible way or any better ideas.
Kind regards
Lars

Hi,
thanx for your reply. Of course we update the attributes:
For example:
Today Infoobjekt IO (Value IO-Value) has Attribute A with the value B.
Row in Cube: IO-Value, B, Keyfigure.
Tomorrow: Today Infoobjekt IO (Value IO-Value) has Attribute A with the value C.
So I have to correct the value of the attribute in the Cube.
Navigation Attributes can't be used.
Lars

Delta refresh and complete cache refresh

Hi,
iam doing the complete cache refresh and delta cache refresh in my scenario. after doing that the data's are reflecting very slowly in the RWB valuemapping cache.
sometimes it is not reflecting in the RWB valuemapping cache.
i refreshed the CPI cache and SLD cache, still it is not reflecting in the RWB.
could anyone tell me the solution for this to reflect in the RWB valuemapping cache????
Regards
sasi

Hi,
In the component monitoring check the RWB component and check the performance monitoring, may be some times performance monitoring is low because of the payload or some other conditions.
Delta Cache Refresh: Any new objects that have been created/modified during the design/configuration
                      activities are inserted into the temporary database tables when we use delta
                      cache refresh option.(Partial process refresh)
Complete Cache Refresh: All entries in temporary cache tables are deleted and a background program
                          for inserting the complete information about all the design/configuration
                          objects.(whole process refresh)

Extraction - full or delta or neither?

Hi all,
I have encountered a strange behaviour.
I am having a DataSource extracts data from R/3 to BW. In the "Test DataSource" screen, I put a range 2007.10 to the posting period, and it extracts all the records for 2007.10 for me.
But when I execute the InfoPackage in BW, and subsequently DTP and activation of DSO, I have got both 2007.10 and 2007.11 data in my DSO (which means all data ran into my DSO).
I suspect there is something wrong with my DS or DTP, because in my Data Transfer Process Monitor under "Details" tab, under "Process Request", there are multiple data package -- and it seems like this includes all the previous request and load that I have performed onto this DSO.
In my DTP extraction mode, I have tried both "Full" and "Delta" and in both cases, I got same problem.
Does anybody have any clue on how to resolve this? Is there a way to reset or I have missed out something? Appreciate for help. Thanks a lot.
- JK

Hi Alec,
If I delete the InfoPackage, would all the requests be deleted as well?
What I have tried is to delete the InfoPackage, delete data in DSO, and create Infopackage again, then execute DTP again.
As said, the PSA got only the data I need, but when loaded DTP and activate ODS, I got everything...
Still don't know why it behaves like that...
- JK

Error in INTEGRATION_DIRECTORY_HMI and CACHE REFRESH

Hi guys, well after checking the forum and several blogs i can't get rid of my problem!
I have a problem concerning INTEGRATION_DIRECTORY_HMI and CACHE REFRESH.
i wanted to get a file from a FTP-Server via CC and i got error:
<SAP:AdditionalText>Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Because of this i tried to update my cache (SXI_CACHE). When i do a Delta Cache Refresh i get:
Prefix Number: entry missing for system SSID client 100.
When i do a complete Cache Refresh nothing happens at all. I also checked the cache notification in IB - Integration Directory where i fin dout that only the Integration Server (ABAP Cache) won't refresh. Well status is started but nothing else is happening.
Then i checked the RFC INTEGRATION_DIRECTORY_HMI, did a connection test where i get an Internal Server error.
Let me tell u that the systems runs very well in the last days but now i have no clue what might be wrong.
Can somebody please advice me? I already read all blogs concerning this and also did a complete system-restart....
br Jens

when you check INTEGRATION_DIRECTORY_HMI with SM59 it is normal to get
HTTP Response 500 - Internal Server Error. In this case it meens everything OK
see the rediness check, that is attached to SAP note 817920
when you start the complete cache refresh, you can see
the function module SAI_CACHE3_REFRESH_BACKGROUND in SM58. As long as you can see this entry, the cache
refresh is ongoing. If the refresh takes too long and runs on an error, try to specify another timeout in INTEGRATION_DIRECTORY_HMI or in the ICM
Best Regards
Alexander
Message was edited by:
        Alexander Wrobel
Message was edited by:
        Alexander Wrobel
Message was edited by:
        Alexander Wrobel

Delta cache Refresh shows error

Hi,
In SXI_CACHE
I did Delta cache Refresh
In XI RunTime Cache Status shows :
1. cache contants are up-to-date (Green light)
2. Error during last attempt to refresh cache(red error)
Adapter Engine Connect Data Cache shows the following error
04D3344F63C6074CBB50E4E910CDB54A
AE Name: af.sxi.eccserver
Adapter Engine URL: http://eccserver:50100/MessagingSystem/receive/AFW/XI
USER: XIISUSER
whats meant by this error ? How to rectify this ?
Thanks,
srinivas
Message was edited by:
        srinivas

Is you adapter engine...centalized or decentralized   and is it a new installation or was it working before....
   If its centralized check the communication channels...If its decentralized you need to select the appropriate name in the drop down list for adapter engine option else you need select it as Integration server.
Also check whether you specified the exact adapter engine and XIAFUSER in exchange profile(Adapter framework node)...also check whether the users XIAFUSER and XIISUSER exists and are not locked......
Hope this helps...
Regards,
Ravi

Error in Full and Delta CPACache refresh.

Similar Messages

Maybe you are looking for