This error indicates that the up.time Data Collector was unable to open sessions with the Oracle database, which can have a negative impact on up.time performance and stability.
This problem typically occurs when the connectionPoolMaximum value in the uptime.conf file exceeds the SESSIONS parameter in the Oracle database. To resolve this issue, either reduce the connectionPoolMaximum value or increase the SESSIONS available on the Oracle database. |
IOException: Not enough space (Java heap) | Rating | Views | |
---|---|---|---|
This article explains the IOException: Not enough space message and how to resolve it. By: uptime Support | Date Created: 1-12-2007 | Last Modified: 7-6-2011 | Index: 115 |
4937 |
Error: java.net.BindException: Address already in use | Rating | Views | |
---|---|---|---|
The exception below appears when starting the up.time data collector service in the following scenarios 1 - The up.time data collector is already running 2 - Another service is using the up.time... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 286 |
4612 |
Data collector won't start - "Not a trusted IP" error in uptime.l... | Rating | Views | |
---|---|---|---|
If your data collector service will not start due to an error in uptime.log similar to: xxx.xxx.xxx.xxx: is not a trusted ip xxx:xxx:000:xxx:xxx:0X0x:x000: is not a trusted ip It is usually due... By: uptime Support | Date Created: 10-2-2009 | Last Modified: 8-10-2011 | Index: 382 |
2424 |
Resolving JVM_BIND Errors in up.time | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 6-7-2006 | Last Modified: 8-9-2011 | Index: 075 |
9672 |
Java heap space Throwable: java.lang.OutOfMemoryError | Rating | Views | |
---|---|---|---|
Example error message: 2010-07-09 16:42:41,654 ERROR (PerfERDC:137) - service Platform Performance Gatherer (192) on host DKLBMMDB1 (34) Error getting data from agent: Java heap space Throwable:... By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 495 |
3617 |