RMAN 迁移ASM到异机文件系统实战-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

RMAN 迁移ASM到异机文件系统实战

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 05:24 PM

asmnumber

环境说明：源库：192.168.0.10 目标库：192.168.0.11 源库备份： RMANgt; run { 2gt; allocate channel c1 device type dis

Linux公社

首页 → 数据库技术

背景：

阅读新闻

RMAN 迁移ASM到异机文件系统实战

[日期：2012-12-30] 来源：Linux社区作者：plwsab6000 [字体：]

环境说明：

源库：192.168.0.10

目标库：192.168.0.11

源库备份：

RMAN> run {

2> allocate channel c1 device type disk;

3> allocate channel c2 device type disk;

4> backup database format '/home/Oracle/full_database%U' include current controlfile;

5> sql 'alter system archive log current';

6> backup archivelog all format '/home/oracle/archivelog_%U';

7> crosscheck backup;

8> delete noprompt obsolete;

9> release channel c1;

10> release channel c2;

11> }

复制备份集到备库：

scp /home/oracle/full* oracle@192.168.0.11:/home/oracle/target_bk/

scp /home/oracle/archive* oracle@192.168.0.11:/home/oracle/target_bk/

[oracle@targetdb target_bk]$ ls

archivelog_0rnu4jbf_1_1 full_database0nnu4ja0_1_1 full_database0pnu4jb4_1_1

archivelog_0snu4jbf_1_1 full_database0onu4ja0_1_1 full_database0qnu4jb5_1_1

目标库操作

[oracle@targetdb sourcedb]$ mkdir {a,b,c,u}dump

[oracle@targetdb sourcedb]$ ls

adump bdump cdump udump

[oracle@targetdb oradata]$ mkdir sourcedb

[oracle@targetdb oradata]$ ls

sourcedb

[oracle@targetdb oradata]$ cd sourcedb/

[oracle@targetdb sourcedb]$ mkdir arch

[oracle@targetdb sourcedb]$ ls

arch

开始恢复：

因为还没有参数文件，先使用rman 无参数启动

export ORACLE_SID=sourcedb

RMAN> startup nomount;

startup failed: ORA-01078: failure in processing system parameters

LRM-00109: could not open parameter file '/u01/oracle/product/10.2.0/dbs/initsourcedb.ora'

starting Oracle instance without parameter file for retrival of spfile

Oracle instance started

Total System Global Area 159383552 bytes

Fixed Size 1218268 bytes

Variable Size 54528292 bytes

Database Buffers 100663296 bytes

Redo Buffers 2973696 bytes

RMAN> exit

Recovery Manager complete.

linux

Oracle 10g ASM 控制文件多路复用

在Hibernate应用中批量更新和批量删除

最新资讯

本周热门

Linux公社简介 - 广告服务 - 网站地图 - 帮助信息 - 联系我们
本站（LinuxIDC）所刊载文章不代表同意其说法或描述，，仅为提供更多信息，也不构成任何建议。

Copyright © 2006-2014　Linux公社　All rights reserved 浙ICP备06018118号

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

Explain the role of InnoDB redo logs and undo logs.Apr 15, 2025 am 12:16 AM

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

What are the key metrics to look for in an EXPLAIN output (type, key, rows, Extra)?Apr 15, 2025 am 12:15 AM

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

What is the Using temporary status in EXPLAIN and how to avoid it?Apr 15, 2025 am 12:14 AM

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

Describe the different SQL transaction isolation levels (Read Uncommitted, Read Committed, Repeatable Read, Serializable) and their implications in MySQL/InnoDB.Apr 15, 2025 am 12:11 AM

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL vs. Other Databases: Comparing the OptionsApr 15, 2025 am 12:08 AM

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

See all articles