alertSID.log文件

这个文件被删除之后,是没有关系的。
数据库会自动重新建的。
 
Dump file d:\oracle\product\10.2.0\admin\orcl\bdump\alert_orcl.log
Tue Dec 07 20:25:44 2010
ORACLE V10.2.0.3.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 3
CPU                 : 2 - type 586, 2 Physical Cores
Process Affinity    : 0x00000000
Memory (Avail/Total): Ph:1058M/1943M, Ph+PgF:2779M/3840M, VA:1939M/2047M
Tue Dec 07 20:25:44 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
  processes                = 150
  __shared_pool_size       = 478150656
  __large_pool_size        = 4194304
  __java_pool_size         = 4194304
  __streams_pool_size      = 0
  sga_target               = 583008256
  control_files            = D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
  db_block_size            = 8192
  __db_cache_size          = 88080384
  compatible               = 10.2.0.3.0
  db_file_multiblock_read_count= 16
  db_recovery_file_dest    = d:\oracle\product\10.2.0\flash_recovery_area
  db_recovery_file_dest_size= 2147483648
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=orclXDB)
  job_queue_processes      = 10
  audit_file_dest          = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
  background_dump_dest     = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
  user_dump_dest           = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
  core_dump_dest           = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
  db_name                  = orcl
  open_cursors             = 300
  pga_aggregate_target     = 192937984
PSP0 started with pid=3, OS id=4996
MMAN started with pid=4, OS id=2776
DBW0 started with pid=5, OS id=7628
LGWR started with pid=6, OS id=5208
CKPT started with pid=7, OS id=7700
SMON started with pid=8, OS id=6628
RECO started with pid=9, OS id=920
CJQ0 started with pid=10, OS id=4528
MMON started with pid=11, OS id=7176
Tue Dec 07 20:25:47 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Dec 07 20:25:47 2010
starting up 1 shared server(s) ...
PMON started with pid=2, OS id=6744
MMNL started with pid=12, OS id=5612
Tue Dec 07 20:25:48 2010
alter database mount exclusive
Setting recovery target incarnation to 2
Tue Dec 07 20:25:52 2010
Successful mount of redo thread 1, with mount id 1264937548
Tue Dec 07 20:25:52 2010
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Tue Dec 07 20:25:52 2010
alter database open
Tue Dec 07 20:25:53 2010
Beginning crash recovery of 1 threads
 parallel recovery started with 2 processes
Tue Dec 07 20:25:53 2010
Started redo scan
Tue Dec 07 20:25:53 2010
Completed redo scan
 254 redo blocks read, 56 data blocks need recovery
Tue Dec 07 20:25:53 2010
Started redo application at
 Thread 1: logseq 138, block 68928
Tue Dec 07 20:25:54 2010
Recovery of Online Redo Log: Thread 1 Group 2 Seq 138 Reading mem 0
  Mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
Tue Dec 07 20:25:54 2010
Completed redo application
Tue Dec 07 20:25:54 2010
Completed crash recovery at
 Thread 1: logseq 138, block 69182, scn 5309833
 56 data blocks read, 56 data blocks written, 254 redo blocks read
Tue Dec 07 20:25:56 2010
Thread 1 advanced to log sequence 139
Thread 1 opened at log sequence 139
  Current log# 3 seq# 139 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Successful open of redo thread 1
Tue Dec 07 20:25:56 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Dec 07 20:25:56 2010
SMON: enabling cache recovery
Tue Dec 07 20:25:58 2010
Successfully onlined Undo Tablespace 1.
Tue Dec 07 20:25:58 2010
SMON: enabling tx recovery
Tue Dec 07 20:25:58 2010
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=17, OS id=6936
Tue Dec 07 20:26:09 2010
Completed: alter database open
Tue Dec 07 20:26:12 2010
db_recovery_file_dest_size of 2048 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.
Oracle数据库的配置文件主要包括以下几个文件: 1 listener.ora:监听器配置文件,用于指定数据库监听器的详细信息,如监听器的名称、监听地址、端口等。 2. tnsnames.ora:TNS服务名称配置文件,用于定义数据库的连接信息,包括数据库的别名、主机名、端口、服务名等。 3. sqlnet.ora:SQL*Net配置文件,用于定义数据库的网络连接属性,如连接超时时间、验证方式、加密算法等。 4. initSID.ora:数据库实例初始化参数文件,用于设置数据库实例的各种参数值,如内存分配、数据文件位置、日志文件位置等。 5. spfileSID.ora:数据库实例参数文件,是一个二进制文件,记录了数据库实例的当前参数值。该文件会在数据库启动时自动生成,并且可以动态修改。 需要注意的是,以上这些配置文件一般位于Oracle安装目录下的network/admin目录中,具体路径可能会根据操作系统和Oracle版本有所不同。 除了上述配置文件,还有一些其他重要的配置文件如: - alertSID.log:数据库实例的警告和错误日志文件,记录了数据库运行过程中的异常情况。 - sqlnet.log:SQL*Net日志文件,用于记录数据库网络连接相关的日志信息。 - listener.log:监听器日志文件,用于记录监听器运行过程中的事件和错误信息。 这些配置文件对于Oracle数据库的正常运行和连接非常重要,通过修改配置文件可以调整数据库的参数设置、连接属性和监听信息等,以满足不同的需求和环境。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值