Oracle INITORCL and Oracle Startup Process missing

Symptom
 
C: \ Users \ CHEN> sqlplus "/as sysdba"
 
SQL * Plus: Release 11.2.0.1.0 Production on Wed Oct 10 13:31:28 2012
 
Copyright (c) 1982,201 0, Oracle. All rights reserved.
 
Connected:
 
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-Production
 
With the Partitioning, OLAP, Data Mining and Real Application Testing options
 
SQL> shutdown immediate
 
Database closed.
 
Database dismounted.
 
ORACLE instance shut down.
 
SQL> startup nomount
 
ORA-01078: failure in processing system parameters
 
LRM-00109: cocould not open parameter file 'e: \ APP \ CSWGGOD \ PRODUCT \ 11.2.0 \ DBHOME_1
 
\ DATABASE \ INITORCL. ORA'
 
Cause: Missing INITORCL. ORA
 
Solution:
 
1. Copy the INITORCL. ORA File
 
C: \ Users \ CHEN> E:
 
-------- Copy the INITORCL. ORA backup file
 
E: \ app \ cswggod \ product \ 11.2.0 \ dbhome_1 \ database> copy E: \ app \ cswggod \ admin \ orcl \ p
 
File \ init. ora.7182012101127 INITORCL. ORA
 
1 file has been copied.
 
E: \ app \ cswggod \ product \ 11.2.0 \ dbhome_1 \ database> dir
 
The volume in drive E is Workware.
 
The serial number of the volume is 027B-A992.
 
E: \ app \ cswggod \ product \ 11.2.0 \ dbhome_1 \ database directory
 
2012/10/10 13:34 <DIR>.
 
<DIR> ..
 
2012/08/18 10:02 <DIR> archive
 
2,048 hc_orcl.dat
 
1,973 INITORCL. ORA
 
2. Start the database
 
C: \ Users \ CHEN> sqlplus "/as sysdba"
 
SQL * Plus: Release 11.2.0.1.0 Production on Wed Oct 10 13:31:28 2012
 
Copyright (c) 1982,201 0, Oracle. All rights reserved.
 
Connected:
 
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-Production
 
With the Partitioning, OLAP, Data Mining and Real Application Testing options
 
SQL> startup nomount
 
ORACLE instance started.
 
Total System Global Area 1071333376 bytes Fixed Size 1375792 bytes Variable Size 528482768 bytes Database Buffers 536870912 bytes Redo Buffers 4603904 bytes SQL> shutdown immediate
 
ORA-01507: database not mounted
 
ORACLE instance shut down. SQL>
 
SQL> startup
 
ORACLE instance started.
 
Total System Global Area 1071333376 bytes Fixed Size 1375792 bytes Variable Size 528482768 bytes Database Buffers 536870912 bytes Redo Buffers 4603904 bytes Database mounted.
 
Database opened.
 
 
 
3. Appendix-database Startup Process
 
1) NOMOUNT
 
This step is only related to the parameter file. If there is a problem in this step, it may be a problem with the system configuration (such as the number of kernel parameters, check whether sufficient system resources are allocated.
 
2) MOUNT
 
This step requires obtaining the control file location from the parameter file, reading the content, and verifying the existence of the data file. In addition, the password file is verified. Oracle searches for the orapw <ORACLE_SID> file by default. If the file cannot be found, it searches for the orapw file. If neither of them exists, an error occurs in the database. However, data can still be opened. Starting from Oracle10g, when the password file is lost, Oracle will not prompt any errors, but some functions related to the password file will not be available.
 
------------------------------------------ <ORACLE_SID> file and function ---------------------------------------
 
This file is created when the database is started and used by the operating system to lock the database. The database is locked when it is started, and the database is released when it is closed. When an exception occurs in the system, the database may have been shut down but the lock has not been released, or the database may fail to be started due to reasons such as the previous process being stopped. The solution is to restart the server or manually release the shared memory segment.
 
3) OPEN
 
In this step, check points and integrity. If all the checks pass, open the database. Otherwise, an error is reported and the database is stopped.
 
------------------------------------------------------- Database startup verification --------------------------------------
 
○ 1. Check whether the Checkpoint CNT in the data file header matches the Checkpoint CNT in the corresponding control file for the first time.
 
. This step checks whether the data file is from the same version, instead of being recovered from the backup.
 
(In hot backup mode, the data file checkpoint is frozen, but the checkpoint count is not frozen and will be modified all the time.) In Oracle10g, use an 8-level dump to obtain control file information.
 
SQL> alter session set events 'immediate trace name controlf level 8 ';
 
Use Level 10 dump in Oracle9i.
 
Bytes ----------------------------------------------------------------------------------------------------------------------------
 
○ 2. For the second time, check whether the starting SCN of the data file header is consistent with the ending SCN of the file recorded in the control file. If they are consistent, you do not need to restore the file.
 
Partial Control File dump content:
 
222 DATA FILE RECORDS
 
223 *************************************** ************************************
 
224 (size = 428, compat size = 428, section max = 100, section in-use = 5,
 
225 last-recid = 8, old-recno = 0, last-recno = 0)
 
226 (extent = 1, blkno = 11, numrecs = 100)
 
227 data file #1:
 
228 (name #7)/u01/app/oracle/oradata/orcl/system01.dbf
 
229 creation size = 0 block size = 8192 status = 0xe head = 7 tail = 7 dup = 1
 
230 tablespace 0, index = 1 krfil = 1 prev_file = 0
 
231 unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00
 
232 Checkpoint cnt: 52 scn: 0x0000. 0007ba16 02/18/2011 16:30:22
 
233 Stop scn: 0xffff. ffffffff 02/16/2011 11:07:26
 
234 Creation Checkpointed at scn: 0x0000.00000009 06/30/2005 19:10:11
 
235 thread: 0 rba :( 0x0. 0.0)
 
236 enabled threads: 00000000 00000000 00000000 00000000 00000000
 
Bytes ----------------------------------------------------------------------------------------------------------------------------
 
When a problem occurs in the database, the prompt may be incomplete information, while the alarm log records the complete error process and error number.
 
Note:
 
The SCN recorded in the control file indicates the checkpoint SCN that was last successfully completed; the SCN index recorded in the data file header indicates the checkpoint SCN that was last successfully completed in the data file;
 
In addition, both the control file and the data file header record a checkpoint count (chkpt cnt), and the data file header also records a control file checkpoint count (ctl cnt ). But this ctl cnt is 1 smaller than the ctl cnt in the control file. This is because when you check
 
When you click to update the chkpt cnt information on the control file and data file, you can
 
Obtain the current ctl cnt
 
This information is recorded in the data file. The reason for this is that the chkpt cnt on the update control file cannot be successful. Recording the previous ctl cnt ensures that the previous chkpt cnt is successfully completed.