Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

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:

Compete cleanup:

Additional examples:

Some sample numbers.

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.


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

Clears events from the event database.

Syntax

wtdbclear [-e] [-f] [-l] [-c classname] [-r severity] [-s status] -t seconds [-a records] [-p TRUE | FALSE] [-w]

Description

The wtdbclear command deletes events from the reception log, event repository or both. Which tables it deletes rows from depends on the options specified.

The wtdbclear command must be run from the event server.

Authorization

senior

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

If more than one of the -c, -s, and -r options is specified, the result is a logical OR.

Examples

The following example deletes all events from the event repository:
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

wdbmaint.sh, wtdumper, wtdumprl, wtdumptr

 



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

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 quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard 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 DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting 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-MonthHow 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


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

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.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

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 author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: July 07, 2013