Cache Distribution failure

Hi all,
What is the optimization features available in the Distribution Cache Mechanism.
Currently Im running two clusters in 2 nodes and observed the performance is degrading when the clusters (from different nodes) are added.
Can any one help me on this?

Hi,
Can you elaborate more on the issue? If you are adding more clusters to the same node, it is obvious that you are trying to squeeze more juice from the same hardware so it is expected.
Cheers,
_NJ                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • (-2004) Critical cache refresh failure

    Dear All,
    We are useing SAP Business One 2007 B PL 10, DB is Sql Server 2005 SP1.
    While logging in to SAP we are getting error msg "(-2004) Critical cache refresh failure" and SAP application closes.
    The DB is accesible from Sql Management Studio and Data is visible.
    But, while restoring the backup of this DB, following error msg is showing..
    System.data.sqllient.sqlError: Could not continue scan with Nolock due to data movement.
    Please help.
    Regards,
    Brijesh Kumar Rai

    Dear Brijesh Kumar Rai,
    Welcome you post on the forum.
    You may check: (-2004) Critical cache refresh failure
    Thanks,
    Gordon

  • Cache distribution - Java object cache

    Hi.
    I'm trying to use Oracle Java Object Cache (cache.jar), the one included in the 9iAS 9.0.3.
    Everything works fine but the cache distribution between different JVM:s.
    Anyone got this to work?
    Regards
    Jesper
    package test;
    import oracle.ias.cache.*;
    * Singleton Cache class.
    public class Cache {
         /** The singleton instance of the object. */
         private static Cache instance = null;
         /** The root region. */
         private final static String APP_NAME = "Test";
         * Protected constructor - Use <code>getInstance()</code>.
         * @throws Exception if error
         protected Cache() throws Exception {
              CacheAccess.defineRegion(APP_NAME);
         * Gets the singleton instance.
         * @return The instance of the Cache object.
         public static Cache getInstance() throws Exception {
              if (instance==null) {
                   createInstance();
              return instance;
         * Creates the singleton instance in a thread-safe manner.
         synchronized private static void createInstance() throws Exception {
              if (instance==null) {
                   instance = new Cache();
         * Put an object on the cache.
         * @param name The object name
         * @param subRegion The sub region
         * @param object The object to cache
         * @throws Exception if error
         public static void put(String name, String subRegion, Object object) throws Exception {
              CacheAccess appAcc = null;
              CacheAccess subAcc = null;
              try {
                   appAcc = CacheAccess.getAccess(APP_NAME);
                   // Create a group
                   Attributes a = new Attributes();
                   a.setFlags(Attributes.DISTRIBUTE);
                   appAcc.defineSubRegion(subRegion, a);
                   subAcc = appAcc.getSubRegion(subRegion);
                   if (!subAcc.isPresent(name)) {
                        subAcc.put(name, a, object);
                   } else {
                        subAcc.replace(name, object);
              } catch (CacheException ex){
                   // handle exception
                   System.out.println(ex.toString());
              } finally {
                   if (subAcc != null) {
                        subAcc.close();
                   if (appAcc != null) {
                        appAcc.close();
         * Gets a cached object from the specified sub region
         * @param name The object name
         * @param subRegion The sub region
         * @return The cached object
         * @throws Exception if requested object not in cache
         public static Object get(String name, String subRegion) throws Exception {
              CacheAccess appAcc = null;
              CacheAccess subAcc = null;
              Object result = null;
              try {
                   appAcc = CacheAccess.getAccess(APP_NAME);
                   subAcc = appAcc.getSubRegion(subRegion);
                   // define an object and set its attributes
                   result = (Object)subAcc.get(name);
              } catch (CacheException ex){
                   // handle exception
                   throw new Exception("Object '" + name + "' not in cache region '" + subAcc.getRegionName() + "'.");
              } finally {
                   if (subAcc != null) {
                        subAcc.close();
                   if (appAcc != null) {
                        appAcc.close();
              return result;
         * Invalidates all objects in all regions
         public static void invalidateAll() throws Exception {
              CacheAccess appAcc = CacheAccess.getAccess(APP_NAME);
              appAcc.invalidate(); // invalidate all objects
              appAcc.close(); // close the CacheAccess access
         // Main method for testing purposes.
         public static void main(String[] args) throws Exception {
              try {
                   System.out.println(">> Caching object OBJ1 into region TEST1.");
                   Cache.getInstance().put("OBJ1", "TEST1", "Object cached in TEST1.");
                   System.out.println(">> Getting OBJ1 from cache region TEST1.");
                   System.out.println(Cache.getInstance().get("OBJ1", "TEST1"));
              } catch (Exception ex) {
                   System.out.println(ex.getMessage());
    Contents of JAVACACHE.PROPERTIES:
    # discoveryAddress is a list of cache servers and ports
    discoveryAddress = host1.myserver.com:12345,host2.myserver.com:12345
    logFileName = c:\javacache.log
    logSeverity = DEBUG
    distribute = true

    I have same problem
    Exist some reason?
    I'm testing Cache with isDistributed() method and I still got false!
    Thanx

  • Fill Olap cache distribution type

    Hi,
    I'm trying to fill the olap cache with information broadcasting, but I cannot see option "Fill olap cache" in the distribution type.
    Only distribution type "broadcast E-Mail" and "Broadcast to portal" are present.
    I reached the broadcasting screen from Tcode RSRT -> ABAP Web.
    Is a Precalc. server required to get access to "fill olap cache" distribution type ?
    How can I get access to distribution type "fill olap cache"  ?
    System: BW 7.01 SP06

    Hi Brian,
    Please check below:
    Broadcasting in BI 7.x - Do I need Portal, Missing Distribution Types
    Also check the expert for
    In SAP NetWeaver BI 7.0 (2004s), which BEx Web functions require SAP NetWeaver 7.0 Portal?
    As soon as you use any of the new BI capabilities for SAP NetWeaver 7.0 (2004s) BEx tools (such as BEx Analyzer & Broadcasting), you require usage types BI Java and Portal. The only exception is if you do not use SAP NetWeaver 7.0 BEx tools and ONLY use the old 3.x BEx tools.
    https://www.sdn.sap.com/irj/sdn/nw-datamanagement?rid=/library/uuid/a5067965-0901-0010-6f8a-bbf0b7424283#q-6
    -Vikram

  • (-1) Critical cache refresh failure!

    Hi Experts,
    While SAP client  is up and running the following message pop ups. "(-1) Critical cache refresh failure" and the application close.
    The issue occurs randomly on some clients.
    We are running SAP Business One for HANA PL09 HF1 AND HANA Server rev 69.
    Please advise
    Vasilis Korolis

    Hi,
    Please check thread:
    http://scn.sap.com/thread/1030870
    Thanks & Regards,
    Nagarajan

  • TopLink 11g Cache Coordination failure in WebSphere 6.1

    Hello,
    I've recently upgraded to TopLink 11g and I am trying to make cache coordination feature work in WebSphere 6.1 using JMS. Once configured I am getting the following errors on the server side:
    [4/14/09 17:22:25:321 PDT] 00000032 SibMessage E [:] CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1511:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol. at com.ibm.ws.sib.msgstore.transactions.MSDelegatingXAResource.addWork(MSDelegatingXAResource.java:140) at com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.cmdRemove(AbstractItemLink.java:1330) at com.ibm.ws.sib.msgstore.AbstractItem.remove(AbstractItem.java:828) at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1487) at com.ibm.ws.sib.processor.impl.ConsumerSessionImpl.receiveWithWait(ConsumerSessionImpl.java:421) at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receiveInboundMessage(JmsMsgConsumerImpl.java:1525) at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receive(JmsMsgConsumerImpl.java:707) at oracle.toplink.internal.remotecommand.jms.JMSTopicRemoteConnection.run(JMSTopicRemoteConnection.java:229) at java.lang.Thread.run(Thread.java:810)
    [4/14/09 17:22:25:353 PDT] 00000032 SystemOut O [TopLink Warning]: 2009.04.14 17:22:25.353--ServerSession(1261194028)--Thread(Thread[Thread-65,5,WebSphere_EJB_Timer_Service_WorkManager: WM Service Group])--Local Exception Stack:
    Exception [TOPLINK-22109] (Oracle TopLink - 11g (11.1.1.0.1) (Build 081030)): oracle.toplink.exceptions.RemoteCommandManagerException
    Exception Description: Failed to receive JMS message from JMS provider
    Internal Exception: javax.jms.JMSException: CWSIA0103E: An exception occurred while receiving a message: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1526:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol..
         at oracle.toplink.exceptions.RemoteCommandManagerException.errorReceivingJMSMessage(RemoteCommandManagerException.java:139)
         at oracle.toplink.internal.remotecommand.jms.JMSTopicRemoteConnection.run(JMSTopicRemoteConnection.java:257)
         at java.lang.Thread.run(Thread.java:810)
    Caused by: javax.jms.JMSException: CWSIA0103E: An exception occurred while receiving a message: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1526:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol..
         at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receiveInboundMessage(JmsMsgConsumerImpl.java:1637)
         at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receive(JmsMsgConsumerImpl.java:707)
         at oracle.toplink.internal.remotecommand.jms.JMSTopicRemoteConnection.run(JMSTopicRemoteConnection.java:229)
         ... 1 more
    Caused by: com.ibm.websphere.sib.exception.SIResourceException: CWSIP0003E: An internal messaging error occurred Default.Topic.Space in com.ibm.ws.sib.processor.impl.LocalConsumerPoint, 1:1526:1.28, com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol.
         at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1521)
         at com.ibm.ws.sib.processor.impl.ConsumerSessionImpl.receiveWithWait(ConsumerSessionImpl.java:421)
         at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.receiveInboundMessage(JmsMsgConsumerImpl.java:1525)
         ... 3 more
    Caused by: com.ibm.ws.sib.msgstore.ProtocolException: CWSIS1001E: The requested action could not be carried out as it does not comply with the resource manager's internal transaction protocol.
         at com.ibm.ws.sib.msgstore.transactions.MSDelegatingXAResource.addWork(MSDelegatingXAResource.java:140)
         at com.ibm.ws.sib.msgstore.cache.links.AbstractItemLink.cmdRemove(AbstractItemLink.java:1330)
         at com.ibm.ws.sib.msgstore.AbstractItem.remove(AbstractItem.java:828)
         at com.ibm.ws.sib.processor.impl.JSLocalConsumerPoint.receive(JSLocalConsumerPoint.java:1487)
         ... 5 more
    Any idea what I am doing wrong here?
    Lukas

    Fixing listener is not enough. Old and lastest code has this for references to ServerPlatform.launchContainerRunnable, which WebSpherePlatform do not override:
    CommandPropagator:
    public void asynchronousPropagateCommand() {
    // The async logic is in the run() method
    rcm.logDebug("async_propagation", (Object[])null);
    this.rcm.getServerPlatform().launchContainerRunnable(this);
    public void propagateCommand(RemoteConnection conn) {
    Object[] arguments = { command.getClass().getName(), conn.getServiceId() };
    rcm.logDebug("propagate_command_to", arguments);
    try {
    // The result will be null on success, and an exception string on failure
    Object result = conn.executeCommand(command);
    if (result != null) {
    // An error occurred executing the remote command
    handleExceptionFromRemoteExecution(conn, (String)result);
    } catch (CommunicationException comEx) {
    // We got a comms exception.
    this.handleCommunicationException(conn, comEx);
    JMSTopicRemoteConnection:
    DiscoveryManager:
    public void startDiscovery() {
    if (rcm.isCommandProcessorASession()) {
    rcm.getCommandProcessor().processCommand(new ProfileDiscoveryStartedCommand());
    // Only start if we are currently stopped
    if (this.isDiscoveryStopped()) {
    this.rcm.getServerPlatform().launchContainerRunnable(this);
    JMSTopicTransportManager:
    public Hashtable getConnectionsToExternalServicesForCommandPropagation() {
    if(this.getConnectionsToExternalServices().isEmpty() && !this.rcm.isStopped()) {
    this.createExternalConnection();
    if(this.localConnection == null) {
    // It's a good time to create localConnection,
    // in a new thread - to return externalConnections promptly.
    this.rcm.getServerPlatform().launchContainerRunnable(new Runnable() {
    public void run() {
    try {
    createLocalConnection();
    } catch (RemoteCommandManagerException ex) {
    // Ignore exception - user had a chance to handle it in createLocalConnection method:
    // for instance to change host url and create a new local connection.
    return super.getConnectionsToExternalServicesForCommandPropagation();
    }

  • Where is ias903 j2ee and web cache distribution for NT?

    http://otn.oracle.com/software/products/ias/devuse.html
    gives option 4
    NT - 324 MB
    Oracle9iAS J2EE and Web Cache
    - Oracle HTTP Server
    - Oracle9iAS Containers for J2EE
    - Oracle9iAS Web Cache
    - Oracle Enterprise Manager
    - New! v9.0.3 Linux , Solaris , HP-UX , HP Tru64
    - NT/2000
    Clicking at NT/2000 points me to 9ias90201_core.zip.
    So where is the 903 distribution? Why is it Sun Solaris?!
    Oracle9iAS Release 2 downloads for Sun SPARC Solaris
    On this page you will find:
    Oracle9iAS J2EE and Web Cache:
    - v9.0.3
    - v9.0.2.0.1
    Oracle9iAS Enterprise Edition
    Oracle9iAS Supplemental CD's
    Other Utilities
    Oracle9iAS J2EE and Web Cache Release 2 v9.0.3
    9ias90201_core.zip - (340,044,344 bytes)
    This is a lightweight version of Oracle9iAS v2. It consists of the following components:
    -Oracle HTTP Server
    -Oracle9iAS Web Cache
    -Oracle9iAS Containers for J2EE (OC4J)

    Hi Ken --
    We are just about wrapped up with our Oracle9iAS Release 2 (9.0.3) version for Windows NT. As you've seen, we have released the 903 version for a number of Unix platforms (Solaris, HP-UX, HP-Tru64, Linux) already and the Windows platform will follow shortly.
    For the moment, if you're running on Windows and want to use the J2EE 1.3 functionality, you can download the pure Java OC4J 903 distribution available from OTN. This is the same set of Java code that is the 9iAS distribution.
    cheers
    -steve-
    http://otn.oracle.com/software/products/ias/devuse.html
    gives option 4
    NT - 324 MB
    Oracle9iAS J2EE and Web Cache
    - Oracle HTTP Server
    - Oracle9iAS Containers for J2EE
    - Oracle9iAS Web Cache
    - Oracle Enterprise Manager
    - New! v9.0.3 Linux , Solaris , HP-UX , HP Tru64
    - NT/2000
    Clicking at NT/2000 points me to 9ias90201_core.zip.
    So where is the 903 distribution? Why is it Sun Solaris?!
    Oracle9iAS Release 2 downloads for Sun SPARC Solaris
    On this page you will find:
    Oracle9iAS J2EE and Web Cache:
    - v9.0.3
    - v9.0.2.0.1
    Oracle9iAS Enterprise Edition
    Oracle9iAS Supplemental CD's
    Other Utilities
    Oracle9iAS J2EE and Web Cache Release 2 v9.0.3
    9ias90201_core.zip - (340,044,344 bytes)
    This is a lightweight version of Oracle9iAS v2. It consists of the following components:
    -Oracle HTTP Server
    -Oracle9iAS Web Cache
    -Oracle9iAS Containers for J2EE (OC4J)

  • LMS 4.1 Patch Distribution Failure

    I didn't have this problem in 4.0, and I've tried to upgrade 2 different model routers (891 and 2811) with the same error, anyone know what this means? Google was no help.
    SWIM0151: The device is not running IOS Modular image in Install mode. Hence patch images cannot be distributed.
    Thanks,
    Craig

    It sounds like you're trying to use the Pathc Distribution workflow for non-modular devices.  Do not select Patch Distribution.  Instead, select Software Distribution, and then follow the specific flow you want from there.

  • Distribution Failure

    Why does my PDF form fail to distribute? PDF form loads
    on-line at Acrobat.com, tracking displays my group list of email
    addressees, however, forms are not being sent. I made the group
    email batch in the only application that seems to to read by
    acrobat professional: Apple Address Book. The list has 65 address
    and are clearly displayed, but personal name information is not
    display in the tracking window. Is this problem a result of glitch
    on Acrobat.com, or is it a problem with the email input? too many
    address? Thank you for anyone's help.

    Can you please list the exact steps you are taking to e-mail
    the form to your list of recipients?

  • (-1) Critical cache refresh failure! Application will be closed.

    Hi Team,
    I have been using VPN to connect into SAPB1 remotely which was working fine all along but past couple of days, i've been encountering this error from the subject. I went thru the attached link which doesn't fall under my concern so i am creating this new thread.
    Upgrading to PL 43
    scenario:
    the user while trying to logon to the system enters UID/PASSWORD and sees the error message and the application closed immediately after that. Any idea why??
    System:
    SapB1 PL 39 all along, no change since installation past 1 year plus
    client settings unchanged also
    Note: Login by remote desktop possible without such errors.
    Kindly advise.
    naz

    please post your question in correct forum to get faster reply
    [SAP Business One System Administration|System Administration;
    Thanks
    Krish

  • CBS Activation Failure

    Hi All,
    We are working on ESS Components which are having few modifications and everything went on well till yesterday. Today we are seeing strange behaviors while activating the activity. It juts throws an error like cache verification failure. Please find below the CBS Request log. Sorry for posting the Build log.
    REQUEST PROCESSING started at 2010-09-02 21:59:15.053 GMT
        ACTIVATION request in Build Space "MRCK_HTRESSDV_D" at Node ID: 14,793,550
         [id: 24,237; parentID: 0; type: 4]
         [options: NO OPTIONS]
        Waiting for access: 3 ms
        ===== Pre-Processing =====  started at 2010-09-02 21:59:15.057 GMT
            List of requested for activation activities:
                'sap.com_SAP_ESS_1' compartment
                    DHTR094 - TIR236 BE ADDR Subtype Text Display Problem
                        [ISN 171][created by KUMARAPP at 2010-09-02 17:56:21.0][OID 303b3c5db6d211df875b00237da9de6a]
                There is 1 activity in compartment sap.com_SAP_ESS_1
                1 activity will be processed by this request
            Analyze dependencies to predecessor activities... started at 2010-09-02 21:59:15.069 GMT
                Analyzing predecessors in compartment "sap.com_SAP_ESS_1"
                    No dependencies to predecessor activities found.
            Analyze dependencies to predecessor activities... finished at 2010-09-02 21:59:15.112 GMT and took 43 ms
            Analyze versions... started at 2010-09-02 21:59:15.112 GMT
                List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2010-09-02 21:59:15.168 GMT and took 55 ms
                Synchronize metadata for [sap.com/ess/be/addr] started at 2010-09-02 21:59:15.170 GMT
                    Verification of DL [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/] finished at 2010-09-02 21:59:15.272 GMT and took 19 ms
                    Verification of cache (level 2: Comparison of attributes) finished at 2010-09-02 21:59:15.294 GMT and took 21 ms
                Synchronize metadata for [sap.com/ess/be/addr] finished at 2010-09-02 21:59:15.303 GMT and took 133 ms
                < CHANGE > 'sap.com/ess/be/addr' DC
            Analyze versions... finished at 2010-09-02 21:59:15.304 GMT and took 192 ms
            Analyze activities... started at 2010-09-02 21:59:15.304 GMT
                Loading component definitions
                1 component to be build in compartment "sap.com_SAP_ESS_1"
            Analyze activities... finished at 2010-09-02 21:59:15.382 GMT and took 78 ms
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2010-09-02 21:59:15.385 GMT
                    'sap.com/ess/be/addr' variant 'default'
            Analyze request DC BV... finished at 2010-09-02 21:59:15.487 GMT and took 102 ms
            Prepare build environment in the file system... started at 2010-09-02 21:59:15.488 GMT
                Synchronize development configuration... started at 2010-09-02 21:59:15.488 GMT
                Synchronize development configuration... finished at 2010-09-02 21:59:15.489 GMT and took 1 ms
                Synchronize sources for [sap.com/ess/be/addr] started at 2010-09-02 21:59:15.518 GMT
                    Verification of DL [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/] finished at 2010-09-02 21:59:17.890 GMT and took 13 ms
                        Verification of cache FAILED due to the following reasons:
                        Cache inconsistency detected: comparison of cache items on the paths:
                            [/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_bg.xlf]
                            [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_bg.xlf]
                        on verification level 2 FAILED:
                        Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]
                        Cache inconsistency detected: comparison of cache items on the paths:
                            [/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_el.xlf]
                            [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_el.xlf]
                        on verification level 2 FAILED:
                        Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]
                        Cache inconsistency detected: comparison of cache items on the paths:
                            [/usr/sap/trans/nwdi/CBS/52/.CACHE/1375/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_es.xlf]
                            [ws/HTRESSDV/sap.com_SAP_ESS/dev/active/DCs/sap.com/ess/be/addr/_comp/src/packages/com/sap/xss/hr/per/be/address/detail/DetailView.wdview_es.xlf]
                        on verification level 2 FAILED:                    Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]
        Difference in attribute 'Timestamp' [Thu Oct 23 15:14:02 EDT 2008][Thu Oct 23 15:14:03 EDT 2008]
                    Verification of cache (level 2: Comparison of attributes) finished at 2010-09-02 21:59:18.498 GMT and took 608 ms
                Synchronize sources for [sap.com/ess/be/addr] finished at 2010-09-02 21:59:18.857 GMT and took 3 s 339 ms
                Synchronize used libraries... started at 2010-09-02 21:59:19.056 GMT
                    PP 'FloorplanManager' of DC 'sap.com/pcui_gp/xssfpm' [DCID=1188] (in SC 'sap.com_SAPPCUI_GP_1' [SCID=1373]) ... OK
                    PP 'default' of DC 'sap.com/tc/wd/webdynpro' [DCID=592] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK
                    PP 'default' of DC 'sap.com/com.sap.exception' [DCID=8] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK
                    PP 'default' of DC 'sap.com/tc/ddic/ddicruntime' [DCID=400] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'default' of DC 'sap.com/tc/col/api' [DCID=397] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'default' of DC 'sap.com/tc/wdp/metamodel/content' [DCID=415] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'default' of DC 'sap.com/com.sap.mw.jco' [DCID=12] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK
                    PP 'default' of DC 'sap.com/com.sap.aii.proxy.framework' [DCID=336] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'default' of DC 'sap.com/tc/logging' [DCID=11] (in SC 'sap.com_SAP-JEE_1' [SCID=1372]) ... OK
                    PP 'default' of DC 'sap.com/com.sap.aii.util.misc' [DCID=337] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'FPMUtils' of DC 'sap.com/pcui_gp/xssutils' [DCID=1189] (in SC 'sap.com_SAPPCUI_GP_1' [SCID=1373]) ... OK
                    PP 'default' of DC 'sap.com/tc/ddic/metamodel/content' [DCID=117] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'default' of DC 'sap.com/tc/cmi' [DCID=396] (in SC 'sap.com_SAP_JTECHS_1' [SCID=1376]) ... OK
                    PP 'InternationalPersInfo' of DC 'sap.com/ess/per' [DCID=844] (in SC 'sap.com_SAP_ESS_1' [SCID=1375]) ... OK
                Synchronize used libraries... finished at 2010-09-02 21:59:20.986 GMT and took 1 s 930 ms
                Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.
            Prepare build environment in the file system... finished at 2010-09-02 21:59:20.987 GMT and took 5 s 499 ms
        ===== Pre-Processing =====  finished at 2010-09-02 21:59:20.988 GMT and took 5 s 931 ms
        Waiting for access: 3 ms
        ===== Processing =====  started at 2010-09-02 21:59:20.991 GMT
            BUILD DCs
                'sap.com/ess/be/addr' in variant 'default'
                    The build was SUCCESSFUL. Archives have been created.
        ===== Processing =====  finished at 2010-09-02 22:00:31.588 GMT and took 1 m 10 s 597 ms
        ===== Post-Processing =====
        Waiting for access: 14 ms
        ===== Post-Processing =====  started at 2010-09-02 22:00:31.603 GMT
            Check whether build was successful for all required variants...
                "sap.com/ess/be/addr" in variant "default"   OK
            STORE activation build results... started at 2010-09-02 22:00:33.402 GMT
                Update DC metadata... started at 2010-09-02 22:00:33.408 GMT
                    'sap.com/ess/be/addr' DC is CHANGED
                Update DC metadata... finished at 2010-09-02 22:00:33.539 GMT and took 131 ms
                STORE build results... started at 2010-09-02 22:00:33.540 GMT
                    "sap.com/ess/be/addr": store meta-data
                    "sap.com/ess/be/addr" in "default" variant  is PROCESSED
                STORE build results... finished at 2010-09-02 22:00:35.549 GMT and took 2 s 9 ms
            STORE activation build results... finished at 2010-09-02 22:00:35.549 GMT and took 2 s 147 ms
            Change request state from PROCESSING to SUCCEEDED
            Analyze effect of applied changes to buildspace state... started at 2010-09-02 22:00:35.550 GMT
                Handle Cycles... started at 2010-09-02 22:00:35.572 GMT
                    No new cycles detected.
                Handle Cycles... finished at 2010-09-02 22:00:39.175 GMT and took 3 s 603 ms
                Determine components that have become DIRTY due to the results of this request started at 2010-09-02 22:00:39.296 GMT
                    No such components have been found.
                Determine components that have become DIRTY due to the results of this request finished at 2010-09-02 22:00:39.297 GMT and took 1 ms
                The following Internal Build Requests will be canceled because Request DCBVs are already built by this request
                INTERNAL BUILD request in Build Space "MRCK_HTRESSDV_D" at Node ID: 14,793,550
         [id: 24,165; parentID: 23,837; type: 32]
            Analyze effect of applied changes to buildspace state... finished at 2010-09-02 22:00:41.498 GMT and took 5 s 948 ms
            Integrate activities into active workspace(s)...
            Integration of activities in compartment "sap.com_SAP_ESS_1" started at 2010-09-02 22:00:41.505 GMT
            Integration of 1 activities in compartment "sap.com_SAP_ESS_1" finished at 2010-09-02 22:00:42.826 GMT and took 1 s 321 ms
            An incomplete integration in compartment "sap.com_SAP_ESS_1" of buildspace "MRCK_HTRESSDV_D" has resulted because of errors during request processing!
    Request 24238 has been created to re-initialize the compartment
        ===== Post-Processing =====  finished at 2010-09-02 22:00:42.852 GMT and took 11 s 249 ms
        Change request state from SUCCEEDED to FAILED
        Error! The following problem(s) occurred  during request processing:
        Error! Communication error when performing integrations. Integration failed with unexpected CONFLICT status [com.sap.dtr.client.lib.protocol.entities.ErrorEntity@5719ce2c]. Request FAILED.
    REQUEST PROCESSING finished at 2010-09-02 22:00:42.865 GMT and took 1 m 27 s 812 ms
    Regards,
    Nagarajan

    Hi,
    first please take a look at the note:
    http://service.sap.com/sap/support/notes/133013
    As long as you don't have any 'real' issue you can ignore this error message.                                 
    If this is not the case, then try to proceed this way:
    1. delete the buildspaces dev and cons (you can do it in the Buildspace view of the CBS webui)
    2. resave the track ,this will recreate the buildspaces. (you do it in the landscape configurator of CMS -- track data tab)
    3. Restore system state (you find a button for it on the development and consolidation tabs in the transport studio of CMS webui)
    4. reimport the software into development and consolidation (transport studio -- development/consolidation tab).
    Until the buildspaces are deleted, your developers won't be able to activate and build. Do not forget to reimport the software back to the buildspaces dev and cons before your developers are continuing their work. Your sources won't get lost as they are stored in DTR.
    Best Regards,
    Ervin

  • Cache / application node configuration

    Hi!
    I am doing a Coherense evaluation and yesterday I talked to the UK Tangosol office that suggested I post these questions here to more quickly get answers. I hope you can help.
    I would like to configure a number of nodes to ONLY hold data for a distributed cache. Let us call them cache nodes.
    A number of other nodes should be configured to participate in the same distributed cache but not hold any data. They will use a "near" cache with the distributed cache as "back cache". This is the nodes were my application logic will go. Let us call them application nodes.
    My first question is if I must have the same configuration on the cache nodes as I have on the application nodes (i.e. must I use a "near cache" even though I do not need or want a "front cache" here since nobody will access the data locally? I assume that the invalidation of even an empty front cache has some associated cost and this is another reason to not have one when not needed.
    My second question is if I must make som special provisions in my CacheStore (that will use JDBC to sync with a database) to ensure that modified data will either not be written to either the cache or the database or both (for instance in the event of a critical hardware failure of the cache node calling the CacheStore during a call to one of the "store" or "erase" methods) - or is this "automagically" taken care of some how by the layer above the CacheStore? Is the answer the same or different if I use replication of the data in the replicated cache or not? My plan is to NOT use replication and instead take the hit that some cache data is lost (will be reloaded if needed later) in the event of a critical error killing one of the cache nodes. If I must do something special in the CacheStore to ensure that the database and cache is always coherent I would like some example code that i can start from...
    My third question is if my proposed configuration is fully coherent or is it theoretically possible that a client can send a request that modify an object to one of the application node and then (assuming my load balancer is NOT sticky) immediately requests the same data from another application node and get the OLD object value back? I.e. is the update/invalidation from/to the near caches synchronous or asynchronous? If this is a "possible" scenario is there anything that can be done to avoid it with this setup (except getting a sticky load balancer)?
    Lastly if you happen to sit on some configuration examples that set up exactly this kind of scenario (or something very close to it) I would appreciate having a look at them. I have found some examples on the forum but none that do the same thing...
    Best Regards
    MagnusE

    Thanks for your quick and informative answer Jon! I need to think more about some of your points to make sure i understand the implications. A few quick follow-up questions though:
    With a write-through cache, Coherence will call your
    CacheStore implementation before updating the cache,
    and so the database will always have the most current
    version of the data, even in the event of a cache
    server failure.But will the cache also get the new verssion of thew data somehow in the event of a failure (that oocur just after the data has been stored in the database but before the storage node managed to put it in the cache) or will this cause non-coherence between database and cache? Will the application node get an exception back from its put operation in this case (so it at least is aware that the data may not have gone into both the cache and the database)?
    What happens if the data store fail to put the data in the database (due to a database constraint or a database failure etc) and the store method in the datastore class throws an exception? Will the storage node still put the new (or changed) object in the cache (causing a non-coherence between databse and cache) or not?
    Do you have some documentation that explains how the product handles all the known "corner cases" (like failures during or just after the datastore methods are called etc - it would be valuable since they are often the cause of the rare but really nasty problems...
    Best Regards
    Magnus
    Message was edited by: Magnus
    Message was edited by: Magnus

  • Write Failure due to packet loss

    Hi All,
    Is it possible to occur a cache put failure due to packet loss. The below JMX report log (network-health-detail.txt) shows that TX success as 0.9999 for NodeId(8 PROXY node) and RxSuccess shows 0.9999 (node id 9 which is a STORAGE) exactly the same time.
    At the same time I have inserted a cache item which went missing in the cache.
    Is it possible to correlate the cache loss with the below data.
    Please correct me if my understanding is work. Really looking forward for some expert look at this.
    Regards
    Srinivas
    Batch Counter Report Time RefreshTime Node Id Tx Success Rx Success PacketsSent Current Packets Sent PacketsResent Current Packet Resent PacketsRepeated Current Repeated PacketsReceived Current Packets Received
    24962 Thu May 05 15:54:37 BST 2011 Thu May 05 15:54:37 BST 2011 8 0.9999806938625789 1.0 116249593 51797.0 20 1.0 179 0.0 479093147 107230.0
    24962 Thu May 05 15:54:37 BST 2011 Thu May 05 15:54:37 BST 2011 9 1.0 0.9999898626387551 110148867 169211.0 118 0.0 61.0 55759817 98645.0

    It is more likely that you had other issues that caused your data to go "missing". Lost packets would be resent anyway so should get there eventually. The success rates of 0.9999 would be fine, you would be lucky to get a success rate of 1.0 all the time unless your cluster was not doing much.
    When you say the data goes "missing" what do you mean. Presumably you do a put to get data into the cache, how to you try to get it back - a get or a query using a Filter.
    What classes are you using for the keys - this can be important and can affect whether your cache works as you expect it to.
    JK

  • Cache agent table update transaction size

    Is there a way to impose a transaction size limit, a "commit every n rows", on readonly cache group updates?
    Specifically for single table cache groups.

    An unexpectedly large number of updates (> 1,000,000 rows) were made to an Oracle table with 89 columns referenced by a readonly cache group. The Cache Agent started an incremental update for this cache group and during the update, the datastore ran out of space, so the update was rolled back. All of the update and rollback records went into the lognnn files, using up most of the disk bandwidth. After the rollback completed and the Cache Agent started a refresh for that interval and the same failure/rollback sequence started again. This cache update failure/rollback cycle continued until the datastore full message was noticed in the log and I was able to pause the automatic refresh of this one table. Then I manually refreshed the cache group with "commit every n rows".

  • MDX cache location in BI

    Experts--
    How can i administer the MDX cache which is used for BI broadcasting in a normal BI system.?
    rsrt/rsrcache can be used  for OLAP cache...would like to know similiar for MDX cache...
    Best Regards,
    Vikash

    BI 7/0 has new distribution types are Fill Precalculation Store, Precalculate Value Set, Fill OLAP Cache, and Fill MDX Cache. These distribution types allow the BEx Broadcaster to replace the functions of the Reporting Agent. (Old Reporting Agent scenarios still run in SAP NetWeaver 2004s. However, the Reporting Agent will not be developed any further and is removed from the SAP NetWeaver 2004s Data Warehousing Workbench. You can now only reach the Reporting Agent using transaction code REPORTING_AGENT.) The Fill Precalculation Store distribution type allows you to precalculate Web templates, and the Precalculate Value Set option you to fill pre-calculated value set variables with values for characteristic values. The pre-calculated value sets are then available as variable values in BEx queries. With the Fill OLAP Cache, and Fill MDX Cache distribution types, you can warm up the OLAP and MDX cache with BEx queries.
    You can check with tcode The new T-code RSRD_ADMIN which allows Administrators easy access to three key sources of information:
    Global broadcast settings
    Schedules of broadcast settings
    Broadcast logs
    You can also check with tcode SDMO with text search for required functionality.
    Check this link http://csc-studentweb.lrc.edu/swp/Berg/Conferences/SAP_Reporting_analytics_2007/pdf/Track6_session7.pdf
    Thank you,
    Shyam

Maybe you are looking for

  • ASSET ACCOUNTING TREATMENT

    HI, I created the Asset PO mentioning the asset number and its GL which is assigned during the asset creation with asset class. While doing GR no accounting document available and when posting invoice it is crediting to vendor and debit to that asset

  • Exporting a report on the Linux server

    We are trying to export a report generated in the Excel format. This works fine in local host, bust has the problem when the application is uploaded on the Linux server. We are getting the below error: java.io.FileNotFoundException: /usr/share/tomcat

  • Mac OS 10.6.7 and Samsung SCH-LC11 Hotspot

    Seems Mac OS 10.6.7 has an issue with keeping a connection when using WPA on certain wireless routers. The Samsung hotspot is one router that is an issue for this version of the OS. If you are having problems connecting with your MAC change the wirel

  • Can't Remove File Path from my Finder Toolbar

    My brother put file path on my computer by going into the Terminal app. and typing something like: killa apps But I don't like it, so I want it gone please help.

  • Content is showing on Mobile and Tablet but not desktop

    Hi, I have been using the DW templates (fluid Grid) to update my site. Somewhere I went wrong and now the gallery content is now not showing on my imac desktop yet it is showing on my ipad and iphone: Advertising and Commercial Photography Orange Cou