Resolution:
Description:
=========
Full error stack is:

[runtime.session] Error performing initAll()
java.lang.RuntimeException: com.tibco.as.space.ASException: SYS_ERROR (space_def_mismatch - SpaceDef mismatch space=objectTableCache-nobs-MenloCEPOperational--ObjectTableIds)
    at com.tibco.cep.runtime.service.dao.impl.tibas.ASControlDao.start(SourceFile:322)
    at com.tibco.cep.runtime.service.om.impl.AbstractDaoProvider.internalCreate(AbstractDaoProvider.java:341)
    at com.tibco.cep.runtime.service.om.impl.AbstractDaoProvider.createControlDao(AbstractDaoProvider.java:325)
    at com.tibco.cep.runtime.service.cluster.system.impl.ObjectTableCache.init(ObjectTableCache.java:62)
    at com.tibco.cep.runtime.service.cluster.MultiAgentCluster.init(MultiAgentCluster.java:117)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:703)
    at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:260)
    at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:151)
    at com.tibco.cep.container.standalone.BEMain.main(SourceFile:69)

Environment:
=========
All platforms; BE 5.1.1


Cause:
=========
This error will happen when a new be-engine joins an existing cluster but has a different definition for the ontology which AS uses. You have to keep projects which use different ontologies from incorrectly joining the same cluster.

Resolution:
=========
There are several ways around this:  

1). Change to Well Known Address for discovery and listen URL.

2). Change the multicast settings for the discovery URL which is used. This certainly should be done if using the defaults.

3). You copy the existing CDD and give the CDD a different name. That will cause the be-engine to use a different name for the cluster preventing conflict.

See also SOL1-E31ML6

TIBCO BusinessEvents (BE) BE engine reports space_def_mismatch - SpaceDef mismatch when connected to the cache and will not start.