oracle自动关闭服务,然后手动stratup启动,又能正常使用!

Thu Dec 05 09:37:05 2019
System state dump requested by (instance=1, osid=44223 (DBW0)), summary=[abnormal instance termination].
System State dumped to trace file /oracle/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_diag_44215_20191205093705.trc
Instance terminated by DBW0, pid = 44223
Thu Dec 05 09:47:25 2019
Adjusting the default value of parameter parallel_max_servers
from 320 to 120 due to the value of parameter processes (150)
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = 64 KB

Total Shared Global Region in Large Pages = 0 KB (0%)

Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB

RECOMMENDATION:
Total System Global Area size is 9634 MB. For optimal performance,
prior to the next instance restart:

  1. Increase the number of unused large pages by at least 4817 (page size 2048 KB, total size 9634 MB) system wide to get 100% of the System Global Area allocated with large pages
  2. Large pages are automatically locked into physical memory. Increase the per process memlock (soft) limit to at least 9642 MB to lock 100% System Global Area's large pages into physical memory ******************************************************************** LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Initial number of CPU is 8 Number of processor cores in the system is 8 Number of processor sockets in the system is 1 CELL communication is configured to use 0 interface(s): CELL IP affinity details: NUMA status: non-NUMA system cellaffinity.ora status: N/A CELL communication will use 1 IP group(s): Grp 0: Picked latch-free SCN scheme 3 Autotune of undo retention is turned on. IMODE=BR ILAT =27 LICENSE_MAX_USERS = 0 SYS auditing is disabled Starting up: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options. ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1 System name: Linux Node name: easdatabase Release: 2.6.32-642.el6.x86_64 Version: #1 SMP Tue May 10 17:27:01 UTC 2016 Machine: x86_64 Using parameter settings in server-side spfile /oracle/app/oracle/product/11.2.0/dbhome_1/dbs/spfileorcl.ora System parameters with non-default values: processes = 150 sga_target = 9632M control_files = "/oracle/app/oracle/oradata/orcl/control01.ctl" control_files = "/oracle/app/oracle/fast_recovery_area/orcl/control02.ctl" db_block_size = 8192 compatible = "11.2.0.4.0" log_archive_dest_1 = "location=/mnt1/archivelog" db_recovery_file_dest = "/oracle/app/oracle/fast_recovery_area" db_recovery_file_dest_size= 35G undo_tablespace = "UNDOTBS1" remote_login_passwordfile= "EXCLUSIVE" db_domain = "" dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)" audit_file_dest = "/oracle/app/oracle/admin/orcl/adump" audit_trail = "DB" db_name = "orcl" open_cursors = 300 _b_tree_bitmap_plans = FALSE _no_or_expansion = TRUE optimizer_index_cost_adj = 50 optimizer_index_caching = 90 pga_aggregate_target = 3210M diagnostic_dest = "/oracle/app/oracle" Thu Dec 05 09:47:26 2019 PMON started with pid=2, OS id=47601 Thu Dec 05 09:47:26 2019 PSP0 started with pid=3, OS id=47603 Thu Dec 05 09:47:28 2019 VKTM started with pid=4, OS id=47607 at elevated priority VKTM running at (1)millisec precision with DBRM quantum (100)ms Thu Dec 05 09:47:28 2019 GEN0 started with pid=5, OS id=47611 Thu Dec 05 09:47:28 2019 DIAG started with pid=6, OS id=47613 Thu Dec 05 09:47:28 2019 DBRM started with pid=7, OS id=47615 Thu Dec 05 09:47:28 2019 DIA0 started with pid=8, OS id=47617 Thu Dec 05 09:47:28 2019 MMAN started with pid=9, OS id=47619 Thu Dec 05 09:47:28 2019 DBW0 started with pid=10, OS id=47621 Thu Dec 05 09:47:28 2019 LGWR started with pid=11, OS id=47623 Thu Dec 05 09:47:28 2019 CKPT started with pid=12, OS id=47625 Thu Dec 05 09:47:28 2019 SMON started with pid=13, OS id=47627 Thu Dec 05 09:47:28 2019 RECO started with pid=14, OS id=47629 Thu Dec 05 09:47:28 2019 MMON started with pid=15, OS id=47631 Thu Dec 05 09:47:28 2019 MMNL started with pid=16, OS id=47634 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = /oracle/app/oracle Thu Dec 05 09:47:28 2019 ALTER DATABASE MOUNT Successful mount of redo thread 1, with mount id 1553952944 Database mounted in Exclusive Mode Lost write protection disabled Completed: ALTER DATABASE MOUNT Thu Dec 05 09:47:33 2019 ALTER DATABASE OPEN Beginning crash recovery of 1 threads parallel recovery started with 7 processes Started redo scan Completed redo scan read 10546 KB redo, 1690 data blocks need recovery Started redo application at Thread 1: logseq 47164, block 39943 Recovery of Online Redo Log: Thread 1 Group 3 Seq 47164 Reading mem 0 Mem# 0: /oracle/app/oracle/oradata/orcl/redo03.log Recovery of Online Redo Log: Thread 1 Group 2 Seq 47165 Reading mem 0 Mem# 0: /oracle/app/oracle/oradata/orcl/redo02.log Completed redo application of 5.86MB Completed crash recovery at Thread 1: logseq 47165, block 4932, scn 500814159 1690 data blocks read, 1688 data blocks written, 10546 redo k-bytes read Thu Dec 05 09:47:40 2019 LGWR: STARTING ARCH PROCESSES Thu Dec 05 09:47:40 2019 ARC0 started with pid=27, OS id=47696 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES Thu Dec 05 09:47:41 2019 ARC1 started with pid=28, OS id=47711 Thu Dec 05 09:47:41 2019 ARC2 started with pid=30, OS id=47713 Thu Dec 05 09:47:41 2019 ARC3 started with pid=29, OS id=47715 ARC1: Archival started ARC2: Archival started ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH ARC2: Becoming the heartbeat ARCH Thread 1 advanced to log sequence 47166 (thread open) Thread 1 opened at log sequence 47166 Current log# 1 seq# 47166 mem# 0: /oracle/app/oracle/oradata/orcl/redo01.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Thu Dec 05 09:47:41 2019 SMON: enabling cache recovery Archived Log entry 44784 added for thread 1 sequence 47165 ID 0x58d8a86f dest 1: [47655] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:1111127512 end:1111127762 diff:250 (2 seconds) Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is AL32UTF8 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Thu Dec 05 09:47:43 2019 Starting background process QMNC Thu Dec 05 09:47:43 2019 QMNC started with pid=31, OS id=47739 ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Thu Dec 05 09:47:44 2019 db_recovery_file_dest_size of 35840 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. Completed: ALTER DATABASE OPEN Thu Dec 05 09:47:45 2019 Starting background process CJQ0 Thu Dec 05 09:47:45 2019 CJQ0 started with pid=32, OS id=47753 Thu Dec 05 09:48:03 2019 Starting background process SMCO Thu Dec 05 09:48:03 2019 SMCO started with pid=47, OS id=47850
Csdn user default icon
上传中...
上传图片
插入图片
抄袭、复制答案,以达到刷声望分或其他目的的行为,在CSDN问答是严格禁止的,一经发现立刻封号。是时候展现真正的技术了!
立即提问