Thanks Skylar.
I noticed it was possible to inactive by running "tdpsqlc inactivate "
but the problem from our TSM side is that we don't notice these things and
doing regular investigations into this matter is a chore. Wondered if there
could be some settings or other tricks to automate this.
Reg
A few ways to do it:
1. Run a full incremental backup on the node after the database is removed
2. Use the client-side EXPIRE command with a list of paths to mark inactive
3. If the entire node is going away, use the server-side DECOMMISSION NODE
command (take note of the caveats in the documentat
Newbie question(only 18 years of experience with TSM) :
How do I ensure that deleted databases get inactivated and expired
according to the copygroup settings? As far as I know inactivation of
copies >retonly occurs when the database is backed up. If the database is
removed all active copies will
Hi All,
Is there a way to exclude docker filesystems? I.e. is it possible to useva
wildcard in exclude.fs?
Richard.
I have a database backup where the DBA just excluded 100 databases (out of
171). To prevent backup "failures" (and trouble tickets) I tried to
exclude them in the command line, but there were 3500 characters just in
the excludes. Windows server 2012R2 can handle over 8000 characters in the
comman
It depends on the signal you use. A standalone "kill" or a "kill -15"
yes. That's called SIGTERM, all it does is send a termination signal to
the process.
https://major.io/2010/03/18/sigterm-vs-sigkill/
-
Thanks,
Marc...
Marc Lanteigne
Spe
So you are saying that issuing the server HALT command via console is no
different than the OS level kill?
On Tue, Mar 12, 2019 at 9:15 AM Marc Lanteigne
wrote:
> That's what I said.
>
> > From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> > command, but without any signal, which
That's what I said.
> From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> command, but without any signal, which means it defaults to -15
> (SIGTERM). That sends a message to the process to shutdown gracefully.
It's in the manual as one of the proper ways to start/stop the server:
tsminst1 is a script in /etc/rc.d/init.d which determines the pid of the
running dsmserv process and then issues a kill against it. From the
tsminst1 script
stop() {
echo "Stopping $prog instance $instance ..."
if [[ -e $pidfile ]]
then
# make sure someone els
"systemctl stop tsminst1" is not a kill. That's a service command to tell
the application it manages to shut down gracefully.
>From the KC:
https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t_srv_startsrv_autolnx-linux.html
6.To start or stop the server, issue one of the
Hi Eric,
Just like Zoltan said, you really need to prevent a kill of TSM. This will
leave the DB2 database in an inconsistent state and thus result in a DB2 crash
recovery which can indeed be a lengthy process. Just use a halt to stop TSM and
the DB2 database will be closed properly.
Kind regard
11 matches
Mail list logo
