oracle database 10.2.0.4 升级到 10.2.0.5-O Record-51CTO博客
某发票开发测试库升级升级前准备，此次升级只是很对测试环境数据库升级，所以没有事先一个月来获取系统，数据库的统计信息，机器性能比对
为了加快升级只是清理了以下信息
01.截断SYS.AUD$基表:
SQL>TRUNCATE TABLE SYS.AUD$;
02.清理DBA回收站:
SQL>purge DBA_RECYCLEBIN;
1.升级开始，升级前首先断开测试环境的中间件应用
查看本机的ORACLE_HOME
$ echo $ORACLE_HOME
/opt/product/10.2.0/db_1
2.把10.2.0.5的补丁p8202632_10205_Linux-x86-64.zip放到/oinstall目录下
# cd /oinstall/
# unzip p8202632_10205_Linux-x86-64.zip解压完成后，再赋予相应的权限，Disk1为10.2.0.5的解压的PATCH目录
# chown -R oracle:oinstall/oinstall/
# ls -al
total 1221952
drwxr-xr-x5 oracle oinstall 4096 Apr 292010 Disk1
-rw-r--r--1 oracle oinstall 1249857866 Nov 22 17:24 p8202632_10205_Linux-x86-64.zip
3.确定当前的数据库版本
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
5.在做升级之前先要进行备份，备份数据库软件与数据文件，备份重中之重
01.数据库软件用tar 命令备份即可（略）
02.数据库本身备份利用RMAN即可（略）
03.备份完成后开始停止相应的服务
instanceSQL>shutdown immediate
listener$lsnrctl stop
EM $emctl stop dbconsole
6.开始安装补丁，首以root用户先进入图形化界面
# xhost +
# su - oracle
$ cd /oinstall/
$ cd Disk1/
$ ls
installpatch_note.htmresponserunInstallerstage
开始安装补丁
$ ./runInstaller
.
.
图形化安装，与安装oracle软件一致，此处忽略安装过程
.
.
7.安装完成后，以upgrade模式启动数据库，升级数据字典
SQL>startup upgrade
SQL> select status from v$instance;
STATUS
------------------------
OPEN MIGRATE
确认此时instance状态为OPEN MIGRATE（）
升级数据库的大版本或大的patch的时候总是需要升级现有数据库的数据字典，升级数据字段的原因是因为随着Oracle版本的升级，
某些对象的属性需要改变，以便保证系统的的数据词典的完整性和有效性这些变更都是在升级脚本$ORACLE_HOME/rdbms/admin/catupgrd.sql中。
以升级模式启动数据库后，开始升级数据字典
SQL>@/opt/product/10.2.0/db_1/rdbms/catupgrd.sql
升级数据字典时，可以看到相应的操作
PL/SQL procedure successfully completed.
Type created.
Grant succeeded.
Package created.
No errors.
Table created.
PL/SQL procedure successfully completed.
View created.
Synonym created.
进而进一步验证了catupgrd.sql作用，升级完数据字典后，sqlplus下会出现以下信息
TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP RUL 2012-11-23 06:56:47
DBUA_TIMESTAMP RUL VALID 2012-11-23 06:56:47
COMP_TIMESTAMP UPGRD_END2012-11-23 06:58:01
.
Oracle Database 10.2 Upgrade Status Utility 11-23-2012 06:58:01
.
Component Status VersionHH:MM:SS
Oracle Database Server VALID 10.2.0.5.000:07:52
JServer JAVA Virtual Machine VALID 10.2.0.5.000:00:56
Oracle XDK VALID 10.2.0.5.000:00:23
Oracle Database Java Packages VALID 10.2.0.5.000:00:12
Oracle Text VALID 10.2.0.5.000:00:18
Oracle XML Database VALID 10.2.0.5.000:02:02
Oracle Workspace Manager VALID 10.2.0.5.000:00:36
Oracle Data Mining VALID 10.2.0.5.000:00:15
OLAP Analytic Workspace VALID 10.2.0.5.000:00:16
OLAP Catalog VALID 10.2.0.5.000:00:42
Oracle OLAP API VALID 10.2.0.5.000:00:31
Oracle interMedia VALID 10.2.0.5.000:02:21
Spatial VALID 10.2.0.5.000:01:32
Oracle Expression Filter VALID 10.2.0.5.000:00:06
Oracle Enterprise Manager VALID 10.2.0.5.000:00:30
Oracle Rule Manager VALID 10.2.0.5.000:00:06
.
Total Upgrade Time: 00:20:01
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>#######################################################################
8.再次重启数据库
SQL> shutdown immediate
SQL> startup
ORACLE instance started.
9.编译无效对象脚本utlrp.sql
utlrp.sql脚本可以在数据库运行的状态下执行以编译、数据库中的invalid对象,oracle建议在对数据库进行迁移、升级、降级后都运行一遍utlrp.sql以编译无效对象。
以sysdba登陆来执行脚本
$ sqlplus / as sysdba
SQL> @/opt/product/11.2.0/db_1/rdbms/admin/utlrp.sql
TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN2012-11-23 07:04:44
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL procedure successfully completed.
TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END2012-11-23 07:05:46
PL/SQL procedure successfully completed.
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
-------------------
0
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
---------------------------
0
PL/SQL procedure successfully completed
SQL> shutdownimmediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 7516192768 bytes
Fixed Size 2107936 bytes
Variable Size 1258292704 bytes
Database Buffers 6241124352 bytes
Redo Buffers 14667776 bytes
Database mounted.
Database opened.
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Linux: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
到此为止，升级工作初步完成
页:
[1]