Private Procedure for Changing Memory Parameters


I have a procedure for changing memory parameters for an Oracle RDBMS database instance.

The reason for this complex procedure is that I have a standard approach to updating parameters that is resilient and repeatable. Although the judicious use of the ALTER SYSTEM SET command can achieve the same results, I still have painful memories of being caught out by bugs and misunderstandings.

The outline of the procedure is:

  1. CREATE PFILE=’/tmp/initorcl_old.ora’ FROM SPFILE;
  2. cp /tmp/initorcl_old.ora /tmp/initorcl_new.ora
  3. vi /tmp/initorcl_new.ora
  4. startup nomount pfile=/tmp/initorcl_new.ora
  5. CREATE SPFILE=’?/dbs/spfileorcl.ora’ FROM PFILE=’/tmp/initorcl_new.ora’;
  6. startup

I create a text version of the system parameter file; edit the copy with the new memory parameters; start up the instance in NOMOUNT in order to verify the parameters; and overwrite the system parameter file with the text file.

NOTE: There are missing steps in the above procedure, and the names have to be changed to match the operating system, and environment.

SEE: Starting Up a Database for more details.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s