Situation:
Windows server 2008
Oracle 11 g 2.0.2 the RAC
Question:
Recently, has been running more than a year, suddenly unable to connect, check found the Windows service (OracleServiceSID) will automatically shut down;
Further found that, when mounted state, services;
Once the startup database, service will fall;
Operation:
Redo a same environment database, the data files, control files, such as the overall migration, the question remains;
The alter some logs:
Fri Jun 02 16:12:12 2017
QMNC started with pid=27, OS id=6616
Completed: the alter database open
Starting background process CJQ0
Fri Jun 02 16:12:13 2017
CJQ0 started with pid=29, OS id=7040
Fri Jun 02 16:12:13 2017
Db_recovery_file_dest_size of 40960 MB is 34.56% 2. This is a
User - specified limit on the amount of space that will be 2 by this
The database for recovery - related files, and does not reflect the amount of
Space available in the physicist filesystem or ASM diskgroup.
Setting the Resource Manager to plan the SCHEDULER x310a [0] : DEFAULT_MAINTENANCE_PLAN via the SCHEDULER window
Setting the Resource Manager plan DEFAULT_MAINTENANCE_PLAN via the parameter
Starting background process VKRM
Fri Jun 02 16:12:16 2017
VKRM started with pid=28, OS id=6604
Fri Jun 02 16:12:19 2017
Shutting down the instance (immediate)
Shutting down the instance: further logons disabled
Stopping background process QMNC
Stopping background process CJQ0
Stopping background process MMNL
Stopping background process MMON
License high water mark=8
Stopping the Job queue slave the processes, flags=7
The Job queue slave the processes stopped
All dispatchers and Shared the servers shutdown
The ALTER DATABASE CLOSE NORMAL
Fri Jun 02 16:12:22 2017
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Jun 02 16:12:22 2017
Shutting down to archive the processes
Archiving is disabled
Active Archive process shutdown avoided: 0
Thread 1 closed at the log sequence 32189
Successful close of redo thread 1
Completed: the ALTER DATABASE CLOSE NORMAL
The ALTER DATABASE DISMOUNT
Completed: the ALTER DATABASE DISMOUNT
The ARCH: Archival disabled due to shutdown: 1089
Shutting down to archive the processes
Archiving is disabled
The ARCH: Archival disabled due to shutdown: 1089
Shutting down to archive the processes
Archiving is disabled
Fri Jun 02 16:12:23 2017
Stopping background process VKTM
Fri Jun 02 16:12:25 2017
The Instance shutdown complete
Fri Jun 02 16:12:32 2017
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION=0
LICENSE_SESSIONS_WARNING=0
Picked latch - free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT=126
LICENSE_MAX_USERS=0
SYS auditing is disabled
Starting up:
Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0-64 - bit Production
With the Partitioning, OLAP, Data Mining, and Real Application Testing options.
Using the parameter Settings in the server - side spfile E: \ \ ADMINISTRATOR \ PRODUCT \ APP 11.2.0 \ DBHOME_1 \ DATABASE \ SPFILESN67 ORA
The System parameters with non - the default values:
The processes=750
Java_pool_size=128 m
Nls_length_semantics="BYTE"
Memory_target=26240 m
Control_files="E: \ \ ADMINISTRATOR \ ORADATA \ APP SN67 \ CONTROL01 CTL"
Control_files="E: \ \ ADMINISTRATOR \ FAST_RECOVERY_AREA APP \ SN67 \ CONTROL02 CTL"
Db_block_size=8192
Compatible="11.2.0.0.0"
Db_recovery_file_dest="e: \ \ Administrator \ fast_recovery_area app"
Db_recovery_file_dest_size 40 g=
Undo_tablespace="UNDOTBS1"
Db_securefile="PERMITTED"
Remote_login_passwordfile="EXCLUSIVE"
Db_domain=""
Dispatchers="(TCP) PROTOCOL=(SERVICE=SN67XDB)"
Audit_file_dest="E: \ \ ADMINISTRATOR \ ADMIN \ APP SN67 \ ADUMP"
Audit_trail="DB"
Sort_area_size=131072
Db_name="SN67"
Open_cursors=750
Optimizer_capture_sql_plan_baselines=FALSE
Optimizer_use_sql_plan_baselines=FALSE
Diagnostic_dest="E: \ APP \ ADMINISTRATOR"
Fri Jun 02 16:12:33 2017
PMON started with pid=2, OS id=6472
Fri Jun 02 16:12:33 2017
PSP0 started with pid=3, OS id=6828
Fri Jun 02 16:12:35 2017
VKTM started with pid=4, OS id=6896 at elevated priority
VKTM running at (10) millisec precision with DBRMS quantum (100) ms
Fri Jun 02 16:12:35 2017
Get started with pid=5, OS id=6040
Fri Jun 02 16:12:35 2017
DIAG started with pid=6, OS id=928
Fri Jun 02 16:12:35 2017
DBRMS started with pid=7, OS id=6760
Fri Jun 02 16:12:35 2017
DIA0 started with pid=8, OS id=6992
Fri Jun 02 16:12:35 2017
MMAN started with pid=9, OS id=5612
Fri Jun 02 16:12:35 2017
DBW0 started with pid=10, OS id=6340
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
