Shulou(Shulou.com)06/01 Report--

When maintaining the data file, it is found that there is a case difference in the name of the data file.

For data files created after a certain point in time, the db_name and "datafile" in their names are all uppercase, while they used to be lowercase.

Check the official document Directory for Datafiles and Controlfiles Become Uppercase in 18.3 DBCA. (Doc ID 2542927.1)

Starting with version 18.3.0.0, changes in the internal design caused this problem.

At the same time, it also points to a document of internal and does not have permission to browse:

BUG:29294715-18.3 DBCA UPPERCASING DB_UNIQUE_NAME FOR DIRECTORY OF DATA FILES AND CONTROL FILES.

Further analysis revealed that after we upgraded the database to 19c and changed compatible from 11.2.0.4 to 19.3.0.0, the data file path was changed to uppercase.

This problem does not occur in databases that use the file system as storage media.

Directory for Datafiles and Controlfiles Become Uppercase in 18.3 DBCA. (Doc ID 2542927.1)

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.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.