Loaction of pfile(INIT<SID>.

ORA) and spfile: /oracle/SID/102_64/dbs($ORACLE_HOME/dbs) Here is an alternative procedure for changing SPFILE parameter values using the above method: o Export the SPFILE with: CREATE PFILE= pfilename FROM SPFILE = spfilename ; o Edit the resulting PFILE with a text editor o Shutdown and startup the database with the PFILE option: STARTUP PFILE=filename o Recreate the SPFILE with: CREATE SPFILE= spfilename FROM PFILE= pfilename ; o On the next startup, use STARTUP without the PFILE parameter and the new SPFILE will be used. How will I know if my database is using a PFILE or SPFILE? Execute the following query to see if your database was started with a PFILE or SPFILE: SQL> SELECT DECODE(value, NULL, PFILE , SPFILE ) Init File Type FROM sys.v_$parameter WHERE name = spfile ; You can also use the V$SPPARAMETER view to check if you are using a PFILE or not: if the value column is NULL for all parameters, you are using a PFILE. What is the difference between a PFILE and SPFILE? A PFILE is a static, client-side text file that must be updated with a standard text editor like notepad or vi . This file normally reside on the server, however, you need a local copy if you want to start Oracle from a remote machine. DBA s commonly refer to this file as the INIT.ORA file. An SPFILE (Server Parameter File), on the other hand, is a persistent server-side binary file that can only be modified with the ALTER SYSTEM SET command. This means you no longer need a local copy of the pfile to start the database from a remote machine. Editing an SPFILE will corrupt it, and you will not be able to start your database anymore. SPFILEs provide the following advantages over PFILEs: o An SPFILE can be backed-up with RMAN (RMAN cannot backup PFILEs) o Reduce human errors. The SPFILE is maintained by the server. Parameters are checked before changes are accepted. o Eliminate configuration problems (no need to have a local PFILE if you want to start Oracle from a remote machine) o Easy to find stored in a central location

EHP4 Installation Syntax to change the DBA SYSTEM Password:

SQL> connect /as sysdba; Connected. SQL> alter user system identified by manager; User altered.

Password changed to manager