【環境介紹】
該報錯信息解釋為數據庫正在啟動或者數據庫關閉狀態
[oracle@alllinux ~]$ oerr ora 01033
01033, 00000, "ORACLE initialization or shutdown in progress"
// *Cause: An attempt was made to log on while Oracle is being started up
// or shutdown.
// *Action: Wait a few minutes. Then retry the operation.
【問題處理】
根據無法連接數據庫，登錄數據庫查看數據庫是否異常，查看open_mode狀態為mount的狀態，嘗試使用alter database open，嘗試打開數據庫，報錯信息為：
SQL> alter database open;
alter database open
*
第 1 行出現錯誤:
ORA-00333: 重做日志讀取塊 2758 計數 7366 出錯
報錯描述為磁盤IO損壞導致讀取日志文件時報錯，當前數據庫是沒有開啟歸檔，建議是進行restore方法或者拷貝其他的備份文件，當前數據庫沒有進行備份；
查詢資料對於這個報錯可以修改隱含參數_allow_resetlogs_corruption=TRUE 嘗試強制重啟
[oracle@oslatm ~]$ oerr ora 00333
00333, 00000, "redo log read error block %s count %s"
// *Cause: An IO error occurred while reading the log described in the
// accompanying error.
// *Action: Restore accessibility to file, or get another copy of the file.
[oracle@oslatm ~]$
由於沒有備份，建議當前對數據庫進行shutdown冷備，這里直接對數據文件拷貝操作，不然后續出現問題無法進行恢復到最初的狀態；
冷備好數據庫后進行修改參數操作：
*.undo_management='MANUAL'
*.rollback_segments='SYSTEM'
ORACLE 例程已經啟動。
Fixed Size 2256464 bytes
Variable Size 1207959984 bytes
Database Buffers 738197504 bytes
Redo Buffers 5746688 bytes
數據庫裝載完畢。
ORA-00279: 更改 11817660 (在 02/26/2020 11:06:42 生成) 對於線程 1 是必需的
ORA-00289: 建議:
D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\HISDB\ARCHIVELOG\2020_02_26\O1_MF_1
_389_%U_.ARC
ORA-00280: 更改 11817660 (用於線程 1) 在序列 #389 中
指定日志: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: 無法打開歸檔日志
'D:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\RDBMS\ARC0000002478_0975754895.000
1'
ORA-27041: 無法打開文件
OSD-04002: 無法打開文件
O/S-Error: (OS 2) 系統找不到指定的文件。
ORA-01547: 警告: RECOVER 成功但 OPEN RESETLOGS 將出現如下錯誤
ORA-01194: 文件 1 需要更多的恢復來保持一致性
ORA-01110: 數據文件 1: 'E:\FSZYYDATA\HISDB\SYSTEM01.DBF'
SQL> alter database open resetlogs;
alter database open resetlogs
*
第 1 行出現錯誤:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [2662], [2888], [676729259], [2888],
[676735192], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [2888], [676729258], [2888],
[676735192], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [2888], [676729256], [2888],
[676735192], [12583040], [], [], [], [], [], []
進程 ID: 1092
會話 ID: 1144 序列號: 5
嘗試使用resetlogs方式打開數據庫時候出現報錯:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [2662], [2888], [676729259], [2888],
[oracle@oslatm ~]$ oerr ORA 00603
00603, 00000, "ORACLE server session terminated by fatal error"
// *Cause: An Oracle server session was in an unrecoverable state.
// *Action: Log in to Oracle again so a new server session will be created
// automatically. Examine the session trace file for more
// information.
[oracle@oslatm ~]$
查詢資料建議添加參數*._corrupted_rollback_segments=true undo回滾段損壞參數
ORACLE 例程已經啟動。
Fixed Size 2257952 bytes
Variable Size 1342180320 bytes
Database Buffers 1207959552 bytes
Redo Buffers 19746816 bytes
數據庫裝載完畢。
數據庫已經打開。
SQL>
--------------------
READ WRITE
------------------------------------ ----------- ------------------------------
spfile string
SQL>
SQL> create spfile='D:\app\Administrator\product\11.2.0\dbhome_1\database\SPFILEHISDB.ORA' from pfile='E:\backup\PFILEHISDB.ora';
SQL> shutdown immediate
數據庫已經關閉。
已經卸載數據庫。
ORACLE 例程已經關閉。
SQL>
SQL> startup
ORACLE 例程已經啟動。
Fixed Size 2260320 bytes
Variable Size 1811940000 bytes
Database Buffers 1728053248 bytes
Redo Buffers 15331328 bytes
數據庫裝載完畢。
數據庫已經打開。
SQL>
SQL> select open_mode from v$database;
--------------------
READ WRITE
ORA-01552: 非系統表空間 'HTHIS' 不能使用系統回退段
01552, 00000, "cannot use system rollback segment for non-system tablespace '%s'"
// *Cause: Tried to use the system rollback segment for operations involving
// non-system tablespace. If this is a clone database then this will
// happen when attempting any data modification outside of the system
// tablespace. Only the system rollback segment can be online in a
// clone database.
// *Action: Create one or more private/public segment(s), shutdown and then
// startup again. May need to modify the INIT.ORA parameter
// rollback_segments to acquire private rollback segment. If this is
// a clone database being used for tablspace point in time recovery
// then this operation is not allowed. If the non-system tablespace
// has AUTO segment space management, then create an undo tablespace.
[oracle@oslatm ~]$
------------------------------------ ----------- ------------------------------
undo_management string MANUAL
undo_retention integer 900
undo_tablespace string UNDOTBS1
SQL> col file_name for a100
SQL> select file_name,bytes/1024/1024 from dba_data_files where TABLESPACE_NAME like'%UNDO%';
---------------------------------------------------------------------------------------------------- ---------------
E:\TESTDBDATA\HISDB\UNDOTBS01.DBF 2048
SQL>
SQL> alter system set undo_tablespace=undotbs2 scope=spfile;
數據庫已經關閉。
已經卸載數據庫。
ORACLE 例程已經關閉。
SQL>
SQL> startup
ORACLE 例程已經啟動。
Fixed Size 2256464 bytes
Variable Size 1207959984 bytes
Database Buffers 738197504 bytes
Redo Buffers 5746688 bytes
數據庫裝載完畢。
數據庫已經打開。
SQL> show parameter undo
------------------------------------ ----------- ------------------------------
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS2
------------------------------------ ----------- ------------------------------
spfile string D:\APP\ADMINISTRATOR\PRODUCT\1
1.2.0\DBHOME_1\DATABASE\SPFILE
HISDB.ORA
SQL>
SQL> col description for a66
SQL> col value for a30
SQL> SELECT i.ksppinm name,
2 i.ksppdesc description,
3 CV.ksppstvl VALUE
4 FROM sys.x$ksppi i, sys.x$ksppcv CV
5 WHERE i.inst_id = USERENV ('Instance')
6 AND CV.inst_id = USERENV ('Instance')
7 AND i.indx = CV.indx
8 AND i.ksppinm LIKE '%&keyword%'
9 ORDER BY 1;
Enter value for keyword: allow_resetlog
old 8: AND i.ksppinm LIKE '%&keyword%'
new 8: AND i.ksppinm LIKE '%allow_resetlog%'
----------------------------------- ------------------------------------------------------------------ ------------------------------
_allow_resetlogs_corruption allow resetlogs even if it will cause corruption FALSE
【總結】
1，在數據庫異常修復時，建議進行備份操作；
2，建議對數據庫開啟歸檔操作；
3，建議定期對數據庫進行備份操作。