Databases Reference
In-Depth Information
ASMCMD [+dg1/rman] > ls
ASMCMD [+dg1/rman] > cd +DG1/IDB1
ASMCMD [+DG1/IDB1] > ls
TEMPFILE/
There is no directory called BACKUPSETS anymore. Since ASM created that directory for you, ASM will delete it
when it is no longer needed.
Now that you know that the actual files created will be different from the names you gave and they will be under
directories different from what you gave, should you bother creating directories under the ASM disk group? In our
opinion, you should. It will be easier to locate and administer backup pieces in that location rather than directly on
the DG1 disk group. If you have multiple databases being backed up to the same disk group, putting them under
different directories will make organization a breeze. Remember, RMAN repository—whether controlfile or
catalog—knows about the aliases alone, not the real file. So, you might find it useful to organize backups under
appropriately named directories, leaving ASM to create the necessary system directories and files as needed.
Specifying ASM Diskgroups as Archivelog Locations
Problem
You want to define the archived logs to go to an ASM disk group instead of to a file system.
Solution
Suppose you want archived logs to go into a disk group called +DG. Use the following steps:
1.
Set the log_archive_dest_1 parameter in the database:
SQL> alter system set log_archive_dest_1 = 'LOCATION=+DG1';
System altered.
2.
Enable that destination, if not enabled already:
SQL> alter system set log_archive_dest_state_1 = enable;
System altered.
3.
Confirm that the archived log location is set:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +DG1
Oldest online log sequence 92
Next log sequence to archive 94
Current log sequence 94
The output “
Archive destination +DG1
” confirms that the location was set properly.
