rman备份恢复到异机报ORA-01110 ORA-01180错误
rman备份恢复到异机报ORA-01110 ORA-01180错误
[Oracle@server1 ORACLE]$ rman target /
Recovery Manager: Release 10.2.0.5.0 - Production on Thu Jul 31 13:51:40 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database (not started)
RMAN> set dbid 1619708557
executing command: SET DBID
RMAN> startup nomount
Oracle instance started
Total System Global Area 8388608000 bytes
Fixed Size 2109640 bytes
Variable Size 5117054776 bytes
Database Buffers 3221225472 bytes
Redo Buffers 48218112 bytes
RMAN> restore controlfile from '/home/oracle/orabase/flash_recovery_area/ORACLE/autobackup/2014_07_31/o1_mf_s_854376584_9xmsr8fm_.bkp';
Starting restore at 31-JUL-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1084 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output filename=/home/oracle/orabase/oradata/ORACLE/control01.ctl
output filename=/home/oracle/orabase/oradata/ORACLE/control02.ctl
output filename=/home/oracle/orabase/oradata/ORACLE/control03.ctl
Finished restore at 31-JUL-14
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
--------------------------------------------------------------------------------
RMAN 配置归档日志删除策略
Oracle基础教程之通过RMAN复制数据库
RMAN备份策略制定参考内容
RMAN备份学习笔记
Oracle数据库备份加密 RMAN加密
Linux-6-64下安装Oracle 12C笔记
在CentOS 6.4下安装Oracle 11gR2(x64)
Oracle 11gR2 在VMWare虚拟机中安装步骤
Debian 下 安装 Oracle 11g XE R2
--------------------------------------------------------------------------------
RMAN> restore database;
启动 restore 于 31-7月-14
使用通道 ORA_DISK_1
创建数据文件 fno = 1 名称 = /home/oracle/orabase/oradata/ORACLE/system01.dbf
MAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: restore 命令 (在 07/31/2014 12:06:00 上) 失败
ORA-01180: 无法创建数据文件 1
ORA-01110: 数据文件 1: '/home/oracle/orabase/oradata/ORACLE/system01.dbf'
RMAN>
RMAN> crosscheck backupset;
Starting implicit crosscheck backup at 31-JUL-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1084 devtype=DISK
Crosschecked 10 objects
Finished implicit crosscheck backup at 31-JUL-14
Starting implicit crosscheck copy at 31-JUL-14
using channel ORA_DISK_1
Finished implicit crosscheck copy at 31-JUL-14
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /home/oracle/orabase/flash_recovery_area/ORACLE/archivelog/2014_07_31/o1_mf_1_116_9xm5yprp_.arc
File Name: /home/oracle/orabase/flash_recovery_area/ORACLE/autobackup/2014_07_31/o1_mf_s_854331141_9xlfd5gc_.bkp
using channel ORA_DISK_1
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_29/fulldb_nvpeiou9_1_1.bak recid=3836 stamp=854156234
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_29/arch_o0peir6m_1_1.bak recid=3837 stamp=854158551
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_30/arch_o2peld7e_1_1.bak recid=3839 stamp=854242543
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_30/fulldb_o3peldbg_1_1.bak recid=3840 stamp=854242673
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_30/arch_o4pelfhd_1_1.bak recid=3841 stamp=854244910
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o6peo1hh_1_1.bak recid=3843 stamp=854328882
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/fulldb_o7peo1la_1_1.bak recid=3844 stamp=854329003
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o8peo3o2_1_1.bak recid=3845 stamp=854331139
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/home/oracle/orabase/flash_recovery_area/ORACLE/autobackup/2014_07_31/o1_mf_s_854331141_9xlfd5gc_.bkp recid=3846
stamp=854373190
Crosschecked 9 objects
由于备份集过期导致无法还原数据库，重新注册备份片。
RMAN> catalog backuppiece '/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o6peo1hh_1_1.bak';
cataloged backuppiece
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o6peo1hh_1_1.bak recid=3847 stamp=854373756
RMAN> catalog backuppiece '/home/oracle/orabackup/rmandata/data/2014_07_31/fulldb_o7peo1la_1_1.bak';
cataloged backuppiece
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/fulldb_o7peo1la_1_1.bak recid=3848 stamp=854373783
RMAN> catalog backuppiece '/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o8peo3o2_1_1.bak';
cataloged backuppiece
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o8peo3o2_1_1.bak recid=3849 stamp=854373809
注册成功之后再次查看
RMAN> crosscheck backupset;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1087 devtype=DISK
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_29/fulldb_nvpeiou9_1_1.bak recid=3836 stamp=854156234
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_29/arch_o0peir6m_1_1.bak recid=3837 stamp=854158551
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_30/arch_o2peld7e_1_1.bak recid=3839 stamp=854242543
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_30/fulldb_o3peldbg_1_1.bak recid=3840 stamp=854242673
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_30/arch_o4pelfhd_1_1.bak recid=3841 stamp=854244910
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o6peo1hh_1_1.bak recid=3847 stamp=854373756
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/fulldb_o7peo1la_1_1.bak recid=3848 stamp=854373783
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/home/oracle/orabackup/rmandata/data/2014_07_31/arch_o8peo3o2_1_1.bak recid=3849 stamp=854373809
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/home/oracle/orabase/flash_recovery_area/ORACLE/autobackup/2014_07_31/o1_mf_s_854331141_9xlfd5gc_.bkp recid=3846
stamp=854373190
Crosschecked 9 objects
还原数据库
RMAN> restore database;
恢复数据库到指定序列。
RMAN> recover database until sequence 13908
恢复结束后，，启动数据库。
RMAN> alter database open resetlogs
本文永久更新链接地址：
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
When might a full table scan be faster than using an index in MySQL?
Apr 09, 2025 am 12:05 AM
Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.
Explain InnoDB Full-Text Search capabilities.
Apr 02, 2025 pm 06:09 PM
InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.
Can I install mysql on Windows 7
Apr 08, 2025 pm 03:21 PM
Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.
Difference between clustered index and non-clustered index (secondary index) in InnoDB.
Apr 02, 2025 pm 06:25 PM
The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.
MySQL: Simple Concepts for Easy Learning
Apr 10, 2025 am 09:29 AM
MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.
Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial).
Apr 02, 2025 pm 07:05 PM
MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.
The relationship between mysql user and database
Apr 08, 2025 pm 07:15 PM
In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.
Can mysql and mariadb coexist
Apr 08, 2025 pm 02:27 PM
MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
