RMAN恢复案例之--不完全恢复错误案例-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

RMAN恢复案例之--不完全恢复错误案例

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 04:48 PM

oracle

RMAN恢复案例之--不完全恢复错误案例RMAN恢复案例：不完全恢复，由于在先前的数据文件备份有误，导致恢复失败。[oracle@rh6~]$rmantarget/RecoveryManager:Relea

RMAN恢复案例之--不完全恢复错误案例

RMAN恢复案例：

不完全恢复，由于在先前的数据文件备份有误，导致恢复失败。

[oracle@rh6 ~]$ rman target / Recovery Manager: Release 11.2.0.1.0 - Production on Sat Sep 20 15:54:25 2014 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: TEST1 (DBID=1195893416) RMAN> run { 2> shutdown immediate; 3> startup mount; 4> set until time '2014-09-20 15:49:36'; 5> restore database; 6> recover database ; 7> alter database open resetlogs; 8> sql'alter system switch logfile'; 9> } using target database control file instead of recovery catalog database closed database dismounted Oracle instance shut down connected to target database (not started) Oracle instance started database mounted Total System Global Area 175767552 bytes Fixed Size 1335276 bytes Variable Size 142606356 bytes Database Buffers 29360128 bytes Redo Buffers 2465792 bytes executing command: SET until clause Starting restore at 20-SEP-14 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=18 device type=DISK flashing back control file to SCN 9601534 channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/test1/sysaux01.dbf channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/test1/users01.dbf channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/test1/perfs.dbf channel ORA_DISK_1: restoring datafile 00007 to /u01/app/oracle/oradata/test1/undotbs2.dbf channel ORA_DISK_1: restoring datafile 00010 to /u01/app/oracle/oradata/test1/index01.dbf channel ORA_DISK_1: reading from backup piece /dsk1/backup/test1/TEST1_240.bak channel ORA_DISK_1: piece handle=/dsk1/backup/test1/TEST1_240.bak tag=TAG20140920T152720 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:35 channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00013 to /u01/app/oracle/oradata/test1/tbs_16.dbf channel ORA_DISK_1: reading from backup piece /dsk1/backup/test1/TEST1_241.bak channel ORA_DISK_1: piece handle=/dsk1/backup/test1/TEST1_241.bak tag=TAG20140920T152720 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/test1/system01.dbf channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/test1/test1.dbf channel ORA_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/test1/dict1.dbf channel ORA_DISK_1: reading from backup piece /dsk1/backup/test1/TEST1_239.bak channel ORA_DISK_1: piece handle=/dsk1/backup/test1/TEST1_239.bak tag=TAG20140920T152720 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:45 Finished restore at 20-SEP-14 Starting recover at 20-SEP-14 using channel ORA_DISK_1 starting media recovery

recover 失败......

media recovery failed

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 09/20/2014 15:59:01

RMAN-20505: create datafile during recovery

RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed

start until time 'SEP 20 2014 15:49:36'

ORA-00283: recovery session canceled due to errors

ORA-01244: unnamed datafile(s) added to control file by media recovery

ORA-01110: data file 8: '/u01/app/oracle/oradata/test1/tbs2.dbf'

查看备份信息：

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Adding Users to MySQL: The Complete TutorialMay 12, 2025 am 12:14 AM

Mastering the method of adding MySQL users is crucial for database administrators and developers because it ensures the security and access control of the database. 1) Create a new user using the CREATEUSER command, 2) Assign permissions through the GRANT command, 3) Use FLUSHPRIVILEGES to ensure permissions take effect, 4) Regularly audit and clean user accounts to maintain performance and security.

Mastering MySQL String Data Types: VARCHAR vs. TEXT vs. CHARMay 12, 2025 am 12:12 AM

ChooseCHARforfixed-lengthdata,VARCHARforvariable-lengthdata,andTEXTforlargetextfields.1)CHARisefficientforconsistent-lengthdatalikecodes.2)VARCHARsuitsvariable-lengthdatalikenames,balancingflexibilityandperformance.3)TEXTisidealforlargetextslikeartic

MySQL: String Data Types and Indexing: Best PracticesMay 12, 2025 am 12:11 AM

Best practices for handling string data types and indexes in MySQL include: 1) Selecting the appropriate string type, such as CHAR for fixed length, VARCHAR for variable length, and TEXT for large text; 2) Be cautious in indexing, avoid over-indexing, and create indexes for common queries; 3) Use prefix indexes and full-text indexes to optimize long string searches; 4) Regularly monitor and optimize indexes to keep indexes small and efficient. Through these methods, we can balance read and write performance and improve database efficiency.

MySQL: How to Add a User RemotelyMay 12, 2025 am 12:10 AM

ToaddauserremotelytoMySQL,followthesesteps:1)ConnecttoMySQLasroot,2)Createanewuserwithremoteaccess,3)Grantnecessaryprivileges,and4)Flushprivileges.BecautiousofsecurityrisksbylimitingprivilegesandaccesstospecificIPs,ensuringstrongpasswords,andmonitori

The Ultimate Guide to MySQL String Data Types: Efficient Data StorageMay 12, 2025 am 12:05 AM

TostorestringsefficientlyinMySQL,choosetherightdatatypebasedonyourneeds:1)UseCHARforfixed-lengthstringslikecountrycodes.2)UseVARCHARforvariable-lengthstringslikenames.3)UseTEXTforlong-formtextcontent.4)UseBLOBforbinarydatalikeimages.Considerstorageov

MySQL BLOB vs. TEXT: Choosing the Right Data Type for Large ObjectsMay 11, 2025 am 12:13 AM

When selecting MySQL's BLOB and TEXT data types, BLOB is suitable for storing binary data, and TEXT is suitable for storing text data. 1) BLOB is suitable for binary data such as pictures and audio, 2) TEXT is suitable for text data such as articles and comments. When choosing, data properties and performance optimization must be considered.

MySQL: Should I use root user for my product?May 11, 2025 am 12:11 AM

No,youshouldnotusetherootuserinMySQLforyourproduct.Instead,createspecificuserswithlimitedprivilegestoenhancesecurityandperformance:1)Createanewuserwithastrongpassword,2)Grantonlynecessarypermissionstothisuser,3)Regularlyreviewandupdateuserpermissions

MySQL String Data Types Explained: Choosing the Right Type for Your DataMay 11, 2025 am 12:10 AM

MySQLstringdatatypesshouldbechosenbasedondatacharacteristicsandusecases:1)UseCHARforfixed-lengthstringslikecountrycodes.2)UseVARCHARforvariable-lengthstringslikenames.3)UseBINARYorVARBINARYforbinarydatalikecryptographickeys.4)UseBLOBorTEXTforlargeuns

See all articles