Multitenant Datafiles Created By DBCA do not follow Normal OFA format in ASM
(Doc ID 2356183.1)
Last updated on APRIL 01, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
SQL> alter session set container=UNKEAWS; <<<< PDB
Session altered.
SQL> select name from v$datafile;
NAME
--------------------------------------------------------------------------------
+DATA/AMBUE178/DATAFILE/undotbs1.265.966093079
+DATA/AMBUE178/63619A18A02401A2E0530ACC009B0EC9/DATAFILE/system.271.966100639
+DATA/AMBUE178/63619A18A02401A2E0530ACC009B0EC9/DATAFILE/sysaux.270.966100639
+DATA/AMBUE178/63619A18A02401A2E0530ACC009B0EC9/DATAFILE/users.274.966100657
63619A18A02401A2E0530ACC009B0EC9 <<<< is added the following to what would be expected output
Goal
This ??????????? is not mentioned anywhere in the documentation.
Oracle® Automatic Storage Management
Administrator's Guide
Chapter 5 Administering Oracle ASM Files, Directories, and Templates
About Oracle ASM File Names
Fully Qualified File Name Form
+diskgroup/dbname/?????????????/filetype/filetypetag.file.incarnation
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |