ERP俱乐部
ERP爱好者、ERP从业者互相交流、互相学习的乐园;我们的愿景是成为全球一流的中文ERP(Enterprise Resource Planning)交流平台
网站首页 论坛首页 搜索 用户列表 FAQ 注册 登录  
ERP俱乐部 -> Oracle Applications专栏 -> Oracle E-Business Suite -> Oracle启动和关闭数据库的几种方法
  Oracle启动和关闭数据库的几种方法
帖子发起人: weilm   发起时间: 2012-05-09 12:51 下午   回复数: 0
? 上一主题 下一主题 ?
楼主
  2012-05-09, 12:51 下午
weilm 离线,最后访问时间: 2012/12/31 15:25:15 weilm

发帖数前150位
男

80级
等级: 80级
注册: 2012年4月17日
区域: 广东深圳
经验: 1,183
积分: 1,163
精华: 0
发贴: 158
排名: 28
Site Registered Users
Oracle启动和关闭数据库的几种方法
 
Oracle启动数据库:
1、startup nomount
打开Oracle实例:读取初始化参数文件、初始化系统全局区、启动后台进程。
SQL> startup nomount
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 79694068 bytes
Database Buffers 83886080 bytes
Redo Buffers 2973696 bytes
这时查看下alter_orcl.log文件看看具体操作:
[oracle@RAC1 bdump]$ cat alert_orcl.log
Tue Mar 20 13:14:05 2012
Starting ORACLE instance (normal)
Cannot determine all dependent dynamic libraries for /proc/self/exe
Unable to find dynamic library libocr10.so in search paths
RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
LD_LIBRARY_PATH is not set!
The default library directories are /lib and /usr/lib
Unable to find dynamic library libocrb10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as /home/oracle/product/10.2.0/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =48
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.1.0.
System parameters with non-default values:
processes = 400
event = 10046 trace name context forever,level 12
__shared_pool_size = 71303168
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
sga_target = 167772160
control_files = /home/oracle/oradata/orcl/control01.ctl, /home/oracle/oradata/orcl/control02.ctl,
/home/oracle/oradata/orcl/control03.ctl
db_block_size = 8192
__db_cache_size = 83886080
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
job_queue_processes = 10
background_dump_dest = /home/oracle/admin/orcl/bdump
user_dump_dest = /home/oracle/admin/orcl/udump
core_dump_dest = /home/oracle/admin/orcl/cdump
audit_file_dest = /home/oracle/admin/orcl/adump
db_name = orcl
db_unique_name = orcl
open_cursors = 300
pga_aggregate_target = 16777216
PMON started with pid=2, OS id=4563
PSP0 started with pid=3, OS id=4565
MMAN started with pid=4, OS id=4567
DBW0 started with pid=5, OS id=4569
LGWR started with pid=6, OS id=4571
CKPT started with pid=7, OS id=4573
SMON started with pid=8, OS id=4575
RECO started with pid=9, OS id=4577
MMNL started with pid=12, OS id=4583
CJQ0 started with pid=10, OS id=4579
MMON started with pid=11, OS id=4581
从alter文件可以看出,oracle读取初始化参数文件然后启动了几个后台进程。
2、startup mount打开实例并装载数据库,但是没有打开数据库:Oracle根据定位控制文件中记录的数据文件和重做日志文件信息,大不打开
这些文件。和startup nomount相比,该方式在打开实例的基础上装载数据库。
SQL> startup mount
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 79694068 bytes
Database Buffers 83886080 bytes
Redo Buffers 2973696 bytes
Database mounted.
alter文件比startup nomount多了一段:
Tue Mar 20 13:17:57 2012
ALTER DATABASE MOUNT
MMON started with pid=11, OS id=4607
CJQ0 started with pid=10, OS id=4605
Tue Mar 20 13:18:01 2012
Setting recovery target incarnation to 2
Tue Mar 20 13:18:01 2012
Successful mount of redo thread 1, with mount id 1306153221
Tue Mar 20 13:18:01 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
3、startup open 或 startup打开实例、装载数据库、打开数据库:Oracle打开控制文件中记录的数据文件和控制文件,使他们在线。同时还会请求一个活
多个回滚段。此时数据库处于正常工作状态,用户可以正常访问数据库了。
SQL> startup open
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 79694068 bytes
Database Buffers 83886080 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
此时alter文件比startup mount多了下面一段:
Tue Mar 20 13:20:16 2012
ALTER DATABASE OPEN
Tue Mar 20 13:20:16 2012
Beginning crash recovery of 1 threads
Tue Mar 20 13:20:16 2012
Started redo scan
Tue Mar 20 13:20:17 2012
Completed redo scan
46 redo blocks read, 5 data blocks need recovery
Tue Mar 20 13:20:17 2012
Started redo application at
Thread 1: logseq 6, block 28034
Tue Mar 20 13:20:17 2012
Recovery of Online Redo Log: Thread 1 Group 3 Seq 6 Reading mem 0
Mem# 0 errs 0: /home/oracle/oradata/orcl/redo03.log
Tue Mar 20 13:20:17 2012
Completed redo application
Tue Mar 20 13:20:17 2012
Completed crash recovery at
Thread 1: logseq 6, block 28080, scn 1335365
5 data blocks read, 5 data blocks written, 46 redo blocks read
Tue Mar 20 13:20:17 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=4640
Tue Mar 20 13:20:17 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=15, OS id=4642
Tue Mar 20 13:20:17 2012
Thread 1 advanced to log sequence 7
Tue Mar 20 13:20:17 2012
ARC0: STARTING ARCH PROCESSES
Tue Mar 20 13:20:17 2012
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Tue Mar 20 13:20:17 2012
Thread 1 opened at log sequence 7
Current log# 2 seq# 7 mem# 0: /home/oracle/oradata/orcl/redo02.log
Successful open of redo thread 1
Tue Mar 20 13:20:17 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Mar 20 13:20:17 2012
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
Tue Mar 20 13:20:17 2012
SMON: enabling cache recovery
ARC2 started with pid=16, OS id=4644
Tue Mar 20 13:20:20 2012
Successfully onlined Undo Tablespace 1.
Tue Mar 20 13:20:20 2012
SMON: enabling tx recovery
Tue Mar 20 13:20:20 2012
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=4646
Tue Mar 20 13:20:27 2012
Completed: ALTER DATABASE OPEN
注意:
如果先startup nomount打开了实例,你想打开数据库怎么办?可以直接alter database open吗?看看吧:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 79694068 bytes
Database Buffers 83886080 bytes
Redo Buffers 2973696 bytes
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01507: database not mounted
SQL> alter database mount;
Database altered.
SQL> alter database open;
Database altered.
也就是说如果先startup nomount打开了实例,如果想打开数据库,必须经过以下两步:
alter database mount;
alter database open;
4、startup restrict数据库允许被打开,但是仅允许一些特权用户(具有dba角色)才可以使用。这种方式常用来对数据库进行维护,如数据导入/
导出操作时不希望有其他用户连接到数据库操作数据。
5、startup force该命令其实是强行关闭数据库(shutdown abort)和启动数据库(startup)的一个组合。该命令仅在关闭数据库遇到问题不能关闭数据库
时用。
6、alter database open read only在打开实例,装载数据库后可以用这种方式打开数据库。
Oracle关闭数据库:
1、shutdown normal
shutdown关闭数据库缺省选项。发出该命令后,任何新连接都不允许连接到数据库。在数据库关闭之前,Oracle将等待目前连
接所有用户都从数据库中退出后才开始关闭数据库。采用这种方式关闭数据库,下次启动不需要任何实例恢复。但需注意,采
用这种方式,也许关闭一个数据库需要很长时间。
2、shutdown immediate
快速、干净关闭数据库。当前正在被执行sql语句立即中断,系统中任何没有提交事务全部回滚。系统不等待连接到数据库的用户
断开连接,强行回滚当前所有活动事务,然后断开所有连接用户。
3、shutdown transaction
8i后才可用。该命令用来计划关闭数据库,它使当前连接到系统且正在活动事务执行完毕,运行该命令后,任何新连接和事务都是
不允许的。在所有活动事务完成后,数据库将和shutdown immediate同样方式关闭数据库。
4、shutdown abort
直接关闭数据库,正在访问数据库的会话会被突然终止。这是关闭数据库的最后一招,一般不要用。不允许新的连接、不等待会话
结束、不等待事务结束、不做检查点且没有关闭数据文件。启动时自动进行实例恢复。可能需要较长时间。

世界上最远的距离是知与行的距离
分享按钮 IP 地址: 已登录   来自: 已登录    返回顶部
 第 1 页 总共 1 页 [共有 1 条记录]
ERP俱乐部 -> Oracle Applications专栏 -> Oracle E-Business Suite -> Oracle启动和关闭数据库的几种方法
(C)Copyright 2005-2020 www.erpclub.org All Rights Reserved.
Tel:+86-755-26444630
Email:webmaster@yok.com.cn