Home » RDBMS Server » Enterprise Manager » ons.log files too large
ons.log files too large [message #250306] Mon, 09 July 2007 10:46 Go to next message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
Hi,

I'm running Oracle10g on RHEL 4. For some reason my ons.log files are getting huge (1.5G) and then they fill up the disk and I can't log in to Oracle. What could cause this? And where can i change the size?

thank you
Re: ons.log files too large [message #250311 is a reply to message #250306] Mon, 09 July 2007 10:56 Go to previous messageGo to next message
Michel Cadot
Messages: 64152
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
From
Enterprise Manager Grid Control Installation and Basic Configuration
Chapter 11 Upgrading Enterprise Manager Grid Control

Quote:
There may be instances where the Enterprise Manager Using a New database installation and its subsequent upgrade encounters an abnormal growth of the ons.log. This can potentially take up a lot of disk space relatively quickly.

In such circumstances, you must check whether or not the ons.log contains repeated messages such as the following:

Local connection 0,127.0.0.1,6100 missing form factor

If such an error message is observed in the ons.log, perform the following steps:

1/ In the Database Oracle home, rename the $ORACLE_HOME/opmn/conf/ons.config file (in order for the Listener not to find the database to sue it). For example,

cd $ORACLE_HOME/opmn/conf
mv ons.config ons.config.orig

2/ Restart the Listener.

Regards
Michel
Re: ons.log files too large [message #250320 is a reply to message #250311] Mon, 09 July 2007 11:09 Go to previous messageGo to next message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
Bingo!! That was the exact document I was looking at.

Thanks Michel
Re: ons.log files too large [message #250357 is a reply to message #250311] Mon, 09 July 2007 14:29 Go to previous message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
I have now found a new issue. If I give the above mentioned command (i.e. renaming the ons.conf file), then I can't start http server. It is looking for the old file name:



[oracle@rh-staging conf]$ /opt/app/oracle/product/10.2.0/http_1/opmn/bin/opmnctl start
open failed for /opt/app/oracle/product/10.2.0/http_1/opmn/conf/ons.conf (No such file or directory)
opmnctl: opmn start failed
Previous Topic: DBConsole Crashes with Page Cannot Be Displayed
Next Topic: em
Goto Forum:
  


Current Time: Sat Dec 10 22:20:55 CST 2016

Total time taken to generate the page: 0.04557 seconds