| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Seeking opinions
It sounds to me that whoever architected this approach really didn't
understand
the idea of "metadata" and the flexibility that OFA provides in terms of
tuning
(I'm not limited to specific disks because I have "customer data") and
performance.
My 2 cents...
RF
Robert G. Freeman - Oracle8i OCP
Oracle DBA Technical Lead
CSX Midtier Database Administration
The Cigarette Smoking Man: Anyone who can appease a man's conscience can take his freedom away from him.
-----Original Message-----
Sent: Tuesday, April 02, 2002 10:03 AM
To: Multiple recipients of list ORACLE-L
Hi Paul,
How's going?
What if someone on the dba group make a mistake (typo or whatever) and put the data file in the wrong place? And other DBAs didn't notice it and work on something. I don't like the idea people assume things will be in the right place because the rule says so. I'd rather trust data dictionary than somethng that has 16 DBA's hands on it.
Do they also write they scripts assuming everything is where it should be?
Richard Ji
-----Original Message-----
Sent: Monday, April 01, 2002 5:48 PM
To: Multiple recipients of list ORACLE-L
Hi everyone.
I'm currently working at a client where the OFA standard has been (as they put it) "taken to the next level". I disagree with their approach, and I'd be interested to see what list members think.
The client believes that any DBA (there are about 16 on staff) should be able to locate data files in any database without querying the data. To this end, mount points are named both /unnn (e.g., /u001) and /annn (e.g., /a001). "System" datafiles (system, temp, rollback tablespaces) go only on the /unnn mount points, and in particular, datafiles for certain tablespaces must go on certain mount points--for instance rollback tablespace files always go on /u004.
"User" datafiles are allowed on /a001 and /a002, tables and indexes, respectively.
To my mind, this standard changes the Optimal Flexible Architecture to the Sub-optimal Inflexible Architecture, and all just to avoid a data dictionary query. What do you think?
Thanks,
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists --------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists --------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists --------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue Apr 02 2002 - 09:53:31 CST
 |
 |