Database Reference
In-Depth Information
5.
The initialization file for the database does not exist yet. You need to create it from the old
server parameter file and adjust it for the new Oracle Home manually. First, create the new
initialization parameter file as follows:
[oracle@s1 PROD_s1]$
sqlplus / as sysdba
...
Connected to an idle instance.
SQL>
create pfile from spfile='$OLD_OH/dbs/spfilePROD.ora';
File created.
Adjust the initialization parameter file
$NEW_OH/dbs/initPROD.ora
to replace all
references to the temporary file system you've been using for the old Oracle Home with
appropriate paths in the new configuration. The following are the parameters you
need to adjust:
6.
*.diagnostic_dest='$NEW_OH/admin/PROD_s1'
*.log_archive_dest_1='LOCATION=+RECO'
*.utl_file_dir='/usr/tmp','$NEW_OH/appsutil/outbound/PROD_s1'
7.
You also need to set the verified initialization parameters for ODA. These settings are set
by default when a new database is created using the ODA's
oakcli
utility. The parameters
have been specifically tuned for ODA, and the e-Business Suite database has to use them
too. Here are the parameters and their values:
*._disable_interface_checking=true
*._gc_undo_affinity=false
*._gc_policy_time=0
*._enable_numa_support=false
*._file_size_increase_increment=2143289344
*.compatible='11.2.0.3.0'
*.db_recovery_file_dest='+RECO'
*.db_create_file_dest='+DATA'
*.db_create_online_log_dest_1='+REDO'
*.db_block_checksum=full
*.db_block_checking=full
*.db_lost_write_protect=typical
*.filesystemio_options=setall
*.use_large_pages=only
8.
The last step that finalizes the implementation of
AutoConfig
managed configuration in
the new Oracle Home is starting the database and running
AutoConfig
. Also, because the
initialization parameter file has been prepared, it can be converted into a server parameter
file, as in the following example:
[oracle@s1 PROD_s1]$
sqlplus / as sysdba
...
Connected to an idle instance.
SQL>
create spfile from pfile;
File created.
SQL>
startup
...
