資料庫第一次resetlogs是發生在db建立時3
第三次啟動,再次建立控制檔案(不知道為什麼?),並以RESETLOG方式開啟資料庫。
Thu Feb 16 11:49:02 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
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.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in client-side pfile /home/oracle/cfgtoollogs/dbca/cow977/initcow977Temp.ora on machine rhel5
System parameters with non-default values:
processes = 150
memory_target = 1568M
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_dest_1 = "LOCATION=/home/oracle/archive/cow977"
log_archive_format = "%t_%s_%r.dbf"
db_create_file_dest = "/home/oracle/oradata"
db_recovery_file_dest = "/home/oracle/flash_recovery_area"
db_recovery_file_dest_size= 3882M
_no_recovery_through_resetlogs= TRUE
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(protocol=TCP)"
shared_servers = 2
max_shared_servers = 5
max_dispatchers = 5
audit_file_dest = "/home/oracle/admin/cow977/adump"
audit_trail = "DB"
db_name = "cow977"
open_cursors = 300
diagnostic_dest = "/home/oracle"
Thu Feb 16 11:49:03 2012
PMON started with pid=2, OS id=6577
Thu Feb 16 11:49:03 2012
VKTM started with pid=3, OS id=6579 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Thu Feb 16 11:49:03 2012
GEN0 started with pid=4, OS id=6583
Thu Feb 16 11:49:03 2012
DIAG started with pid=5, OS id=6585
Thu Feb 16 11:49:03 2012
DBRM started with pid=6, OS id=6587
Thu Feb 16 11:49:03 2012
PSP0 started with pid=7, OS id=6589
Thu Feb 16 11:49:03 2012
DIA0 started with pid=8, OS id=6591
Thu Feb 16 11:49:03 2012
MMAN started with pid=9, OS id=6593
Thu Feb 16 11:49:03 2012
DBW0 started with pid=10, OS id=6595
Thu Feb 16 11:49:03 2012
LGWR started with pid=11, OS id=6597
Thu Feb 16 11:49:03 2012
CKPT started with pid=12, OS id=6599
Thu Feb 16 11:49:03 2012
SMON started with pid=13, OS id=6601
Thu Feb 16 11:49:03 2012
RECO started with pid=14, OS id=6603
Thu Feb 16 11:49:03 2012
MMON started with pid=15, OS id=6605
Thu Feb 16 11:49:03 2012
MMNL started with pid=16, OS id=6607
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 2 shared server(s) ...
ORACLE_BASE from environment = /home/oracle
Thu Feb 16 11:49:04 2012
Create controlfile reuse set database "cow977"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/home/oracle/oradata/COW977/datafile/o1_mf_system_7mrz24r2_.dbf',
'/home/oracle/oradata/COW977/datafile/o1_mf_sysaux_7mrz24vh_.dbf',
'/home/oracle/oradata/COW977/datafile/o1_mf_undotbs1_7mrz24yt_.dbf',
'/home/oracle/oradata/COW977/datafile/o1_mf_users_7mrz254l_.dbf'
LOGFILE GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K,
GROUP 3 SIZE 51200K RESETLOGS
WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
Default Temporary Tablespace will be necessary for a locally managed database in future release
Successful mount of redo thread 1, with mount id 4060257136
Completed: Create controlfile reuse set database "cow977"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'/home/oracle/oradata/COW977/datafile/o1_mf_system_7mrz24r2_.dbf',
'/home/oracle/oradata/COW977/datafile/o1_mf_sysaux_7mrz24vh_.dbf',
'/home/oracle/oradata/COW977/datafile/o1_mf_undotbs1_7mrz24yt_.dbf',
'/home/oracle/oradata/COW977/datafile/o1_mf_users_7mrz254l_.dbf'
LOGFILE GROUP 1 SIZE 51200K,
GROUP 2 SIZE 51200K,
GROUP 3 SIZE 51200K RESETLOGS
Stopping background process MMNL
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
Thu Feb 16 11:49:08 2012
MMON started with pid=15, OS id=6652
ALTER SYSTEM enable restricted session;
Thu Feb 16 11:49:09 2012
MMNL started with pid=16, OS id=6654
alter database "cow977" open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 945183
Errors in file /home/oracle/diag/rdbms/cow977/cow977/trace/cow977_ora_6616.trc:
ORA-00313: open failed for members of log group 1 of thread 1
Errors in file /home/oracle/diag/rdbms/cow977/cow977/trace/cow977_ora_6616.trc:
ORA-00313: open failed for members of log group 1 of thread 1
Thu Feb 16 11:49:14 2012
Errors in file /home/oracle/diag/rdbms/cow977/cow977/trace/cow977_ora_6616.trc:
ORA-00313: open failed for members of log group 2 of thread 1
Errors in file /home/oracle/diag/rdbms/cow977/cow977/trace/cow977_ora_6616.trc:
ORA-00313: open failed for members of log group 2 of thread 1
Thu Feb 16 11:49:19 2012
Checker run found 5 new persistent data failures
Errors in file /home/oracle/diag/rdbms/cow977/cow977/trace/cow977_ora_6616.trc:
ORA-00313: open failed for members of log group 3 of thread 1
Errors in file /home/oracle/diag/rdbms/cow977/cow977/trace/cow977_ora_6616.trc:
ORA-00313: open failed for members of log group 3 of thread 1
Thu Feb 16 11:49:25 2012
Setting recovery target incarnation to 2
Thu Feb 16 11:49:26 2012
Assigning activation ID 4060257136 (0xf2029b70)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /home/oracle/oradata/COW977/onlinelog/o1_mf_1_7mrz5o4g_.log
Current log# 1 seq# 1 mem# 1: /home/oracle/flash_recovery_area/COW977/onlinelog/o1_mf_1_7mrz5qs2_.log
Successful open of redo thread 1
Thu Feb 16 11:49:26 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Feb 16 11:49:26 2012
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Dictionary check beginning
Tablespace 'TEMP' #3 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE
Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
*********************************************************************
Database Characterset is US7ASCII
No Resource Manager plan active
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
then disabled.
**********************************************************
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/81227/viewspace-718330/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 資料庫第一次resetlogs是發生在db建立時資料庫
- 資料庫第一次resetlogs是發生在db建立時2資料庫
- 資料庫第一次resetlogs是發生在db建立時1資料庫
- db2 建立資料庫與資料放置DB2資料庫
- DB2建立資料庫,建立表空間DB2資料庫
- 資料庫resetlogs後進行rman恢復3資料庫
- DB2建立聯邦資料庫DB2資料庫
- [DB2]資料庫建立實驗DB2資料庫
- 分析發生在過去的資料庫效能問題資料庫
- 資料庫 建立 3表資料庫
- 關於開啟資料庫時的resetlogs選項資料庫
- 建立資料庫時使用schema資料庫
- Oracle資料庫恢復之resetlogsOracle資料庫
- ORACLE建立資料庫時無法建立目錄Oracle資料庫
- 10G建立資料庫時發生的錯誤資料庫
- 10可以穿越resetlogs恢復資料庫!資料庫
- DB資料庫面試資料庫面試
- SQLServer資料庫中建立臨時表SQLServer資料庫
- db2 資料庫DB2資料庫
- 使用RESETLOGS重建控制檔案恢復資料庫資料庫
- 資料庫resetlogs後進行rman恢復7資料庫
- 資料庫resetlogs後進行rman恢復6資料庫
- 資料庫resetlogs後進行rman恢復5資料庫
- 資料庫resetlogs後進行rman恢復4資料庫
- 資料庫resetlogs後進行rman恢復2資料庫
- 資料庫resetlogs後進行rman恢復1資料庫
- 建立資料庫資料庫
- ORACLE資料庫修改資料庫名db_nameOracle資料庫
- 手工建立資料庫及刪除資料庫示例--附建庫時alert日誌資料庫
- DB2_資料庫角色DB2資料庫
- mysql 建立 資料庫時指定編碼很重要MySql資料庫
- MySQL 建立資料庫 建立表MySql資料庫
- DB-Engines:2018年3月資料庫排名資料庫
- 使用RESETLOGS重建控制檔案恢復資料庫(二)資料庫
- 使用_allow_resetlogs_corruption強制開啟資料庫資料庫
- 第一次手工建資料庫資料庫
- 建立資料庫表資料庫
- Mysql建立資料庫MySql資料庫