Re: stop chugging hard drive

> No it isn't anything like that.

Are you 100% sure....there's lots going on here. Lots of automated collection and storing of data in 10g. It could be many things. What makes you so sure I'm wrong?

> It's an option I chose when installing the database. Something
> straightforward, like to do with archiving.....but I just can't remember.

There is an option which lets you set the database in archive log mode or not. In archive log mode, when the online redo log fills up, it gets copied to the archive log destination. Without archivelog mode, the contents of the online redo log simply get overwritten, never to be seen again. Archive logging can have performance impacts, especially if all I/O is on the same drive.

> One alternative causes the "chugging" the other doesn't.

That could be the cause, or it might not be. Turn off archiving and see if the chugging goes away. But in any case, this has nothing to do with, as you said, "I had turned off rollback segments or redo logs" because you cannot turn off all undo (rollback) segments and all online redo logs. This are quite different animals than archiving the online redo logs.

> I installed on two v. similar machines with the different results. The old
> machine, which doesn't chug, is kaput at the moment so I can't check out the
> difference.

Why is the machine "kaput"? Is it a harddrive failure? Or some other reason?

> I thought someone would just say "turn archiving off with XYZ" or similar.

Then let me say it...."turn off archiving"!!! You now have a definitive answer to help solve your problem.

I have absolutely no idea if archiving could be causing your problem as your problem could have other root causes that have nothing to do with archiving. For instance, if your machine is "kaput" due to a harddrive failure, then the root cause is probably due to bad hardware. IDE drives tend to "chug" when they are about ready to up and die. Of course, I'm assuming you are using an IDE drive, but I can do nothing but assume because you did not provide any details to help further diagnose your problem.

> As I said, when I have a bit of time I'll sort it out as no one can provide
> a straightforward
> solution.

There is not a single person who can say with 100%, 99%, or even 90% certainty that your problem is caused by XYZ. That is because you have not provided enough details to help us help you solve your problem.

You have come to this group seeking its expertise. When someone asked you for more information, it is because their expertise tells them that they need more information to help you out. Yet your reply is "I dont think any of those facts are relevant" and "No it isn't anything like that". If you feel your expertise level is higher than those whom counsel you seek, they why post the question? I don't go to the doctor and complain of a constant headache then after the doctor asks me if anything has changed at work lately, reply "I dont think any of those facts are relevant". Apparently the doctor asked me about my life at work because that information may be relevant. Or it may not be relevant. If I told the doctor that they recently repainted my office, he might suspect allergies. If I told the doctor I was under the pressure of a major deadline, he might suspect stress as the cause. If I told the doctor the only that has changed at work is that I got a 10% payraise, he'd probably decide that my professional life was not a factor of the root cause. You've effectively gone to the doctor and then refused to help him correctly diagnose your ailment.

HTH,
Brian

-- 
===================================================================

Brian Peasland
oracle_dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown