HP Data Protector Software A.06.00 Instant Recovery of Oracle databases using Automatic Storage Management (ASM) feature

Enabling atomic split
Atomic split support is enabled and controlled through three omnirc variables:
 SSEA_ATOMIC_SPLIT
0 Disabled (default)
1 Enabled
 SSEA_ATOMIC_SPLIT_MULTIPLE_CTGROUPS
0 Strict mode (default)
Only one CT group inside a ZDB is allowed. For an Oracle ASM environment, it is expected to
operate in STRICT mode.
1 Multiple mode
Multiple CT groups are allowed inside a ZDB, but each CT group is split individually.
 SSEA_ATOMIC_SPLIT_MIXED_CONFIG
0 Simple mode (default)
Any LDEVs in the backup outside the CT groups will cause a session failure.
1 Mixed mode
LDEVs outside a CT group are allowed in the session. These LDEVs will be split serially by the array
agent, while the CT group is split atomically. This is intended for compatibility where a system
requires both atomic split and normal behavior.
All LDEVs that belong to a CT group must be part of a backup session. Any LDEVs that are part of the
CT group, but are not connected to the backup session, will cause the session to fail. Splitting of a CT
group splits all LDEVs and the splitting of LDEVs that are not part of the ZDB is potentially disruptive to
the environment.
The following Data Protector A.06.00 Installation Server patches deliver the atomic split feature:
1. On HPUX PARISC
 PHSS_38661 (SSEA)
 PHSS_39015 (CORE)
2. On HP-UX Integrity
 PHSS_38662 (SSEA)
 PHSS_39016 (CORE)
Instant Recovery procedures for ASM-based databases
Instant Recovery in a standalone environment
1. Shut down the database instance manually on the application host.
2. Start the Instant Recovery procedure through the Data Protector GUI’s Instant Recovery context.
3. After the recovery, the database instance will be in one of three states depending on what options
were selected on the options tab when starting the IR session: