HA, the SA's here commonly stop by my desk to see if I have
anything for them to do. They feel that they are my minion.
Have them well trained. Just took one of them into the DBA
team actually.
Really though, it makes your job so much easier to have a
good relationship with your SA's cause
I ply my SAs with chocolate and candy. Works like a charm :)
From: Kimberly Smith [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: OT - File System to Disk Mapping
Date: Sun, 26 Aug 2001 09:50:19 -0800
HA, the SA's here
On Thursday 23 August 2001 02:00, Jonathan Lewis wrote:
A logical volume is not necessarily associated with
a single disc
I made a painful discovery in that regard one time.
Well into a perl script to display drive/tablespace
mappings, I discovered that the volume for my TEMP
tablespace had
A logical volume is not necessarily associated with
a single disc as in most cases people tend to
mirror/stripe a volume group across many disks
before creating logical volumes in the volume
group.
However, if you execute
vgdisplay -v /dev/vg00
then the tail end of the report will show you
Hello,
Oops..its alright..I was 'able to retrieve' it!!!
However, if you want to 'add any details' to it..please feel
free..
Thanks
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Cyril Thankappan
INET: [EMAIL PROTECTED]
Fat City Network Services--
, 2001 4:01 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: OT - File System to Disk Mapping
A logical volume is not necessarily associated with
a single disc as in most cases people tend to
mirror/stripe a volume group across many disks
before creating logical volumes
Thanks to all, I got the required info.
rgds,
raja
--
On Thu, 23 Aug 2001 01:00:31
Jonathan Lewis wrote:
A logical volume is not necessarily associated with
a single disc as in most cases people tend to
mirror/stripe a volume group across many disks
before creating logical volumes in the
Hello all,
If I want to know from the unix system point of view, which disk is being bombarded by
a particular data file, how do I come to know. I have used the mount command but that
gives me the logical volume, but does not give the disk name that it is hitting.
This is on hp11. I can come
