--回复完后启动用
startup RESETLOGS;
解决方案 »
- 我真的无路可走了吗?慢!!
- 如何在数据中察看表的内容
- java.sql.SQLException: 类型长度大于最大值
- 需要建表,但是可能已经有了这个表了,该怎么办呢?
- Oracle数据库中多重Gruop By与Order by连接在一起怎么弄 ?怎么写,给个思路或者实例吧!
- oracle中LOB的存储---能否把一个文件拆分为多条记录存储?
- 很难的SQL
- 表空间已经建好了。为什么用户建不成功?
- Oracle8i 下载
- python ,cx_Oracle.DatabaseError ORA-12715问题咨询。
- sql2005通过odbc向oracle中insert数据报下列错误,请高手指教!
- 存储过程创建
三个都恢复失败了,使用startup resetlogs;还有用吗?
数据文件也坏了?检查一下磁盘。
你第一步应该就没有成功
有提示消息,没有启动起来,你应该直接
startup resetlogs;
回车后,根据给出的 suggestion 查找对应的归档日志,如果不在,看是否有备份。
执行startup open resetlogs,报错。结果:
SQL> startup open resetlogs
ORACLE instance started.Total System Global Area 1603411968 bytes
Fixed Size 2213776 bytes
Variable Size 402655344 bytes
Database Buffers 1191182336 bytes
Redo Buffers 7360512 bytes
ORA-01504: database name 'RESETLOGS' does not match parameter db_name 'oral'
查看的记过
SQL> show parameter recoveryNAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string /home/oracle/software/applicat
ion/oracle/flash_recovery_area
db_recovery_file_dest_size big integer 3882M
recovery_parallelism integer 0
SQL>
ORA-00289: suggestion :
/home/oracle/software/application/oracle/flash_recovery_area/oral/archivelog/2012
_11_28/o1_mf_1_70_%u_.arc
=====================================================================================
从这里看,需要 2012-11-28 的 sequence# 为 70 的归档日志,看看在不在,文件名为 O1_mf_1_70_xxx.arc根据 ora-00289 给出的建议(suggestion)查找对应的归档日志
startup 直接就不能管用了 还有就是公司里外网没法上邮箱
startup 直接就不能管用了 还有就是公司里外网没法上邮箱
没有任何信息,我无法帮你
Thread 1 cannot allocate new log, sequence 118
Private strand flush not complete
Current log# 3 seq# 117 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO03.LOG
Thread 1 advanced to log sequence 118 (LGWR switch)
Current log# 1 seq# 118 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO01.LOG
Mon Oct 07 13:32:21 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Release 11.2.0.1.0 - Production.
Using parameter settings in server-side spfile D:\ORACLE\PRODUCT\11.2.0\DBHOME_2\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 150
memory_target = 1232M
control_files = "D:\ORACLE\ORADATA\ORCL\CONTROL01.CTL"
control_files = "D:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
db_recovery_file_dest = "D:\oracle\flash_recovery_area"
db_recovery_file_dest_size= 3852M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
local_listener = "LISTENER_ORCL"
audit_file_dest = "D:\ORACLE\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 300
diagnostic_dest = "D:\ORACLE"
Mon Oct 07 13:32:28 2013
PMON started with pid=2, OS id=2916
Mon Oct 07 13:32:28 2013
VKTM started with pid=3, OS id=2920 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Mon Oct 07 13:32:28 2013
GEN0 started with pid=4, OS id=2924
Mon Oct 07 13:32:28 2013
DIAG started with pid=5, OS id=2928
Mon Oct 07 13:32:28 2013
DBRM started with pid=6, OS id=2932
Mon Oct 07 13:32:28 2013
PSP0 started with pid=7, OS id=2936
Mon Oct 07 13:32:28 2013
DIA0 started with pid=8, OS id=2940
Mon Oct 07 13:32:28 2013
MMAN started with pid=9, OS id=2944
Mon Oct 07 13:32:28 2013
DBW0 started with pid=10, OS id=2948
Mon Oct 07 13:32:28 2013
LGWR started with pid=11, OS id=2952
Mon Oct 07 13:32:28 2013
CKPT started with pid=12, OS id=2956
Mon Oct 07 13:32:28 2013
SMON started with pid=13, OS id=2960
Mon Oct 07 13:32:28 2013
RECO started with pid=14, OS id=2964
Mon Oct 07 13:32:28 2013
MMON started with pid=15, OS id=2968
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Mon Oct 07 13:32:28 2013
MMNL started with pid=16, OS id=2972
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\oracle
Mon Oct 07 13:32:35 2013
alter database mount exclusive
Mon Oct 07 13:32:41 2013
Successful mount of redo thread 1, with mount id 1355968883
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Mon Oct 07 13:32:45 2013
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
read 16959 KB redo, 2091 data blocks need recovery
Started redo application at
Thread 1: logseq 118, block 27332
Recovery of Online Redo Log: Thread 1 Group 1 Seq 118 Reading mem 0
Mem# 0: D:\ORACLE\ORADATA\ORCL\REDO01.LOG
Completed redo application of 12.72MB
Mon Oct 07 13:33:08 2013
Completed crash recovery at
Thread 1: logseq 118, block 61250, scn 4049286
2091 data blocks read, 2091 data blocks written, 16959 redo k-bytes read
Mon Oct 07 13:33:11 2013
Thread 1 advanced to log sequence 119 (thread open)
Thread 1 opened at log sequence 119
Current log# 2 seq# 119 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO02.LOG
Successful open of redo thread 1
Mon Oct 07 13:33:12 2013
SMON: enabling cache recovery
Mon Oct 07 13:33:22 2013
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
Mon Oct 07 13:33:32 2013
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Oct 07 13:33:44 2013
Starting background process QMNC
Mon Oct 07 13:33:44 2013
QMNC started with pid=20, OS id=3824
Mon Oct 07 13:33:59 2013
Completed: alter database open
Mon Oct 07 13:34:19 2013
Starting background process CJQ0
Mon Oct 07 13:34:19 2013
CJQ0 started with pid=28, OS id=4944
Mon Oct 07 13:34:28 2013
db_recovery_file_dest_size of 3852 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.
Mon Oct 07 13:38:45 2013
Starting background process SMCO
Mon Oct 07 13:38:45 2013
SMCO started with pid=39, OS id=5412
Mon Oct 07 15:09:14 2013
(LOCAL=NO) VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0 - Production
Time: 07-10月-2013 15:09:14
Tracing not turned on.
Tns error struct:
ns main err code: 12641
TNS-12641: 验证服务无法初始化
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (2372) as a result of ORA-609
Mon Oct 07 15:09:15 2013
***********************************************************************Fatal NI connect error 12641, connecting to:
(LOCAL=NO) VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0 - Production
Time: 07-10月-2013 15:09:15
Tracing not turned on.
Tns error struct:
ns main err code: 12641
TNS-12641: 验证服务无法初始化
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (3504) as a result of ORA-609
Mon Oct 07 15:09:15 2013
***********************************************************************Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0 - Production
Time: 07-10月-2013 15:09:15
Tracing not turned on.
Tns error struct:
ns main err code: 12638
TNS-12638: 身份证明检索失败
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Mon Oct 07 17:12:04 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Mon Oct 07 17:12:16 2013
Starting up:
Oracle Database 11g Release 11.2.0.1.0 - Production.
Using parameter settings in server-side spfile D:\ORACLE\PRODUCT\11.2.0\DBHOME_2\DATABASE\SPFILEORCL.ORA
System parameters with non-default values:
processes = 150
memory_target = 1232M
control_files = "D:\ORACLE\ORADATA\ORCL\CONTROL01.CTL"
control_files = "D:\ORACLE\FLASH_RECOVERY_AREA\ORCL\CONTROL02.CTL"
db_block_size = 8192
compatible = "11.2.0.0.0"
db_recovery_file_dest = "D:\oracle\flash_recovery_area"
db_recovery_file_dest_size= 3852M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=orclXDB)"
local_listener = "LISTENER_ORCL"
audit_file_dest = "D:\ORACLE\ADMIN\ORCL\ADUMP"
audit_trail = "DB"
db_name = "orcl"
open_cursors = 300
diagnostic_dest = "D:\ORACLE"
Mon Oct 07 17:12:19 2013
PMON started with pid=2, OS id=3476
Mon Oct 07 17:12:19 2013
VKTM started with pid=3, OS id=3480 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Mon Oct 07 17:12:19 2013
GEN0 started with pid=4, OS id=3484
Mon Oct 07 17:12:19 2013
DIAG started with pid=5, OS id=3488
Mon Oct 07 17:12:19 2013
DBRM started with pid=6, OS id=3492
Mon Oct 07 17:12:19 2013
PSP0 started with pid=7, OS id=3496
Mon Oct 07 17:12:19 2013
DIA0 started with pid=8, OS id=3500
Mon Oct 07 17:12:19 2013
MMAN started with pid=9, OS id=3504
Mon Oct 07 17:12:19 2013
DBW0 started with pid=10, OS id=3508
Mon Oct 07 17:12:19 2013
LGWR started with pid=11, OS id=3512
Mon Oct 07 17:12:19 2013
CKPT started with pid=12, OS id=3516
Mon Oct 07 17:12:19 2013
SMON started with pid=13, OS id=3520
Mon Oct 07 17:12:19 2013
RECO started with pid=14, OS id=3524
Mon Oct 07 17:12:19 2013
MMON started with pid=15, OS id=3528
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Mon Oct 07 17:12:19 2013
MMNL started with pid=16, OS id=3532
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\oracle
Mon Oct 07 17:12:22 2013
alter database mount exclusive
Successful mount of redo thread 1, with mount id 1355994103
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
Started redo scan
Mon Oct 07 17:12:33 2013
Completed redo scan
read 1802 KB redo, 363 data blocks need recovery
Started redo application at
Thread 1: logseq 119, block 24202
Recovery of Online Redo Log: Thread 1 Group 2 Seq 119 Reading mem 0
Mem# 0: D:\ORACLE\ORADATA\ORCL\REDO02.LOG
Completed redo application of 0.77MB
Completed crash recovery at
Thread 1: logseq 119, block 27806, scn 4077955
363 data blocks read, 363 data blocks written, 1802 redo k-bytes read
Mon Oct 07 17:12:41 2013
Thread 1 advanced to log sequence 120 (thread open)
Thread 1 opened at log sequence 120
Current log# 3 seq# 120 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO03.LOG
Successful open of redo thread 1
Mon Oct 07 17:12:41 2013
SMON: enabling cache recovery
Mon Oct 07 17:12:48 2013
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Oct 07 17:13:11 2013
Starting background process QMNC
Mon Oct 07 17:13:11 2013
QMNC started with pid=20, OS id=3816
Mon Oct 07 17:13:31 2013
Completed: alter database open
Mon Oct 07 17:13:41 2013
Starting background process CJQ0
Mon Oct 07 17:13:41 2013
CJQ0 started with pid=25, OS id=4600
Mon Oct 07 17:13:50 2013
db_recovery_file_dest_size of 3852 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.
Mon Oct 07 17:18:14 2013
Starting background process SMCO
Mon Oct 07 17:18:14 2013
SMCO started with pid=37, OS id=6880
Mon Oct 07 21:59:27 2013
***********************************************************************