RE: What should sys admins know about Oracle?

Yes, one of my friend does take a fbackup of complete system without shutting down oracle. This is not at our place.

But even after pointing out that "you don't have a backup if you do like this" he continues to do. Unfortunately that shop doesn't even have a oracle dba and he is squeezed out 12 hrs daily.

Bhat

-----Original Message-----

From: Winnie_Liu_at_infonet.com [mailto:Winnie_Liu_at_infonet.com] Sent: Wednesday, June 14, 2000 7:30 AM
To: Multiple recipients of list ORACLE-L Subject: RE: What should sys admins know about Oracle?

The least that they should know is how to shutdown Oracle cleanly. I have system admin working with me before who will never shutdown oracle before the shutdown.

Also, they need a bit more knowledge on backup also. They somethings think that by copying the datafile, they have "backup the database!".

Winnie

"Shreter, Hilary" <ShreterH_at_orau.gov> on 06/13/2000 02:13:42 PM

Please respond to ORACLE-L_at_fatcity.com

To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> cc: (bcc: Winnie Liu/HQ/ISC)

Before I get nailed on attitude: my sysadmin is a good dude, and most of this list is stuff we've come across over time. But it's time to start mutual understanding of the World of Backup: maybe we can use some new tools, new techniques in here if we start talking. We both have the same ends in mind, so it's time to pool our knowledge.

-----Original Message-----

Sent: Tuesday, June 13, 2000 3:07 PM
To: 'ORACLE-L_at_fatcity.com'

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-----

Sent: Tuesday, June 13, 2000 12:56 PM
To: Multiple recipients of list ORACLE-L

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 Received on Wed Jun 14 2000 - 02:58:27 CDT