Problem description: I used the C # program to operate the image data-to synthesize multiple images into one image. Due to the large image size, it was stored through the Oracle database, however, after running the program for a period of time, the system consumes too many resources and the result program is a response, I close the program. As a result, the Oracle database collapsed.
The ORA-01033: Oracle initialization or shutdown in progress prompt is displayed when you connect to the database through the Oracle Enterprise Manager Console.
(1) I found the dependency solution on the Internet, as shown below:
The customer Oracle server enters PL/SQL developer times ora-01033: Oracle initializationg or shutdown in progress error message, the application system cannot connect to the Oracle service. Solve the problem remotely. The process is as follows:
1. Go to CMD and run set oracle_sid = fbms to ensure the correct Sid is connected;
2. Run sqlplus "/As sysdba"
SQL> shutdown immediate
SQL> startup start the service, observe that no data file loading error occurs at startup, and remember the error data file number.
SQL> shutdown immediate stop the service again
SQL> startup Mount
SQL> recover datafile 2 restore the wrong data file
SQL> shutdown immediate stop the service again
SQL> startup starts the service. This time it is normal.
3. Go to PL/SQL developer for check. No error is displayed.
The running result is as follows:
C:/Documents and Settings/Jiang Yi> set oracle_sid = supermapdb
C:/Documents and Settings/Jiang Yi> sqlplus "/As sysdba"
SQL * Plus: Release 10.2.0.1.0-production on Sunday September 26 20:06:13 2010
Copyright (c) 1982,200 5, Oracle. All rights reserved.
Connect:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-Production
With the partitioning, OLAP and Data Mining options
SQL> shutdown immediate
ORA-01109: the database is not open
The database has been detached.
The Oracle routine has been disabled.
SQL> startup
The Oracle routine has been started.
Total system global area 612368384 bytes
Fixed size 1250428 bytes
Variable Size 230689668 bytes
Database buffers 373293056 bytes
Redo buffers 7135232 bytes
The database has been loaded.
ORA-01157: unable to identify/lock data file 4-see dbwr trace file
ORA-01110: data file 4:
'E:/database/Oracle/product/10.2.0/oradata/supermapdb/. dbf'
SQL> shutdown immediate
ORA-01109: the database is not open
The database has been detached.
The Oracle routine has been disabled.
SQL> startup Mount
The Oracle routine has been started.
Total system global area 612368384 bytes
Fixed size 1250428 bytes
Variable Size 230689668 bytes
Database buffers 373293056 bytes
Redo buffers 7135232 bytes
The database has been loaded.
SQL> recover datafile 4
ORA-00283: resume session canceled due to an error
ORA-01110: data file 4:
'E:/database/Oracle/product/10.2.0/oradata/supermapdb/. dbf'
ORA-01157: unable to identify/lock data file 4-see dbwr trace file
ORA-01110: data file 4:
'E:/database/Oracle/product/10.2.0/oradata/supermapdb/. dbf'
SQL> shutdown immediate
ORA-01109: the database is not open
The database has been detached.
The Oracle routine has been disabled.
SQL> startup
The Oracle routine has been started.
Total system global area 612368384 bytes
Fixed size 1250428 bytes
Variable Size 230689668 bytes
Database buffers 373293056 bytes
Redo buffers 7135232 bytes
The database has been loaded.
ORA-01157: unable to identify/lock data file 4-see dbwr trace file
ORA-01110: data file 4:
'E:/database/Oracle/product/10.2.0/oradata/supermapdb/. dbf'
SQL>
This shows that the problem cannot be solved by following his methods.
As a result, I found that the. DBF file is not in the E:/database/Oracle/product/10.2.0/oradata/supermapdb folder. Only the supermapdb. DBF file is available. I think this supermapdb. DBF may be the. DBF file, so I changed the supermapdb. DBF file to. DBF. Retry the above method. ORA-16038, ORA-19809, ORA-00312 error!
I followed the solution below,
(2) solution of ORA-16038 ORA-19809 ORA-00312
Oracle 10 Gb archive logs are stored in flash_recovery_area by default, and 1 GB is selected during the default installation.
When the size of archived logs exceeds 1 GB, the space is insufficient, so the archived log files cannot be archived. Oracle cannot identify whether the archived log files are released. The database cannot be started.
Solution:
1. Mount the database
SQL> startup Mount (note that an error is reported at this time, but the system parameters can be changed)
2. Change System Parameters
SQL> alter system set db_recovery_file_dest_size = 2G scope = spfile;
{Or alter system set db_recovery_file_dest_size = 4G scope = both ;}
The value of db_recovery_file_dest_size is determined based on the remaining disk space and actual needs.
3. Open the database
SQL> alter database open
4. Delete invalid archive logs.
RMAN
RMAN> connect target/
RMAN> crosscheck archivelog all;
RMAN> Delete expired archivelog all;
RMAN> exit
5. Restart the database
SQL> shutdown immediate
SQL> startup
My supermapdb database is recovered again
OK, everything is normal! Thank you for your support and help.