No, as long as you are in noarchivelog mode, you should be OK on that front.
Printable View
No, as long as you are in noarchivelog mode, you should be OK on that front.
Yeah everything seems to be running great. Have a peaceful weekend Jeff. Thanks again for everyones comments.
Of course, you understand the implications of not running in archivelog mode, right?
Implications of not running in archivelog mode? I'm not sure I understand, I am under the impression this is the preferable scenario. Could you explain?
no archived log no PITR
How offen that you do a backup. If your database were to go down, or fail for some reason, then you would only be able to recover the data to the last backup. But with the archive logs, you can recover the database to the point of failure.
Sam
For the vast majority of our clients we set up AT scripts to run a bat file that does an export/warm backup of the database at certain off-peak times during the day. This occurs 3 times a day for most clients.
Here is an example of AT scripts that run once a day.
AT 6:00 /EVERY:M CMD /C C:\DATDUMP MONDAY
AT 6:00 /EVERY:T CMD /C C:\DATDUMP TUESDAY
AT 6:00 /EVERY:W CMD /C C:\DATDUMP WEDNESDAY
AT 6:00 /EVERY:Th CMD /C C:\DATDUMP THURSDAY
AT 6:00 /EVERY:F CMD /C C:\DATDUMP FRIDAY
AT 6:00 /EVERY:Sa CMD /C C:\DATDUMP SATURDAY
AT 6:00 /EVERY:Su CMD /C C:\DATDUMP SUNDAY
The DATDUMP file looks like this:
EXP DATABASEUSERNAME/PASSWORD FILE=C:\DATADMPS\%1
So you can afford at least 8-hours worth of data loss? Good for you.
BTW, exp/imp is *no kind of database backup* method, I hope you are aware of that. And I hope you are aware that you are actually exporting the data is inconsistent (regarding one table content to another), because you are not using CONSISTENT=Y during your exp. And if your exp batch file realy consists only that line that you have written I realy do hope you are aware that you are exporting only one users' objects all the time.....
If your database encounters media failure you'll certanly have a lot of work to do....