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
本文永久更新链接地址：
Alat AI Hot
Undresser.AI Undress
Apl berkuasa AI untuk mencipta foto bogel yang realistik
AI Clothes Remover
Alat AI dalam talian untuk mengeluarkan pakaian daripada foto.
Undress AI Tool
Gambar buka pakaian secara percuma
Clothoff.io
Penyingkiran pakaian AI
Video Face Swap
Tukar muka dalam mana-mana video dengan mudah menggunakan alat tukar muka AI percuma kami!
Artikel Panas
Alat panas
Notepad++7.3.1
Editor kod yang mudah digunakan dan percuma
SublimeText3 versi Cina
Versi Cina, sangat mudah digunakan
Hantar Studio 13.0.1
Persekitaran pembangunan bersepadu PHP yang berkuasa
Dreamweaver CS6
Alat pembangunan web visual
SublimeText3 versi Mac
Perisian penyuntingan kod peringkat Tuhan (SublimeText3)
Topik panas
1664
14
1422
52
1316
25
1267
29
1239
24
Bilakah imbasan jadual penuh lebih cepat daripada menggunakan indeks di MySQL?
Apr 09, 2025 am 12:05 AM
Pengimbasan jadual penuh mungkin lebih cepat dalam MySQL daripada menggunakan indeks. Kes -kes tertentu termasuk: 1) jumlah data adalah kecil; 2) apabila pertanyaan mengembalikan sejumlah besar data; 3) Apabila lajur indeks tidak selektif; 4) Apabila pertanyaan kompleks. Dengan menganalisis rancangan pertanyaan, mengoptimumkan indeks, mengelakkan lebih banyak indeks dan tetap mengekalkan jadual, anda boleh membuat pilihan terbaik dalam aplikasi praktikal.
Mysql: Konsep mudah untuk pembelajaran mudah
Apr 10, 2025 am 09:29 AM
MySQL adalah sistem pengurusan pangkalan data sumber terbuka. 1) Buat Pangkalan Data dan Jadual: Gunakan perintah Createdatabase dan Createtable. 2) Operasi Asas: Masukkan, Kemas kini, Padam dan Pilih. 3) Operasi lanjutan: Sertai, subquery dan pemprosesan transaksi. 4) Kemahiran Debugging: Semak sintaks, jenis data dan keizinan. 5) Cadangan Pengoptimuman: Gunakan indeks, elakkan pilih* dan gunakan transaksi.
MySQL: Kemudahan Pengurusan Data untuk Pemula
Apr 09, 2025 am 12:07 AM
MySQL sesuai untuk pemula kerana mudah dipasang, kuat dan mudah untuk menguruskan data. 1. Pemasangan dan konfigurasi mudah, sesuai untuk pelbagai sistem operasi. 2. Menyokong operasi asas seperti membuat pangkalan data dan jadual, memasukkan, menanyakan, mengemas kini dan memadam data. 3. Menyediakan fungsi lanjutan seperti menyertai operasi dan subqueries. 4. Prestasi boleh ditingkatkan melalui pengindeksan, pengoptimuman pertanyaan dan pembahagian jadual. 5. Sokongan sokongan, pemulihan dan langkah keselamatan untuk memastikan keselamatan data dan konsistensi.
Peranan MySQL: Pangkalan Data dalam Aplikasi Web
Apr 17, 2025 am 12:23 AM
Peranan utama MySQL dalam aplikasi web adalah untuk menyimpan dan mengurus data. 1.MYSQL dengan cekap memproses maklumat pengguna, katalog produk, rekod urus niaga dan data lain. 2. Melalui pertanyaan SQL, pemaju boleh mengekstrak maklumat dari pangkalan data untuk menghasilkan kandungan dinamik. 3.MYSQL berfungsi berdasarkan model klien-pelayan untuk memastikan kelajuan pertanyaan yang boleh diterima.
MySQL: Pengenalan kepada pangkalan data paling popular di dunia
Apr 12, 2025 am 12:18 AM
MySQL adalah sistem pengurusan pangkalan data relasi sumber terbuka, terutamanya digunakan untuk menyimpan dan mengambil data dengan cepat dan boleh dipercayai. Prinsip kerjanya termasuk permintaan pelanggan, resolusi pertanyaan, pelaksanaan pertanyaan dan hasil pulangan. Contoh penggunaan termasuk membuat jadual, memasukkan dan menanyakan data, dan ciri -ciri canggih seperti Operasi Join. Kesalahan umum melibatkan sintaks SQL, jenis data, dan keizinan, dan cadangan pengoptimuman termasuk penggunaan indeks, pertanyaan yang dioptimumkan, dan pembahagian jadual.
Terangkan peranan log redo innoDB dan membatalkan log.
Apr 15, 2025 am 12:16 AM
InnoDB menggunakan redolog dan undologs untuk memastikan konsistensi dan kebolehpercayaan data. 1. Pengubahsuaian halaman data rekod untuk memastikan pemulihan kemalangan dan kegigihan transaksi. 2.UNDOLOGS merekodkan nilai data asal dan menyokong penggantian transaksi dan MVCC.
Tempat Mysql: Pangkalan Data dan Pengaturcaraan
Apr 13, 2025 am 12:18 AM
Kedudukan MySQL dalam pangkalan data dan pengaturcaraan sangat penting. Ia adalah sistem pengurusan pangkalan data sumber terbuka yang digunakan secara meluas dalam pelbagai senario aplikasi. 1) MySQL menyediakan fungsi penyimpanan data, organisasi dan pengambilan data yang cekap, sistem sokongan web, mudah alih dan perusahaan. 2) Ia menggunakan seni bina pelanggan-pelayan, menyokong pelbagai enjin penyimpanan dan pengoptimuman indeks. 3) Penggunaan asas termasuk membuat jadual dan memasukkan data, dan penggunaan lanjutan melibatkan pelbagai meja dan pertanyaan kompleks. 4) Soalan -soalan yang sering ditanya seperti kesilapan sintaks SQL dan isu -isu prestasi boleh disahpepijat melalui arahan jelas dan log pertanyaan perlahan. 5) Kaedah pengoptimuman prestasi termasuk penggunaan indeks rasional, pertanyaan yang dioptimumkan dan penggunaan cache. Amalan terbaik termasuk menggunakan urus niaga dan preparedStatemen
Mengapa menggunakan mysql? Faedah dan kelebihan
Apr 12, 2025 am 12:17 AM
MySQL dipilih untuk prestasi, kebolehpercayaan, kemudahan penggunaan, dan sokongan komuniti. 1.MYSQL Menyediakan fungsi penyimpanan dan pengambilan data yang cekap, menyokong pelbagai jenis data dan operasi pertanyaan lanjutan. 2. Mengamalkan seni bina pelanggan-pelayan dan enjin penyimpanan berganda untuk menyokong urus niaga dan pengoptimuman pertanyaan. 3. Mudah digunakan, menyokong pelbagai sistem operasi dan bahasa pengaturcaraan. 4. Mempunyai sokongan komuniti yang kuat dan menyediakan sumber dan penyelesaian yang kaya.
