IBM Support

IBM Tivoli Storage Manager for Databases: Data Protection for Oracle V7.1 documentation updates

Product documentation


Abstract

This document contains documentation updates for IBM Tivoli Storage Manager for Databases: Data Protection for Oracle V7.1.

Content

The release notes for Tivoli Storage Manager for Databases are available online at:

http://www.ibm.com/support/knowledgecenter/SSTFZR_7.1.4/db.sql/relnote_dpsql71.html

----------------------------------------------------------------------------------------------------------------------------------------------
(IT02697) The following information is an addition to the content published for IBM Tivoli Storage Manager for Databases Version 7.1.0, Data Protection for Oracle for Windows, Installation and User's Guide

Configuring Data Protection for Oracle -> Configuration with default settings -> Step 5

Additional information for step 5 ->

For Oracle 12c Release 1 (12.1) and later releases, the Oracle home user that is specified on installation of the Oracle database must be granted sufficient permission to access the Windows registry. Otherwise, Data Protection for Oracle operations might fail.

----------------------------------------------------------------------------------------------------------------------------------------------

Update to the LAN-free data transfer with Data Protection for Oracle information.

The following sentence is not correct:
"Before you enable LAN-free support, you must install the Tivoli Storage Manager Managed System for SAN Storage Agent on the same system as Data Protection for Oracle. "

Correct information:
"Data Protection for Oracle can be installed on a client without the Storage Agent (STA). The agents can be installed on a non-STA client. The backup data is sent over the LAN (TCP/IP) to the STA client. The STA client sends the data over the SAN LAN-free, directly to tape or disk."

You can see all of the Tivoli Storage Manager for Databases: Data Protection for Oracle V7.1.0 information online at http://www.ibm.com/support/knowledgecenter/SSTFZR_7.1.0/com.ibm.itsm.db.orc.doc/t_protect_dpdborc.html.



The following information is an addition to the content published for IBM Tivoli Storage Manager for Databases Version 7.1, Data Protection for Oracle for Windows, Installation and User's Guide.


Update to the Configuring Data Protection for Oracle > Configuring Data Protection for Oracle > Define Tivoli Storage Manager options in the client options file > Other options topic

To run Data Protection for Oracle in a LAN-free environment, you must specify an additional option that was not previously documented in this topic. Use the lanfreetcpserveraddress option to specify the TCP/IP address for the Tivoli Storage Manager storage agent.

The omission is corrected in the following Knowledge Center topics. A comment added to the first topic points users to the information in the second topic.

1)
http://www-01.ibm.com/support/knowledgecenter/SSTFZR_7.1.0/com.ibm.itsm.db.orc.doc/r_dporc_cfg_otheroptions.html

2)http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_bac_lanfreeopts.html

This information will be included in the next revision of the Tivoli Storage Manager for Databases: Data Protection for Oracle for Windows, Installation and User's Guide.

----------------------------------------------------------------------------------------------------------------------------------------------

(IT07038) The following information is a clarification to the content published for IBM Tivoli Storage Manager for Databases Version 7.1 and later, Data Protection for Oracle for UNIX and Linux

Configuring Data Protection for Oracle -> Configuration with default settings

There is no immediate need for changing operational environments which are set up according to the existing instructions because
these environments continue to work until the client node password expires. When the password expires, the current instructions are not compatible with successful password renewal by 'passwordaccess generate' when using Data Protection for Oracle with the client scheduler.

At password expiration, when storing the new node credentials to TSM.PWD, 'passwordaccess generate' couples the password with
the 'servername' from dsm.sys.

Because of the differently named stanzas 'servername TSMOracle' and 'servername DPSched', the password will become out of sync between Data Protection for Oracle and the scheduler.

In addition, the existing instructions, when applied to new setups, should use the following guidance:

  • Instead of using 'passwordaccess prompt', use 'passwordaccess generate'.
  • Make sure the dsm.sys file for the backup-archive client /usr/tivoli/tsm/client/ba/bin64/dsm.sys is not linked with the API client dsm.sys file /usr/tivoli/tsm/client/api/bin64/dsm.sys. For some options, identical values in both files can lead to a malfunction.

Protecting Oracle Server data -> Using the Tivoli Storage Manager scheduler with Data Protection for Oracle -> Setting up a schedule example -> Setting up a schedule on the client machine (NodeA1)

Add the following information:

Security
In a default installation, the Tivoli Storage Manager client's trusted communications agent (dsmtca) allows both root access for the scheduler and non-root access for Data Protection for Oracle to read and write the same password file TSM.PWD in 'passworddir'. If your system is set up otherwise, see the "Enable non-administrators to manage their own data" topic in the Tivoli Storage Manager client manual.

Create 'servername' stanzas in both dsm.sys files by the same 'servername' as in the dsmi_orc_config file which is set in your TDPO_OPTFILE.

For Data Protection for Oracle, the stanza must be in /usr/tivoli/tsm/client/api/bin64/dsm.sys

For the scheduler associated with Data Protection for Oracle a stanza by the same 'servername' must be in /usr/tivoli/tsm/client/ba/bin64/dsm.sys

Ensure the following 6 options are identical in both files:
  • servername TSMOracle
  • tcpserveraddress site.xyzinc.com
  • tcpport 1500
  • nodename NodeA1
  • passwordaccess generate
  • passworddir /home/oracle

Other options can or even must be different in both files.

To the stanza 'servername TSMOracle' in /usr/tivoli/tsm/client/api/bin64/dsm.sys, you can add options specific to Data Protection for Oracle, for example:
INCLUDE /adsmorc/.../DB* mgmtclassnameforDBs
INCLUDE /adsmorc/.../LOG* mgmtclassnameforLogs
enablelanfree yes
lanfreecommmethod sharedmem
* errorlogname /home/oracle/dsierror__NodeA1.log

When the option DSMI_LOG is set in your TDPO_OPTFILE to point to a directory with read and write permissions for the Oracle user, you don't need to set 'errorlogname' in /usr/tivoli/tsm/client/api/bin64/dsm.sys.

However, if you decide to set 'errorlogname' for Data Protection for Oracle, then its value must be different from 'errorlogname' in
/usr/tivoli/tsm/client/ba/bin64/dsm.sys, to prevent concurrent write access to the same file by Data Protection for Oracle running as oracle user and the scheduler running as root.

To the stanza 'servername TSMOracle' in /usr/tivoli/tsm/client/ba/bin64/dsm.sys
you may add scheduler specific options, for example:
schedmode prompted
tcpclientport 1502
schedlogname /home/root/dsmsched_NodeA1.log
* commmethod tcpip <- unnecessary because it's default.
errorlogname /home/root/dsmerror_NodeA1.log

Note 1
When using 'passwordaccess generate', the options TDPO_NODE, TDPO_OWNER and TDPO_PSWDPATH must not be set in your TDPO_OPTFILE.

Note 2
The temporary switching from 'passwordaccess generate' to 'passwordaccess prompt' can become necessary when existing Oracle backups in TSM storage with a certain OWNER need to be accessed by a user with a different user name, for example, when restoring a database to a system with another Oracle user name. In this type of situation you can avoid the typical restore error
ANS1302E (RC2) No objects on server match query by setting /usr/tivoli/tsm/client/api/bin64/dsm.sys to 'passwordaccess prompt', because this allows specifying a TDPO_OWNER in your TDPO_OPTFILE, who is different from the name of the user who is restoring the data.

For this scenario you also have to complete the following steps:
a) set TDPO_NODE and TDPO_PSWDPATH in your TDPO_OPTFILE and
b) rerun 'tdpoconf password'


----------------------------------------------------------------------------------------------------------------------------------------------
The following information is a clarification to the content published for IBM Tivoli Storage Manager for Databases Version 7.1 and later, Data Protection for Oracle for UNIX and Linux

Configuring Data Protection for Oracle -> Configuration with default settings

In the Before you begin section, the following note was added to highlight that the listed link was not relevant for Linux operating systems.

After Data Protection for Oracle is installed, make sure that the following link exists:
$ORACLE_HOME/lib/libobk.a -> /usr/lib/libobk64.a

Note:If you are using Linux as your operating system, this link is not required.

In the Procedure section, the following information was added to explain the directory paths for the different operating systems.

Procedure
1. Depending on your operating system, change your directory to one of the following:
AIX® 64-bit operating system:/usr/tivoli/tsm/client/oracle/bin64
Linux operating system:/opt/tivoli/tsm/client/oracle/bin64
Windows 32-bit Server system: C:\Program Files\Tivoli\TSM\AgentOBA
Note: For a Windows 64-bit Server system, the directory is C:\Program Files\Tivoli\TSM\AgentOBA64. All other aspects of the installation are the same as for the 32-bit Server system.”

You can see all of the Tivoli Storage Manager for Databases: Data Protection for Oracle V7.1.0 information online at the following link: http://www.ibm.com/support/knowledgecenter/SSTFZR_7.1.0/com.ibm.itsm.db.orc.doc/t_protect_dpdborc.html.


--------------------------------------------------------------------------------------------------------------
(IT11447) Documentation contains duplicate and obsolete information

The IBM Tivoli Storage Manager for Databases: Data Protection for Oracle 7.1.3 documentation includes a topic entitled: Setting up a schedule on the client machine NodeA1, which contains duplicate and obsolete information. The duplicate and obsolete information resulted from a new "What to do next" section being added to the topic to accommodate the updated instructions contained in APAR IT07038. However, some instructions remained in the rest of the topic.

The corrected information will be published in the next release of the Tivoli Storage Manager for Databases: Data Protection for Oracle documentation.

The updates relate to the topics entitled: Configuration with default settings, and Setting up a schedule on the client machine NodeA1.

The topic Configuration with default settings Step 6 should read as follows:

    6. (UNIX) Change to the /usr/tivoli/tsm/client/api/bin64 directory. Edit the dsm.sys file to include another server stanza with the following options:
      servername TSMOracle
      tcpserveraddress site.xyzinc.com
      tcpport 1500
      nodename NodeA1
      passwordaccess generate
      passworddir /home/oracle

    Replace  site.xyzinc.com with the IP address of the Tivoli Storage Manager server to which Data Protection for Oracle backs up data. Replace /home/oracle with the Oracle database instance user's home directory.

    For more information about these options and the dsm.sys file, see Define Tivoli Storage Manager options in the client options file.

The topic Setting up a schedule on the client machine NodeA1 has changed significantly, because of the volume of changed information it has been documented here:

http://www-01.ibm.com/support/docview.wss?uid=swg27047179


--------------------------------------------------------------------------------------------------------------
(All versions) Incorrect file paths for the Windows platform in the showenvironment command topic

The IBM Tivoli Storage Manager for Databases: Data Protection for Oracle 7.1.3 documentation includes a topic entitled: showenvironment command, which contains file paths for the supported platforms. However, the file paths for the Windows platform are incorrect.

The corrected information will be published in the next release of the Tivoli Storage Manager for Databases: Data Protection for Oracle documentation.

The file paths for the Windows platform in the topic should read as follows:
    DSMI_DIR:             C:\Program Files\Common Files\Tivoli\TSM\api64
    DSMI_ORC_CONFIG:      C:\Program Files\Tivoli\TSM\AgentOBA64\dsm.opt
    TDPO_OPTFILE:         C:\Program Files\Tivoli\TSM\AgentOBA64\tdpo.opt

Document information

More support for: Tivoli Storage Manager for Databases
Data Protection for Oracle

Software version: 7.1, 7.1.1, 7.1.2, 7.1.3, 7.1.4

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: All Editions

Reference #: 7039331

Modified date: 22 September 2014