RE: pctincrease --SYS objects

From: MacGregor, Ian A. <ian_at_SLAC.Stanford.EDU>
Date: Mon, 03 Jul 2000 15:24:04 -0700
Message-Id: <10547.111142@fatcity.com>

I'm fully aware fo what the documentation states. Oracle is fence-sitting on the issue. What's in a README file overrides anything in the documentation; it is the purpose of readme files to convey the most up-to-date information to the user.

This dichotomy has existed since long before the 8.1.6 release; one wonders why they don't amend the readme file to correspond with the documentation? They have had plenty of chances to do so.

IMHO, Oracle would not yank support form someone who has modified the sql.bsq file under the confines stated in Oracle's own documentation. But one should be aware that as things stand they can do exactly that, and say ,"You should have checked the README.txt file before making your changes to sql.bsq."

Ian MaGregor
Stanford Linear Accelerator Center
ian_at_slac.stanford.edu

-----Original Message-----
From: Charlie Mengler [mailto:charliem_at_mwh.com] Sent: Monday, July 03, 2000 2:15 PM
To: Multiple recipients of list ORACLE-L Subject: Re: pctincrease --SYS objects

Below is from the V8.1.6 DOC CD -

---

---

The SQL.BSQ file runs when you issue the CREATE DATABASE statement. This file contains the table definitions that make up the Oracle server. The views you use as a DBA are based on these tables. Oracle recommends that you strictly limit modifications to SQL.BSQ.      If necessary, you can increase the value of the following storage parameters: INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE, FREELISTS, FREELIST GROUPS, and OPTIMAL.

              See Also:

              For complete information about these parameters, see Oracle8i SQL Reference.

     With the exception of PCTINCREASE, do not decrease the setting of a storage parameter to a value below the default. (If the value of MAXEXTENTS is large, then you can lower the value for PCTINCREASE or even set it to zero.)

     No other changes to SQL.BSQ are supported. In particular, you should not add, drop, or rename a column.

---

---

HTH & YMMV! "MacGregor, Ian A." wrote:
>
> 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.
>

-- 
Author: Charlie Mengler
  INET: charliem_at_mwh.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_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

Received on Mon Jul 03 2000 - 17:24:04 CDT