HP P6000 Replication Solutions Manager Administrator Guide (T3680-96069, June 2012)

• archive log list;
Issues the archive log command with the list parameter. The command output looks
similar to this:
Archive ModeDatabase log mode
EnabledAutomatic archival
H:\archiveArchive destination
312Oldest online log sequence
313Next log sequence to archive
313Current log sequence
Identify the current log sequence number (313 in this exapmple), which shows the output from
SQL *Plus being redirected to a log file.
• alter system switch logfile;
Forces a log file switch. Oracle stops recording redo information in the current log sequence
number and forces a switch to the next sequential log file (314 in this example). The log file
that was current (313) is then archived. The oldest online log sequence identified in the PRE
routine and the current log sequence from this POST routine now specify the entire range of
archived redo logs that must be backed up in order to ensure a complete recovery. The
snapshots and snapclones that were just created will not contain the most recent log; therefore
they must be backed up separately, as must any additional logs that are generated. You can
do this using another replication manager job or outside the replication manager.
• quit;
Exits SQL *Plus and returns control to the replication manager job.
When the POST routine is complete, the specified tablespaces are taken out of online backup
mode. The replication manager can now present and mount the snapshot and snapclone copies
on the specified host.
Determining which volumes need to be replicated
Most Oracle databases consist of multiple storage volumes. Because the unit of online backup for
Oracle is the tablespace, any replication manager jobs you create must take into account that a
single tablespace can span multiple volumes. If that is the case, you must create a replica of every
volume that contains a portion of the tablespace. For example, if your Oracle implementation
involves four volumes (E:, F:, G:, and H:) and four tablespaces (SYSTEM, USER, TEMP, and WEB),
assume the data files for these tablespaces are located as follows:
Volume E:
Data file #1 for SYSTEMSYSTEMorc1.ora
Data file #1 for USERUSERorc1.ora
Data file #1 for TEMPTEMPorc1.ora
Data file #1 for WEBWEBorc1.ora
Volume F:
Data file #2 for SYSTEMSYSTEMorc2.ora
Data file #2 for USERUSERorc2.ora
70 Using the replication manager with Oracle tools