Storage Administration - Oracle Exadata Recipes: A Problem-Solution Approach - page 267

Registry, use the following command as the Oracle database owner to display the expected location of your server
parameter file:

[oracle@cm01dbm01 ~]$ srvctl config database -d visx
Database unique name: visx
Database name: visx
Oracle home: /u01/app/oracle/product/11.2.0.3/dbhome_1
Oracle user: oracle
Spfile: +DATA_CM01/visx/spfilevisx.ora
... output omitted

Using the parameter file backed up previously in this recipe, start your database in nomount mode and create
your server parameter file in the expected location, which in our case is +DATA_CM01/visx/spfilevisx.ora :

SQL> startup nomount pfile='/home/oracle/initvisx.ora';
ORACLE instance started.

Total System Global Area 1.7103E+10 bytes
Fixed Size 2245480 bytes
Variable Size 2483031192 bytes
Database Buffers 1.4462E+10 bytes
Redo Buffers 155926528 bytes

SQL> create spfile='+DATA_CM01/visx/spfilevisx.ora' from pfile='/home/oracle/initvisx.ora';

File created.

SQL>

As your Oracle Grid Infrastructure owner, you can validate that Oracle successfully placed a server parameter file
in the expected location using the following command:

[grid@cm01dbm01 ~]$ asmcmd ls DATA_CM01/VISX
PARAMETERFILE/
spfilevisx.ora
[grid@cm01dbm01 ~]$

Once your server parameter file has been created, start one of your instances in nomount mode using the spfile
and restore your control file using RMAN.

■ the following example assumes that you have control file backups available. in our example, our control file is
backed up to an external nFS-mounted naS device.

Note

[oracle@cm01dbm01 ~]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Sep 13 17:16:26 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: VISX (not mounted)
RMAN> shutdown immediate;
using target database control file instead of recovery catalog