溫馨提示×

溫馨提示×

您好，登錄后才能下訂單哦！

密碼登錄×
登錄注冊×
其他方式登錄
點擊 登錄注冊 即表示同意《億速云用戶服務(wù)條款》

oracle升級后數(shù)據(jù)文件路徑變?yōu)榇髮?/h1>
發(fā)布時間：2020-08-11 12:17:25 來源：ITPUB博客 閱讀：188 作者：to_be_Dba 欄目：關(guān)系型數(shù)據(jù)庫

進行數(shù)據(jù)文件維護時，發(fā)現(xiàn)數(shù)據(jù)文件的名稱存在大小寫差異。

在某個時間點以后創(chuàng)建的數(shù)據(jù)文件，名稱中的db_name和“datafile”都是大寫，而以前都是小寫。

oracle升級后數(shù)據(jù)文件路徑變?yōu)榇髮?></p> <p>查詢官方文檔 <span>Directory for Datafiles and Controlfiles Become Uppercase in 18.3 DBCA. (Doc ID 2542927.1)</span></p> <p>在18.3.0.0版本開始，內(nèi)部設(shè)計上的變化導致了此問題。</p> <p>同時還指向一個internal的文檔，無權(quán)限瀏覽：</p> <p> <span> BUG:29294715 <span> - 18.3 DBCA UPPERCASING DB_UNIQUE_NAME FOR DIRECTORY OF DATA FILES AND CONTROL FILES.</span></span></p> <p>進一步分析發(fā)現(xiàn)，我們將數(shù)據(jù)庫升級到19c，并將compatible由11.2.0.4改為19.3.0.0后，數(shù)據(jù)文件路徑就改為大寫了。</p> <p>使用文件系統(tǒng)作為存儲介質(zhì)的數(shù)據(jù)庫未出現(xiàn)此問題。</p> <p> <span>Directory for Datafiles and Controlfiles Become Uppercase in 18.3 DBCA. (Doc ID 2542927.1)</span></p> <h3 class=APPLIES TO:

Oracle Database Configuration Assistant - Version 18.3.0.0.0 and later
Information in this document applies to any platform.

SYMPTOMS

When you specified lowercase "DB_UNIQUE_NAME" variable(for example:orcl) in DB:18.3 DBCA to create DB instance
after the instance be created, you will find the directory of data files and control files contains uppercase DB_UNIQUE_NAME which you specified.
-----------------------------
/u01/app/oracle/oradata/ORCL
-----------------------------
This result is different from the previous version(DB:12.2/DB:12.1).

If we save the DBCA scripts which can be generated by DBCA, we could see that even if you specified lowercase DB_UNIQUE_NAME in DBCA, 
the script is to create uppercase DB_UNIQUE_NAME in the directory path of data files and control files.

$ pwd
../..oracle/admin/orcl/scripts
 scripts]$ grep "ORCL" *.sql
cloneDBCreation.sql:LOGFILE GROUP 1
('...oradata/ORCL/redo01.log') SIZE 200M,
cloneDBCreation.sql:GROUP 2 ('..oradata/ORCL/redo02.log') SIZE
200M,
cloneDBCreation.sql:GROUP 3 ('../oradata/ORCL/redo03.log') SIZE
200M RESETLOGS;
cloneDBCreation.sql:LOGFILE GROUP 1
('..oradata/ORCL/redo01.log') SIZE 200M,
cloneDBCreation.sql:GROUP 2 ('..oradata/ORCL/redo02.log') SIZE
200M,
...
plug_PDBSeed.sql:host mkdir -p .../oradata/ORCL/pdbseed;
plug_PDBSeed.sql:host mkdir -p .../oracle/oradata/ORCL/pdbseed;
...
rmanRestoreDatafiles.sql:set newname for datafile 4 to  
'..oradata/ORCL/undotbs01.dbf' ;
rmanRestoreDatafiles.sql:set newname for datafile 7 to  
'...oradata/ORCL/users01.dbf' ;

CHANGES

Using DB:18.3 DBCA to create database instance and specified lowercase "DB_UNIQUE_NAME" variable.

CAUSE

It is a limitation according to current design.

SOLUTION

The following method can avoid this issue.

STEP 1: Generate the DBCA Scripts.
STEP 2: Change the uppercase DB_UNIQUE_NAME to lowercase DB_UNIQUE_NAME manually.
STEP 3: Execute these scripts to create DB instance.

向AI問一下細節(jié)

免責聲明：本站發(fā)布的內(nèi)容（圖片、視頻和文字）以原創(chuàng)、轉(zhuǎn)載和分享為主，文章觀點不代表本網(wǎng)站立場，如果涉及侵權(quán)請聯(lián)系站長郵箱：is@yisu.com進行舉報，并提供相關(guān)證據(jù)，一經(jīng)查實，將立刻刪除涉嫌侵權(quán)內(nèi)容。

AI
助
手