Performing Oracle User-Managed Backups - OCP: Oracle Database 12c Administrator Certified Professional - page 48

C:\oracle\diag\rdbms\orcl\orcl\trace>dir
Volume in drive C has no label.
Volume Serial Number is 08DE-E1AB
Directory of C:\oracle\diag\rdbms\orcl\orcl\trace
08/02/2013 03:38 PM <DIR> .
08/02/2013 03:38 PM <DIR> ..
08/02/2013 03:38 PM 1,027,520 alert_orcl.log
08/02/2013 03:38 PM 9,572 orcl_ora_12120.trc
08/02/2013 03:38 PM 91 orcl_ora_12120.trm
4 File(s) 1,037,183 bytes
4 Dir(s) 9,964,507,136 bytes free
The trace file is called orcl_ora_12120.trc (it's easy to tell since there are no other trace
files in the directory). If you have a number of trace files in the directory, you can sort the
contents ascending by date and time and generally the correct trace file will be at the top
(i.e., the LS -ALT command). Also, the V$PROCESS view has a TRACEFILE column in it
that will display the name of the trace file for that process.
Another option with the ALTER DATABASE BACKUP CONTROLFILE TO TRACE command is
to define an alternate location for the trace file. The syntax for this command is as follows:
alter database backup controlfile to trace as '/tmp/my_control_trace.trc';
If you look in the file, you will find a trace-file header in it first. Later down the trace
file, you will find two different versions of the CREATE CONTROLFILE command. Here is an
example of the CREATE CONTROLFILE command that you might find in this file:
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 'C:\ORACLE\ORADATA\ORCL\REDO01.LOG' SIZE 50M,
GROUP 2 'C:\ORACLE\ORADATA\ORCL\REDO02.LOG' SIZE 50M,
GROUP 3 (
'C:\ORACLE\ORADATA\ORCL\REDO03A.LOG',
'C:\ORACLE\ORADATA\ORCL\REDO03B.LOG'
) SIZE 100M
-- STANDBY LOGFILE
DATAFILE
'C:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF',
'C:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF',