Skip to main content

How to fix : ORA-03113: end-of-file on communication channel

Today when I tried to open my db (that db was created and lunched inside container) I saw ORA-03113: end-of-file on communication channel.


 SQL> startup  
 ORACLE instance started.  
 Total System Global Area 3.4206E+10 bytes  
 Fixed Size   2270360 bytes  
 Variable Size  3422554984 bytes  
 Database Buffers 3.0736E+10 bytes  
 Redo Buffers   45649920 bytes  
 Database mounted.  
 ERROR at line 1:  
 ORA-03113: end-of-file on communication channel  
 Process ID: 11344  
 Session ID: 380 Serial number: 3 



There is a lot of reason can be, after check it out from the forum all I need is clear unarchivelog.

First start instance mount mode.


 SQL> startup mount  
 ORACLE instance started.  
 Total System Global Area 3.4206E+10 bytes  
 Fixed Size   2270360 bytes  
 Variable Size  3422554984 bytes  
 Database Buffers 3.0736E+10 bytes  
 Redo Buffers   45649920 bytes  
 Database mounted.Database mounted. 



-check how many group we have:


SQL> set linesize 200  
 SQL> select group#, members, status from v$log;  
   GROUP#  MEMBERS STATUS  
 ---------- ---------- ----------------  
  1   2 INACTIVE  
  2   2 INACTIVE  
  3   2 INACTIVE  
  4   2 INACTIVE  
  5   2 INACTIVE  
  6   2 CURRENT  
  14   2 INACTIVE  
  8   2 INACTIVE  
  9   2 INACTIVE  
  10   2 INACTIVE  
  11   2 INACTIVE  
   GROUP#  MEMBERS STATUS  
 ---------- ---------- ----------------  
  12   2 INACTIVE  
  13   2 INACTIVE  
  7   2 INACTIVE  
 14 rows selected.  
 SQL>  


Writing this simple PLSQL anonyms block to clear unarchived log files.



SQL> BEGIN FOR i IN 1 .. 14 LOOP execute immediate 'alter database clear unarchived logfile group '||i; END LOOP; END; / PL/SQL procedure successfully completed. SQL>


--look alertlog
alter database clear unarchived logfile group 13
WARNING! CLEARING REDO LOG WHICH HAS NOT BEEN ARCHIVED. BACKUPS TAKEN
    BEFORE 04/15/2020 12:35:11 (CHANGE 228093) CANNOT BE USED FOR RECOVERY.
Clearing online log 13 of thread 1 sequence number 195
Completed: alter database clear unarchived logfile group 13
alter database clear unarchived logfile group 14
WARNING! CLEARING REDO LOG WHICH HAS NOT BEEN ARCHIVED. BACKUPS TAKEN
    BEFORE 04/15/2020 12:40:12 (CHANGE 228198) CANNOT BE USED FOR RECOVERY.
Clearing online log 14 of thread 1 sequence number 196
Wed Apr 15 15:22:49 2020
Completed: alter database clear unarchived logfile group 14




you can restart db or just try to switch from mount mode to open

alter database open;

or

 SQL> shut immediate  
 ORA-01109: database not open  
 Database dismounted.  
 ORACLE instance shut down.  
 SQL>  
 SQL> startup  
 ORACLE instance started.  
 Total System Global Area 3.4206E+10 bytes  
 Fixed Size   2270360 bytes  
 Variable Size  3422554984 bytes  
 Database Buffers 3.0736E+10 bytes  
 Redo Buffers   45649920 bytes  
 Database mounted.  
 Database opened.  
 SQL>  




Comments

Popular posts from this blog

Rman encryption and other techniques

Today I will demonstrate Recovery Manager features, especially encryption and some other techniques. First of all let me note about RMAN backup encryption. Staring from Oracle 10g RMAN now creates encrypted backups that cannot be restored by unauthorized people. There are 3 modes of backup encryption: * Transparent encryption * Password encryption * Dual-mode encryption using either transparent or password encryption All RMAN backups are not encrypted but you can encrypt any RMAN backup in the form of a backup set. In this tutorial I will show you how to configure Password encryption. Let`s finish talking and start to demonstrate. check parameters with "SHOW ALL" command, by default encryption is OFF RMAN> show all; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTR...

ORA-03206: maximum file size of (5242880) blocks in AUTOEXTEND clause is out of range

Today when I want to change max size of datafile I got strange error. ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/MYDB/users01.dbf' AUTOEXTEND ON NEXT 1280K MAXSIZE 32GB ORA-03206: maximum file size of (5242880) blocks in AUTOEXTEND clause is out of range Here is reason: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed. After research internet I found that instead of using 32GB we can use 32767M. (same values but in MB). Or you may use 31GB too. ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/MYDB/users01.dbf' AUTOEXTEND ON NEXT 1280K MAXSIZE 32767M;

Fix ORA-01139: RESETLOGS option only valid after an incomplete database recovery

While shutting down my TEST database process was hanged. Then I had to use shutdown abort. But when I wanted to start database it did not open. SQL> select name from v$database; NAME --------- TEST SQL> shut abort; ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area 6597406720 bytes Fixed Size 2265664 bytes Variable Size 3204451776 bytes Database Buffers 3372220416 bytes Redo Buffers 18468864 bytes Database mounted. SQL> alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 6552 Session ID: 191 Serial number: 3  What`s wrong?  SQL> alter database open resetlogs; ERROR:    ORA-03114: not connected to ORACLE    SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Pr...