Hi JD, I think it's got to be something mis-configured, it's obviously not random as it's only affecting the system-data as you've described.. I think for more help you need to explain the config. How's the tns setup? Is it a server group? Is there a loadbalancer for the db? How many app servers vs db nodes. If there was a RAC problem then surely all data would be affected. Surely Updates to the data described only happen when you make admin changes? I had some crazy thoughts about things like a dev or test environment somehow hitting the production db via a mis configured load balanced VIP for the DB (we never used a load balanced db connection for RAC, the TNS failover gave us much more control) that is pointing to a prod node. That could cause the problems described. Could different servers in a server group be enabled for admin somehow (not sure if you'd get the same problem though)?
I'd definitely add TNS affinity for the admin server to node 1, and if it's a server group I'd have all other servers set to NULL in the rankings for admin. It's like the cache is getting messed up - which is understandable if you've got db problems - but why that gets written back to the db is a mystery. We don't use any out of the box stuff - so it could ITSM type stuff that is doing commits to the db. You might list all the things you've checked so far? Regards, JP. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
