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
本文永久更新链接地址：
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
1663
14
1419
52
1313
25
1264
29
1237
24
When might a full table scan be faster than using an index in MySQL?
Apr 09, 2025 am 12:05 AM
Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.
Can I install mysql on Windows 7
Apr 08, 2025 pm 03:21 PM
Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.
MySQL: Simple Concepts for Easy Learning
Apr 10, 2025 am 09:29 AM
MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.
Can mysql and mariadb coexist
Apr 08, 2025 pm 02:27 PM
MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
Laravel Eloquent ORM in Bangla partial model search)
Apr 08, 2025 pm 02:06 PM
LaravelEloquent Model Retrieval: Easily obtaining database data EloquentORM provides a concise and easy-to-understand way to operate the database. This article will introduce various Eloquent model search techniques in detail to help you obtain data from the database efficiently. 1. Get all records. Use the all() method to get all records in the database table: useApp\Models\Post;$posts=Post::all(); This will return a collection. You can access data using foreach loop or other collection methods: foreach($postsas$post){echo$post->
RDS MySQL integration with Redshift zero ETL
Apr 08, 2025 pm 07:06 PM
Data Integration Simplification: AmazonRDSMySQL and Redshift's zero ETL integration Efficient data integration is at the heart of a data-driven organization. Traditional ETL (extract, convert, load) processes are complex and time-consuming, especially when integrating databases (such as AmazonRDSMySQL) with data warehouses (such as Redshift). However, AWS provides zero ETL integration solutions that have completely changed this situation, providing a simplified, near-real-time solution for data migration from RDSMySQL to Redshift. This article will dive into RDSMySQL zero ETL integration with Redshift, explaining how it works and the advantages it brings to data engineers and developers.
The relationship between mysql user and database
Apr 08, 2025 pm 07:15 PM
In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.
MySQL: The Ease of Data Management for Beginners
Apr 09, 2025 am 12:07 AM
MySQL is suitable for beginners because it is simple to install, powerful and easy to manage data. 1. Simple installation and configuration, suitable for a variety of operating systems. 2. Support basic operations such as creating databases and tables, inserting, querying, updating and deleting data. 3. Provide advanced functions such as JOIN operations and subqueries. 4. Performance can be improved through indexing, query optimization and table partitioning. 5. Support backup, recovery and security measures to ensure data security and consistency.
