Home > Articles > Data > Oracle

Like this article? We recommend

Like this article? We recommend

Understanding the Server Parameter File (SPFILE)

Prior to Oracle9i, the initialization parameters for an Oracle instance were read during instance startup by looking at the init<sid>.ora file. This file is actually a client-side file because it should be available to any client tool (such as Oracle Enterprise Manager) that allows the facility to start and shut down a database instance. The problem with the init<sid>.ora file is that, for any change made to this file to become effective, the database instance has to be restarted (because the file is read-only during instance startup). As discussed in Part 1 of this series, in Oracle9i you can dynamically change the size of the SGA. In addition, Oracle9i allows you to record parameter settings for your database instance in a server initialization parameter file (referred to as the SPFILE). The server parameter file can be created during the installation process; it has the name SPFILE.ORA by default. Use of SPFILE is particularly valuable for Oracle9i Real Application Clusters, as it allows Oracle to perform self-tuning of the database by automatically modifying parameter settings in SPFILE.ORA.

Even though the traditional client-side parameter file can be used with Oracle9i, Oracle Corporation recommends that you use the server parameter file; otherwise, parameter changes made by Oracle as a result of auto-tuning are lost after instance shutdown.

In Oracle9i, if PFILE is not specified in your STARTUP command, by default Oracle uses the server parameter file. The initialization file is searched in the following order:

  1. $ORACLE_HOME/dbs/spfile$ORACLE_SID.ora
  2. $ORACLE_HOME/dbs/spfile.ora
  3. $ORACLE_HOME/dbs/init$ORACLE_SID.ora

NOTE

For UNIX, the platform-specific default location of SPFILE is $ORACLE_HOME/dbs. For Windows NT/2000, the location is $ORACLE_HOME\database.

It's possible to use an SPFILE in a non-default location and use it to start the database. This can be achieved by using the SPFILE parameter in the PFILE. For example, place the following line in the PFILE:

SPFILE=/database/mydir/spfilem901.ora

The simplest way to determine whether an SPFILE or a PFILE was used to start the database is to execute the following command from SQL*PLUS:

SQL>show parameter pfile
NAME       TYPE           VALUE
--------   ------------   ---------------------------------------
spfile     string         /database/mydir/spfilem901.ora

The above output indicates the parameter file that was used to start this database instance.

The SPFILE is a binary file and should not be edited in the same manner that you would have used to edit a client-side initialization file (init<sid>.ora). Instead, the ALTER SYSTEM command should be used to modify the SPFILE. It's possible to use the same SPFILE for all the database instances on the same machine; you may even want to use a separate SPFILE for each instance on a machine. Using separate SPFILEs for each instance allows you to configure and tune each instance independently, whereas using the same SPFILE for all the instances simplifies maintenance. Both global as well as instance-specific parameters can be recorded in the SPFILE.

The following two clauses of the ALTER SYSTEM command are useful when working with SPFILE parameters:

  • SCOPE

  • This clause is used to specify the scope of parameter changes. Three possible values can be used with the SCOPE clause:

    • MEMORY

      This setting indicates that the change is made in memory and takes effect immediately. The change persists until the database is shut down. If the database instance was started using a PFILE (that is, the init<sid>.ora client-side file), then this is the only option available with the scope. If a PFILE was used to start the database, this is the default setting.

    • SPFILE

      This setting indicates that the change is made in the server parameter file. When changing the value of a static parameter, you must use this setting. The change takes effect when the database instance is restarted.

    • BOTH

      This setting indicates that the change is made in memory as well as in the server parameter file. The change takes effect immediately and persists after the database is restarted. If an SPFILE was used to start the database, this is the default setting.

  • SID

    This clause is relevant only in an Oracle9i Real Application Clusters environment. Oracle9i Real Application Clusters has three types of parameters:

    • Those that can have any valid value for any instance

    • Those that must have identical settings for all instances

    • Those that must have unique settings for each instance

    It allows you to specify the SID of the instance where the value will take effect. If you want the change to affect all the instances of the database, specify SID='*' (on the other hand, if you want the change to affect a particular instance only, specify SID='instance_name'). If an instance other than the current instance is specified, Oracle sends a message to that instance to change the parameter value in its memory. Not specifying the SID clause results in Oracle assuming the SID of the current instance (if the instance was started with a PFILE) or SID='*' (if the instance was started up with an SPFILE).

The ALTER SYSTEM...RESET clause works complementary to the ALTER SYSTEM...SET clause in that it can be used to restore parameters to their default values.

Let's consider some examples to understand the SCOPE and SID clauses of the ALTER SYSTEM command.

SQL>alter system set job_queue_processes=10 scope=memory sid='*'

The above command sets job_queue_processes to 10 in memory and for all the instances on that machine.

SQL>alter system set job_queue_processes=20 scope=memory sid='M901'

The above command sets job_queue_processes to 20 in memory but only for the instance 'M901'. This overrides any prior setting of job_queue_processes for the M901 instance.

SQL>alter system reset job_queue_processes scope=memory sid='M901'

The above command restores the job_queue_processes parameter for the instance M901 to its default value. The job_queue_processes setting for all other instances of this database remain unchanged.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020