Performance Audit Document

Performance Audit Document
The IT Performance Management & Capacity Planning Company
EDB PostgreSQL IT Resources
Remove Tricks/Tips
Author:
Walter Verhoeven
Doc. Ref.:
edb_pgsql_it_resources_remove_v1.0.doc
Version:
1.0
Date:
26 February 2014
TeamQuest Tips & Tricks
Page 2 of 17
IT Resources Removal From ITSAR
I.
II.
Version 1.0
Document History
Version
Date
Name
Description
1.0
26/02/2014
W. Verhoeven
Intermediate copy for discussion.
Stakeholders
Company
Responsible Stakeholder
CREATIVE Associates
Walter Verhoeven
CREATIVE Associates
Donderveldstraat 52
1651 Lot/Beersel
Belgium
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 3 of 17
IT Resources Removal From ITSAR
III.
Version 1.0
Contents
Table of Contents
1.MANAGEMENT SUMMARY......................................................................................4
1.1Introduction........................................................................................................................................................4
2.TEST INFRASTRUCTURE DESCRIPTION..............................................................5
3.IT SERVICES REMOVAL CASES.............................................................................6
3.1Remove Entire Server........................................................................................................................................6
3.1.1Step1: Remove Server From The Harvesting Process..................................................................................6
3.1.2Step2: Remove The Server References From EDB Table “tq$itr”...............................................................7
3.2Remove Entire Workload Set............................................................................................................................8
3.2.1Step1: Verify If The Workload Set “Example” Is Removed From “production”.........................................8
3.2.2Step2: Remove The “Example” Workload Set IT Resource From “production”.........................................9
3.2.3Step3: Remove Workload Set “Example” References From EDB Table “tq$itr”......................................10
3.3Remove Workload From an Active Workload Set.........................................................................................11
3.3.1Step1: Verify If The Workload “memalloc” Is Removed From “production”............................................11
3.3.2Step2: Remove The “memalloc” Workload Definition IT Resource From “production”..........................13
3.3.3Step3: Remove Workload Definition “memalloc” References From EDB Table “tq$itr”.........................14
3.4Remove A User Table Reference.....................................................................................................................14
3.4.1Step1: Remove The User Table Reference From “production”..................................................................15
3.4.2Step2: Remove The User Table Harvesting Reference From Your EDB...................................................16
3.4.3Step3: Remove The User Table Reference IT Resource From “production”.............................................16
3.4.4Step4: Remove User Table “RPF4.SpecInt” References From EDB Table “tq$itr”..................................17
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 4 of 17
IT Resources Removal From ITSAR
1.
Version 1.0
Management Summary
Introduction
1.1
This document describes some examples/cases of TeamQuest IT Resources removals from a
configuration where a set of systems are harvested into a ProgreSQL database. The goal is that
unwanted resources do not appear any more in ITSAR.
The configuration used here is TeamQuest Manager 11.1 on the clients (only on sunny we tested with
10.3) and 11.2 PF 20130930 on the central server for both TQ Manager and ITSAR. The ProgreSQL
DB has version 9.2.4.
The following cases have been tested:
•
Remove entire server
•
Remove an entire Workload Set.
•
Remove a Workload from an active Workload Set.
•
Remove a User Table reference.
This does not cover the removal of the actual data in the EDB.
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 5 of 17
IT Resources Removal From ITSAR
2.
Version 1.0
Test Infrastructure Description
The test infrastructure involved looks as following:
Figure 2-1: Test Infrastructure Overview
The measured environment looks as following in TeamQuest ITSAR:
Figure 2-2: Measured Environment
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 6 of 17
IT Resources Removal From ITSAR
3.
Version 1.0
IT Services Removal Cases
3.1
Remove Entire Server
In this case we will remove an obsoleted server that was previously harvested into our PostgreSQL
Open Enterprise Database. In our case the server to be removed is named “dell2”.
Figure 3-1: Server Resources List
3.1.1
Step1: Remove Server From The Harvesting Process
Edit the Monitored Databases and Delete the server of interest.
Figure 3-2: Delete From Harvested Server List
Once this is done we should remove the server IT Resource references from the IT Resources table.
Simply deleting this node in the ITSAR screen will not work as after a “tqmeta” run it will appear again
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 7 of 17
IT Resources Removal From ITSAR
Version 1.0
as a node under your “System” tree.
A check in the database “edb_pgsql” for table “tq$itr” shows that we have still references towards this
server “dell2” after a manual delete in ITSAR.
edb_pgsql=# select "Name" from tq$itr where "Name" like '%System/dell2%';
Name
---------------------------------------------------------------/TeamQuest/System/dell2
/TeamQuest/System/dell2/CPU
/TeamQuest/System/dell2/Disk
/TeamQuest/System/dell2/Kernel
/TeamQuest/System/dell2/Memory
/TeamQuest/System/dell2/Network
/TeamQuest/System/dell2/Process
/TeamQuest/System/dell2/TeamQuest Log
/TeamQuest/System/dell2/User Data
/TeamQuest/System/dell2/User Data/KVM.Activity
/TeamQuest/System/dell2/Workload
/TeamQuest/System/dell2/Workload/cass_awld
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhl1
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhl2
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhlatos1
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhlatos2
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhlora
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhlpostgr
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhlprebits
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmrhlprebits2
/TeamQuest/System/dell2/Workload/cass_awld/KVM_kvmxp1
/TeamQuest/System/dell2/Workload/cass_awld/KVM_nmbsmigrate
/TeamQuest/System/dell2/Workload/cass_awld/KVM_Rest
...
/TeamQuest/System/dell2/Workload/MobistarDebug/tqview
/TeamQuest/System/dell2/Workload/MobistarDebug/tqwarp
/TeamQuest/System/dell2/Workload/MobistarDebug/Xorg
/TeamQuest/System/dell2/Workload/MobistarDebug/yum
(97 rows)
We have 97 rows in this table that relate to server “dell2”. So these need to be removed.
3.1.2
Step2: Remove The Server References From EDB Table “tq$itr”
With the following command we remove the above listed records:
edb_pgsql=# delete from tq$itr where "Name" like '%System/dell2%';
DELETE 97
edb_pgsql=# select "Name" from tq$itr where "Name" like '%System/dell2%';
Name
-----(0 rows)
Now this server will no more pop-up after a manual delete in ITSAR for the service db that points to
this EDB “edb_pgsql”.
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 8 of 17
IT Resources Removal From ITSAR
3.2
Version 1.0
Remove Entire Workload Set
In this case we want to remove a Workload Set which is no more active on production. In our case we
have a server named “bacserver” which has a Workload Set named “Example” that has been removed
from the TQ proprietary production database.
We deleted it from the Workload Policy and removed the corresponding records.
Figure 3-3: Workload Set Records Delete
3.2.1
Step1: Verify If The Workload Set “Example” Is Removed From “production”
We check if all data records related to this Workload Set are really removed from the proprietary
“production” database. This can be done by the following command:
tqzip -d production -o paramlist.txt
This file “paramlist.txt” contains all parameters that exist in the “production” database. Normally we
should not find any “Example” workload reference any more.
/var/tmp/wav # cat paramlist.txt | grep Workload | grep Example
/var/tmp/wav #
If you find that there are still some parameters left you need to create a file that contains all
parameters that you want to REMOVE. It needs the following header & footer (can be found in the file
you generated above).
BEGIN PARAMETER LIST created from <production> on Mon 02 Dec 2013 09:21:04 PM CET
System:CatGroup:Cat:SubCat:Stat:Res:WL Set:WL
bacserver:Workload:by Workload::usrcpu::Example:root
bacserver:Workload:by Workload::syscpu::Example:root
bacserver:Workload:by Workload::threads::Example:root
...
bacserver:Workload:by Workload::rwsysc::Example:OTHER
bacserver:Workload:by Workload::rwKB::Example:OTHER
END PARAMETER LIST
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 9 of 17
IT Resources Removal From ITSAR
Version 1.0
Once you have this file you can use the following command to remove them:
# tqzip -d production -p paramremove.txt
*Info* TZ variable reset to Europe/Brussels
TQZIP 11.1 PF 20130716 (Europe/Brussels) Mon 02 Dec 2013 09:31:33 PM CET
Copyright (c) 2012-2013 TeamQuest Corporation. All Rights Reserved.
bacserver Linux x86_64 2.6 18-164.el5 Red Hat Enterprise Linux Server release 5.4 (Tikanga) 14501
Using database /opt/teamquest/data/production
...generating list of pnums to delete
72 parameters selected for deletion
Proceed with deletion (y,<n>)? y
...deleting parameters
72 parameters were deleted.
End TQZIP Mon 02 Dec 2013 09:31:50 PM CET
3.2.2
Step2: Remove The “Example” Workload Set IT Resource From “production”
Even with these Workload Set parameters/records deleted from the proprietary TeamQuest
“production” database you will find an IT Resource reference in ITSAR. Again deleting this entry
manually will not solve it as an entry in the “itrdef” file exists.
In order to get rid of it you need to shut-down TQManager:
bacserver:/tqdata/production# tqmgr -shut-down
And then edit the “tlist” file in the “production” db directory by removing the following entry in bold:
[Tables]
Table1=Dictionary, Tables, 2, Internal, dicttab, 23
Table2=Dictionary, PNumber, 2, Internal, dictpnum, 22
Table3=Dictionary, Derived, 2, Internal, dictderi, 20
...
Table21=System, ITR, 2, Internal, itrdef, 13
Table22=Aggregation, 1-hour-projection, 1, Internal, a1-hour-projec, 32
Table23=System, DataLocation, 2, Internal, datalocdef, 14
Table24=HINV, FileSystem, 8, Performance, hinvfs, 1101
Table25=HINV, Devices, 11, Performance, hinvdev, 1100
Table26=HINV, Summary, 14, Performance, hinvsum, 1102
...
This “itrdef” table still contains references to the “EXAMPLE” Workload Set. Afterwards remove the
actual file(s) of this table in the “production” db directory.
bacserver:/tqdata/production# ls -l
total 1589112
-rw-rw-r-- 1 root root 21676032 Feb 26 13:30 AgentInterval
-rw-rw-r-- 1 root root
32 Feb 26 13:30 AgentInterval.roll
-rw-rw-r-- 1 root root
16384 Nov 14 17:04 HBA:Activity
-rw-rw-r-- 1 root root
32 Feb 26 13:08 HBA:Activity.roll
-rw-rw-r-- 1 root root
0 Dec 10 2010 TcpdRec.2710
-rw-rw-r-- 1 root root 13709312 Feb 26 12:00 a1-hour
...
-rw-rw-r-- 1 root root
135168 Feb 26 00:00 itrdef
-rw-rw-r-- 1 root root
32 Feb 26 13:26 itrdef.roll
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 10 of 17
IT Resources Removal From ITSAR
Version 1.0
-rw-rw-r-- 1 root root
12288 Feb 26 12:00 licenses
-rw-rw-r-- 1 root root
32 Feb 26 13:29 licenses.roll
-rw-rw-r-- 1 root root
112 Dec 10 2010 lock
drwxrwsr-x 2 root root
512 Jan 15 00:00 log
-rw-rw-r-- 1 root root
471 Oct 17 09:41 maxdef
-rw-rw-r-- 1 nobody root
626 Oct 17 09:39 mdldef
-rw-rw-r-- 1 root root
370 Feb 26 13:30 misc
...
Now you can start the TQ agent again:
bacserver:/tqdata/production# tqmgr -service
You will see that the “tlist” table has a new “itrdef” reference and a new file “itrdef” has been created
too. No reference to the “EXAMPLE” Workload Set any more when connecting directly with ITSAR to
this server.
Figure 3-4: “bacserver” workload
3.2.3
Step3: Remove Workload Set “Example” References From EDB Table “tq$itr”
We check these references as following:
edb_pgsql=> select "Name" from tq$itr where "Name" like '%System/bacserver/Workload/Example%';
Name
---------------------------------------------------/TeamQuest/System/bacserver/Workload/Example
/TeamQuest/System/bacserver/Workload/Example/admin
/TeamQuest/System/bacserver/Workload/Example/OTHER
/TeamQuest/System/bacserver/Workload/Example/root
/TeamQuest/System/bacserver/Workload/Example/users
(5 rows)
You can remove these rows now as following:
edb_pgsql=> delete from tq$itr where "Name" like '%System/bacserver/Workload/Example%';
DELETE 5
Check if really removed.
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 11 of 17
IT Resources Removal From ITSAR
Version 1.0
edb_pgsql=> select "Name" from tq$itr where "Name" like '%System/bacserver/Workload/Example%';
Name
-----(0 rows)
Now that these are removed you can manually delete in ITSAR these references too. After a run of
“tqmeta” these will no longer re-appear.
3.3
Remove Workload From an Active Workload Set
In this case we want to remove a Workload from an active Workload Set. In our case we have a
server named “mogol1” which has a Workload Set named “Example” that contains a Workload
reference “memalloc” which should be removed.
We deleted it from the Workload Set as following:
Figure 3-5: Workload Definition Delete
3.3.1
Step1: Verify If The Workload “memalloc” Is Removed From “production”
We check if all data records related to this Workload Set are really removed from the proprietary
“production” database. This can be done by the following command:
tqzip -d production -o paramlist.txt
This file “paramlist.txt” contains all parameters that exist in the “production” database. Normally we
should not find any “memalloc” workload reference any more.
/var/tmp/wav # cat paramlist.txt | grep Workload | grep memalloc
# cat paramlist.txt | grep Workload | grep memalloc
mogol1:Workload:by Workload::usrcpu::Example:memalloc
mogol1:Workload:by Workload::syscpu::Example:memalloc
mogol1:Workload:by Workload::threads::Example:memalloc
mogol1:Workload:by Workload::lioch::Example:memalloc
mogol1:Workload:by Workload::pio::Example:memalloc
mogol1:Workload:by Workload::avgmem::Example:memalloc
mogol1:Workload:by Workload::etime::Example:memalloc
mogol1:Workload:by Workload::totcpu::Example:memalloc
mogol1:Workload:by Workload::%cpu::Example:memalloc
mogol1:Workload:by Workload::pstart::Example:memalloc
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 12 of 17
IT Resources Removal From ITSAR
Version 1.0
mogol1:Workload:by Workload::pcomplete::Example:memalloc
mogol1:Workload:by Workload::pongoing::Example:memalloc
mogol1:Workload:by Workload::rss::Example:memalloc
mogol1:Workload:by Workload::srss::Example:memalloc
mogol1:Workload:by Workload::prss::Example:memalloc
mogol1:Workload:by Workload::waitcpu::Example:memalloc
mogol1:Workload:by Workload::textfltslp::Example:memalloc
mogol1:Workload:by Workload::datafltslp::Example:memalloc
mogol1:Workload:by Workload::kernfltslp::Example:memalloc
mogol1:Workload:by Workload::userlckslp::Example:memalloc
mogol1:Workload:by Workload::otherslp::Example:memalloc
mogol1:Workload:by Workload::invswch::Example:memalloc
mogol1:Workload:by Workload::majflt::Example:memalloc
So clearly not removed, this is normal since the deletion of the Workload in an active Workload Set
does not remove the records from the TQ production database.
So in order to remove these manually you need to create a file that contains all parameters that you
want to REMOVE. It needs the following header & footer (can be found in the file you generated
above).
System:CatGroup:Cat:SubCat:Stat:Res:WL Set:WL
mogol1:Workload:by Workload::usrcpu::Example:memalloc
mogol1:Workload:by Workload::syscpu::Example:memalloc
mogol1:Workload:by Workload::threads::Example:memalloc
mogol1:Workload:by Workload::lioch::Example:memalloc
mogol1:Workload:by Workload::pio::Example:memalloc
mogol1:Workload:by Workload::avgmem::Example:memalloc
mogol1:Workload:by Workload::etime::Example:memalloc
mogol1:Workload:by Workload::totcpu::Example:memalloc
mogol1:Workload:by Workload::%cpu::Example:memalloc
mogol1:Workload:by Workload::pstart::Example:memalloc
mogol1:Workload:by Workload::pcomplete::Example:memalloc
mogol1:Workload:by Workload::pongoing::Example:memalloc
mogol1:Workload:by Workload::rss::Example:memalloc
mogol1:Workload:by Workload::srss::Example:memalloc
mogol1:Workload:by Workload::prss::Example:memalloc
mogol1:Workload:by Workload::waitcpu::Example:memalloc
mogol1:Workload:by Workload::textfltslp::Example:memalloc
mogol1:Workload:by Workload::datafltslp::Example:memalloc
mogol1:Workload:by Workload::kernfltslp::Example:memalloc
mogol1:Workload:by Workload::userlckslp::Example:memalloc
mogol1:Workload:by Workload::otherslp::Example:memalloc
mogol1:Workload:by Workload::invswch::Example:memalloc
mogol1:Workload:by Workload::majflt::Example:memalloc
END PARAMETER LIST
Once you have this file you can use the following command to remove them:
bash-3.00# tqzip -d production -p paramremove.txt
TQZIP 11.2 PF 20130930 (Europe/Brussels) Wed Feb 26 15:02:42 2014
Copyright (c) 2012-2013 TeamQuest Corporation. All Rights Reserved.
mogol1 SunOS i386 5.10 global 18705
Using database /opt/teamquest/data/production
...generating list of pnums to delete
23 parameters selected for deletion
Proceed with deletion (y,<n>)?
y
...deleting parameters
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 13 of 17
IT Resources Removal From ITSAR
Version 1.0
23 parameters were deleted.
End TQZIP Wed Feb 26 15:03:54 2014
3.3.2
Step2: Remove The “memalloc” Workload Definition IT Resource From
“production”
Even with these Workload Definition parameters/records deleted from the proprietary TeamQuest
“production” database you will find an IT Resource reference in ITSAR. Again deleting this entry
manually will not solve it as an entry in the “itrdef” file exists.
In order to get rid of it you need to shut-down TQManager:
bacserver:/tqdata/production# tqmgr -shut-down
And then edit the “tlist” file in the “production” db directory by removing the following entry in bold:
[Tables]
Table1=Dictionary, Tables, 2, Internal, dicttab, 23
Table2=Dictionary, PNumber, 2, Internal, dictpnum, 22
Table3=Dictionary, Derived, 2, Internal, dictderi, 20
...
Table21=System, ITR, 2, Internal, itrdef, 13
Table22=Aggregation, 1-hour-projection, 1, Internal, a1-hour-projec, 32
Table23=System, DataLocation, 2, Internal, datalocdef, 14
Table24=HINV, FileSystem, 8, Performance, hinvfs, 1101
Table25=HINV, Devices, 11, Performance, hinvdev, 1100
Table26=HINV, Summary, 14, Performance, hinvsum, 1102
Table27=Zones, ExtraStats, 1, Performance, ZonesExtraStats, 1
Table28=Pools, ExtraStats, 1, Performance, PoolsExtraStats, 1
Table29=SOLARIS, Zone, 3, Performance, solzone, 1403
...
This “itrdef” table still contains references to the “memalloc” Workload Definition. Afterwards remove
the actual file(s) of this table in the “production” db directory.
bash-3.00# ls -l
total 1782816
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 nobody root
...
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
-rw-rw-r-- 1 root root
...
12079104 Feb 26 15:07 AgentInterval
24 Feb 26 15:07 AgentInterval.roll
90632192 Feb 26 15:07 PoolsExtraStats
24 Feb 26 15:07 PoolsExtraStats.roll
454656 Feb 26 14:54 hinvfs
24 Feb 26 15:02 hinvfs.roll
503808 Feb 26 14:54 hinvsum
24 Feb 26 15:02 hinvsum.roll
40960 Feb 26 14:54 intsystb
24 Feb 26 15:01 intsystb.roll
114688 Feb 26 14:54 itrdef
24 Feb 26 15:02 itrdef.roll
12288 Feb 26 12:00 licenses
24 Feb 26 15:02 licenses.roll
Now you can start the TQ agent again:
bash-3.00# tqmgr -service
You will see that the “tlist” table has a new “itrdef” reference and a new file “itrdef” has been created
too. No reference to the “memalloc” Workload Definition any more when connecting directly with
ITSAR to this server.
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 14 of 17
IT Resources Removal From ITSAR
Version 1.0
Figure 3-6: “mogol1” Workload
3.3.3
Step3: Remove Workload Definition “memalloc” References From EDB Table
“tq$itr”
We check these references as following:
edb_pgsql=> select "Name" from tq$itr where "Name" like '%System/mogol1/Workload/Example/memalloc%';
Name
---------------------------------------------------/TeamQuest/System/mogol1/Workload/Example/memalloc
(1 row)
You can remove this row as following:
edb_pgsql=> delete from tq$itr where "Name" like '%System/mogol1/Workload/Example/memalloc%';
DELETE 1
Now that it has been removed you can manually delete in ITSAR this reference too. After a run of
“tqmeta” it will no longer re-appear.
3.4
Remove A User Table Reference
In this case we want to remove a User Table Reference. In we have a server named “sunny” which
has a User Table reference named “RPF4.SpecInt” which should be removed.
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 15 of 17
IT Resources Removal From ITSAR
Version 1.0
Figure 3-7: “sunny” User Table RPF4.SpecInt
In both cases of User Table or User Parameter Agent types, sees that these data collections are
removed/disabled from TQ Manager before proceeding.
3.4.1
Step1: Remove The User Table Reference From “production”
In case of a User Table Agent type you need to remove the actual table from the production database
as following:
/tmp # tqzip -d production -z all | grep RPF
RPF4:SpecInt
/tmp # tqtblprb -d production -r -t RPF4:SpecInt
TQTBLPRB 10.3 PF 20101004 (Europe/Brussels) Wed Feb 26 16:09:14 2014
Copyright (c) 2007-2010 TeamQuest Corporation. All Rights Reserved.
sunny SunOS sparc 5.9 4518
Deleted table: RPF4:SpecInt
End TQTBLPRB Wed Feb 26 16:09:15 2014
For a User Parameter Agent type we check if all data records related to this User Table
“RPF4.SpecInt” are really removed from the proprietary “production” database. This can be done by
the following command:
tqzip -d production -o paramlist.txt
This file “paramlist.txt” contains all parameters that exist in the “production” database. Normally we
should not find any “RPF4.SpecInt” reference since our agent was a User Table Type.
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 16 of 17
IT Resources Removal From ITSAR
Version 1.0
If in your case it is a User Parameter Agent type proceed with the removal as described in the sections
3.2.1 Step1: Verify If The Workload Set “Example” Is Removed From “production” and 3.3.1 Step1:
Verify If The Workload “memalloc” Is Removed From “production”
3.4.2
Step2: Remove The User Table Harvesting Reference From Your EDB
In both cases, User Parameter & User Table Agents, remove the reference from your Harvest Policy.
3.4.3
Step3: Remove The User Table Reference IT Resource From “production”
Even with these User Table Reference parameters/records deleted from the proprietary TeamQuest
“production” database you will find an IT Resource reference in ITSAR. Again deleting this entry
manually will not solve it as an entry in the “itrdef” file exists.
In order to get rid of it you need to shut-down TQManager:
/tmp # tqmgr -shut-down
And then edit the “tlist” file in the “production” db directory by removing the following entry in bold:
[Tables]
Table1=Dictionary, Tables, 1, Internal, dicttab, 23
Table2=Dictionary, PNumber, 1, Internal, dictpnum, 22
Table3=Dictionary, Derived, 1, Internal, dictderi, 20
Table4=Dictionary, Parameter, 1, Internal, dictparm, 21
...
Table16=Internal, System-Table, 1, Internal, intsystb, 11
Table17=System, DerivedTable, 1, Internal, dtdef, 17
Table18=System, Licenses, 1, Internal, licenses, 12
Table19=System, ITR, 1, Internal, itrdef, 13
Table20=System, Alarms, 3, Performance, alarms, 1000
...
This “itrdef” table still contains references to the “memalloc” Workload Definition. Afterwards remove
the actual file(s) of this table in the “production” db directory.
/opt/teamquest/data/production # ls -l
total 203594
-rw-rw-r-- 1 root other
0 Dec 8 2010 TcpdRec.2710
-rw-rw-r-- 1 root other 4431872 Feb 26 16:00 a1-hour
-rw-rw-r-- 1 root other 1040384 Feb 26 04:00 a1-hour-dow
-rw-rw-r-- 1 root other
32 Feb 26 16:15 a1-hour-dow.roll
-rw-rw-r-- 1 root other 184320 Feb 26 00:00 a1-hour-projec
-rw-rw-r-- 1 root other
32 Feb 26 16:15 a1-hour-projec.roll
...
-rw-rw-r-- 1 root other
69632 Feb 26 15:34 itrdef
-rw-rw-r-- 1 root other
32 Feb 26 16:19 itrdef.roll
-rw-rw-r-- 1 root other
16384 Feb 26 16:00 licenses
-rw-rw-r-- 1 root other
32 Feb 26 16:19 licenses.roll
-rw-rw-r-- 1 root other
112 Dec 8 2010 lock
drwxrwsr-x 2 root other
512 Nov 29 20:00 log
-rw-rw-r-- 1 root other
471 Oct 17 09:44 maxdef
-rw-rw-r-- 1 root other
380 Feb 26 16:19 misc
-rw-rw-r-- 1 root other
73728 Feb 26 15:34 parmtab
...
Now you can start the TQ agent again:
/tmp # tqmgr -service
Walter Verhoeven – CREATIVE Associates
TeamQuest Tips & Tricks
Page 17 of 17
IT Resources Removal From ITSAR
Version 1.0
You will see that the “tlist” table has a new “itrdef” reference and a new file “itrdef” has been created
too. No reference to the User Table Definition “RPF4.SpecInt “ any more when connecting directly
with ITSAR to this server.
Figure 3-8: “sunny” User Table
3.4.4
Step4: Remove User Table “RPF4.SpecInt” References From EDB Table
“tq$itr”
We check these references again as following:
edb_pgsql=> select "Name" from tq$itr where "Name" like '%RPF4%';
Name
---------------------------------------------------/TeamQuest/System/sunny/User Data/RPF4.SpecInt
(1 rows)
You can remove this row as following:
edb_pgsql=> delete from tq$itr where "Name" like '%RPF4%';
DELETE 1
Now that it has been removed you can manually delete in ITSAR this reference too. After a run of
“tqmeta” it will no longer re-appear.
-ENDWalter Verhoeven – CREATIVE Associates
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising