Oracle 11.2.0.4 单实例的 db instance 启动的alert
Oracle 11.2.0.4 单实例的 db instance 启动的alert
Oracle 11.2.0.4 单实例的 db instance 启动的alert
Fri Jan 09 03:11:17 2015
DIAG started with pid=19, OS id=6031
Dumping diagnostic data in directory=[cdmp_20150109031118], requested by (instance=1, osid=2456 (CJQ0)), summary=[incident=45657].
Mon Feb 09 01:51:09 2015
Adjusting the default value of parameter parallel_max_servers
from 160 to 120 due to the value of parameter processes (150) --->自动调整parallel_max_servers参数
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 1026 MB. For optimal performance,
prior to the next instance restart:
1. Increase the number of unused large pages by
at least 513 (page size 2048 KB, total size 1026 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 1034 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 4 --->启动时的cpu个数
CELL communication is configured to use 0 interface(s):
CELL IP affinity details:
NUMA status: non-NUMA system--->启动时的NUMA信息
cellaffinity.ora status: N/A
CELL communication will use 1 IP group(s):
Grp 0:
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u02/app/oracle/product/11.2.0.4/db_1/dbs/arch
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 = /u02/app/oracle/product/11.2.0.4/db_1
System name: Linux
Node name: rhel63single
Release: 2.6.32-279.el6.x86_64 --->linux 的内核版本号
Version: #1 SMP Wed Jun 13 18:24:36 EDT 2012
Machine: x86_64
VM name: VMWare Version: 6 --->主机是 vm虚拟机，，vm虚拟机的版本
Using parameter settings in server-side spfile /u02/app/oracle/product/11.2.0.4/db_1/dbs/spfiletest.ora
System parameters with non-default values:--->上一行是启动时的所读取的spfile文件的位置
processes = 150
sga_max_size = 1G
shared_pool_size = 256M
java_pool_size = 256M
sga_target = 1G
control_files = "/u01/app/oracle/oradata/test/control01.ctl"
control_files = "/u01/app/oracle/oradata/test/control02.ctl"
db_block_size = 8192
compatible = "11.2.0.0.0"
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=testXDB)"
audit_file_dest = "/u01/app/oracle/admin/test/adump"
audit_trail = "DB"
db_name = "test"
open_cursors = 300
pga_aggregate_target = 96M
diagnostic_dest = "/u01/app/oracle"
Mon Feb 09 01:51:13 2015
PMON started with pid=2, OS id=2397
Mon Feb 09 01:51:13 2015
PSP0 started with pid=3, OS id=2399
Mon Feb 09 01:51:15 2015
VKTM started with pid=4, OS id=2401 at elevated priority
Mon Feb 09 01:51:15 2015
GEN0 started with pid=5, OS id=2405
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Mon Feb 09 01:51:15 2015
DIAG started with pid=6, OS id=2407
Mon Feb 09 01:51:15 2015
DBRM started with pid=7, OS id=2409
Mon Feb 09 01:51:15 2015
DIA0 started with pid=8, OS id=2411
Mon Feb 09 01:51:15 2015
MMAN started with pid=9, OS id=2413
Mon Feb 09 01:51:15 2015
DBW0 started with pid=10, OS id=2415
Mon Feb 09 01:51:15 2015
LGWR started with pid=11, OS id=2417
Mon Feb 09 01:51:15 2015
CKPT started with pid=12, OS id=2419
Mon Feb 09 01:51:15 2015
SMON started with pid=13, OS id=2421
Mon Feb 09 01:51:15 2015
RECO started with pid=14, OS id=2423
Mon Feb 09 01:51:15 2015
MMON started with pid=15, OS id=2425
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Mon Feb 09 01:51:15 2015
MMNL started with pid=16, OS id=2427
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u02/app/oracle
Mon Feb 09 01:51:17 2015
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 2169318165
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Mon Feb 09 01:51:22 2015
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Started redo scan
Completed redo scan
read 7 KB redo, 0 data blocks need recovery
Started redo application at
Thread 1: logseq 124, block 3492
Recovery of Online Redo Log: Thread 1 Group 1 Seq 124 Reading mem 0
Mem# 0: /u01/app/oracle/oradata/test/redo01.log
Completed redo application of 0.00MB
Completed crash recovery at
Thread 1: logseq 124, block 3506, scn 3065931
0 data blocks read, 0 data blocks written, 7 redo k-bytes read
Thread 1 advanced to log sequence 125 (thread open)
Thread 1 opened at log sequence 125
Current log# 2 seq# 125 mem# 0: /u01/app/oracle/oradata/test/redo02.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
[2437] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:4867074 end:4868274 diff:1200 (12 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 ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Feb 09 01:51:29 2015
QMNC started with pid=23, OS id=2465
Mon Feb 09 01:51:40 2015
Completed: ALTER DATABASE OPEN
Mon Feb 09 01:51:41 2015
Starting background process CJQ0
Mon Feb 09 01:51:41 2015
CJQ0 started with pid=28, OS id=2483
Mon Feb 09 01:53:42 2015
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Mon Feb 09 01:53:43 2015
Stopping background process CJQ0
Stopping background process QMNC
Stopping background process MMNL
Stopping background process MMON
License high water mark = 13
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Mon Feb 09 01:53:48 2015
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Feb 09 01:53:48 2015
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 125
Successful close of redo thread 1
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Feb 09 01:53:50 2015
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Feb 09 01:53:52 2015
Instance shutdown complete
Mon Feb 09 01:54:34 2015
Adjusting the default value of parameter parallel_max_servers
from 160 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 1026 MB. For optimal performance,
prior to the next instance restart:
1. Increase the number of unused large pages by
at least 513 (page size 2048 KB, total size 1026 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 1034 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 4
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
Using LOG_ARCHIVE_DEST_1 parameter default value as /u02/app/oracle/product/11.2.0.4/db_1/dbs/arch
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 = /u02/app/oracle/product/11.2.0.4/db_1
System name: Linux
Node name: rhel63single
Release: 2.6.32-279.el6.x86_64
Version: #1 SMP Wed Jun 13 18:24:36 EDT 2012
Machine: x86_64
VM name: VMWare Version: 6
Using parameter settings in client-side pfile /home/oracle/lei20150212.ora on machine rhel63single
System parameters with non-default values:--->上一行是启动时的所读取的pfile文件的位置
processes = 150
sga_max_size = 1G
shared_pool_size = 256M
java_pool_size = 256M
sga_target = 1G
control_files = "/u01/app/oracle/oradata/test/control01.ctl"
control_files = "/u01/app/oracle/oradata/test/control02.ctl"
db_block_size = 8192
compatible = "11.2.0.0.0"
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=testXDB)"
audit_file_dest = "/u01/app/oracle/admin/test/adump"
audit_trail = "DB"
db_name = "test"
open_cursors = 300
pga_aggregate_target = 96M
diagnostic_dest = "/u01/app/oracle"
Mon Feb 09 01:54:37 2015
PMON started with pid=2, OS id=2519
Mon Feb 09 01:54:37 2015
PSP0 started with pid=3, OS id=2521
Mon Feb 09 01:54:38 2015
VKTM started with pid=4, OS id=2523 at elevated priority
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Mon Feb 09 01:54:38 2015
GEN0 started with pid=5, OS id=2527
Mon Feb 09 01:54:39 2015
DIAG started with pid=6, OS id=2529
Mon Feb 09 01:54:39 2015
DBRM started with pid=7, OS id=2531
Mon Feb 09 01:54:39 2015
DIA0 started with pid=8, OS id=2533
Mon Feb 09 01:54:39 2015
MMAN started with pid=9, OS id=2535
Mon Feb 09 01:54:39 2015
DBW0 started with pid=10, OS id=2537
Mon Feb 09 01:54:39 2015
LGWR started with pid=11, OS id=2539
Mon Feb 09 01:54:39 2015
CKPT started with pid=12, OS id=2541
Mon Feb 09 01:54:39 2015
SMON started with pid=13, OS id=2543
Mon Feb 09 01:54:39 2015
RECO started with pid=14, OS id=2545
Mon Feb 09 01:54:39 2015
MMON started with pid=15, OS id=2547
Mon Feb 09 01:54:39 2015
MMNL started with pid=16, OS id=2549
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u02/app/oracle
Mon Feb 09 01:54:39 2015
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 2169320159
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Mon Feb 09 01:54:43 2015
ALTER DATABASE OPEN
Thread 1 opened at log sequence 125
Current log# 2 seq# 125 mem# 0: /u01/app/oracle/oradata/test/redo02.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
[2560] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:5067704 end:5068244 diff:540 (5 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 ZHS16GBK --->数据库字符集
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Feb 09 01:54:49 2015
QMNC started with pid=20, OS id=2562
Mon Feb 09 01:54:57 2015
Completed: ALTER DATABASE OPEN
Mon Feb 09 01:54:58 2015
Starting background process CJQ0
Mon Feb 09 01:54:58 2015
CJQ0 started with pid=22, OS id=2574
Mon Feb 09 01:59:50 2015
Starting background process SMCO
Mon Feb 09 01:59:50 2015
SMCO started with pid=21, OS id=2620
本文永久更新链接地址：
热AI工具
Undresser.AI Undress
人工智能驱动的应用程序，用于创建逼真的裸体照片
AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。
Undress AI Tool
免费脱衣服图片
Clothoff.io
AI脱衣机
Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸！
热门文章
热工具
记事本++7.3.1
好用且免费的代码编辑器
SublimeText3汉化版
中文版，非常好用
禅工作室 13.0.1
功能强大的PHP集成开发环境
Dreamweaver CS6
视觉化网页开发工具
SublimeText3 Mac版
神级代码编辑软件(SublimeText3)
与MySQL中使用索引相比，全表扫描何时可以更快？
Apr 09, 2025 am 12:05 AM
全表扫描在MySQL中可能比使用索引更快，具体情况包括：1)数据量较小时；2)查询返回大量数据时；3)索引列不具备高选择性时；4)复杂查询时。通过分析查询计划、优化索引、避免过度索引和定期维护表，可以在实际应用中做出最优选择。
可以在 Windows 7 上安装 mysql 吗
Apr 08, 2025 pm 03:21 PM
是的，可以在 Windows 7 上安装 MySQL，虽然微软已停止支持 Windows 7，但 MySQL 仍兼容它。不过，安装过程中需要注意以下几点：下载适用于 Windows 的 MySQL 安装程序。选择合适的 MySQL 版本（社区版或企业版）。安装过程中选择适当的安装目录和字符集。设置 root 用户密码，并妥善保管。连接数据库进行测试。注意 Windows 7 上的兼容性问题和安全性问题，建议升级到受支持的操作系统。
mysql 和 mariadb 可以共存吗
Apr 08, 2025 pm 02:27 PM
MySQL 和 MariaDB 可以共存，但需要谨慎配置。关键在于为每个数据库分配不同的端口号和数据目录，并调整内存分配和缓存大小等参数。连接池、应用程序配置和版本差异也需要考虑，需要仔细测试和规划以避免陷阱。在资源有限的情况下，同时运行两个数据库可能会导致性能问题。
mysql：简单的概念，用于轻松学习
Apr 10, 2025 am 09:29 AM
MySQL是一个开源的关系型数据库管理系统。1）创建数据库和表：使用CREATEDATABASE和CREATETABLE命令。2）基本操作：INSERT、UPDATE、DELETE和SELECT。3）高级操作：JOIN、子查询和事务处理。4）调试技巧：检查语法、数据类型和权限。5）优化建议：使用索引、避免SELECT*和使用事务。
RDS MySQL 与 Redshift 零 ETL 集成
Apr 08, 2025 pm 07:06 PM
数据集成简化：AmazonRDSMySQL与Redshift的零ETL集成高效的数据集成是数据驱动型组织的核心。传统的ETL（提取、转换、加载）流程复杂且耗时，尤其是在将数据库（例如AmazonRDSMySQL）与数据仓库（例如Redshift）集成时。然而，AWS提供的零ETL集成方案彻底改变了这一现状，为从RDSMySQL到Redshift的数据迁移提供了简化、近乎实时的解决方案。本文将深入探讨RDSMySQL零ETL与Redshift集成，阐述其工作原理以及为数据工程师和开发者带来的优势。
Bangla 部分模型检索中的 Laravel Eloquent ORM）
Apr 08, 2025 pm 02:06 PM
LaravelEloquent模型检索：轻松获取数据库数据EloquentORM提供了简洁易懂的方式来操作数据库。本文将详细介绍各种Eloquent模型检索技巧，助您高效地从数据库中获取数据。1.获取所有记录使用all()方法可以获取数据库表中的所有记录：useApp\Models\Post;$posts=Post::all();这将返回一个集合(Collection)。您可以使用foreach循环或其他集合方法访问数据：foreach($postsas$post){echo$post->
mysql用户和数据库的关系
Apr 08, 2025 pm 07:15 PM
MySQL 数据库中，用户和数据库的关系通过权限和表定义。用户拥有用户名和密码，用于访问数据库。权限通过 GRANT 命令授予，而表由 CREATE TABLE 命令创建。要建立用户和数据库之间的关系，需创建数据库、创建用户，然后授予权限。
MySQL：初学者的数据管理易用性
Apr 09, 2025 am 12:07 AM
MySQL适合初学者使用，因为它安装简单、功能强大且易于管理数据。1.安装和配置简单，适用于多种操作系统。2.支持基本操作如创建数据库和表、插入、查询、更新和删除数据。3.提供高级功能如JOIN操作和子查询。4.可以通过索引、查询优化和分表分区来提升性能。5.支持备份、恢复和安全措施，确保数据的安全和一致性。
