Standby上执行RMAN报错RMAN-10006错误处理
环境:Oracle 10g 10.2.0.4 on SuSE 11 + Oracle Data Guard,说明:每天凌晨Standby DB定时只读打开供统计用,之后再继续同步。
环境:Oracle 10g 10.2.0.4 on SUSE 11 + Oracle Data Guard
说明:每天凌晨Standby DB定时只读打开供统计用,之后再继续同步。
故障现象:
执行copy datafile命令报错RMAN-10006.
如下所示:
RMAN> copy datafile 14 to '/u/oracle/oradata/XXDB22/db2_c037dat03.dbf';
Starting backup at 04/25/2011 10:44:31
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1602 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00014 name=/u/oracle/oradata/XXDB22/db_c037dat03.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10006: error running SQL statement: select sofar, context, start_time from v$session_longops where (start_time > nvl(:1, sysdate-100) or start_time = nvl(:2, sysdate+100)) and sid = :3 and serial# = :4 and opname like 'RMAN:%' order by start_time desc, context desc
RMAN-10002: ORACLE error: ORA-00000: normal, successful completion
故障解决:
平时甚少会在Standby DB上执行RMAN操作,第一次碰到这样的报错。
查询metalink,发现是oracle的Bug。
Metalink NoteID:1080134.1.
Cause
Unpublished Bug 4230058: FAIL TO CONNECT TO RMAN AFTER PHYSICAL STANDBY IS OPENED READ ONLY
If the standby database is opened readonly and then managed recovery is restarted without bouncing the database, queries against v$session_longops will fail with:
ORA-01219: database not open: queries allowed on fixed tables/views only
RMAN likewise will fail trying to access this view with RMAN-10006 error.
Solution
Restart the standby database after opening it in READ ONLY mode before restarting the Managed Recovery process.
重启Standby DB后成功执行RMAN命令。
RMAN> copy datafile 14 to '/u/oracle/oradata/XXDB22/db2_c037dat03.dbf';
Starting backup at 04/25/2011 10:55:53
copy datafile 15 to '/u/oracle/oradata/XXDB22/db2_c037dat02.dbf';
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1627 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00014 name=/u/oracle/oradata/XXDB22/db_c037dat03.dbf
output filename=/u/oracle/oradata/XXDB22/db2_c037dat03.dbf tag=TAG20110425T105554 recid=53 stamp=749386639
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:35
Finished backup at 04/25/2011 10:57:29
Starting Control File and SPFILE Autobackup at 04/25/2011 10:57:29
piece handle=/u/oracle/product/10.2.0/db_1/dbs/c-1988110398-20110425-00 comment=NONE
Finished Control File and SPFILE Autobackup at 04/25/2011 10:57:31
相关阅读:
Oracle DG 修改逻辑Standby端数据
Oracle DG 逻辑Standby创建说明
Oracle DG 逻辑Standby的相关视图管理
Oracle 10g rac Standby 归档日志自动删除脚本
DataGuard 之物理Standby 的监控与管理

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





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.

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.

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.

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.

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.

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.

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.

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.
