TDP for ERP on DB2 + HACMP

SkyRE

ADSM.ORG Member
Joined
Sep 21, 2006
Messages
9
Reaction score
0
Points
0
Location
Ukraine, Kyiv
Website
Visit site
I've some situation...may be some one can help?

1.
Code:
- 2 machines with AIX 5.3 (1st - App, 2nd - DB)
- SAP on DB2 8.1 fix 12
- TDP for ERP on DB2
- DB2 in roll-forward mode, 1 DB instance.
I've succesfully archived full/inctemental/delta db online
archive logs also archived when bacame unneeded.

One word - all work fine.

2. But after installing HACMP on AIX (hostnames was changed)
backom -c password, begun work only on App Node
and say goto node "DB" to change password from DB Node.
Code:
BKI8806I: Data Protection for mySAP(R) - BackOM 5.3.3.0 (293) Jul 12 2006
BKI2027I: Using TSM-API version 5.3.4.0 (compiled with 5.3.0.0).
BKI8652I: DB2 UDB version 'SQL08025' with 64 bits detected.

BKI8511I: The command is: -c password
BKI8559W: For partition 'NODE0000' switch to host 'DB' and issue the command again.
BKI8512I: Return code is: 1

archive logs steel archiving to TSM, but I cant make any full/increment/delta archiving of DB to TSM.
got error like
Code:
BKI8806I: Data Protection for mySAP(R) - BackOM 5.3.3.0 (293) Jul 12 2006
BKI2027I: Using TSM-API version 5.3.4.0 (compiled with 5.3.0.0).
BKI8652I: DB2 UDB version 'SQL08025' with 64 bits detected.

BKI8511I: The command is: -c b_db -a bip -R full -O -x
BKI8658E: 0 is not a partition number of the database or does not denote a partition on this host.
BKI8548I: Elapsed time: 0 sec
BKI8634E: Backup command failed due to an error.
BKI8512I: Return code is: 611
 
The 611 error comes back as
"#define DSM_RC_NLS_CANT_READ_HDR 611 /* error trying to read header */"

And this kinda looks like you are using userexit to shoot the logs off to TSM -
Can you confirm that?

-Chef.
 
I'm not using USEREXIT to shoot logs on TSM...
I've been using VENDOR:/db2/XXX/tdp_r3/libtdpdb2.a for LOGARCHMETH1
and LOGARCHOPT1 /db2/XXX/tdp_r3/vendor.env (I can wrong with DB2 Option names, but something like this).

Cause USEREXIT - method is Data Protection for UDB DB2
And Method mentioned above is Data Protection for ERP on UDB DB2.

As I know that RC=611 here it's not from dsmrc.h it's something other...and after main error BKI8658E
 
Well, ya - DB2 v 8.1 FP 6 and below still uses userexit though, as v8.2 (FP 7 and above) use the vendor method you show above.
You are logging the correct way...

Anyway -
Your DB2 version is 64-bit.
Are you using the 64-bit API?

-Chef.
 
Well, ya - DB2 v 8.1 FP 6 and below still uses userexit though, as v8.2 (FP 7 and above) use the vendor method you show above.
You are logging the correct way...
Yes, I know this limitations (mentioned in RedBook)
Anyway -
Your DB2 version is 64-bit.
Are you using the 64-bit API?
Yes.
here code from /usr/tivoli/tsm/client/api/bin64/dsm.sys
Code:
SErvername			ttt-tsm-sap
	COMMMethod		TCPip
	TCPPort			1500
	TCPServeraddress	ttt-tsm
	PasswordAccess		Prompt
	PasswordDir		/db2/XXX/tdp_r3/
	NodeName		xxx-sap
  TCPBuffsize        32
  TCPWindowsize      24
  Compression        Off
	ErrorLogName		/db2/XXX/tdp_r3/dsierror.log
and here /db2/XXX/tdp_r3/initXXX.utl
Code:
#--------------------------------------------------------------------------
#
# Data Protection for mySAP (R) interface for DB2 UDB
#
# Sample profile for Data Protection for mySAP (R) Version 5.3
#
#--------------------------------------------------------------------------
#
# See the 'Data Protection for mySAP (R) Installation & 
# User's Guide' for a full description.
#
# For a comment symbol the character '#' can be used.
# Everything following this character will be interpreted as comment.
#
# Data Protection for mySAP (R) accesses its profile 
# in "read only" mode. All variable parameters like passwords, date of 
# last password change, current version number will be written into the file
# specified with the CONFIG_FILE parameter. The passwords will be encrypted.


#--------------------------------------------------------------------------
# Prefix of the 'Backup ID' which is used for communication with 
# the SAP-DB2 Administration Tools and stored in the description field of 
# the Tivoli Storage Manager archive function.
# Maximum 6 characters.
# Default: none.
#--------------------------------------------------------------------------
BACKUPIDPREFIX      XXX___


#--------------------------------------------------------------------------
# Number of parallel sessions to be established.
# Note: This number must not exceed the number of tape drives simultaneously
# available to the node on the Tivoli Storage Manager servers to be accessed.
# The valid range of MAX_SESSIONS is from 1 and 32.
# Default: none.
#--------------------------------------------------------------------------
MAX_SESSIONS		2 # Tivoli Storage Manager client sessions


#--------------------------------------------------------------------------
# Number of backup copies of the DB2 log files.
# The valid range of REDOLOG_COPIES is from 1 to 9.
# Default: 1.
#--------------------------------------------------------------------------
#REDOLOG_COPIES		2


#--------------------------------------------------------------------------
# Specifies the block size for disk I/O (in bytes).
# The default values have been chosen from our performance experiments in
# standard hardware environments.
# The valid range of BUFFSIZE is from 4KB to 32MB.
# Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows.
#--------------------------------------------------------------------------
BUFFSIZE		131072              # block size in bytes


#--------------------------------------------------------------------------
# This optional parameter controls how Data Protection for mySAP(R) uses 
# the internal buffers for transferring data during a backup. 
# Valid values:   SIMPLE | PREVENT | AUTO
# Default: SIMPLE
#--------------------------------------------------------------------------
#BUFFCOPY               AUTO 


#--------------------------------------------------------------------------
# Name of a program to be called before the backup task is started.
# Default: none.
#--------------------------------------------------------------------------
#FRONTEND               pgmname parameterlist


#--------------------------------------------------------------------------
# Name of a program to be called after the backup task is completed.
# Default: none.
#--------------------------------------------------------------------------
#BACKEND                pgmname parameterlist


#--------------------------------------------------------------------------
# Maximum number of data base backup versions to be kept.
# Note: Version control by Data Protection for mySAP (R) is only activated 
# only activated if the parameter MAX_VERSION is not 0.
# The valid range of MAX_VERSIONS is from 0 to 9999.
# A value of 0 means no versioning. 
# Default: 0, no versioning.
#--------------------------------------------------------------------------
MAX_VERSIONS		2


#--------------------------------------------------------------------------
# Specifies whether a null block compression of the data is to be performed
# before transmission to Tivoli Storage Manager. 
# Although RL compression introduces additional CPU load, throughput can be
# improved when the network is the bottleneck. RL compression in Data
# Protection for mySAP(R) should not be used together with
# Tivoli Storage Manager API compression.
# Default: NO
#--------------------------------------------------------------------------
#RL_COMPRESSION		YES                 # NO is default


#--------------------------------------------------------------------------
# Controls generation of a trace file.
# Note: We recommend using the trace function only in cooperation with
# Data Protection for mySAP (R) support.
# Default: OFF.
#--------------------------------------------------------------------------
#TRACE			OFF
#TRACEFILE            /db2/C21/sqllib/log/tdpr3.trace


#--------------------------------------------------------------------------
# Denotes the maximum size of the trace file in KB.
# If not specified, the trace file size is unlimited.
#--------------------------------------------------------------------------
#TRACEMAX           <max. size>             # trace file size in KB

#--------------------------------------------------------------------------
# Specify the full path of the configuration file.
# Default: none.
#--------------------------------------------------------------------------
CONFIG_FILE      /db2/XXX/tdp_r3/%DB2NODE/initXXX.bki


#--------------------------------------------------------------------------
# Denotes if Data Protection for mySAP (R) shall send error/status 
# information to a Tivoli Storage Manager server. 
# The servername must match one of the servers listed in a SERVER statement. 
# Valid values for verbosity are ERROR | WARNING | DETAIL.
# Default: none.
#--------------------------------------------------------------------------
#LOG_SERVER             servername    [verbosity]
#LOG_SERVER             server_a      ERROR


#**************************************************************************
# Statement for servers and paths.
# Multiple servers may be defined.
#**************************************************************************


SERVER          ttt-tsm-sap
  SESSIONS            4                  # Maximum number of sessions 
                                         # to server_a
  PASSWORDREQUIRED    YES                # Use a password
  ADSMNODE            XXX
  BRBACKUPMGTCLASS    mdb
  BRARCHIVEMGTCLASS   mlog1
# TCP_ADDRESS         192.168.1.1        # IP address of network interface 
                                         # on server_a 
                                         # Overrides IP address of dsm.sys
# USE_AT              0 1 2 3 4 5 6      # Days when server_a is used for 
                                         # backup
#**************************************************************************
# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa
# The valid range of USE_AT is from 0 to 6.
# Default: all days
#**************************************************************************

#SERVER         server_b                  # Servername, as defined in dsm.sys
#  SESSIONS            2                  # Maximum number of sessions 
                                          # to server_b
#  PASSWORDREQUIRED    YES                # Use a password
#  ADSMNODE            NODE               # Tivoli Storage Manager Nodename
#  BRBACKUPMGTCLASS    MDB                # Mgmt-Classes for database backup
#  BRARCHIVEMGTCLASS   MLOG1 MLOG2        # Mgmt-Classes for redo log backup
#  TCP_ADDRESS 	       192.168.1.1        # IP address of network interface 
                                          # on server_b 
                                          # Overrides IP address of dsm.sys 
#  USE_AT              0 1 2 3 4 5 6      # Days when server_b is used for 
                                          # backup
#**************************************************************************
# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa
# Default: all days
#**************************************************************************



#--------------------------------------------------------------------------
# End of profile


END
Sorry to say that...
I'm not newbie in TSM (1,5 years of deployment).
 
I've found solution - need do correct settings in DB2 config files (They wasn't correct, according to DB2 Documentation for HACMP Enviroment)
Doc: High Availability and Scalability Guide for DB2 on Linux, UNIX, and Windows (SG24-7363-00) (Draft RedBook) ->8.5 Considerations for db2nodes.cfg file
 
Doc: High Availability and Scalability Guide for DB2 on Linux, UNIX, and Windows (SG24-7363-00) (Draft RedBook) ->8.5 Considerations for db2nodes.cfg file
There are 5 ways to configure DB2 for HACMP, but not all of them appropriate for TDP.

1. Modify the file entry in the start script.
2. Use the db2start command with the restart option.
3. Use the db2gcf command with the -u option.
4. Use an alias in the hosts files.
5. Use the service IP address in db2nodes.cfg.

For work with TDP need to be configured by first method - modification of db2nodes.cfg at startup of DB2 instance (in db2 startup scripts).
 
Back
Top