After discussing this with my colleague who does tralertd, I think you will
need to open a problem on this and get some tracing donn to really get to
the bottom of it. Per my colleague, the gist of the situation is this:
It is not easy to determine why tralertd is unable to write to the tralertd
database as there are lots of possible reasons
(ie, permissions problem, full database, a configuration problem in the
tralertd.conf or trapd.conf). It is best to configure
the alerts so that the alerts are less than 512 bytes, and there are not
too many mib variables.
I believe most customers do not even use or need the tralertd database.
The mib variables from the alert are written
to the database when the alert goes over 512 bytes, or the mib variables go
over 44 bytes. The alert is then truncated
and the alert sent. The data can be retrieved by the host by issuing:
runcmd sp=spname,appl=applname,gettrap log-id-of-alert
In the later levels of NetView/6000 customers can turn off the tralertd
database and avoid this problem
by: smit nv6000, Configure, set options for daemons, set options for host
connection daemons, set options for
Set "Using tralertd database" to no.
So if you have to use the database for historical purposes, then my advice
is to open a problem to Support.
Tivoli (NetView for UNIX) L3 Support
Vynita Pretorius <vpretor AT fast.co DOT za> on 07/14/98 09:14:42 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L AT ucsbvm.ucsb DOT edu>
To: NV-L AT ucsbvm.ucsb DOT edu
cc: (bcc: James Shanks)
Subject: Tralertd database
-- [ From: Vynita Pretorius * EMC.Ver #2.5.02 ] --
We run msmip which feed msm on Netview M/F
Our system AIX 4.1.5. Netview 4.1 Service point and SNA comms server and
Automation on the mainframe checks to see messages/ alerts being
sent from the Netview /AIX. If in an allotted time it does not receive an
it starts alerting on the Netview M/F consoles.
I have written automation to check Spappld and tralertd Service point and
SNA connectivity and send an alert every 5 minutes, which works well,
However sometimes The automation
on the M/F starts alerting yet if I send an alert it gets to NPDA.
1) Could our alerts be corrupt
2) The only warning on the AIX side is that tralertd is unable to write to
the database yet the filesystem has plenty on space.
Could anybody tell me why this is happening.