Oracleupdateto19cusingDBU

升級(jí)關(guān)鍵點(diǎn)
1.可以從11.2.0.4、12.1.0.2、12.2.0.1和18c直接升級(jí)到19c。
2.兼容參數(shù)至少應(yīng)為11.2.0
3.升級(jí)后,Oracle默認(rèn)帳戶(在升級(jí)之前尚未重置其密碼)將被鎖定并設(shè)置為NO AUTHENICATE MODE。
4.升級(jí)后,由于采用了新的身份驗(yàn)證方法,您可能無(wú)法使用密碼登錄現(xiàn)有用戶。 若要解決此問(wèn)題,需要更新sqlnet.ora文件。

軟件準(zhǔn)備
數(shù)據(jù)庫(kù)軟件
數(shù)據(jù)庫(kù)升級(jí)版本:
Oracle Database 19.3.0.0
當(dāng)前環(huán)境詳細(xì)信息
DATABASE TYPE – single
DATABASE NAME – TESTDB
DATABASE VESION – 12.1.0.2
CURRENT ORACLE_HOME=/oracle/app/oracle/product/12.1.0.2/dbhome_1
NEW ORACLE_HOME = /oracle/app/oracle/product/19.0.0.0/dbhome_1

為嵩明等地區(qū)用戶提供了全套網(wǎng)頁(yè)設(shè)計(jì)制作服務(wù),及嵩明網(wǎng)站建設(shè)行業(yè)解決方案。主營(yíng)業(yè)務(wù)為成都網(wǎng)站建設(shè)、做網(wǎng)站、嵩明網(wǎng)站設(shè)計(jì),以傳統(tǒng)方式定制建設(shè)網(wǎng)站,并提供域名空間備案等一條龍服務(wù),秉承以專業(yè)、用心的態(tài)度為用戶提供真誠(chéng)的服務(wù)。我們深信只要達(dá)到每一位用戶的要求,就會(huì)得到認(rèn)可,從而選擇與我們長(zhǎng)期合作。這樣,我們也可以走得更遠(yuǎn)!

**安裝DB**

解壓安裝包創(chuàng)建安裝目錄
unzip the binary and run runInstaller.sh
mkdir -p /oracle/app/oracle/product/19.0.0.0/dbhome_1

安裝數(shù)據(jù)庫(kù)軟件
Oracle update to 19c using DBU

Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU

升級(jí)前檢查
運(yùn)行升級(jí)前工具腳本
oracle數(shù)據(jù)庫(kù)二進(jìn)制文件提供了preupgrade.jar工具文件。運(yùn)行此進(jìn)行預(yù)檢查

export ORACLE_HOME=/oracle/app/oracle/product/12.1.0.2/dbhome_1

$ORACLE_HOME/jdk/bin/java -jar /oracle/app/oracle/product/19.0.0.0/dbhome_1/rdbms/admin/preupgrade.jar

==================
PREUPGRADE SUMMARY

/oracle/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/TESTDB/preupgrade/preupgrade.log
/oracle/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/TESTDB/preupgrade/preupgrade_fixups.sql
/oracle/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/TESTDB/preupgrade/postupgrade_fixups.sql

Execute fixup scripts as indicated below:

Before upgrade:

Log into the database and execute the preupgrade fixups
@/oracle/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/TESTDB/preupgrade/preupgrade_fixups.sql

After the upgrade:

Log into the database and execute the postupgrade fixups
@/oracle/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/TESTDB/preupgrade/postupgrade_fixups.sql

Preupgrade complete: 2019-08-26T13:09:51

運(yùn)行升級(jí)前修正腳本

SQL> @/oracle/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/TESTDB/preupgrade/preupgrade_fixups.sql

Executing Oracle PRE-Upgrade Fixup Script

Auto-Generated by: Oracle Preupgrade Script
Version: 19.0.0.0.0 Build: 1
Generated on: 2019-08-26 13:09:37

For Source Database: TESTDB
Source Database Version: 12.1.0.2.0
For Upgrade to Version: 19.0.0.0.0

Preup Preupgrade
Action Issue Is
Number Preupgrade Check Name Remedied Further DBA Action


1.  invalid_objects_exist     NO          Manual fixup recommended.
2.  exclusive_mode_auth       NO          Manual fixup recommended.
3.  case_insensitive_auth     NO          Manual fixup recommended.
4.  underscore_events         NO          Informational only.
                                          Further action is optional.
5.  dictionary_stats          YES         None.
6.  parameter_deprecated      NO          Informational only.
                                          Further action is optional.
7.  min_archive_dest_size     NO          Informational only.
                                          Further action is optional.
8.  rman_recovery_version     NO          Informational only.
                                          Further action is optional.

The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database is not ready
for upgrade. To resolve the outstanding issues, start by reviewing
the preupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.

PL/SQL procedure successfully completed.

運(yùn)行utlrp.sql :(編譯無(wú)效對(duì)象)

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

SQL> select count(*) from dba_objects where status='INVALID';

COUNT(*)


     0

檢查數(shù)據(jù)庫(kù)組件狀態(tài)
set pagesize500
set linesize 100
select substr(comp_name,1,40) comp_name, status, substr(version,1,10) version from dba_registry order by comp_name;

COMP_NAME


STATUS VERSION


JServer JAVA Virtual Machine
VALID 12.1.0.2.0

Oracle Database Catalog Views
VALID 12.1.0.2.0

Oracle Database Java Packages
VALID 12.1.0.2.0

Oracle Database Packages and Types
VALID 12.1.0.2.0

Oracle Multimedia
VALID 12.1.0.2.0

Oracle Text
VALID 12.1.0.2.0

Oracle Workspace Manager
VALID 12.1.0.2.0

Oracle XDK
VALID 12.1.0.2.0

Oracle XML Database
VALID 12.1.0.2.0

SQL> SELECT o.name FROM sys.obj$ o, sys.user$ u, sys.sum$ s WHERE o.type# = 42 AND bitand(s.mflags, 8) =8;

no rows selected

檢查時(shí)區(qū)版本
SQL> select * from v$timezone_file;

FILENAME VERSION CON_ID


timezlrg_18.dat 18 0

在備份模式下檢查文件:(應(yīng)返回零行)
SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';

no rows selected

SQL> SELECT * FROM v$recover_file;

no rows selected

清除回收站
SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';

no rows selected

SQL> SELECT * FROM v$recover_file;

no rows selected

升級(jí)數(shù)據(jù)庫(kù)
Enable the flashback on the database.

  1. To enable restore , in case of failure, enable flashback option.

alter system set db_recovery_file_dest_size=20G scope=both;
alter system set db_recovery_file_dest='/dumparea/FRA/' scope=both;
alter database flashback on;

export ORACLE_HOME=/oracle/app/oracle/product/19.0.0.0/dbhome_1/
cd $ORACLE_HOME/bin
./dbua
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Oracle update to 19c using DBU
Upgrade completed successfully.
升級(jí)后檢查
SQL> select comp_id,status from dba_registry;

COMP_ID STATUS


CATALOG VALID
CATPROC VALID
JAVAVM VALID
XML VALID
CATJAVA VALID
RAC OPTION OFF
XDB VALID
OWM VALID
CONTEXT VALID
ORDIM VALID

10 rows selected.

SQL> select * from v$timezone_file;

FILENAME VERSION CON_ID


timezlrg_32.dat 32 0

更新sqlnet.ora文件
Post upgrade, you might not be able to connect to the existing users with the passwords. So to fix this add SQLNET.ALLOWED_LOGON_VERSION_SERVER=11 to sqlnet.ora file
export ORACLE_HOME=/oracle/app/oracle/product/19.0.0.0/dbhome_1
cd $ORACLE_HOME/network/admin
cat sqlnet.ora

SQLNET.ALLOWED_LOGON_VERSION_SERVER=11

一旦確認(rèn)升級(jí)成功并且沒(méi)有回滾,就可以刪除還原點(diǎn)。
select * from v$restore_point;

drop restore point

在升級(jí)后更新兼容的參數(shù)。
升級(jí)成功后,請(qǐng)對(duì)數(shù)據(jù)庫(kù)進(jìn)行測(cè)試。 測(cè)試成功后,您可以更新兼容參數(shù)。 但是,一旦更新了兼容參數(shù),就無(wú)法降級(jí)數(shù)據(jù)庫(kù)。 因此,在更新兼容參數(shù)之前,請(qǐng)務(wù)必進(jìn)行適當(dāng)?shù)臏y(cè)試并進(jìn)行完整備份。

alter system set compatible='19.0.0' scope=spfile;
shutdown immediate;
startup

SELECT name, value FROM v$parameter
WHERE name = 'compatible';

標(biāo)題名稱:Oracleupdateto19cusingDBU
文章分享:http://muchs.cn/article44/gphsee.html

成都網(wǎng)站建設(shè)公司_創(chuàng)新互聯(lián),為您提供動(dòng)態(tài)網(wǎng)站、營(yíng)銷型網(wǎng)站建設(shè)、品牌網(wǎng)站制作網(wǎng)頁(yè)設(shè)計(jì)公司、ChatGPT、小程序開(kāi)發(fā)

廣告

聲明:本網(wǎng)站發(fā)布的內(nèi)容(圖片、視頻和文字)以用戶投稿、用戶轉(zhuǎn)載內(nèi)容為主,如果涉及侵權(quán)請(qǐng)盡快告知,我們將會(huì)在第一時(shí)間刪除。文章觀點(diǎn)不代表本網(wǎng)站立場(chǎng),如需處理請(qǐng)聯(lián)系客服。電話:028-86922220;郵箱:631063699@qq.com。內(nèi)容未經(jīng)允許不得轉(zhuǎn)載,或轉(zhuǎn)載時(shí)需注明來(lái)源: 創(chuàng)新互聯(lián)

營(yíng)銷型網(wǎng)站建設(shè)