Make sure you update the stored procedures on your SQL Server.
Everytime you make a change the ODBC driver I'd think you have to
modify the stored procedure on the server. You can run the command
from the \winnt\system32 directory.
ISQL /Usa /S(name of your server) /iinstcat.sql
Also, you may want to setup maintenance procedures for all of your
databases. During the initial discovery process, you my want to
temporarily stops the
discovery, truncate the transactions logs on tempdb. Check you log
under \MSSQL\log\errorlog. Make sure it is not getting to large.
Also, do you have snmpcollect running? if you do, try shutting it down
temporarily. It may improve the performance. Also, it won't fill up
the tempdb as quickly.
Xu He
Network Solutions, Inc
--- "Boyles, Gary P" <gary.p.boyles@INTEL.COM> wrote:
> I ran into some of those same problems, but
> installing the
> new mdac fixed it for me. I installed it before I
> upgraded
> to V5.1.1, though. Don't know if that makes a
> difference or not.
>
> You might want to try this... to re-init the
> event-db:
> 1) Do an ovstop (of everything... shotgun
> approach).
> 2) Goto \usr\ov\databases\odbc
> 3) Copy tess_db.mdb_empty (to) tess_db.mdb
> 4) Start everything back up.
>
> Its worth a shot.
>
> Regards,
>
> Gary Boyles
>
>
> -----Original Message-----
> From: OGrant [mailto:OGrant@PEC.COM]
> Sent: Tuesday, May 04, 1999 11:08 AM
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: netview 5.1.1/nt and trapd/netmon problems
>
>
> Installed netview 5.1.1 over 5.1/nt last week with
> so-so results -
> apparantly linked to outdated odbc drivers (sql
> server was 2.65, core were
> all 3.0.x). Discussed situation with tivoli support
> and implemented their
> suggested fix, which was as follows:
> - deinstall netview entirely
> - install mdac 2.0 from 5.1.1 cd
> - reinstall 5.1, followed by 5.1.1
>
> Problems appear to continue - event browser comes up
> very slowly, if at all
> - nv.log shows, among other lines, repeated error
> message of "trapd caught
> in do purge exeception - attempting to recover."
> When (if) it does come up,
> events are being processed and written to sql
> server.
>
> Although netmon is verifiably up, demand polling
> works intermittendly -
> frequent inabilities to connect to netmon on server.
>
> I suspect odbc as the cause again, but its seems
> less than likely now that
> mdac 2.0 (with updated odbc drivers) has been
> installed -- has anyone
> experienced similiar problems? I'm running nt 4.0
> w/ sp3 - Thanks much,
>
> Oliver Grant
> Performance Engineering Corp.
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|