Database Reference
In-Depth Information
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1 770 SYSTEM *** +DATA/CDB2/DATAFILE/system.288.823542809
3 660 SYSAUX *** +DATA/CDB2/DATAFILE/sysaux.279.823542829
4 85 UNDOTBS1 *** +DATA/CDB2/DATAFILE/undotbs1.284.823542885
5 250 PDB$SEED:SYSTEM *** +DATA/CDB2/E40..C51/DATAFILE/system.285.823542883
6 5 USERS *** +DATA/CDB2/DATAFILE/users.283.823542887
7 590 PDB$SEED:SYSAUX *** +DATA/CDB2/E40...C51/DATAFILE/sysaux.280.823542845
8 260 MASTER:SYSTEM *** +DATA/CDB2/E40...53A/DATAFILE/system.286.823542875
9 590 MASTER:SYSAUX *** +DATA/CDB2/E40...53A/DATAFILE/sysaux.287.823542861
10 5 MASTER:USERS *** +DATA/CDB2/E40...53A/DATAFILE/users.282.823542887
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1 60 TEMP 32767 /u01/oradata/CDB2/temp01.dbf
2 20 PDB$SEED:TEMP 32767 /u01/oradata/CDB2/pdbseed/pdbseed_temp01.dbf
3 20 MASTER:TEMP 32767 /u01/oradata/CDB2/MASTER/temp01.dbf
RMAN>
You can see that the permanent tablespaces have been switched, but not the temp files. This can be corrected
by adding a new temp file to the tablespace TEMP and dropping the existing one. The last part of the database to be
migrated are the online redo logs. The strategy to move those into ASM requires the creation of a new set of groups
within ASM, and dropping the old ones. First you need to check the status of your current online redo logs, still on the
file system.
SQL> select group#,thread#,sequence#,bytes,status
2 from v$log;
GROUP# THREAD# SEQUENCE# BYTES STATUS
---------- ---------- ---------- ---------- ----------------
1 1 13 52428800 INACTIVE
2 1 14 52428800 CURRENT
3 1 12 52428800 INACTIVE
A total number of three groups are required, which can be added using the alter database add logfile command.
The difficult bit is dropping the existing groups. If the group is needed by Oracle you will not be able to drop it.
Instead, you have to switch the logfile and try again.
When you are done with the migration, you should take a full backup of the database. In this context a full backup
is either a level 0 or a “full” backup as per the RMAN terminology.
Search WWH ::
Custom Search