![]() Typically, all users with the CREATE SESSION system privilege can connect to an open database. Perform certain migration or upgrade operations Temporarily prevent typical users from using data Use this mode of instance startup when you need to accomplish one of the following tasks: You can start an instance, and optionally mount and open a database, in restricted mode so that the instance is available only to administrative personnel (not general database users). Restricting Access to an Instance at Startup If you use the Database Configuration Assistant (DBCA) to configure a database to use ASM, DBCA creates an SPFILE for the database instance in an ASM disk group, and then creates a text initialization parameter file in the default location in the local file system to point to the SPFILE. Initialization Files an d Automatic Storage ManagementĪ database that uses Automatic Storage Management (ASM) usually has a non-default SPFILE. When the client machine reads the initialization parameter file containing the SPFILE parameter, it passes the value to the server where the specified SPFILE is read. It also eliminates the need for a client machine to maintain a client-side initialization parameter file. Therefore, the preceding method also provides a means for a client machine to start a database that uses an SPFILE. The SPFILE must reside on the machine running the database server. STARTUP PFILE = /u01/oracle/dbs/spf_init.ora Start up the instance pointing to this initialization parameter file. In this context, you must use the SPFILE initialization parameter. ![]() You cannot use the IFILE initialization parameter within a text initialization parameter file to point to a server parameter file. The value of the parameter is the non-default server parameter file location.įor example, create a text initialization parameter file /u01/oracle/dbs/spf_init.ora that contains only the following parameter: However, should such a need arise, you can use the PFILE clause to start an instance with a non-default server parameter file as follows:Ĭreate a one-line text initialization parameter file that contains only the SPFILE parameter. ![]() It is not usually necessary to start an instance with a non-default SPFILE. Starting Up with a Non-Default Server Parameter FileĪ non-default server parameter file ( SPFILE) is an SPFILE that is in a location other than the default location. If you (or the Database Configuration Assistant) created a server parameter file, but you want to override it with a text initialization parameter file, you can specify the PFILE clause of the STARTUP command to identify the initialization parameter file. There is no instance-specific location for storing a server parameter file.įor more information about the server parameter file for a Real Application Clusters environment, see Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide. The spfile.ora file is included in this search path because in a Real Application Clusters environment one server parameter file is used to store the initialization parameter settings for all instances.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |