Message-Id: <10547.111118@fatcity.com> From: "MacGregor, Ian A." Date: Mon, 03 Jul 2000 09:06:33 -0700 Subject: RE: pctincrease --SYS objects Be warned! The README.txt file for Oracle 8.1.6 states: ---------------------------------------------------------------------------- ------- 1.5 SQL.BSQ ----------- Do not modify SQL.BSQ before installation. Some customers, especially those with a large number of objects in their installation, have noticed performance improvements when they modify SQL.BSQ before installation (for example, by increasing initial extents). However, making such modifications may jeopardize customer supportability. ---------------------------------------------------------------------------- --------- Personally, I don't see anything wrong with amending the sql.bsq within the restrictions stated in the included message. However, readme files are supposed to be the "last" word on a topic; that is, what's in the readme file takes precedence over what's stated in the documentation. Ian MacGregor Stanford Linear Accelerator Center ian@slac.stanford.edu -----Original Message----- From: Steve Orr [mailto:sorr@arzoo.com] Sent: Friday, June 30, 2000 4:57 PM To: Multiple recipients of list ORACLE-L Subject: RE: pctincrease --SYS objects I'll take the liberty of quoting directly from Steve Adams' website to which I referred. Steve A. addresses this nicely as follows... "Most DBAs are reluctant to customize the sql.bsq file prior to database creation, in the belief that doing so is unsupported. However, since release 7.3, limited customization of the sql.bsq file has been supported. You may still see comments to the contrary, even from within Oracle. However, the Tuning guide of the official Oracle documentation set allows that modifications may be made to the sql.bsq file to optimize the physical storage of the data dictionary. You may not, however, modify the logical structure of the data dictionary." "We strongly recommend that you take the opportunity to customize the sql.bsq file prior to the creation of any performance critical database. A failure to do so will introduce problems that can only be repaired by recreating the database. But before you can make your changes to sql.bsq, you need to consider to the following question." ...and that question which follows is on the same web page at: http://www.ixora.com.au/tips/creation/bsq.htm If one is not comfortable with this "radical" idea after a little study then do nothing. The point is... do a little studying up on the matter before making your decision. You could even practice and experiement on a scratch database until you are comfortable with the results. Or you could just do nothing. As with ALL things Oracle... use with caution. Steve Orr -----Original Message----- Sent: Friday, June 30, 2000 2:06 PM To: Multiple recipients of list ORACLE-L Steve, Come over here and let me speak with you in private.... Do you really want to advise people to start editing the sql.bsq file if they don't know whether or not they can change data dictionary defaults? Don't you think that if they are asking the question then the answer for them (at that level of experience) is a hale and hearty NO? What's next, indexes on the data dictionary? Analyzing the sys schema? DOGS AND CATS LIVING TOGETHER? To quote from "Bridge Over the River Quai": "Madness! Madness!" Once they reach the level of experience where they know what doing things like changing the DD defaults means, then they will also know whether or not it is a good idea and why. Until they know, just say no! Just call it the zen philosophy of being an Oracle DBA. Jack Silvey ocp x 2 senior @ xol.com -----Original Message----- Sent: Friday, June 30, 2000 12:04 PM To: Multiple recipients of list ORACLE-L ricochet... Ah, but it is "broken" or will become broken if you use it much. "Broken" being defined as poor space management and performance hindering fragmentation. Do experienced DBA's accept the all the Oracle defaults for DB creation? Of course not so why accept the defaults within the data dictionary? Have courage, be a man, or goddess, and copy the sql.bsq to $ORACLE_BASE/admin//create and edit it to set the proper storage clauses. Set the following in your init.ora file (for db_creation only): _init_sql_file = /PathToOracleBase/admin//create/sql.bsq Then choose a healthy db_block_size and create your database. Then set the system tablespace defaults to something like the following: ALTER TABLESPACE SYSTEM DEFAULT STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 4096 PCTINCREASE 100) ; ALTER TABLESPACE SYSTEM MINIMUM EXTENT 64K ; Then create the rest of your tablespaces and rollback segments and install any Oracle supplied packages. OK, you may want to think about that PCTINCREASE 100 setting. But don't get crazy and make system a locally managed tablespace. Wait for Oracle on this one. Need more encouragement? See Steve Adam's "Customizing SQL.BSQ" web page: http://www.ixora.com.au/tips/creation/bsq.htm Be thou of good courage. Shrink not from thine appointed destiny. Seek and ye shall find, ask and it shall be given thee, knock and it shall be opened to thee. Take heart, the Oracle is with thee. Steve Orr -----Original Message----- Sequeira Sent: Friday, June 30, 2000 12:36 AM To: Multiple recipients of list ORACLE-L Or, 'If ain't broke, don't fix it' -- S. Anthony Sequeira Wait for the ricochet Opinions expressed herein are my own and do not necessarily represent those of my employer ----- Original Message ----- To: Multiple recipients of list ORACLE-L Sent: 29 June 2000 22:25 > At 12:09 PM 6/29/00 -0800, you wrote: > >domain? Knowest thy not the meaning oft the adage "Leave well enough alone?" > > > > Or, in the modern vernacular: "You f**k with that, you're on your own!" > --- > Dennis Taylor > --- > The opinions expressed herein are mine. Get your own opinions! > --- > -- > Author: I.S. Manager > INET: ismgr@pctc.com > -- Author: Steve Orr INET: sorr@arzoo.com 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@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L