Hello
We have a RHEL server that backs up the filesystem nightly via cron as root.
However our DB2 users also run the DB2 api command
db2 backup database <DBNAME> use tsm open 4 sessions COMPRESS INCLUDE LOGS without prompting
Issue-
env variables for DB2 user
export DSMI_CONFIG=/opt/tivoli/tsm/client/api/bin64/dsm.opt
export DSMI_DIR=/opt/tivoli/tsm/client/api/bin64/
export DSMI_LOG=/db2home/db2itmd3/
dsm.sys both in api at /opt/tivoli/tsm/client/api/bin64/dsm.sys
and for root filesystem = /opt/tivoli/tsm/client/ba/bin/dsm.sys
Problem if db2 user runs dsmc -se=Filsystem or dsmc -se=db they get into dsmc propmt for their node.
Problem is dsmc without variables brings them into the wrong node - the filesystem node as its the only one mentioned in /opt/tivoli/tsm/client/ba/bin/dsm.sys
For some reason DB2 user is NOT looking at opt/tivoli/tsm/client/api/bin64/dsm.opt but rather /opt/tivoli/tsm/client/ba/bin/dsm.opt
So if the db2 user runds dsmc they get the wrong TSM node
Looks like db2 user is ignoring DSMI_CONFIG settign and goign to the defulat dsm.opt for thfilesystem.
Workaround ?
What would be the "db2 backup database" command to have it use tsm "se=db2"
client is 8.1.15
I believe its in "options" ie
db2 backup database <my_DB2_database> ONLINE INCREMENTAL use tsm open 4 sessions COMPRESS INCLUDE LOGS without prompting
CHANGE TO: (RHEL OS v8)
db2 backup database <my_DB2_database> ONLINE INCREMENTAL use tsm open 4 sessions options `"se=db2"` COMPRESS INCLUDE LOGS without prompting
Would that tell dB@ to use tsm with the correct dsm.sys entyr for the correct node?
Any idea why DB2 user is not using dsm.opt in its DSMI_CONFIG ???
Thanks for help
We have a RHEL server that backs up the filesystem nightly via cron as root.
However our DB2 users also run the DB2 api command
db2 backup database <DBNAME> use tsm open 4 sessions COMPRESS INCLUDE LOGS without prompting
Issue-
env variables for DB2 user
export DSMI_CONFIG=/opt/tivoli/tsm/client/api/bin64/dsm.opt
export DSMI_DIR=/opt/tivoli/tsm/client/api/bin64/
export DSMI_LOG=/db2home/db2itmd3/
dsm.sys both in api at /opt/tivoli/tsm/client/api/bin64/dsm.sys
and for root filesystem = /opt/tivoli/tsm/client/ba/bin/dsm.sys
Problem if db2 user runs dsmc -se=Filsystem or dsmc -se=db they get into dsmc propmt for their node.
Problem is dsmc without variables brings them into the wrong node - the filesystem node as its the only one mentioned in /opt/tivoli/tsm/client/ba/bin/dsm.sys
For some reason DB2 user is NOT looking at opt/tivoli/tsm/client/api/bin64/dsm.opt but rather /opt/tivoli/tsm/client/ba/bin/dsm.opt
So if the db2 user runds dsmc they get the wrong TSM node
Looks like db2 user is ignoring DSMI_CONFIG settign and goign to the defulat dsm.opt for thfilesystem.
Workaround ?
What would be the "db2 backup database" command to have it use tsm "se=db2"
client is 8.1.15
I believe its in "options" ie
db2 backup database <my_DB2_database> ONLINE INCREMENTAL use tsm open 4 sessions COMPRESS INCLUDE LOGS without prompting
CHANGE TO: (RHEL OS v8)
db2 backup database <my_DB2_database> ONLINE INCREMENTAL use tsm open 4 sessions options `"se=db2"` COMPRESS INCLUDE LOGS without prompting
Would that tell dB@ to use tsm with the correct dsm.sys entyr for the correct node?
Any idea why DB2 user is not using dsm.opt in its DSMI_CONFIG ???
Thanks for help