Less04_实例.pptVIP

Initialization Parameter Files When you start the instance, an initialization parameter file is read. There are two types of parameter files: Server parameter file: This is the preferred type of initialization parameter file. It is a binary file that can be written to and read by the database server and must not be edited manually. It resides in the server that Oracle is executing on, and is persistent across shutdown and startup. This is often referred to as an SPFILE. Text initialization parameter file: This type of initialization parameter file can be read by the database server, but it is not written to by the server. The initialization parameter settings must be set and changed manually by using a text editor so that they are persistent across shutdown and startup. It is recommended that you create a server parameter file (SPFILE) as a dynamic means of maintaining initialization parameters. By using a server parameter file, you can store and manage your initialization parameters persistently in a server-side disk file. MS Tip: The equivalent file for SQL Server is sysconfig. Viewing and Modifying Initialization Parameters The Oracle database provides several initialization parameters to optimize its operation in diverse environments. Initialization parameters are divided into two groups: basic and advanced. In the majority of cases, it is necessary to set and tune only the basic parameters to get reasonable performance. There are 28 basic parameters. Only a few of these parameters must be explicitly set because the default values are adequate in the majority of cases. In rare situations, modification to the advanced parameters may be needed for optimal performance. The advanced parameters are preserved to allow expert DBAs to adapt the behavior of the Oracle database to meet unique requirements. Managing Memory Components The SGA comprises several components. The size of many of these components can be managed by the Oracle server through the use of the Automa