Cache Connect in cluster

Hi!!!
We have 4-nodes linux cluster based on MC Service Guard.
T10 works as a standalone in the packet "pack1" with other apps. Apps uses t10.
Packet "pack1" (with t10 and apps) can be moved to any of 4 cluster nodes, and it doesn't have a home node (it may live on node 1 year, 3 month on node 2, 1 day on node 3, etc...).
Is there any possibilities to set up cache connect in that kind of cluster configuration?
We don't want to install additional T10 instance on all nodes :)

Chris,
but then pack1 moved to another node, a host name (where t10 now works) is changed.
And since pack1 has moved to another node, values like BOOKMARK and REPORTS in TT_03_AGENT_STATUS for that t10-subscriber remains the same, and off course it turns to growth TT_03_34575_L table.
Maybe, it is because t10-subscriber identified in TT_03_AGENT_STATUS by hostname?
In t10 cache connect works fine.
But in oracle we have growing table and we can't make our own monitoring of cache connect based on BOOKMARK and REPORTS.
I believe that I've done something wrong. But what exactly?
Linux Cluster:
node1 pack1(T10 7.0.5 64bit, Oracle client 11 64bit, other apps...)
node2 pack2
node3 pack3
node4 pack4
Oracle 11G R1 64 bit is installed on remote linux machine
Cache Connect:
CREATE READONLY CACHE GROUP MYCACHE
AUTOREFRESH INTERVAL 15 SECONDS ...
Alexander

Similar Messages

@CMS shorthand - unable to connect to cluster

Hi
We are moving from CE10 to BOE XIR3.1.
We make a fair bit of use of the shorthand CMS syntax for system, say for eg:
@Reports instead of the server name of RPNSBLK7
It just makes it easier for users/developers to use the @Reports syntax. When we run our VB Scripts now, or try authenticating from CR2008, we get the following error:
"Unable to connect to cluster @Reports:6400 to retrieve CMS member list. Locally cached member list not present. Logon cannot continue."
Has anyone else noticed this, and is there a workaround/solution?
Our production server name is extremely laborious and the cluster name is far easier.
Ta
Glenn

The first time you login, use the full server name of the CMS machine. Once the list of cluster members is locally cached, the next time on you should be able to use just the cluster name.
BTW, why are you saying @Reports:6400? You do not need the port number when using the cluster name. You need to use the port # only with the CMS name and when it is a non-standard port #.
Edited by: Sarang Deshpande on Jun 3, 2009 5:07 PM

PI : unable to connect to IR with cache connectivity test via RWB

Hi,
Please help to resolve the issues.
Server Details: SAP PI 7.0, SUNSOLARIS with DB2.
PI server was working fine without any issues for the past 2 weeks, Unfortunately issue is the connection failure.
PI services were unable to interlink internally.
cache connection Test Error Below:
Connection to system null using application null lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/conntest/int?" with user "PIRWBUSER". Response code is 404, response message is "Not Found"
SLDCHECK done with success,SPROXY no issues,
users are not locked & password not changed.
Thanks,
Bala

After full cache refresh. with SXI_CACHE i got cache error "UPDATE" detail error as below.
com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://sap-02.aig.com:50000/rep/hmi_service_swc_manager/int?container=any" with user "PIDIRUSER". Response code is 404, response message is "Not Found"
     at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doGet(HmisServletImpl.java:640)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

When i doing cache connectivity test , i am getting below error

When i doing cache connectivity test , i am getting below error, could you please suggest me what action need's to be done
Integration repository, Integration Directory,Integration server ABAP, Integration server java is green, only adapter engine is showing red.
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem
[Fetch Data]: com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:490)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: Unable to find an associated SLD element (source element: SAP_BusinessSystem, [CreationClassName, SAP_BusinessSystem, string, Name, BS_PI_DEV, string], target element type: SAP_BCSystem)
at com.sap.aii.ib.server.sldquery.SLDQuery.dammiIlMioCentralAdapterFramework(SLDQuery.java:70)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:191)
at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:155)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
[Data Evaluation]:

Check Surya's reply: Cache-Connectivity-Test in RWB
The same procedure in detail manner is given in this How-to guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34
Are you using any Business System? If yes then make sure that you have imported it properly into ID....in this case ID --> Environment --> Clear SLD Cache.
Regards,
Abhishek.

CPA Cache Connectivity test fails

Hi All,
We are facing the following issues that have to do with the Adapter Engine:
1) In RWB, the Adapter Engine is in error/red status with the following details: Adapter Engine, message: fatal DeleteJob (Default Delete Job) failed.
2) In RWB, the Cache Connectivity Test fails with the following error: Communication with JMS server failed.
3) The CPA Cache refresh gives erros.
Any ideas? There are no Service users locked, SLDCHECK works fine etc.

Hi,
It seems to like problem with your JMS Connector.
For this, login into Visual admin -->cluster >services>JMS connector-->runtime (tab)->check the factories / destinations. Please contact with your basis team, they will might be helpful to you. After that restart your server, it will solve your issue.
Regards,
P.Rajesh
Edited by: Rajesh_1113 on Jun 5, 2011 9:01 AM

Cache Connectivity Test in RWB fails

Hi Guys,
When I go to RWB in Cache Connectivity Test, I get the following error:
" Error during last test run executed by EGKATZIOS, on 10 u039Du03BFu03B5 2009 3:35:37 u03BCu03BC: Error executing testClientServerException exception:Communication with JMS server failed
com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed"
Any ideas ?
Also in IR, in Cache Notifications, remain in Red Status "Not Yet Started" and I have to manually Execute them.
Which I realized is related to an error I get when I activate the Change List in IR "Communication with JMS server failed Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service". However, activation works with a second attempt.
Everything else, SXI_CACHE, HTTP Connections, SLDCHECK, Service Users, HTTP and JMS services in VA work fine.

Hi,
Pls follow this path,
login to J2EE Visual aadmin>cluster>services.JMS connector>runtime(Righ hand side tab)->check the factories / destinations (if anything is in red color X mark).
Ask your basis admin to correct this.Final possible solution is to restart the server....
Hope dis will help.
Regds,
Pinangshuk.

Cache Connect passthrough

I have a 32bit Oracle client installed on Solarus 8 server. Have DSN defined to passthrough to backend oracle database. When I try to select from the backend database I get the following 5102 error
5102: Cannot load backend library 'libclntsh.so' for Cache Connect. OS error message 'ld.so.1: ttIsqlCmd: fatal: /oracle/product/9.2.0/lib/libclntsh.so: wrong ELF class: ELFCLASS32'. See TimesTen Reference Guide for possible causes.
LD_LIBRARY_PATH has $ORACLE_HOME/lib and libclntsh.so exists although it is a link to libclntsh.so.9.0

Found the problem - Loaded the 64bit version of TimesTen vs the 32bit version. I was sure I loaded the 32bit version. Oh well - Reinstall time

Cache connect to multi instance

Hi all,
By seeing previous forum lists, I found that TimesTen's one Data Store can cache connect to one Oracle instance.
Does TimesTen has a plan to support for multi database instance in upcoming verions?
And.. let say that i made data store for each Oracle database instance. Can I refer to each data store in the query as db link?
Best regards,
Yu-Mi

There are no current plans to allow a single TT cache datastore to cache data from multiple Oracle databases.
TimesTen does not currently support anything like DB links and there are no plans to do so. Each datastore is a separate entity and queries and transactions cannot span datastores.
Sorry.
Chris

Cache connect to any DB

hi,
The cache connect supports only for oracle. Is this a strategic limitation or the
cache connect to any db is in the development queue?
Coz we find we loose many
deals since timesten can't coexist with databases other than oracle.
(Its true that timesten can coexist with other databases, provided that we write code
using XLA to sync data between TT and Other DB. but that incurres an additional development cycle)

There are currently no plans to support other databases as backends via Cache Connect.
Chris

Only one connection established between TT Cache Connect and Oracle10g

When I use AWT, I found in a TT datastore only one connection established between TT Cache Connect and Oracle10g .
In our project, the massive real-time data in TT need to be propagated to Oracle10g, but the data are blocked beacuse the slower Oracle10g DB. Can I establish a connection pool that have multiple connections between TT Cache Connect and Oracle10g?
Thanks for your help.

Hi,
I'm afraid that the current implementation of AWT uses just one connection to Oracle and there is no way to change that. This is indeed a significant bottleneck...
One possible workaround is to split your data across multiple datastores as each datastore will have its own AWT connection to Oracle. Not very nice but about your only option with AWT...
Sorry, Chris

Please recommend solutions for Cache Connect and ?

---> Solution I
2 servers create Cache Connect to RDBMS
---> Solution II
1 server create Cache Connect to RDBMS and create active standby pair with another server

Hi,
If you only need READONLY caching in TimesTen and all updates will be made in Oracle then you have two main options:
Multiple READONLY Caches
For this you have one or more separate TimesTen caches each with a READONLY cache group defined against the oracle DBMS. Each cache can cache different tables/data or they can can cache the same tables/data as required.
This architecture is very flexible (adding or removing TimesTen servers is very simple) and very scalable. It also provides very good HA; if one cache is down applications can just access a different cache.
However, due to the asynchronous, time based nature of the refresh from Oracle to Timesten at any moment in times the data in all the caches may not be 100% consistent with each other or Oracle.
By this I mean the following:
- Assume that you have 2 (or more) READONLY caches caching the same data from Oracle, with an AUTOREFRESH interval of T1
- At some time, T2, you update, in Oracle, one of the rows cached by the caches.
- At some later time, T3, you query the updated row via both caches
If (T3 - T2) < T1 then the values returned by your query may differ between the caches (depending on where exactly they are in the autorefresh interval when the update is done).
Active/Standby pair using 2-SAFE replication with READONLY cache group and optional read-only subscribers
With this architecture you define a TimesTen Active/Standby replicated pair using 2-safe replication and containing the READONLY cache group. 'Scale out' is accomplished in one of three ways:
1. Adding further A/S pairs with a READONLY cache group
2. Adding read-only subscriber datastores to the original A/S pair
3. A mixture of (1) and (2)
The main advantages of this architecture are as follows:
1. When 2-Safe is used within the A/S pair, queries to either cache will always return consistent results (i.e. the consistency issue that I described for the first scenario does not exist in this configuration). However, threr can still be inconsitencies in results between the A/S pair and any readonly subscribers (since the replication to them is asynchronous) but given the high performance of TimesTen replication the latency between a change appearing at the A/S pair and the readonly subscribers will typically be a few ms rather than potentially several seconds for the multiple-cache scenario.
2. The loading on the central Oracle DBMS arising from AuTOREFRESH processing is reduced compared to the multiple-cache scenario. The difference in loading between this solution and the multiple cache solution will be larger as more TT servers are deployed.
It should be noted that the operational management of this solution is a little more complex than for the first scenario since the A/S pair must be monitored and a 'failover' trigerred if there is some fauilure within the pair.
Hope that helps a little.
Chris

RWB Component Monitoring - Cache Connectivity Test failure

Hi,
I have done the Cache Connectivity test in RWB-Component monitoring.
For the Integration Server - Integration Engine XYZ.
I am getting error
Result of Self-Test
   Can the SLD be reached?   ... Details OK
   Does the Integration Engine know the business system?   ... Details   OK
   Are roles in SXMS_CONF_ITEMS and SLD consistent?   ... Details Error
   Is Web service security available?   ... Details
The error message os
Details for 'Are roles in SXMS_CONF_ITEMS and SLD consistent?'
Inconsistent roles. System Landscape: Integration Server. SXMSGLOBAL: Application System
How to solve this issue.
Regards
Farhat

Hi
Use Tcode SXMB_ADM -> integration engine ,Assign proper Client to Integration Server.
look this similar thread
Are roles in SXMS_CONF_ITEMS and SLD consistent?

TimesTen Cache Connect support for Oracle 11g

The latest 7.0.5 readme mentioned that "Oracle Release 11gR1 is supported with TimesTen Cache Connect to Oracle on Linux x86 32-bit and 64-bit platforms, and on Windows 32-bit."
What about Solaris 10? It looks like on Solaris 10 only Oracle 10gR2 being supported. What is so specific about Oracle 11?
Thank you,
Alex

TimesTen 7.0.5 can be used to cache data from different versions of Oracle database.
The reason why the support for Solaris, AIX, and HP-UX were not at the same time as the Linux platform was because Oracle database 11g was not available on those platforms initially. So TimesTen 7.0.5 was certified to support only the ones available first, and support for other platforms was added as 11g became available on those platforms. It was just timing of the certification, code base is the same.
Susan

Cache Connect TimesTen v7.0.5 and Oracle DB 11.1g error

I tested Cache Connect on HP-UX v11.31. I have error when running the command
"call ttCacheUidPwdSet" with error "Cannot load backend library
'libclntsh.so' for Cache Connect." as below:
$ sh bin/ttIsql demo
Copyright (c) 1996-2008, Oracle. All rights reserved.
Type ? or "help" for help, type "exit" to quit ttIsql.
All commands must end with a semicolon character.
connect "DSN=demo";
Enter password for 'testuser':
Connection successful:
DSN=demo;UID=testuser;DataStore=/home/timesten/demo;DatabaseCharacterSet=US7ASCII;ConnectionCharacterSet=US7ASCII;DRIVER=/etc/TimesTen/timesten70/lib/libtten.so;OracleId=demodb;PermSize=128;TempSize=128;TypeMode=0;
(Default setting AutoCommit=1)
Command> call ttCacheUidPwdSet('testuser','testuser');
5102: Cannot load backend library 'libclntsh.so' for Cache Connect. OS
error message 'Unsatisfied code symbol 'sem_destroy' in load module
'/u01/app/oracle/product/11.1.0/lib/libclntsh.so'.'.
The command failed.
Command>
We use Timesten version 7.0.5, Oracle Enterprise Database 11.1g, HP-UX
Itanium 64bit v11.31, Oracle Client 11.1g.
ORACLE_HOME=/u01/app/oracle/product/11.1.0/
I have tried for several days but to no results. Please advise how to solve the problem. Thank you very much

Dear all,
I have found a solution for this error. We could use Oracle 10.2 g on HP-UX v11.31. However, when you do the installation, command will be: "./runInstaller -ignoreSysPrereqs".
The steps to install oracle client are following ( $ORACLE_CLIENT_HOME):
1) su - oracle
2) Download Oracle 10.2g HP-UX Itanium "10gr2_client_hpi.zip"
3) unzip the file : "jar xvf 10gr2_client_hpi.zip " . The new folder name "client"
4) cd client; ./runInstaller -ignoreSysPrereqs
After that, you need to remove the $ORACLE_HOME/lib/libclntsh.so and link to new file
5) rm $ORACLE_HOME/lib/libclntsh.so
6) ln -s $ORACLE_CLIENT_HOME/lib/libclntsh.so.10.1 $ORACLE_HOME/lib/libclntsh.so
7) export LD_LIBRARY_PATH=$ORACLE_CLIENT_HOME/lib:$TIMESTEN_HOME/lib:$ORACLE_HOME/lib
8) export PATH=$ORACLE_CLIENT_HOME/bin:$PATH
Then you need to restart the TimesTen Daemon so that it could get the new system parameters
9) ttDaemonAdmin -restart
if you do not restart the TimesTen Daemon, you could get the error:
Command> call ttCacheStart;
10024: Could not start cache agent for the requested data store. Could not initialize OCI function pointers. Error: none
The command failed.
And finally, the CacheConnect is up
$ ttIsql demo
Copyright (c) 1996-2008, Oracle. All rights reserved.
Type ? or "help" for help, type "exit" to quit ttIsql.
All commands must end with a semicolon character.
connect "DSN=demo";
Enter password for 'testuser':
Connection successful: DSN=demo;UID=testuser;DataStore=/home/timesten/demo;DatabaseCharacterSet=US7ASCII;ConnectionCharacterSet=US7ASCII;DRIVER=/etc/TimesTen/timesten70/lib/libtten.so;OracleId=demodb;PermSize=128;TempSize=128;TypeMode=0;
(Default setting AutoCommit=1)
Command> call ttCacheUidPwdSet('testuser','testuser');
Command> call ttCacheStart;
Command> CREATE READONLY CACHE GROUP readcache
AUTOREFRESH INTERVAL 5 SECONDS
FROM readtab
(a NUMBER NOT NULL PRIMARY KEY, b VARCHAR2(31));Command> LOAD CACHE GROUP readcache COMMIT EVERY 256 ROWS;
2 cache instances affected.
Command> SELECT * FROM readtab;
< 1, hello >
< 2, world >
2 rows found.
Command>
Thank you for all of your help.

Cache connectivity fails

Hi Experts,
We have done some configurations in SLD for XI system ,scenario is like several systems will be connecting to Central SLD system.
After all the configurations have been completed and when we test the cache connectivity,it will successful on first attempt and further attempts it fails.
*Error is Cache notification from integration repository failed error when accessing the integration directory*
We have tried like deleting the cache notifications from IR , ID and refresh the cache like java cache refresh ,delta cache refresh,full cache refresh.
Eventhough all we tried and test the cache connectivity it fails.
Please help on this issue.

Hi Experts,
The Notes 939592 and 720717 are not applicable to our problem because we have migrated the configurations of the existing SLD system to new SLD system(New System installed) to reduce the Load on the existing SLD system.
We have done the necessary configurations for the new SLD system in our PI system and when we test the cache connectivity test in the component monitoring in RWB,it is failing .
So please suggest and help in resolving the problem to make the cache connectivity test successful.
Thanks
Pradeep

Cache Connect in cluster

Similar Messages

Maybe you are looking for