Oracle 在RMAN部分复制后ORA-376

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

服务热线 ： 13764045638 QQ号:47079569 邮箱：[email protected]

ORA-00376

oerr ora 376
00376, 00000, "file %s cannot be read at this time"
// *Cause: attempting to read from a file that is not readable. Most likely
// the file is offline.
// *Action: Check the state of the file. Bring it online

适用于:

Oracle Server – Enterprise Edition – 版本10.2.0.1 及以上
本文信息适用于任何平台。

症状

在将所有表和索引移动到另一个表空间后，我执行部分复制，跳过旧的表空间。

对新复制数据库的查询报告一个属于被跳过表空间的数据文件的错误：

ORA-00376: file 18 cannot be read at this time
ORA-01111: name for data file 18 is unknown – rename to correct file
ORA-01110: data file 18: ‘/u01/app/oracle/product/10.2.0/db_1/dbs/MISSING00018’

更改

原因

部分RMAN 复制失败，显示如下：

sql 语句： drop tablespace PRASACPARAM including contents cascade constraints
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/26/2012 18:00:23
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 08/26/2012 18:00:23
RMAN-11003: failure during parse/execution of SQL statement: drop tablespace PRASACPARAM including contents cascade constraints
ORA-23515: materialized views and/or their indices exist in the tablespace <<<<—————–

在被跳过的表空间中有依赖性。
解决方案

确保在被跳过的表空间中没有依赖性。依赖性包括物化视图，和高级排列表advanced queuing tables。

否则，在辅助站点，drop该表空间中所有依赖性，并最终drop在辅助站点的表空间。