讲解Oracle数据库ORA-00257故障的解决过程ssf（Explain the Oracle database ORA-00257 fault resolution process SSF）.doc

讲解Oracle数据库ORA-00257故障的解决过程ssf（Explain the Oracle database ORA-00257 fault resolution process SSF） By bear The Oracle database is currently the industrys most commonly used large database system, I met ORA-00257 error in the actual project (space error), by looking for information, most said it was because of the archive log too much, take up hard disk space all cause, by simply deleting the log or increase the storage space can be solved but I am in Oracle 10g found that there is still a lot of storage space, but also reported that this error was originally a new feature in Oracle 10g, resulting in the management of Flash Recovery 1 hardware and software environment Server HP, Proliant, DL580G4 (Intel, Xeon, 3.16GHz/4GB/, 72.8*4/RAID4) Operating system Red, Flag, DC, Server, release 5 (Trinity), for, x86-64, Linux Database Oracle 10.2.0.1.0 2, the phenomenon of problems The database system has been running for more than half a month, and the ORA-00257 error occurred when the data was updated after connecting the database in the evening of July 24th, as shown below That filing errors, by searching the ORACLE error code, explanation for the lack of disk space, need to delete log space increases, but the server space available 200GB, currently only 10GB or so, which is why? 3 diagnostic process: (1) check the ORACLE database archive log status [root@hrmsdb CD /oracle/flash_recovery_area/HKCHR/archivelog /]# [root@hrmsdb archivelog]# LS 2006_07_04, 2006_07_13, 2006_07_17, 2006_07_20, 2006_07_23 2006_07_11, 2006_07_14, 2006_07_18, 2006_07_21, 2006_07_24 2006_07_12, 2006_07_15, 2006_07_19, 2006_07_22, 2006_07_25 [root@hrmsdb archivelog]# CD 2006_07_25 [root@hrmsdb 2006_07_25]# LS [root@hrmsdb 2006_07_25]# CD../2006_07_24 [root@hrmsdb 2006_07_24]# LS O1_mf_1_92_2d933vgb_.arc o1_mf_1_96_2d954ns7_.arc o1_mf_1_98_2d969d5h_.arc O1_mf_1_95_2d9537cs_.arc o1_mf_1_97_2d956km0_.arc Explains that database archiving has been normal before a problem occurs (2) look at the database RE