My Oracle Support Banner

After upgrade to, Database Failed to MOUNT (Doc ID 1622319.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


After a successful upgrade to Database will not mount reporting ORA-03113 error.

SQL> startup
ORACLE instance started.

Total System Global Area 2137886720 bytes
Fixed Size                  2282944 bytes
Variable Size             620759616 bytes
Database Buffers         1509949440 bytes
Redo Buffers                4894720 bytes
ORA-03113: end-of-file on communication channel
Process ID: 758176
Session ID: 122 Serial number: 1


There are no errors in alert file. Only instance forced to terminate.
Thu Jan 30 11:54:29 2014
MMNL started with pid=21, OS id=706912
NOTE: initiating MARK startup
Starting background process MARK
Thu Jan 30 11:54:30 2014
MARK started with pid=22, OS id=704704
NOTE: MARK has subscribed
Thu Jan 30 11:54:29 2014
SMON started with pid=16, OS id=710392
Thu Jan 30 11:54:29 2014
MMON started with pid=20, OS id=710444
Thu Jan 30 11:54:29 2014
RBAL started with pid=18, OS id=710228
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = J:\app\oracle
Thu Jan 30 11:54:37 2014
Shutting down instance (abort)
License high water mark = 2
USER (ospid: 708568): terminating the instance      <<<<< Process is terminating the instance <<<<
Thu Jan 30 11:54:52 2014
Instance terminated by USER, pid = 708568
Thu Jan 30 11:54:52 2014
Instance shutdown complete


Upgrade to


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.