nv-l
[Top] [All Lists]

Re: netview/nt and trapd

To: nv-l@lists.tivoli.com
Subject: Re: netview/nt and trapd
From: "Boyles, Gary P" <gary.p.boyles@INTEL.COM>
Date: Fri, 19 Feb 1999 07:33:00 -0800
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Oliver,
Is this on a multi-processor system?

Running ACCESS or MS-SQL DB?

If its access... there are some fixes availble at the Microsoft URL.
(I believe you go to "Databases").  Seems like the filename was
mdac_type.exe
(or something like that).

Gary Boyles


-----Original Message-----
From: OGrant [mailto:OGrant@PEC.COM]
Sent: Friday, February 19, 1999 7:15 AM
To: NV-L@UCSBVM.UCSB.EDU
Subject: netview/nt and trapd


For some time, I've been receiving the same message in my nv.log file -
here's a sampling:

02/19/99 07:08:04 [trapd] an application has disconnected.
02/19/99 07:49:02 [trapd] Trapd: (initODBC) Information from attempt to
connect to database: 00000 02/19/99 07:49:02 [trapd]   1. (00000)
[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to
'master'. 02/19/99 07:49:02 [trapd]   2. (01000) [Microsoft][ODBC SQL Server
Driver][SQL Server]Changed language setting to 'us_english'. 02/19/99
07:49:02 [trapd]   3. (01000) [Microsoft][ODBC SQL Server Driver][SQL
Server]Changed database context to 'NetViewDb'.

This message was appearing approx. once every hour....all day and week long.

The help files address the issue of netview disconnecting from the sql
database as being most likely an odbc problem.  After multiple attempts at
fixing the problem, I gave up and took the lazy man's out - thoroughly blow
away the server, re-install NT 4.0/sp3, sql server 6.5 and netview 5.1.  I
assumed the box was as odbc-"clean" as it would ever be, but yesterday's
re-appearance of this message seems to say otherwise.

In addition, prior to yesterday's re-install, netmon would periodically
cease functioning (i.e., no polling/discovery occuring), without the daemon
actually dying (showing a "stopped" message in the server setup.)
Physically restarting all daemons would suffice in correcting the problem.

Question: is an hourly disconnect message perhaps normal?  What, in fact, is
going here?  For those who have seen this message before, how have you
handled it (if at all)?  Many thanks from a netview/nt (relative) newbie,

Oliver M. Grant
Performance Engineering Corp.
703/273-9880, (F) 703/273-9881, (Alpha. Pager) 800/800-7759
ogrant@pec.com

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web