一次vm虚拟机时间倒流而导致的oracle数据库启动故障
一次vm 虚拟机时间倒流而导致的oracle 数据库启动故障 本文是原创文章，若转载请注明出处： http://blog.csdn.net/msdnchina/article/details/38782163 直接上数据库的alert日志： Fri Apr 25 22:00:54 2014 -----注意该时间Archived Log entry 1766 added f
一次vm 虚拟机时间倒流而导致的oracle 数据库启动故障
本文是原创文章，若转载请注明出处：
http://blog.csdn.net/msdnchina/article/details/38782163
直接上数据库的alert日志：
Fri Apr 25 22:00:54 2014 <-----注意该时间
Archived Log entry 1766 added for thread 1 sequence 1770 ID 0x4e0785c3 dest 1:
Sun Sep 02 23:04:52 2012 <-----注意该时间
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = 32 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 4226 MB. For optimal performance,
prior to the next instance restart:
1. Increase the number of unused large pages by
at least 2113 (page size 2048 KB, total size 4226 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 4234 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 USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =51
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 = /opt/oracle/product/11g/dbname_1
System name: Linux
Node name: oracle
Release: 2.6.18-371.el5
Version: #1 SMP Thu Sep 5 21:21:44 EDT 2013
Machine: x86_64
VM name: VMWare Version: 6
Using parameter settings in server-side spfile /opt/oracle/product/11g/dbname_1/dbs/spfileorcl.ora
System parameters with non-default values:
processes = 300
sessions = 472
nls_language = "SIMPLIFIED CHINESE"
nls_territory = "CHINA"
sga_target = 4224M
control_files = "/oracledata/orcl/control01.ctl"
control_files = "/opt/oracle/fast_recovery_area/orcl/control02.ctl"
control_files = "/oracledata/orcl/control03.ctl"
control_files = "/oracledata/orcl/control04.ctl"
control_files = "/oracledata/orcl/control05.ctl"
db_block_size = 8192
compatible = "11.2.0.4.0"
log_archive_format = "%t_%s_%r.dbf"
db_files = 2000
db_recovery_file_dest = "/opt/oracle/fast_recovery_area"
db_recovery_file_dest_size= 40G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
audit_file_dest = "/opt/oracle/admin/orcl/adump"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 300
pga_aggregate_target = 1403M
deferred_segment_creation= FALSE
diagnostic_dest = "/opt/oracle"
Sun Sep 02 23:04:53 2012
PMON started with pid=2, OS id=4452
Sun Sep 02 23:04:53 2012
PSP0 started with pid=3, OS id=4454
Sun Sep 02 23:04:54 2012
VKTM started with pid=4, OS id=4456 at elevated priority
Sun Sep 02 23:04:54 2012
GEN0 started with pid=5, OS id=4460
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Sun Sep 02 23:04:54 2012
DIAG started with pid=6, OS id=4462
Sun Sep 02 23:04:54 2012
DBRM started with pid=7, OS id=4464
Sun Sep 02 23:04:54 2012
DIA0 started with pid=8, OS id=4466
Sun Sep 02 23:04:54 2012
MMAN started with pid=9, OS id=4468
Sun Sep 02 23:04:54 2012
DBW0 started with pid=10, OS id=4470
Sun Sep 02 23:04:54 2012
LGWR started with pid=11, OS id=4472
Sun Sep 02 23:04:54 2012
CKPT started with pid=12, OS id=4474
Sun Sep 02 23:04:54 2012
SMON started with pid=13, OS id=4476
Sun Sep 02 23:04:54 2012
RECO started with pid=14, OS id=4478
Sun Sep 02 23:04:55 2012
MMON started with pid=15, OS id=4480
Sun Sep 02 23:04:55 2012
MMNL started with pid=16, OS id=4482
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /opt/oracle
Sun Sep 02 23:04:55 2012
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 1320728727
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Sun Sep 02 23:04:59 2012
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Started redo scan
Completed redo scan
read 69 KB redo, 66 data blocks need recovery
Started redo application at
Thread 1: logseq 1771, block 16853
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1771 Reading mem 0
Mem# 0: /oracledata/orcl/redo01.log
Completed redo application of 0.04MB
Completed crash recovery at
Thread 1: logseq 1771, block 16992, scn 13030631482598
66 data blocks read, 66 data blocks written, 69 redo k-bytes read
************************************************************
Warning: The SCN headroom for this database is only -652 hours!
************************************************************
Errors in file /opt/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_4492.trc (incident=43353):
ORA-00600: internal error code, arguments: [kcm_headroom_warn_1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /opt/oracle/diag/rdbms/orcl/orcl/incident/incdir_43353/orcl_ora_4492_i43353.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /opt/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_4492.trc:
ORA-00600: internal error code, arguments: [kcm_headroom_warn_1], [], [], [], [], [], [], [], [], [], [], []
ORA-600 signalled during: ALTER DATABASE OPEN...
Dumping diagnostic data in directory=[cdmp_20120902230501], requested by (instance=1, osid=4492), summary=[incident=43353].
Sun Sep 02 23:05:58 2012
Sweep [inc][43353]: completed
Sweep [inc2][43353]: completed
Sun Sep 02 23:19:58 2012
db_recovery_file_dest_size of 40960 MB is 29.05% 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 Sep 02 23:38:25 2012
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
AI Hentai Generator
Generate AI Hentai for free.
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
How long will Oracle database logs be kept?
May 10, 2024 am 03:27 AM
The retention period of Oracle database logs depends on the log type and configuration, including: Redo logs: determined by the maximum size configured with the "LOG_ARCHIVE_DEST" parameter. Archived redo logs: Determined by the maximum size configured by the "DB_RECOVERY_FILE_DEST_SIZE" parameter. Online redo logs: not archived, lost when the database is restarted, and the retention period is consistent with the instance running time. Audit log: Configured by the "AUDIT_TRAIL" parameter, retained for 30 days by default.
Oracle database server hardware configuration requirements
May 10, 2024 am 04:00 AM
Oracle database server hardware configuration requirements: Processor: multi-core, with a main frequency of at least 2.5 GHz. For large databases, 32 cores or more are recommended. Memory: At least 8GB for small databases, 16-64GB for medium sizes, up to 512GB or more for large databases or heavy workloads. Storage: SSD or NVMe disks, RAID arrays for redundancy and performance. Network: High-speed network (10GbE or higher), dedicated network card, low-latency network. Others: Stable power supply, redundant components, compatible operating system and software, heat dissipation and cooling system.
How much memory does oracle require?
May 10, 2024 am 04:12 AM
The amount of memory required by Oracle depends on database size, activity level, and required performance level: for storing data buffers, index buffers, executing SQL statements, and managing the data dictionary cache. The exact amount is affected by database size, activity level, and required performance level. Best practices include setting the appropriate SGA size, sizing SGA components, using AMM, and monitoring memory usage.
Oracle scheduled tasks execute the creation step once a day
May 10, 2024 am 03:03 AM
To create a scheduled task in Oracle that executes once a day, you need to perform the following three steps: Create a job. Add a subjob to the job and set its schedule expression to "INTERVAL 1 DAY". Enable the job.
How much memory is needed to use oracle database
May 10, 2024 am 03:42 AM
The amount of memory required for an Oracle database depends on the database size, workload type, and number of concurrent users. General recommendations: Small databases: 16-32 GB, Medium databases: 32-64 GB, Large databases: 64 GB or more. Other factors to consider include database version, memory optimization options, virtualization, and best practices (monitor memory usage, adjust allocations).
How much memory does an oracle database require?
May 10, 2024 am 02:09 AM
Oracle Database memory requirements depend on the following factors: database size, number of active users, concurrent queries, enabled features, and system hardware configuration. Steps in determining memory requirements include determining database size, estimating the number of active users, understanding concurrent queries, considering enabled features, and examining system hardware configuration.
Detailed tutorial on establishing a database connection using MySQLi in PHP
Jun 04, 2024 pm 01:42 PM
How to use MySQLi to establish a database connection in PHP: Include MySQLi extension (require_once) Create connection function (functionconnect_to_db) Call connection function ($conn=connect_to_db()) Execute query ($result=$conn->query()) Close connection ( $conn->close())
How to start the listening program in oracle
May 10, 2024 am 03:12 AM
Oracle listeners are used to manage client connection requests. Startup steps include: Log in to the Oracle instance. Find the listener configuration. Use the lsnrctl start command to start the listener. Use the lsnrctl status command to verify startup.
