RE: What should sys admins know about Oracle?

They should know that unlike academic locations, Oracle will need shared memory and semaphores, and they should become able to provide them.

They should know that Oracle performance isn't likely to be improved by priority modification, and that the database normally takes up a lot of energy, even if there are no users.

They should never move anything that lives in a directory with the name "oradata" in it.

They should understand that I need continuous archived redo logs, and that's why I have to get involved with their scripts in order that they may be purged correctly.

They should understand that I do care which backups failed: that it affects my recovery schemes.

They should understand that there are other backups than cold backups, and that if we go there then I'll need to really know which backups finished and which didn't, and they'll have to be willing to do more than reboot and pray.

They should understand if it gets full, the disk to which archived logs get archived, can stop the process and cause lots of helpline calls and alphanumeric paging activity.

I gave a little paper on this at ECO, and then went to OAUG and saw the same main topic areas (apps=oracle+apps; resource hog; recovery logic) covered in three different papers.

I get to modify the talk and give this to my entire department, and maybe then we can have a discussion (previously it's been my biz, your biz, never do we need to talk).

-----Original Message-----
From: Jonathan Gennick [mailto:jonathan_at_gennick.com] Sent: Tuesday, June 13, 2000 12:56 PM
To: Multiple recipients of list ORACLE-L Subject: What should sys admins know about Oracle?

Chris brings up something that I was just thinking about the other day. There are some key things about Oracle that system administrators may not understand by default. What are they? What do you want your system administrators to Received on Tue Jun 13 2000 - 14:06:37 CDT