no vista.taf in 5.7?

[Greg Eriksen]

We have a set of database cleanup instructions from when we were on 5.4, and I’ve only recently become aware that there is no “vista.taf” file to remove now that we are on 5.7.  I do see an “rdm.taf” file, but don’t remember if that was always there on 5.4 as well.

Is rdm.taf a newer version of vista.taf, and should it be removed at the same time we remove the monitorShmemFile?

Topic

[Robert Kersemakers]

Hi Greg,

Hmm… Hadn’t noticed that yet. Thanks for pointing this out.

We are going to upgrade from CL5.5 to 5.7 and are testing 5.7 at the moment (if we have time for it…). In 5.5 there is no rdm.taf, just a vista.taf. So it really looks like vista.taf has been replaced by rdm.taf. They are almost the same size and they both show the lockmanager of the specific site.

We also remove vista.taf when doing a restart/cleanup of a site, so it would be nice to know whether rdm.taf has really replaced vista.taf.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Russ Ross]

I checked our clear_db.ksh script because I couldn’t remember doing anything to it for rdm.taf but looks like I did and removing the rdm.taf file on Cloverleaf 5.6 which I do see is being created hasn’t been any problem so far.

Here is my clear_db.ksh script as of today

Code:

#!/usr/bin/ksh

# here are some other usefule database commands
#———————————————-
#
# lmclear -u TEST -mp (if the user locks the database by doing ctrl-c during a hcidbdump -r
#
# lmclear -s -mp (that gives you a list of active database users)
#
# hcilmclear -p ris    (if the ris process hangs the database)
#
# from clovertech post:  http://clovertech.infor.com/viewtopic.php?t=3783
#
#    Another handy flag is U (username)
#
#    hcidbdump -r -D -U MIKE
#
#    This way if you do control-c, you don’t hose the engine’s TEST user name.
#    If you control-c with user MIKE on accident, then use user JANE next time.
#    Ah Michael: you made my day!!
#    I now use this -U option to use a different user and also lmclear this user first when running the script.
#    Works like a charm. Fro example:
#
#    lmclear -u RUSS -mp
#    hcidbdump -r -U RUSS
#    ctrl-c or whatever
#    lmclear -u RUSS -mp

if [[ -d $HCISITEDIR/exec/databases ]]; then

   cd $HCISITEDIR/exec/databases

   hcisitectl -k l

   rm -f *.log
   rm -f lm_*
   rm -f vista.taf
   rm -f rdm.taf

   rm -f mid.ctr

   hcidbinit -ACi

   keybuild rlog; dchain rlog
   keybuild elog; dchain elog

fi

Russ Ross
RussRoss318@gmail.com

[Robert Kersemakers]

Thanks Ross, just what I needed to know. Removing them both is best.

And your script is very handy as well. We do everything manually…

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Rob Abbott]

Hi all,

“rdm.taf” is the new “vista.taf”.  This is a result of the Raima upgrade that happened in (IIRC) 5.6.

FYI, if you use the “-C” option on hcidbinit, it should remove the .taf file.  If you want to re-init the database without affecting error or recovery, you can use “hcidbinit -i -C -f”.

As always, make sure all engines are down when performing operations like this on the embedded database!

Rob Abbott
Cloverleaf Emeritus

[Kevin Scantlan]

I notice your procedure, you remove the mid.ctr file.  What is this file for?  In the clean-up instructions for customers, I do not see this step.

Thanks.

[Robert Kersemakers]

mid.ctr is a counter file. Mid is short for for message id, so this counter file gives each Cloverleaf message its id.

Never have removed this. I guess you can, but it will make message id start with 1 again.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Author]

Replies