Resolution:
Following stack trace is thrown when cache server is started
---------------------------------------------------------------------------
javax.management.InstanceAlreadyExistsException: com.tibco.be:service=BackingStore,name=objectTableCache-bs$WF-ILWHOLESALE-CLUSTER$$ObjectTableIDs
at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:470)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1428)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:954)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:355)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:515)
at com.tibco.be.oracle.BECoherenceOracleStore.registerMBean(BECoherenceOracleStore.java:179)
at com.tibco.be.oracle.BECoherenceOracleStore.&ltinit>(BECoherenceOracleStore.java:97)


Solutions(s) :
--------------
The above exception is because of the Oracle driver problem Or improper ojdbc.jar And is not related to TIBCO BE.
It can be because of any one or combination of more than one scenarios listed below -

Scenario 1:
----------

1. Check for the occurrences of the ojdbc.jar in the system from where you want to run the BE application.
  
Windows - You can use the "Search" Utility to find all the directories where ojdbc.jar is present.

Unix -  Run the below command from root location. This will give location of all the ojdbc.jar in this
         environment.            
            find . -name "ojdbc.jar" -print


2. After you find all the locations, just remove it from everywhere and simply put the latest ojdbc.jar in the
   &ltTIBCO_HOME>/tra/&ltversion>/lib and re-run the test.

3. The reason for it is that there may be some older versions of ojdbc.jar present in the system. So for clarity, put
   the latest ojdbc.jar at one place.You can check the version of Implementation-Version of Oracle driver in the Manifest.MF file
   which can be found when you unjar/unzip the contents of ojdbc.jar.
  

Scenario 2:
----------
If you still get the problems after performing changes in Scenario 1, simply put the reference of latest ojdbc.jar in the
BusinessEvents tra file and re-run the test.

Scenario 3:
----------
The problem can be because of not using the Oracle thin driver and using other Oracle driver.