If a hot backup was done with the archive logs active, then the backup should be consistent, whether the app is up or down. Oracle is very good with hot backups...looks like your DBA needs to get a better understanding of this kind of backups
Guillaume -----Original Message----- From: Action Request System discussion list(ARSList) on behalf of William Rentfrow Sent: Mon 06/22/09 1:07 PM To: [email protected] Subject: Re: Root cause of Nextid out of wack after DB restore I had shut down the app before the backup so I don't think that was the problem - and this was a DEV system with only a couple of people on it. However, I'd prefer to trust the logs over my memory. I'll go and see what the data proves. William Rentfrow Principal Consultant, StrataCom Inc. [email protected] O 715-592-5185 C 715-410-8056 ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Dennis Ruble Sent: Monday, June 22, 2009 11:59 AM To: [email protected] Subject: Re: Root cause of Nextid out of wack after DB restore ** Was the backup an offline backup? We've had the same thing happen when doing backups with users online. The database does the backup alphabetically making arschema one of the first tables backed up. Users can still create tickets which gets their C1 higher than nextid was in arschema when it was backed up. We've gone to offline backups or have shut down AR System when we need a clean restore. The other thing that would probably work would be to make an additional backup of arschema AFTER the full db backup and use that in your restore. HTH Regards, Dennis Ruble William Rentfrow <[email protected]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 06/22/2009 11:41 AM Please respond to [email protected] To [email protected] cc Subject Root cause of Nextid out of wack after DB restore ** We were doing some destructive data cleansing - we knew we'd wreck stuff so before hand we had the DBA take a DB backup (oracle 9i, ARS 6.3 patch 20 running CSS - not that it matters). After we were done we had a restore of the full database done. Immediately we started getting index errors, etc, so I check the nextid versus the max(c1) for a few tables and found they were out of wack (ie, max(c1) > nextid for a particular table). I know how to fix this of course - it's pretty straightforward SQL and I've had it happen a few times over the years - yet I've never been able to pinpoint a root cause. Has anyone else found out why? The DBA says she dropped all users and objects and then restored so I'd have to assume the synch error occurs before the database is backed up. William Rentfrow Principal Consultant, StrataCom Inc. [email protected] Personal blog: www.williamrentfrow.com <file://www.williamrentfrow.com/> O 715-592-5185 C 715-410-8056 _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
