近期公司的生产库出现监听奔溃的问题，具体症状如下：
1、客户机提示无监听程序，部分连着的客户机不受影响。
2、故障时使用Telnet ping 1521失败；
3、本地打开服务器，使用sys登录失败[使用sqlplus ]
对应：
1、在Windows任务管理器中，重启监听程序==〉无效
2、强制重启服务器==〉恢复，但是Oracle启动日志很奇怪，非正常。
求助事项：
因为近一周已经出现了2次，之前用了几年都没有问题，有谁能帮忙分析一下原因的处理办法。
以下是系统信息：
1、OS windows2008 r2
2、Oracle 11G 11.2.0.1
Oracle日志：
Sun Nov 12 02:33:20 2017
Errors in file d:\app\administrator\diag\rdbms\bpass\bpass\trace\bpass_cjq0_4880.trc (incident=259220):
ORA-00445: 后台进程 "J000" 在 120 秒之后仍没有启动
kkjcre1p: unable to spawn jobq slave process
Errors in file d:\app\administrator\diag\rdbms\bpass\bpass\trace\bpass_cjq0_4880.trc:
Sun Nov 12 02:35:25 2017
Errors in file d:\app\administrator\diag\rdbms\bpass\bpass\trace\bpass_smco_2296.trc (incident=259228):
ORA-00445: 后台进程 "W000" 在 120 秒之后仍没有启动
Sun Nov 12 02:37:31 2017
Errors in file d:\app\administrator\diag\rdbms\bpass\bpass\trace\bpass_cjq0_4880.trc (incident=259221):
ORA-00445: 后台进程 "J000" 在 120 秒之后仍没有启动
kkjcre1p: unable to spawn jobq slave process
Errors in file d:\app\administrator\diag\rdbms\bpass\bpass\trace\bpass_cjq0_4880.trc:
Sun Nov 12 02:40:52 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 =134
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production.
Using parameter settings in server-side spfile D:\APP\ADMINISTRATOR\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILEBPASS.ORA
System parameters with non-default values:
processes = 800
sessions = 1224
nls_language = "SIMPLIFIED CHINESE"
nls_territory = "CHINA"
memory_target = 11488M
control_files = "D:\APP\ADMINISTRATOR\ORADATA\BPASS\CONTROL01.CTL"
control_files = "D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\BPASS\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
db_recovery_file_dest = "D:\app\Administrator\flash_recovery_area"
db_recovery_file_dest_size= 3912M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=bpassXDB)"
audit_file_dest = "D:\APP\ADMINISTRATOR\ADMIN\BPASS\ADUMP"
audit_trail = "DB"
db_name = "bpass"
open_cursors = 300
diagnostic_dest = "D:\APP\ADMINISTRATOR"
Sun Nov 12 02:40:54 2017
PMON started with pid=2, OS id=2644
Sun Nov 12 02:40:54 2017
VKTM started with pid=3, OS id=2648 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Sun Nov 12 02:40:54 2017
GEN0 started with pid=4, OS id=2652
Sun Nov 12 02:40:54 2017
DIAG started with pid=5, OS id=2656
Sun Nov 12 02:40:54 2017
DBRM started with pid=6, OS id=2660
Sun Nov 12 02:40:54 2017
PSP0 started with pid=7, OS id=2664
Sun Nov 12 02:40:54 2017
DIA0 started with pid=8, OS id=2668
Sun Nov 12 02:40:54 2017
MMAN started with pid=9, OS id=2672
Sun Nov 12 02:40:54 2017
DBW0 started with pid=10, OS id=2676
Sun Nov 12 02:40:54 2017
LGWR started with pid=11, OS id=2680
Sun Nov 12 02:40:54 2017
CKPT started with pid=12, OS id=2684
Sun Nov 12 02:40:54 2017
SMON started with pid=13, OS id=2688
Sun Nov 12 02:40:54 2017
RECO started with pid=14, OS id=2692
Sun Nov 12 02:40:54 2017
MMON started with pid=15, OS id=2696
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\app\Administrator
Sun Nov 12 02:40:55 2017
alter database mount exclusive
Sun Nov 12 02:40:54 2017
MMNL started with pid=16, OS id=2700
Sun Nov 12 02:40:58 2017
Sweep [inc][259228]: completed
Sweep [inc][259227]: completed
Sweep [inc][259226]: completed
Sweep [inc][259225]: completed
Sweep [inc][259221]: completed
Sweep [inc][259220]: completed
Sweep [inc][259219]: completed
Sweep [inc][259218]: completed
Sweep [inc][259217]: completed
Sweep [inc][253768]: completed
Sweep [inc][253767]: completed
Sweep [inc][253766]: completed
Sweep [inc][253765]: completed
Sweep [inc][253764]: completed
Sweep [inc][253763]: completed
Sweep [inc][253762]: completed
Sweep [inc][253761]: completed
Sweep [inc][253048]: completed
Sweep [inc][253047]: completed
Sweep [inc][253046]: completed
Sweep [inc][253045]: completed
Sweep [inc][253044]: completed
Sweep [inc][253043]: completed
Sweep [inc][253042]: completed
Sweep [inc][253041]: completed
Sweep [inc][252938]: completed
Sweep [inc][252937]: completed
Sweep [inc2][253762]: completed
Sweep [inc2][253761]: completed
Sweep [inc2][253043]: completed
Sweep [inc2][253042]: completed
Sweep [inc2][253041]: completed
Successful mount of redo thread 1, with mount id 2426116855
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
read 83211 KB redo, 9758 data blocks need recovery
Started redo application at
Thread 1: logseq 292932, block 16803
Recovery of Online Redo Log: Thread 1 Group 3 Seq 292932 Reading mem 0
Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\BPASS\REDO03.LOG
Recovery of Online Redo Log: Thread 1 Group 1 Seq 292933 Reading mem 0
Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\BPASS\REDO01.LOG
Recovery of Online Redo Log: Thread 1 Group 2 Seq 292934 Reading mem 0
Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\BPASS\REDO02.LOG
Sun Nov 12 02:41:06 2017
Completed redo application of 47.18MB
Completed crash recovery at
Thread 1: logseq 292934, block 42494, scn 35114626295
9758 data blocks read, 9758 data blocks written, 83211 redo k-bytes read
Sun Nov 12 02:41:11 2017
Thread 1 advanced to log sequence 292935 (thread open)
Thread 1 opened at log sequence 292935
Current log# 3 seq# 292935 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\BPASS\REDO03.LOG
Successful open of redo thread 1
Sun Nov 12 02:41:12 2017
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Sun Nov 12 02:41:16 2017
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Sun Nov 12 02:41:20 2017
QMNC started with pid=20, OS id=3952
Completed: alter database open
Sun Nov 12 02:41:24 2017
db_recovery_file_dest_size of 3912 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Sun Nov 12 02:41:24 2017
Starting background process CJQ0
Sun Nov 12 02:41:24 2017
CJQ0 started with pid=19, OS id=1900
Sun Nov 12 02:50:47 2017
Starting background process SMCO
Sun Nov 12 02:50:47 2017
SMCO started with pid=54, OS id=3612 
