ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist

打开Oracle警告日志文件判断错误的具体原因。

警告日志文件的具体位置:C:\app\zjuvlis\diag\rdbms\orcl\orcl\trace\alert_orcl.log

orcl换成你数据库的特定SID

打开警告日志文件并浏览最后(即最新产生的日志)


Errors in file c:\app\zjuvlis\diag\rdbms\orcl\orcl\trace\orcl_ora_4008.trc:
ORA-16038: ?? 2 sequence# 449 ????
ORA-19809: ???????????
ORA-00312: ???? 2 ?? 1: 'C:\APP\ZJUVLIS\ORADATA\ORCL\REDO02.LOG'
USER (ospid: 4008): terminating the instance due to error 16038
Errors in file c:\app\zjuvlis\diag\rdbms\orcl\orcl\trace\orcl_arc2_4652.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 4102029312 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************

确定为ORA-19809 超出了恢复文件数的限制。


下面就解决ORA-19809错误:

C:\ RMAN  TARGET orcl

提示输入口令,输入当前操作系统登录用户的口令

如果提示(未启动),肯定是未启动,因为你此时是无法正常启动数据库的。

RMAN>STARTUP MOUNT;

RMAN>DELETE ARCHIVELOG ALL;  // 删除所有归档日志

RMAN>CROSSCHECK ARCHIVELOG ALL;  // 对归档做一致性检查

退出RMAN

C:\SQLPLUS /nolog

SQL>conn /as  sysdba;

SQL>SHUTDOWN  IMMEDIATE

SQL>STARTUP

一切恢复正常

你可能感兴趣的:(ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist)