Solved

nmi.log file

Posted on 2003-11-17
2
1,060 Views
Last Modified: 2009-12-16
Hi Experts,
I have a file in my c:\oracle\ora81\network\log directory named nmi.log.  This file is almost 2 gig in size and is a text document. What is this and is it really needed.

Can I delete it to free up some disc space .. ?
How can I control the size of this in the future?

Romans
0
Comment
Question by:Romans
  • 2
2 Comments
 
LVL 13

Accepted Solution

by:
anand_2000v earned 50 total points
ID: 9768860
PURPOSE
-------
 
The purpose of this note is to explain to you why you are getting very  
large log/trace files, e.g. nmi.log and how you can get around that.
 
 
Why are you getting large log/trace files:
------------------------------------------
 
You upgraded the database from 7.3.4 to 8.1.5.  You are using 815 agent with
OEM 2.0.4.  Some of the log or trace files, e.g. Nmi.log keeps expanding and  
filling the hardware drive.
 
There are many reasons for this problem.  However, you need to consider the  
following reasons.
 
Usually after the agent writes something in nmi.log, dbsnmpc.log, dbsnmpw.log,  
dbsnmpc.trc, dbsnmpw.trc, oratcl.trc, it should close the file to make a  
cleanup.  
However, if you are facing that problem, you can do the following to avoid it:
 
1) Stop the agent  
2) Remove and/or copy log and trace files,  
3) Restart agent  
 
Another reason for that problem that you may need to consider is if the  
listener.ora includes EXTPROC1, the agent keeps log and trace files locked and  
you will not be able to cleanup while running.    External procedure (EXTPROC)  
causes that problem in version 8.0.5 (bug 908515).  This problem occurs when  
you have two Oracle homes, one for 7.3.4 and another for 8.0.5.  The agent and  
the listener are in the 8.0.5 home.  The agent is unable to connect to the  
7.3.4.  OEM events will not function because the database will always show as  
DOWN, thus UP DOWN events will always fail with the RED flag, others will  
fail.
 
 
If the listener.ora is causing the large nmi.log, you need to do the following:
 
1) remove the following standard entries from the listener.ora
                 (ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC) (KEY=EXTPROC1))
 
and
 
              (SID_DESC=(SID_NAME=EXTPROC) (PROGRAM=EXTPROC))
 
Once these entries have been removed and the listener has been restarted the  
errors will no longer appear in the .log files, but you will not be able to  
use external procedures and thus oracle cartridges.   Agent 815 does not cause  
this problem when used with multiple oracle homes and external procedures.
 
There might be other reasons for large log files, e.g. nmi.log.  
Just consider the above two workarounds if applicable.

.
0
 
LVL 13

Expert Comment

by:anand_2000v
ID: 9768867
Prevent the nmi.log file(s) from growing large:

1. Insert these lines in snmp_rw.ora (located in \network\admin dir):
---------------------------------------------------------------------
nmi.trace_filecnt = Number of trace files the Intelligent Agent will keep on the system. If the maximum number is
reached, the trace files will cycle, and re-use the first one again.

Use this parameter in combination with the
nmi.trace_filesize parameter.

nmi.trace_filesize = Maximum filesize, in Kb, allowed per trace file.If the trace file grows beyond this size, the current one will be closed, and a new one, with a higher sequence number will be created.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction A previously published article on Experts Exchange ("Joins in Oracle", http://www.experts-exchange.com/Database/Oracle/A_8249-Joins-in-Oracle.html) makes a statement about "Oracle proprietary" joins and mixes the join syntax with gen…
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
This video shows how to copy a database user from one database to another user DBMS_METADATA.  It also shows how to copy a user's permissions and discusses password hash differences between Oracle 10g and 11g.

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question