Académique Documents
Professionnel Documents
Culture Documents
Administration Tips
Administration Tips
general rule of thumb that says 'I will switch logs around once every hour' (or perhaps once every half hour or so). That's not bad as a rule of thumb, but that's all it is. You need to find out whether applying such a rule degrades performance unacceptably in your specific environment. Incidentally: how do you find out how often your log switches are occurring? Well, there are several ways, but perhaps the easiest is to locate your Alert Log. That will be sitting in wherever the "background_dump_dest" init.ora parameter is pointing (you could do a SHOW PARAMETER BACKGROUND to display that). Every log switch is recorded there, along with the precise time (down to the second) when it happened. The relevant lines usually read something like "Thread 1 advanced to Log Sequence 391". What you are looking for is an average rate of switching over the course of a typical working day (you will, of course, tend to switch rather more often during busy periods, and rather slower during lunchtimes and at the end of the day). If you find your average switching rate is too high, you can't correct the problem by resizing existing logs. You have, instead, to add new logs of a bigger size, and remove the small logs as a separate exercise. ALTER DATABASE ADD LOGFILE '/PATH/FILENAME' SIZE 500M is the command to add new, single member, groups. ALTER DATABASE DROP LOGFILE GROUP 1 gets rid of all members of an existing group (obviously replace the group number there with something appropriate).
10/17/2001
Page 2 of 2