Abnormal Instance Shutdown (307)
In unusual circumstances, shutdown of an instance might not occur cleanly; all memory structures might not be removed from memory or one of the background processes might not be terminated. When remnants of a previous instance exist, a subsequent instance startup most likely will fail. In such situations, the database administrator can force the new instance to start up by first removing the remnants of the previous instance and then starting a new instance, or by issuing a SHUTDOWN ABORT statem
Unmount a Database (305)
After the database is closed, Oracle unmounts the database to disassociate it from the instance. At this point, the instance remains in the memory of your computer. After a database is unmounted, Oracle closes the control files of the database. 卸载数据库1. 数据库被关闭后,Oracle 将卸载数据库,使之与实例分离 . 此时,实例依旧存在于计算机的内存中2. 数据库被卸载后,Oracle 将关闭数据库的控制文件[@more@]
Close the Database by Terminating the Instance (304)
In rare emergency situations, you can terminate the instance of an open database to close and completely shut down the database instantaneously. This process is fast, because the operation of writing all data in the buffers of the SGA to the datafiles and redo log files is skipped. The subsequent reopening of the database requires recovery, which Oracle performs automatically. 通过终止实例来关闭数据库1. 在紧急情况下,可以终止一个处于打开状态的数据库的实例,以便立即关闭并完全停止一个数据库2.
Shut Down an Instance (306)
The final step in database shutdown is shutting down the instance. When you shut down an instance, the SGA is removed from memory and the background processes are terminated. 关闭实例停止数据库的最后一个步骤是停止实例 , 关闭实例时,SGA 将被从内存中清除,后台进程将被终止.[@more@]
Close a Database (303)
When you close a database, Oracle writes all database data and recovery data in the SGA to the datafiles and redo log files, respectively. Next, Oracle closes all online datafiles and redo log files. (Any offline datafiles of any offline tablespaces have been closed already. If you subsequently reopen the database, any tablespace that was offline and its datafiles remain offline and closed, respectively.) At this point, the database is closed and inaccessible for normal operations. The control f
Overview of Database and Instance Shutdown (302)
The three steps to shutting down a database and its associated instance are: 1. Close the database. 2. Unmount the database. 3. Shut down the instance. A database administrator can perform these steps using Enterprise Manager. Oracle automatically performs all three steps whenever an instance is shut down. 数据库和实例的关闭1. 关闭数据库和相关实例的三个步骤如下 a. 关闭数据库 b. 卸载数据库 c. 停止实例[@more@]
Open a Database in Read-Only Mode (301)
You can open any database in read-only mode to prevent its data from being modified by user transactions. Read-only mode restricts database access to read-only transactions, which cannot write to the datafiles or to the redo log files. Disk writes to other files, such as control files, operating system audit trails, trace files, and alert logs, can continue in read-only mode. Temporary tablespaces for sort operations are not affected by the database being open in read-only mode. However, you can
Resolution of In-Doubt Distributed Transaction (300)
Occasionally a database closes abnormally with one or more distributed transactions in doubt (neither committed nor rolled back). When you reopen the database and recovery is complete, the RECO background process automatically, immediately, and consistently resolves any in-doubt distributed transactions. 解决拿不准的分布式事务1. 拿不准的分布式事务 : 数据库异常关闭时 , 一个或多个分布式事务既没有提交也没有回滚2. 重新打开数据库并完成恢复工作后 , RECO 后台进程将自动地处理拿不准的分布式事务[@
Undo Space Acquisition and Management (299)
When you open the database, the instance attempts to acquire one or more undo tablespaces. You determine whether to operate in automatic undo management mode or manual undo management mode at instance startup using the UNDO_MANAGEMENT initialization parameter. The supported values are AUTO or MANUAL. If AUTO, then the instance is started in automatic undo management mode. The default value is MANUAL.■ If you use the undo tablespace method, then you are using automatic undo management mode. This
Instance Recovery (298)
If the database was last closed abnormally, either because the database administrator terminated its instance or because of a power failure, then Oracle automatically performs recovery when the database is reopened.实例恢复数据库非正常关闭 , 当数据库重新打开的时候Oracle自动进行恢复[@more@]
What Happens When You Open a Database (297)
Opening a mounted database makes it available for normal database operations. Anyvalid user can connect to an open database and access its information. Usually, adatabase administrator opens the database to make it available for general use.When you open the database, Oracle opens the online datafiles and redo log files. If atablespace was offline when the database was previously shut down, the tablespaceand its corresponding datafiles will still be offline when you reopen the database.If any of
How a Clone Database Is Mounted (296)
A clone database is a specialized copy of a database that can be used for tablespacepoint-in-time recovery. When you perform tablespace point-in-time recovery, youmount the clone database and recover the tablespaces to the desired time, then exportmetadata from the clone to the primary database and copy the datafiles from therecovered tablespaces.克隆数据库如何装载1. 克隆数据库可用于按时间点恢复2. 当用户按时间点恢复表空间时,需要将克隆数据库装载 , 将其中的表空间恢复到期望的时间,然后将克隆
How a Standby Database Is Mounted (295)
A standby database maintains a duplicate copy of your primary database and provides continued availability in the event of a disaster. The standby database is constantly in recovery mode. To maintain your standby database, you must mount it in standby mode using the ALTER DATABASE statement and apply the archived redo logs that your primary database generates. You can open a standby database in read-only mode to use it as a temporary reporting database. You cannot open a standby databa
How a Database Is Mounted with Real Application Clusters (294)
If Oracle allows multiple instances to mount the same database concurrently, then thedatabase administrator can use the CLUSTER_DATABASE initialization parameter tomake the database available to multiple instances. The default value of the CLUSTER_DATABASE parameter is false. Versions of Oracle that do not support RealApplication Clusters only allow CLUSTER_DATABASE to be false.If CLUSTER_DATABASE is false for the first instance that mounts a database, thenonly that instance can mount the datab
What database aspects should be monitored?
摘自orafaqOne should implement a monitoring system to constantly monitor the following aspects of a database. This can be achieved by writing custom scripts, implementing Oracle's Enterprise Manager, or buying a third-party monitoring product. If an alarm is triggered, the system should automatically notify the DBA (e-mail, page, etc.) to take appropriate action.Infrastructure availability:Is the database up and responding to requestsAre the listeners up and responding to requestsAre the Oracle
Why and when should one tune?
摘自orafaqOne of the biggest responsibilities of a DBA is to ensure that the Oracle database is tuned properly. The Oracle RDBMS is highly tunable and allows the database to be monitored and adjusted to increase its performance.One should do performance tuning for the following reasons:The speed of computing might be wasting valuable human time (users waiting for response); Enable your system to keep-up with the speed business is conducted; and Optimize hardware usage to save money (companies ar
How a Database Is Mounted (293)
The instance mounts a database to associate the database with that instance. To mountthe database, the instance finds the database control files and opens them. Control filesare specified in the CONTROL_FILES initialization parameter in the parameter fileused to start the instance. Oracle then reads the control files to get the names of thedatabase’s datafiles and redo log files.At this point, the database is still closed and is accessible only to the databaseadministrator. The database adminis
Forced Startup in Abnormal Situations (292)
In unusual circumstances, a previous instance might not have been shut down cleanly.For example, one of the instance’s processes might not have terminated properly. Insuch situations, the database can return an error during normal instance startup. Toresolve this problem, you must terminate all remnant Oracle processes of the previousinstance before starting the new instance异常情况下强制启动管理员需要在启动实例前手工结束系统中残留的 Oracle 进程才能解决这个问题[@more@]
Restricted Mode of Instance Startup (291)
You can start an instance in restricted mode (or later alter an existing instance to be inrestricted mode). This restricts connections to only those users who have been grantedthe RESTRICTED SESSION system privilege.以限制模式启动实例管理员可以用限制模式启动实例 . 运行在限制模式下的实例只允许具有 RESTRICTED SESSION系统权限的用户连接到数据库[@more@]
How an Instance Is Started (290)
When Oracle starts an instance, it reads the server parameter file (SPFILE) orinitialization parameter file to determine the values of initialization parameters. Then,it allocates an SGA, which is a shared area of memory used for database information,and creates background processes. At this point, no database is associated with thesememory structures and processes.实例是如何启动的当 Oracle 启动实例时,首先需要从服务器参数文件或初始化参数文件中读取初始化参数,之后创建存储数据库信息的共享内存区SG