2014.1.16实施数据迁移时遇到的问题（ORA-00214和ORA-39700问题解决）

实施数据迁移的环境：从win server 2003（32位？）的oracle 11.2.0.1到win server 2008(64 位)的oracle 11.2.0.3

=============================================================

百度 ora-00214
http://jenny-86.iteye.com/blog/433701

ORA-00214的解決办法

博客分类：
数据库

OracleF#

原因是oracle在同步controlfile的时候磁盘或者其它原因导致失败,在mount数据库阶段,如果所有controlfile的状态不一致就会出这个问题.

解决方法:

我首先备份了控制文件，启动了数据库到nomount状态下，分别指定系统控制文件为三个中的其中一个:

ALTER SYSTEM SET CONTROL_FILES='F:\ORACLE\ORADATA\ORACAS\CONTROL01.CTL' SCOPE=SPFILE

然后启动数据库到Mount状态下，如果还是报错，就指定下一个.

只要上面三次操作中有一次成功，就可以用那个成功的控制文件来重新作出另外两个控制文件。即先关闭打开的数据库,然后删掉无用的控制文件,把有用的复制一份然后alter system set control_files='../control01.ctl','../control02.ctl' scope=spfile; 打开数据库即可
http://bulkaunt.itpub.net:8080/58242/viewspace-817222/
百度 ora39700

ORA-00704,ORA-39700问题解决

(2008-10-08 00:03:41)


转载▼

标签： 杂谈

分类：MSN搬家

　　一数据库空间不够，故迁移到新的一台服务器，因为配置一样，直接shutdown，然后copy数据文件，control,redo文件到另外一台机器上，启动，发现实例自动关闭，alertlog 发现如下：
Errors in file/u01/admin/ora9/udump/ora9_ora_1333.trc:

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADEoption

　　　想起应该是原来的数据库版本为10.2.0,3, 新的版本为10.2.0.4,需要升级。
　　　故执行了如下操作：
SQL>startup upgrade

SQL>@?/rdbms/admin/catupgrd.sql

SQL>@?/rdbms/admin/catalog.sql

SQL>@?/rdbms/admin/catproc.sql

SQL>@?/rdbms/admin/utlrp.sql

SQL>shutdown immediate

SQL>startup

　　　问题解决！

其中如果不执行catalog.sql的话，无法执行utlrp.sql。

catupgrd.sql似乎不用执行，看注释如下：
Rem NAME

Rem catupgrd.sql - CATalog UPGraDe tothe new release

Rem

Rem DESCRIPTION

Rem This script is to be used for upgradingan 8.1.7, 9.0.1, 9.2

Rem or 10.1 database to the newrelease. This script provides a direct

Rem upgrade path from these releases to thenew Oracle release.

其它

Rem NAME

Rem CATALOG.SQL

Rem FUNCTION

Rem Creates data dictionary views.

Rem NAME

Rem catproc.sql

Rem DESCRIPTION

Rem Run all sql scripts for the procedural option

Rem NAME

Rem utlrp.sql - Recompile invalidobjects

Rem

Rem DESCRIPTION

Rem This script recompiles invalid objectsin the database.

Rem

Rem When run as one of the last stepsduring upgrade or downgrade,

Rem this script will validate all remaininginvalid objects. It will

Rem also run a component validationprocedure for each component in

Rem the database. See the README notes foryour current release and

Rem the Oracle Database Upgrade book formore information about

Rem using utlrp.sql

ORA-39700错误(一般升级数据库容易遇到)2008-08-09 17:36:26

分类： Linux

最近有人遇到了ORA-39700错误是在DB升级后遇到的,查了下解释如下:

SQL> !oerr ora 39700

39700, 00000, "database must be opened with UPGRADE option"

// *Cause: A normal database open was attempted, but the database has not

// been upgraded to the current server version.

// *Action: Use the UPGRADE option when opening the database to run

// catupgrd.sql (for database upgrade), or to run catalog.sql

// and catproc.sql (after initial database creation).

说明需要运行这些数据字典脚本,也就是数据字典里的东西被改变了

顺便查阅了其他人遇到的这个问题解决方法,也归纳如下:

1、

ORA-39700

上星期升级以后重新启动database发生这样的情况ORA-01092: ORACLE instance terminated. Disconnection forced

检察alertfile发现
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)

tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

主要原因是升级以后数据字典的一些基表的内容修改了。catalog.sql和catproc.sql这2个脚本需要在运行一下把数据字典视图在更新一下。

2、

oerr ora 39700

解决方法:使用startup upgrade启动就可以了。

[oracle@localhost bdump]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.2.0 - Production on ÐÇÆÚÒ» 7ÔÂ 31 09:26:28 2006
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> STARTUP UPGRADE

ORACLE instance started.
Total System Global Area 167772160 bytes

Fixed Size 1259744 bytes

Variable Size 75499296 bytes

Database Buffers 88080384 bytes

Redo Buffers 2932736 bytes

Database mounted.

Database opened.

SQL> @$ORACLE_HOME/rdbms/admin/catupgrd.sql
...

No errors.

No errors.

No errors.

No errors.

No errors.

No errors.

No errors.
TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP RUL 2006-07-31 10:37:41

DBUA_TIMESTAMP RUL VALID 2006-07-31 10:37:41

TIMESTAMP

--------------------------------------------------------------------------------

COMP_TIMESTAMP UPGRD_END 2006-07-31 10:37:41

.

Oracle Database 10.2 Upgrade Status Utility 07-31-2006 10:37:41

.

Component Status Version HH:MM:SS

Oracle Database Server VALID 10.2.0.2.0 00:14:58

JServer JAVA Virtual Machine VALID 10.2.0.2.0 00:03:58

Oracle XDK VALID 10.2.0.2.0 00:00:58

Oracle Database Java Packages VALID 10.2.0.2.0 00:01:03

Oracle Text VALID 10.2.0.2.0 00:00:27

Oracle XML Database VALID 10.2.0.2.0 00:01:42

Oracle Data Mining VALID 10.2.0.2.0 00:00:27

OLAP Analytic Workspace VALID 10.2.0.2.0 00:00:32

OLAP Catalog VALID 10.2.0.2.0 00:01:04

Oracle OLAP API VALID 10.2.0.2.0 00:01:06

Oracle interMedia VALID 10.2.0.2.0 00:08:36

Spatial VALID 10.2.0.2.0 00:00:58

Oracle Expression Filter VALID 10.2.0.2.0 00:00:21

Oracle Enterprise Manager VALID 10.2.0.2.0 00:01:04

Oracle Rule Manager VALID 10.2.0.2.0 00:00:20

.

Total Upgrade Time: 00:37:41

DOC>#######################################################################

DOC>#######################################################################

DOC>

DOC> The above PL/SQL lists the SERVER components in the upgraded

DOC> database, along with their current version and status.

DOC>

DOC> Please review the status and version columns and look for

DOC> any errors in the spool log file. If there are errors in the spool

DOC> file, or any components are not VALID or not the current version,

DOC> consult the Oracle Database Upgrade Guide for troubleshooting

DOC> recommendations.

DOC>

DOC> Next shutdown immediate, restart for normal operation, and then

DOC> run utlrp.sql to recompile any invalid application objects.

DOC>

DOC>#######################################################################

DOC>#######################################################################

DOC>#

SQL> shutdown

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup

ORACLE instance started.
Total System Global Area 167772160 bytes

Fixed Size 1259744 bytes

Variable Size 121636640 bytes

Database Buffers 41943040 bytes

Redo Buffers 2932736 bytes

Database mounted.

Database opened.

SQL>

阅读(2696) | 评论(0) | 转发(0) |

0
上一篇：Oracle临时表相关知识

下一篇：关于ORACLE锁的总结
http://blog.sina.com.cn/s/blog_538285a70100nvxg.html
请大家帮帮忙 谢谢了

SQL> startup

ORACLE 例程已经启动。

Total System Global Area 1046224896 bytes

Fixed Size 1379212 bytes

Variable Size 343934068 bytes

Database Buffers 696254464 bytes

Redo Buffers 4657152 bytes

数据库装载完毕。

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

进程 ID: 2456

会话 ID: 9 序列号: 3

什么方法迁移的，肯定是版本不一样或数据字典结构不一样

SQL> @?/rdbms/admin/utlirp.sql;

SQL> spool /tmp/upgrade.log;

SQL> @?/rdbms/admin/utlrp.sql;

SQL> startup force

@?/rdbms/admin/catupgrd.sql
http://www.itpub.net/thread-1513641-1-1.html
============================================================

Oracle数据库升级后报ORA-00704和ORA-39700错误

把数据库从10.2.0.1.0升级到10.2.0.5.0，

启动数据库，报错：ORA-01092:
Oracle 例程终止，强制断开。

查看alert文件，显示

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

因为数据库升级以后数据字典的内容被修改了，需要运行catalog.sql和catproc.sql这两个脚本再更新数据字典。

处理方法如下：

SQL>startup upgrade;

SQL>@ORACLE_HOME\rdbms\admin\catupgrd.sql;

这个脚本会执行比较长时间，我在虚拟机上用了快22分钟.

Total Upgrade Time: 00:21:58

执行完成以后，关闭数据库，再使用正常模式启动数据库.

再运行一下utlrp.sql这个脚本来重新编译一下一些无效的对象

SQL>startup

SQL>@ORACLE_HOME\rdbms\admin\utlrp.sql;

...

OBJECTS WITH ERRORS

-------------------

0

...

ERRORS DURING RECOMPILATION

---------------------------

0

升级完成．

参见：
http://www.linuxidc.com/Linux/2012-02/54039.htm
**********************************************************************************

小结：

　故执行了如下操作：

SQL>startup upgrade

SQL>@?/rdbms/admin/catupgrd.sql/ /更新数据库软件里的组件

SQL>@?/rdbms/admin/catalog.sql//这两个脚本再更新数据字典。

SQL>@?/rdbms/admin/catproc.sql //这两个脚本再更新数据字典。

SQL>@?/rdbms/admin/utlrp.sql //这个脚本来重新编译一下一些无效的对象

...

OBJECTS WITH ERRORS

-------------------

0

...

ERRORS DURING RECOMPILATION

---------------------------

0

SQL>shutdown immediate

SQL>startup



最后验证一下各个组件的版本和状态：

Run utlu112s.sql todisplay the results of the upgrade as follows:

SQL> @?/rdbms/admin/utlu112s.sql
或是用下面语句：

SQL> SELECT COMP_NAME, VERSION, STATUSFROM SYS.DBA_REGISTRY;

COMP_NAME VERSION STATUS

———————————————————————- ———————-

OWB 11.2.0.1.0 VALID

Oracle Application Express 3.2.1.00.10 VALID

Oracle Enterprise Manager 11.2.0.3.0 VALID

OLAP Catalog 11.2.0.3.0 VALID

Spatial 11.2.0.3.0 VALID

Oracle Multimedia 11.2.0.3.0 VALID

Oracle XML Database 11.2.0.3.0 VALID

Oracle Text 11.2.0.3.0 VALID

Oracle Expression Filter 11.2.0.3.0 VALID

Oracle Rules Manager 11.2.0.3.0 VALID

Oracle Workspace Manager 11.2.0.3.0 VALID

COMP_NAME VERSION STATUS

———————————————————————- ———————-

Oracle Database Catalog Views 11.2.0.3.0 VALID

Oracle Database Packages and Types 11.2.0.3.0 VALID

JServer JAVA Virtual Machine 11.2.0.3.0 VALID

Oracle XDK 11.2.0.3.0 VALID

Oracle Database Java Packages 11.2.0.3.0 VALID

OLAP Analytic Workspace 11.2.0.3.0 VALID

Oracle OLAP API 11.2.0.3.0 VALID

18 rows selected.

参见：

Oracle 11.2.0.1 升级到 11.2.0.3 示例