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

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...

Fix: ORA-13639: The current operation was interrupted because it timed out.

Sometimes SQL Tuning Advisor interrupts cause time limit took more than defined. You have to analyze it or increase value. Here you can see increasing of value. Example result of sql select                  execution_name, advisor_name,                  to_char(execution_start,'dd-mon-yy hh:mi:ss') execution_start,                  to_char(execution_end,'dd-mon-yy hh:mi:ss') execution_end, status,error_message from dba_advisor_executions where task_name = 'SYS_AUTO_SQL_TUNING_TASK' order by execution_start; Check value of TIME_LIMIT`s parameter : SQL> column parameter_value for A35 SQL> select parameter_name, parameter_value from dba_advisor_parameters where task_name = 'SYS_AUTO_SQL_TUNING_TASK' and parameter_name in ('TIME_LIMIT', 'DEFAULT_EXECUTION_TYP...

How to fix ORA-26040: Data block was loaded using the NOLOGGING option

Today I faced with new ORA error. After solving I want to share this experience with yours. So, today 5`th datafile of my database was corrupted (/u01/app/oracle/oradata/ulfet_db/example01.dbf). After recover via RMAN I saw strange error. RMAN> recover datafile 5 block 443; Starting recover at 24-MAR-13 using channel ORA_DISK_1 channel ORA_DISK_1: restoring block(s) channel ORA_DISK_1: specifying block(s) to restore from backup set restoring blocks of datafile 00005 channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/ULFET_DB/backupset/2013_03_24/o1_mf_nnndf_TAG20130324T223233_8nykp220_.bkp channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/ULFET_DB/backupset/2013_03_24/o1_mf_nnndf_TAG20130324T223233_8nykp220_.bkp tag=TAG20130324T223233 channel ORA_DISK_1: restored block(s) from backup piece 1 channel ORA_DISK_1: block restore complete, elapsed time: 00:00:03 starting media recovery media recovery complete, elapsed ti...