iengca, I’m aware that this message is old, but I figured that it might be worth placing extra info related to the issue for future users. Note these instructions are for 7.1.x users only.
In the MWS tablespaces tables and indexes starting with CCS are related to the central configurator. These tables are create by the MWS the first time it starts up.
If you are getting invalid objects because the central configurator’s tables or indexes are missing then we need to create those tables & indexes.
- Stop all MWS instances that use this data pool
- Back up the MWS file system and table spaces
- Drop all tables like CCS_%
- Drop all indexes like CCS%
- Restart one of the MWS
- After the MWS is completely started then start the others.
The MWS will automatically recreate the Central Configurators tables and indexes on startup. Note, you may need to setup your O4P and O4I in the central configurator, but shouldn’t have to push the configurations.
I had an issue similar to this and these are the instruction that support gave me. Also there is an article in the advantage knowledge base, which I’m currently locked out of :(.