wtdbclear

There are two versions: binary executable and Perl script:

# file /opt/TMF/bin/aix4-r1/bin/wtdbclear
/opt/TMF/bin/aix4-r1/bin/wtdbclear: executable (RISC System/6000) or object module

# which wtdbclear.pl
/opt/TMF/bin/aix4-r1/bin/wtdbclear.pl

http://www.ibm.com/support/docview.wss?uid=swg21390748

Good troubleshooting steps:

• $BINDIR/bin/wtdbclear -e -s CLOSED -t 0  # to remove all closed events
• $BINDIR/bin/wtdbclear -e -r HARMLESS -t 0  # to remove all harmless events

Compete cleanup:

• wtdbclear -left 86400 #  clears out all the entries in TEC older then 24 hours.
• wtdbclear -let  86400 #  clears out all events older then 24 hours if everything is OK.  Never use if TEC server is running.
• wtdbclear -left 0 # clears out all events queued and waiting from tec reception, tec repository and task repository to basically start from scratch)

Additional examples:

• wtdbclear -r HARMLESS (clears out all events of HARMLESS severity)
• wtdbclear -r WARNING (clears out all events of WARNING severity)
• wtdbclear -s CLOSED (clears out all events with closed status)
• wtdbclear -left 1900800 -> this command will clear out history events before 22 days prior to today.
• wtdbclear -elt 4406400 # To keep 51 days...use 4406400 seconds
  > wtdbclear.pl -elt 4406400
  
  Some sample numbers.

Some sample numbers.

• 86400 seconds per day.
• 604800 seconds per week.
• 22 days x 24 hours x 60 min x 60 sec =1900800 seconds

Usage: wtdbclear [-e] [-l] [-f] [-w] [-c <class>] [-r <severity>] [-s <status>] [-t <seconds>] [-p FALSE] [-a <# rows to commit after>]

Note: Never use if TEC server is running.

NEWS CONTENTS

• 200102 : IBM - Reading the wtdbspace at TEC 3.8 and 3.9 ( IBM - Reading the wtdbspace at TEC 3.8 and 3.9, )
• 200102 : IBM IBM Tivoli Enterprise Console V3.9 Implementation ( IBM IBM Tivoli Enterprise Console V3.9 Implementation, )
• 200102 : IBM - Running wtdbclear.pl, events queue up in TEC ( IBM - Running wtdbclear.pl, events queue up in TEC, )

Old News ;-)

IBM - Reading the wtdbspace at TEC 3.8 and 3.9

Question

Since the database schema has changed at version 3.8 how do you tell quickly that your TEC database is in a healthy state?

Answer

Firstly you can run wtdbspace with the -T option to limit the output to the TEC related data and the TEMP areas.

If any tablespace other than the TS_TEST_DATA is getting to about 80% you would want to run wtdbclear.

The new third section of wtdbspace shows you what tables are on which table spaces, and knowing which tables are cleared with wtdbclear and its options, you can decide which options of wtdbclear to use.

For example:
If only the TS_REC_LOG is getting full you can just run wtdbclear -lt 0.
If the TS_EVT_REP or TS_SLOTS_TASK are filling up you would need to do wtdbclear -et 0.
If TS_LONG or TS_INDEXES are getting full you'd probably need to run wtdbclear -elt 0 as all the TEC tables use those tablespaces.

Be aware that the table space names are customizable and so may not be TS_REC_LOG, etc.

IBM IBM Tivoli Enterprise Console V3.9 Implementation

Why is the wtdbclear binary preferred over the wtdbclear.pl Perl script?

1. The wtdbclear binary accesses the new database stored procedures to improve rate of database clearing.

IBM - Running wtdbclear.pl, events queue up in TEC

tips on improving the performance of wtdbclear.pl -- sometimes the wtdbclear.pl processes run for hours as well as the queuing of events

Cause need to use options on wtdbclear.pl

Solution To improve the running of wtdbclear.pl processes, perform the following steps:

1. Set the -b parameter higher than the number of events to be retrieved.

NOTE: This makes the database read happen only once and not contend with the deletes. If this is not done, the program reads '-b buffer' amount of events, starts the deletes, reads the next set of events, and so on. Either process can get locked out at this point because of RIM internal hangs.

TEC 3.6.1-TMF-0049 fixes this problem by having separate 'agent' processes servicing each program. This is no longer an issue after patch 3.6.1-TEC-0006 is applied, as this patch changes wrimsql to read in all requested records in one pass.

2. Set the -a option low enough to get more frequent commits.

NOTE: The commit will free all held locks. This helps avoid contention and lock escalation to table or database locks.

3. Run clears for the reception log in a different job than the event repository clears.

NOTE: This helps avoid locks being set by one user on both tables at once and ending up with lock escalation to the database level. It would be best to only have one wtdbclear.pl job running at any given time.

4. Ensure the database's locking parameters are tuned well.

NOTE: Properly tuned databases are essential for applications with updating.

Reference

Syntax

Description

The wtdbclear command must be run from the event server.

Authorization

Options

-a records

A commit is performed after x number of records are deleted.

-c classname

Clears events with the specified class name.

Note:

You cannot use the this option when clearing the reception log with the -l option.

-e

Deletes events in the event repository, task repository, and extended event attribute table. You must use the -t option to specify the age of the events to be deleted.

-f

Forces deletion of QUEUED and WAITING events from the reception log.

Note:

Never use this option while the Tivoli Enterprise Console server is running.

-l

Deletes events in the reception log. You must use the -t option to specify the age of the events to be deleted.

Note:

You cannot use the -c, -r, or -s options when clearing the reception log with this option.

-p TRUE | FALSE

Indicates whether the stored procedure, tec_p_clear_events, should be called. The default value is TRUE. The tec_p_clear_events procedure improves the runtime performance of wtdbclear.

-r severity

Clears events with the specified severity. The valid default values are FATAL, CRITICAL, MINOR, WARNING, HARMLESS, and UNKNOWN.

Note:

You cannot use the this option when clearing the reception log with the -l option.

-s status

Clears events with the specified status. The valid default values are OPEN, CLOSED, RESPONSE, and ACK.

Note:

You cannot use the this option when clearing the reception log with the -l option.

-t seconds

Deletes events that are older than the specified number of seconds. This option is required.

-w

Forces deletion of events that have not yet been processed by the data warehouse extract, transform, and load (ETL) process. If the Tivoli Enterprise Console warehouse enablement pack is installed, events in the repository are periodically processed by the warehouse ETL process. If you issue the wtdbclear command and specify a time window that includes events that have not yet been processed by the warehouse ETL process, the wtdbclear command returns a warning message. Use the -w option to force deletion of these events.

Notes

Examples

wtdbclear -e -t 0

The following example clears the entire database:

wtdbclear -elf -t 0

The following example disables the use of the stored procedure:

wtdbclear -elt 0 -p FALSE

The following example, because it specifies more than one of the -c, -s,, and -r options, deletes all events that have a severity of HARMLESS or all events that have a class value of TEC_Start:

wtdbclear -r HARMLESS -c TEC_Start -et 0

See Also

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019