Hi JD, I'd say RAC with one node running is very close to a stand alone db...
Post restore I presume if you don't make any admin changes - the problem doesn't happen? If that's the case then it's got to be worth putting SQL logging whilst you make changes, and until the problem occurs. Either Remedy isn't issuing the full SQL statements, or the db is silently not applying them (both sound a little crazy). If Remedy is issuing the correct SQL, then I'm thinking that dev and test are getting mixed up, i.e. admin changes made on dev, some of the SQL goes to dev RAC, some goes to test RAC, Remedy wouldn't complain - niether would the respective dbs (initially) - The whole things sounds crazy, but it would only take a load balanced VIP to get messed up or a tns.ora update to go bad. There's many ways to check this at db level - but with no db support at all, I'd add a script to cron (assuming unix) to output netstat|grep 1521 to a file every few minutes and look for any IPs that aren't as per the tns entry for your SID. Since the problem is crazy - I'm hedging that the explanation is crazy :-) JP _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
