snapmanager 3.3 for oracle release notes...8 ibm system storage n series: snapmanager 3.3 for oracle...

IBM System Storage N series

SnapManager 3.3 for Oracle ReleaseNotes

GC27-2058-12

��

Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Generic limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Limitations related to standby databases . . . . . . . . . . . . . . . . . . . . . . 5SnapManager features and Oracle configurations not supported in Windows . . . . . . . . . 6

Fixed issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Profile sometimes might not open from the GUI after the password is reset by using the CLI . . . . 7Backup schedules cannot be viewed in the SnapManager GUI and CLI . . . . . . . . . . . 7Viewing of backup schedules fails when pruning is enabled . . . . . . . . . . . . . . . 7Clone create operation fails when the default temporary tablespace is not available . . . . . . . 8Redo log files are not archived during an archive log-only backup operation . . . . . . . . . 8You cannot add multiple values for some parameters in the clone specification . . . . . . . . . 8Snapshot copies associated with the cloned volume are deleted after the clone split operation . . . . 8Operations fail in the NFSv4 environment in Data ONTAP operating in 7-Mode . . . . . . . . 8

Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Backup creation of database involving control files fails when using NFS or dNFS . . . . . . . 10The SnapDrive daemon fails to start when you use Emulex OneCommand Manager 6.1 . . . . . 11SnapDrive dataset operations fail when performed from tertiary storage. . . . . . . . . . . 11Cloning operation fails if the audit trail parameter is assigned multiple values . . . . . . . . 11The primary backup retention for pre-created datasets is not managed by SnapManager . . . . . 11Cloning of online backups to remote host fails if the group ID is different for the source and remotehosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12SnapManager operations fail when running parallel operations . . . . . . . . . . . . . . 12Clone operation fails for a Snapshot copy that was created by using SnapVault . . . . . . . . 13Restore from the protected backup copy fails when the ASM disk group has multiple disks and allthe disks reside on the same volume in the multipath environment . . . . . . . . . . . . 13Restore or clone operation of filespec from backups fails . . . . . . . . . . . . . . . . 14Database clone creation fails in an NFS environment . . . . . . . . . . . . . . . . . 14The members of the dataset are not included in the backup but they still exist in the host . . . . . 14Backup schedules are triggered from multiple hosts after the profile is updated for the new host in aRAC environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Profile creation succeeds even when invalid Oracle account details are specified . . . . . . . . 15Profile generation fails after the clone split operation . . . . . . . . . . . . . . . . . 15Database operations might fail on Red Hat Enterprise Linux 4 Update 7 if the device name ends witha letter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SnapManager for Oracle incorrectly starts the database in the nomount state . . . . . . . . . 16SnapManager for Oracle cannot clone, restore, or mount the last protected backup that is freed fromthe primary storage system . . . . . . . . . . . . . . . . . . . . . . . . . . 17Unable to unmount a backup in WSFC and MSCS cluster environments. . . . . . . . . . . 17Backup clone operations fail in WSFC and MSCS cluster environments . . . . . . . . . . . 17

© Copyright IBM Corp. 2013 iii

Scheduled backups fail to run in the active node after HACMP failover in MSCS and WSFC clusterenvironments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Changes to known issues . . . . . . . . . . . . . . . . . . . . . . . . . 19

Documentation resources . . . . . . . . . . . . . . . . . . . . . . . . . 21

Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . 25Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

iv IBM System Storage N series: SnapManager 3.3 for Oracle Release Notes

Overview

These release notes contain information about new features and limitations ofSnapManager 3.3 for Oracle. Further, the release notes include descriptionsabout fixed issues and known issues of the software. Updates and additionsto the documentation of SnapManager 3.3 for Oracle are also provided.

© Copyright IBM Corp. 2013 1

2 IBM System Storage N series: SnapManager 3.3 for Oracle Release Notes

New features

SnapManager 3.3 for Oracle includes the following new and enhancedfeatures:v Support for sqlnet.authentication_services=NONE for

database-authenticated profiles onlyv Flexible cloning

– Manually roll forward a cloned database to the desired point in time– Manually configure a cloned database to a standby database

v Enhanced profile management– Ability to change the profile name and password

v Improved SnapManager scalability and performancev Support for managing the primary backup retention for all new datasets

created using SnapDrive 5.1 for UNIXRelated information:

IBM N series support website

IBM N series interoperability matrix


http://www.ibm.com/storage/support/nseries/http://www.ibm.com/systems/storage/network/interophome.html

Limitations

SnapManager 3.3 for Oracle has the following limitations:v “Generic limitations”v “Limitations related to standby databases”v “SnapManager features and Oracle configurations not supported in

Windows” on page 6

Note: For the complete list of limitations, see the SnapManager 3.3 for OracleInstallation and Administration Guide.

Generic limitations

SnapManager 3.3 for Oracle has the following generic limitations:v SnapManager does not support Live Partition Mobility (LPM) and Live

Application Mobility (LAM).v SnapManager does not support Oracle Wallet Manager and transparent

data encryption (TDE).v If a profile is renamed after performing a rolling upgrade of a

SnapManager server, rollback of the SnapManager server is not possible.v SnapManager does not support vaulting of backups using the smsv script

included with SnapDrive for UNIX.v SnapManager operations might fail if the Oracle database language is not

set to English.v When you install SnapManager on Windows and start the CLI in UNIX, the

features not supported on Windows are displayed.

Limitations related to standby databases

SnapManager 3.3 for Oracle has the following limitations related to Standbydatabases:v SnapManager does not support logical standby databases.v SnapManager does not support standby databases with the Active Data

Guard option.v SnapManager does not allow online backups of standby databases.v SnapManager does not allow partial backups of standby databases.v SnapManager does not allow restoring of standby databases.v SnapManager does not allow pruning of archive log files for standby

databases.


SnapManager features and Oracle configurations not supported in Windows

SnapManager 3.3 for Oracle does not support the following features,platforms, and Oracle technologies on Windows:v Policy-based data protection available with the integration of the N Series

Management Console data-protection capabilityv Role-based access control (RBAC) available with the integration of

Operations Managerv Fast restore or volume-based SnapRestore (VBSR)v Clone split operation Oracle Real Application Clusters (RAC) using any

protocolv Oracle Automatic Storage Management (ASM) using any protocolv Oracle Direct NFS (dNFS)v Itanium-64 platforms

Note: The supported hardware platforms for the Windows operating systemare 32 bit (Windows x86) and 64 bit (Windows x86_64).


Fixed issues

The following issues have been fixed in SnapManager 3.3 for Oracle:v “Profile sometimes might not open from the GUI after the password is reset

by using the CLI”v “Backup schedules cannot be viewed in the SnapManager GUI and CLI”v “Viewing of backup schedules fails when pruning is enabled”v “Clone create operation fails when the default temporary tablespace is not

available” on page 8v “Redo log files are not archived during an archive log-only backup

operation” on page 8v “You cannot add multiple values for some parameters in the clone

specification” on page 8v “Snapshot copies associated with the cloned volume are deleted after the

clone split operation” on page 8v “Operations fail in the NFSv4 environment in Data ONTAP operating in

7-Mode” on page 8

Profile sometimes might not open from the GUI after the password is reset byusing the CLI

After you reset the profile password by using the command-line interface(CLI), sometimes the profile might not open from the graphical user interface(GUI) when you use the new password. This issue occurs because the newpassword set by using the CLI does not get updated in the GUI.

Backup schedules cannot be viewed in the SnapManager GUI and CLI

If you have upgraded from SnapManager 3.1 to 3.2, you cannot view thebackup schedules created in the earlier version in the SnapManager graphicaluser interface (GUI) and command-line interface (CLI).

Viewing of backup schedules fails when pruning is enabled

When you create a backup schedule with pruning enabled in a newinstallation of SnapManager 3.2, you cannot view the backup schedules in theSnapManager GUI and CLI. The NullPointerException error message isdisplayed and logged in the SnapManager server logs.


Clone create operation fails when the default temporary tablespace is notavailable

When the default temporary tablespace is not available, the clone createoperation fails with the following error message: SMO-13032: Cannot performoperation: Clone Create. Root cause: ORACLE-10003: Error executing SQL"SELECT STATUS FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = ’TEMP’"against Oracle database NFT11MSV: ORA-25153: Temporary Tablespace isEmpty

From SnapManager 3.3, the clone create operation succeeds even if the defaulttemporary tablespace is not available.

Note: SnapManager creates the tablespace files during the clone createoperation.

Redo log files are not archived during an archive log-only backup operation

In an archive log-only backup operation, SnapManager does not archive theredo log files as is done in the online database backup process.

You cannot add multiple values for some parameters in the clone specification

You cannot add multiple values for the db_file_name_convert orlog_file_name_convert parameter in the clone specification file.

Snapshot copies associated with the cloned volume are deleted after the clonesplit operation

When a clone is split from its underlying parent volume, the Snapshot copiesassociated with the cloned volume are deleted as a result of the clone splitoperation. The backups created for the cloned database before the clone splitoperation cannot be used, because these backups do not have any Snapshotcopies, and remain as stale entries in the repository.

Operations fail in the NFSv4 environment in Data ONTAP operating in 7-Mode

If NFSv2 and NFSv3 or one of these protocols are disabled in Data ONTAPoperating in 7-Mode, operations in the NFSv4 environment fail.

However, NFSv4 is supported when nfs.v2.enable and nfs.v3.enable are setto on in Data ONTAP operating in 7-Mode.


Known issues

SnapManager 3.3 for Oracle has the following known issues:v “Backup creation of database involving control files fails when using NFS

or dNFS” on page 10v “The SnapDrive daemon fails to start when you use Emulex OneCommand

Manager 6.1” on page 11v “SnapDrive dataset operations fail when performed from tertiary storage”

on page 11v “Cloning operation fails if the audit trail parameter is assigned multiple

values” on page 11v “The primary backup retention for pre-created datasets is not managed by

SnapManager” on page 11v “Cloning of online backups to remote host fails if the group ID is different

for the source and remote hosts” on page 12v “SnapManager operations fail when running parallel operations” on page

12v “Clone operation fails for a Snapshot copy that was created by using

SnapVault” on page 13v “Restore from the protected backup copy fails when the ASM disk group

has multiple disks and all the disks reside on the same volume in themultipath environment” on page 13

v “Restore or clone operation of filespec from backups fails” on page 14v “Database clone creation fails in an NFS environment” on page 14v “The members of the dataset are not included in the backup but they still

exist in the host” on page 14v “Backup schedules are triggered from multiple hosts after the profile is

updated for the new host in a RAC environment” on page 15v “Profile creation succeeds even when invalid Oracle account details are

specified” on page 15v “Profile generation fails after the clone split operation” on page 15v “Database operations might fail on Red Hat Enterprise Linux 4 Update 7 if

the device name ends with a letter” on page 16v “SnapManager for Oracle incorrectly starts the database in the nomount

state” on page 16v “SnapManager for Oracle cannot clone, restore, or mount the last protected

backup that is freed from the primary storage system” on page 17


v “Unable to unmount a backup in WSFC and MSCS cluster environments”on page 17

v “Backup clone operations fail in WSFC and MSCS cluster environments” onpage 17

v “Scheduled backups fail to run in the active node after HACMP failover inMSCS and WSFC cluster environments” on page 18

Backup creation of database involving control files fails when using NFS ordNFS

If you are using Direct NFS (dNFS) or a Network File System (NFS) to createa backup of the database involving control files, the operation fails. Thefollowing error message is displayed:

-- [ERROR] SMO-11014: File /mnt/oractl/SMOBakCtl_1348450244301_2 doesnot exist in the filesystem.

SnapManager for Oracle uses SQL*Plus to create the backup control files andstores them in the storage system by using dNFS or an NFS. WhenSnapManager for Oracle tries to read the control file by using kNFS, thestorage system checks the local NFS cache area. The file cannot be foundbecause dNFS or an NFS does not populate the kNFS cache.

Workaround: Mount control files with actimeo=0, so that the local cache isignored and all the requests go to the storage system.

Note: You should perform this action only if you are backing up a databaseinvolving control files and not datafiles.

Perform the following steps to set actimeo=0:1. Stop the database.2. Unmount the control file mountpoint.3. Edit the fstab file to include actimeo=0 as a mount option for the control

file mount points.4. Mount the control file mountpoint.5. Restart the database.


The SnapDrive daemon fails to start when you use Emulex OneCommandManager 6.1

The SnapDrive daemon fails to start when you use Emulex OneCommandManager 6.1 with Emulex LightPulse host bus adapters (HBAs). The followingerror message is displayed:

Unable to start daemon...check daemon log file for more details.

Workaround: Use Emulex OneCommand Manager 6.0.

SnapDrive dataset operations fail when performed from tertiary storage

The dataset operations, such as restore and cloning, fail from tertiary storage,if the protection policy is set to Mirror, then Back up. This issue occurs if youare using OnCommand Unified Manager 5.1.

Workaround: None.

Cloning operation fails if the audit trail parameter is assigned multiple values

If you assign xml, extended as values for the audit_trail parameter, theclone operation fails with the following error message:

--[ERROR] SMSAP-13032: Cannot perform operation: Clone Create. Rootcause: ORACLE-00001: Error executing SQL: [STARTUP NOMOUNT EXCLUSIVEPFILE= /u01/oracledb/product/11.2.0/dbhome_1/dbs/ initclonedb1.ora;].The command returned: ORA-01078: failure in processing systemparameters --[ INFO] SMSAP-07316: Shutting down database "clonedb1"

Workaround: Create the clone with xml assigned to the audit_trailparameter. Later, modify the audit_trail parameter to assign xml, extended.

For example, you can modify the audit_trail parameter value by entering thefollowing command:

alter system set audit_trail=xml,extended scope=spfile;

The primary backup retention for pre-created datasets is not managed bySnapManager

The primary backup retention for all new datasets created by using SnapDrive5.1 is managed by SnapManager. However, the primary backup retention forany datasets created using SnapDrive 5.0.1 or earlier are managed by theOnCommand Unified Manager server. Therefore, after upgrading to

Known issues 11

SnapDrive 5.1, all the pre-created datasets will still be managed by theOnCommand Unified Manager server and not by SnapManager.

Workaround: Run the dfpm dataset fix_smo command on the OnCommandUnified Manager server to allow SnapManager to manage the primary backupretention.

Note: You must run this command only once after upgrading to SnapDrive5.1.

Cloning of online backups to remote host fails if the group ID is different for thesource and remote hosts

When you try to clone the online backup to a remote host, the operationmight fail with the following error message:

ORA-00308: cannot open archived log and ORA-27041: unable to open file/ permission denied.

This issue occurs when the group ID is different for both the source andremote hosts.

Workaround: Perform one of the following:v Modify the group ID (GID) of the remote host to match the GID of the

source host.v Create an additional group in the remote host with the same GID as that of

the source host and map this to the user ID (UID) of the remote host.

SnapManager operations fail when running parallel operations

When you run multiple parallel SnapManager operations on various profilesin a single repository, sometimes the operations might fail with the followingerror message: SMO-09032: Failed to connect to repository: Io exception:Connection reset: [ORA-17002]. This problem occurs if you are notauthenticated within the time specified in theSQLNET.INBOUND_CONNECT_TIMEOUT parameter and the repository connection istimed out.

Workaround: Perform the following steps:1. Edit the sqlnet.ora file located at $ORACLE_HOME/network/admin.

If the file does not exist, create a new one.2. Update the SQLNET.INBOUND_CONNECT_TIMEOUT parameter with a value

higher than the default or existing value.3. Restart the listener.


Clone operation fails for a Snapshot copy that was created by using SnapVault

If you are using the N series Management Console with data protectioncapability, and try to clone a Snapshot copy that was created by usingSnapVault, the operation fails with the following error message: SD-10028:SnapDrive Error (id:2618 code:102) Unable to find the snapshot.

This problem occurs if you have not set the pmUseSDUCompatibleSnapshotNamesvalue to YES.

Workaround: Run the following Operations Manager command:

dfm options set pmUseSDUCompatibleSnapshotNames=Yes

Note: After setting the value, you do not have to restart SnapDrive for UNIX.

You can now create new backups, protect them, and then perform the cloneoperation on the newly protected backup.

Restore from the protected backup copy fails when the ASM disk group hasmultiple disks and all the disks reside on the same volume in the multipathenvironment

After you restore from the protected backup copy by using the direct storagemethod, the logical unit numbers (LUNs) have a new device mapper ID.Because of the new mapper ID, the Automatic Storage Management (ASM)instance does not discover the ASM disks as members and SnapManager failsto mount the ASM disk group. This issue occurs because of an Oracle bug(Oracle- SR: 3-6205944191).

Workaround: Before performing restore from the protected backup copy, addthe foreign files in the ASM disk group containing multiple LUNs from thesame volume.

Note: After adding the foreign files, you cannot perform a restore operationby using the volume-based restore method because volume-based restore isnot supported when there are foreign files in the volume. You can restore byusing only the storage-side file restore method. If you want to performvolume-based restore from the primary storage, the foreign files must bedeleted.

Known issues 13

Restore or clone operation of filespec from backups fails

If you are trying to restore or clone a filespec from the backups that werecreated before moving the primary volumes from one storage system toanother, the operation fails. This problem occurs because dataset backup_inforefers to the primary volumes residing on the old storage system.

Workaround: None.

Database clone creation fails in an NFS environment

After you upgrade to SnapDrive 5.1, in an NFS environment, SnapManagerfails to create database clones by using the secondary backups or on to thesecondary host (does not have export permissions on the parent volume).

The following error message is displayed:

0001-859 Admin error: The host's Host_Name interfaces, Interface_Namesare not allowed to access the path Volume_Path on the storage systemStorage_Name. To resolve this problem, please configure the exportpermission for path Volume_Path on the storage system Storage_Name sothat host Host_Name can access the path.

This issue occurs because the default value of the check-export-permission-nfs-clone parameter in the snapdrive.conf file is ON.

Workaround: You can perform one of the following:v Configure the export permissions for the volume so that the host can access

the volume.v Set the check-export-permission-nfs-clone parameter value to OFF.

The members of the dataset are not included in the backup but they still exist inthe host

While updating a protected profile to separate the archive log backups fromthe data files backup, if at least one of the archive log files is associated withthe dataset member, then while creating a backup, the following message isdisplayed:

The members of the dataset are not included in this backup but theystill exist in this host.

This issue occurs because SnapManager fails to delete archive log mount pointdataset members.


Workaround: If the dataset members are no longer in use, delete the datasetmembers from the host.

Backup schedules are triggered from multiple hosts after the profile is updatedfor the new host in a RAC environment

When the profile is updated for the new host in a RAC environment, backupschedules are triggered from multiple hosts. Because backup schedules aretriggered from multiple hosts, the schedule triggered from one of host failswith the error that it should be run from the other host.

Workaround: To delete the backup schedule from the host on which you donot want the schedule to be triggered, complete the following steps:1. Stop the SnapManager server.2. Delete the schedule file from the repositories directory located in the

SnapManager installation directory, from the host where you do not wantto trigger the schedule.The schedule file name will be in the following format:repository#repo_username#repository_database_name#repository_host#repo_port.Ensure that you delete the schedule file in the exact format that matchesthe repository details.If you find the schedule file name in the repository-repo_usernamerepository_ database_name-repository_host-repo_portformat, you can delete this file too.

3. Restart the SnapManager server.Open the other profiles under the same repository from the SnapManagerGUI to ensure that you do not miss any schedule information of thoseprofiles.

Profile creation succeeds even when invalid Oracle account details are specified

SnapManager does not validate the Oracle account details of a database whilecreating a profile.

Workaround: Ensure that you have a valid Oracle user account and Oracleuser group name values for the database before creating a profile for thedatabase.

Profile generation fails after the clone split operation

If the profile generation fails when a clone split operation is executed as anonroot user from the SnapManager CLI or GUI, then the failed profile getslisted when you run the profile list command.

Known issues 15

Workaround: Execute the profile sync command as a nonroot user toremove the failed profile entry.

Example

The following example demonstrates how you—as a nonroot user—can deletethe failed profile entry.

smo profile sync -repository -dbname repodb -host hostA -port 1521 -login -username userA -verbose[ INFO] SMO-20010: Synchronizing mapping for profiles in repository"userA@repodb/[hostA]:1521".[ INFO] SMO-20011: Loaded mapping for profile "PRFL".[ INFO] SMO-20012: Deleted stale mapping for profile "AUTOPRFL".

Database operations might fail on Red Hat Enterprise Linux 4 Update 7 if thedevice name ends with a letter

On an ASM and Linux multipathing I/O environment with Red HatEnterprise Linux, if the device name ends with a letter, SnapManager mightfail to perform database operations such as backup create, backup mount, andbackup verify with ASM on raw disk, clone create, and restore or recover ofonline tablespace with ASM on raw disk.

Workaround: Complete the following steps:1. Create a platform.override.txt file located in the SnapManager

installation directory.2. Update the major and minor versions of the operating system in the

versions.linux.rh5mpio configuration variable:versions.linux.rh5mpio=RHEL 5,RHEL 4U8,RHEL OS Major VersionUOSMinor Version

SnapManager for Oracle incorrectly starts the database in the nomount state

SnapManager for Oracle starts the database in the nomount state even if youdo not provide the -force option from the SnapManager CLI or select theAllow to startup or Shutdown the database checkbox from the SnapManagerGUI.

Workaround: None


SnapManager for Oracle cannot clone, restore, or mount the last protectedbackup that is freed from the primary storage system

SnapManager for Oracle cannot clone, restore, or mount the last protectedbackup that is freed from the primary storage system. An error messageappears describing why it failed. Protection Manager controls the secondarytransfer schedules.

Workaround: Create another protected backup, and mount, clone, or restorethe backup from the previous backup. Alternatively, you might want tocontact the storage administrator and ask for the backup to be transferred.

Unable to unmount a backup in WSFC and MSCS cluster environments

In Windows Server Failover Clustering (WSFC) and Microsoft Cluster Service(MSCS), the unmount backup operation fails and an authentication errormessage is displayed. In Windows cluster environments, when you performthe backup operation, SnapManager does not store the host credentials in theclient cache. While performing the unmount backup operation, the clientcommunicates with the node and tries to authenticate the node. The operationfails and an authentication error message is displayed because the credentialsof the node are not available in the client cache.

Workaround: Create dummy profiles for all the nodes in a cluster by usingthe host name of each node. These profiles must be authenticated, so thatSnapManager stores the credentials of the node in the client cache. You mustensure that the SnapManager server is running on the physical node, which isstored in the repository.

Backup clone operations fail in WSFC and MSCS cluster environments

If the mount points specified in the clone specification file are shared andSnapManager tries to clone a backup in WSFC and MSCS, the clone operationfails. The clone operation fails with the following error message:

SD-10016: Error executing snapdrive command "snap mount F:\ ->F:\_RET": Operating System does not support mounting non-shared disk ona shared volume. Please change disk type or select different mountpoint.

Workaround: Edit the clone specification file to specify the non-shared disk asthe mount point.

Known issues 17

Scheduled backups fail to run in the active node after HACMP failover in MSCSand WSFC cluster environments

After HACMP failover in Windows cluster environments (MSCS and WSFC),the scheduled backups do not run in the active node. This issue occursbecause SnapManager does not know about the HACMP failover.

Workaround: Restart the SnapManager server.


Changes to known issues

Topics moved to Installation and Administration Guide

The following topic has been moved to the SnapManager for Oracle Installationand Administration Guide:v Archive log file pruning fails with RMAN exceptionv Online backup fails if Oracle database is not in Englishv SnapManager log files have read-write permissions for the root usersv SnapManager does not support vaulting of backup using the

post-processing script

Topics removed

The following topic has been removed because it is not an issue anymore:v Unmount operation fails for a mounted backup after failover in the WSFC

cluster environment


Documentation resources

The following table describes where to find additional information aboutSnapManager 3.3 for Oracle.

To learn about... Go to this information source...

The latest supported configurations www.ibm.com/storage/support/nseries/

Supported Fibre Channel SAN topologies The SAN Configuration Guide (called FibreChannel and iSCSI Configuration Guide inData ONTAP 8.1 and earlier)

How to download and installSnapManager for Oracle

The SnapManager 3.3 for Oracle Installationand Administration Guide

Configuring your host for the HostUtilities

The HP-UX Host Utilities Installation andSetup Guide

The Linux Host Utilities Installation andSetup Guide

The AIX Host Utilities Installation andSetup Guide

The Windows Host Utilities Installation andSetup Guide


http://www.ibm.com/storage/support/nseries/

Websites

IBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates. Thefollowing web pages provide N series information:v A listing of currently available N series products and features can be found

at the following web page:www.ibm.com/storage/nas

v The IBM System Storage N series support website requires users to registerin order to obtain access to N series support content on the web. Tounderstand how the N series support web content is organized andnavigated, and to access the N series support website, refer to the followingpublicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well asother important N series product resources.

v IBM System Storage N series products attach to a variety of servers andoperating systems. To determine the latest supported attachments, go to theIBM N series interoperability matrix at the following web page:www.ibm.com/systems/storage/network/interophome.html

v For the latest N series hardware product documentation, includingplanning, installation and setup, and hardware monitoring, service anddiagnostics, see the IBM N series Information Center at the following webpage:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp


http://www.ibm.com/storage/nashttp://www.ibm.com/storage/support/nseries/http://www.ibm.com/systems/storage/network/interophome.htmlhttp://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Copyright and trademark information

This section includes copyright and trademark information, and importantnotices.

Copyright information

Copyright ©1994 - 2013 Network Appliance, Inc. All rights reserved. Printedin the U.S.A.

Portions copyright © 2013 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services donot imply that IBM intends to make these available in all countries in whichIBM operates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM’s product, program, or service maybe used. Any functionally equivalent product, program, or service that doesnot infringe any of IBM’s or NetApp’s intellectual property rights may beused instead of the IBM or NetApp product, program, or service. Evaluationand verification of operation in conjunction with other products, except thoseexpressly designated by IBM and NetApp, are the user’s responsibility.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to thefollowing license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,


INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty rights of NetApp.

The product described in this manual may be protected by one or more U.S.A.patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofthe Rights in Technical Data and Computer Software clause at DFARS252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the Web at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,


FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster,MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro,OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, ServiceBuilder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Copyright and trademark information 27

Notices

This information was developed for products and services offered in theU.S.A.

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.


Notices 31

��

NA 210-06148_A0, Printed in USA

GC27-2058-12

IBM System Storage N series SnapManager 3.3 for Oracle Release NotesContentsOverviewNew featuresLimitationsGeneric limitationsLimitations related to standby databasesSnapManager features and Oracle configurations not supported in Windows

Fixed issuesProfile sometimes might not open from the GUI after the password is reset by using the CLIBackup schedules cannot be viewed in the SnapManager GUI and CLIViewing of backup schedules fails when pruning is enabledClone create operation fails when the default temporary tablespace is not availableRedo log files are not archived during an archive log-only backup operationYou cannot add multiple values for some parameters in the clone specificationSnapshot copies associated with the cloned volume are deleted after the clone split operationOperations fail in the NFSv4 environment in Data ONTAP operating in 7-Mode

Known issuesBackup creation of database involving control files fails when using NFS or dNFSThe SnapDrive daemon fails to start when you use Emulex OneCommand Manager 6.1SnapDrive dataset operations fail when performed from tertiary storageCloning operation fails if the audit trail parameter is assigned multiple valuesThe primary backup retention for pre-created datasets is not managed by SnapManagerCloning of online backups to remote host fails if the group ID is different for the source and remote hostsSnapManager operations fail when running parallel operationsClone operation fails for a Snapshot copy that was created by using SnapVaultRestore from the protected backup copy fails when the ASM disk group has multiple disks and all the disks reside on the same Restore or clone operation of filespec from backups failsDatabase clone creation fails in an NFS environmentThe members of the dataset are not included in the backup but they still exist in the hostBackup schedules are triggered from multiple hosts after the profile is updated for the new host in a RAC environmentProfile creation succeeds even when invalid Oracle account details are specifiedProfile generation fails after the clone split operationDatabase operations might fail on Red Hat Enterprise Linux 4 Update 7 if the device name ends with a letterSnapManager for Oracle incorrectly starts the database in the nomount stateSnapManager for Oracle cannot clone, restore, or mount the last protected backup that is freed from the primary storage systeUnable to unmount a backup in WSFC and MSCS cluster environmentsBackup clone operations fail in WSFC and MSCS cluster environmentsScheduled backups fail to run in the active node after HACMP failover in MSCS and WSFC cluster environments

Changes to known issuesDocumentation resourcesWebsitesCopyright and trademark informationTrademark information

Notices

snapmanager 3.3 for oracle release notes...8 ibm system storage n series: snapmanager 3.3 for oracle...

Documents