Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

OCI-22053: overflow error

Since we upgraded to 4.0.2 some of our Oracle queries are returning down with the error 'OCI-22053: overflow error'. This is apparently due to the way the Oracle API is used with regards to high precision numbers.

Did something change somewhere along the line? We can put in some temporary fixes, but would rather fix the underlying issue with SolarWinds.

Find more posts tagged with

Accepted answers

All comments

martin.susil

Hello,

what APM version were you using previously? APM 3.5? There were some changes in this area to allow SQL Monitors also return a message, not just numeric value...

Could you give us example of SQL query which fails now?

Also, could you execute this SQL query directly on Oracle database and share what value it returns there?

Thank you

FormerMember

One of the queries is:

SELECT ((P1.value + P2.value - P3.value) / (P1.value + P2.value))*100
FROM v$sysstat P1, v$sysstat P2, v$sysstat P3
WHERE P1.name = 'db block gets'
AND P2.name = 'consistent gets'
AND P3.name = 'physical reads'

I'll get one of our DBAs to get the actual value from the system point of view.

FormerMember

select (disk.VALUE/memory.VALUE)*100
from
(
select NAME,VALUE
from v$sysstat
where NAME like 'sorts (disk)'
) disk,
(select NAME,VALUE
from v$sysstat
where NAME like 'sorts (memory)'
) memory

That also overflows, and our DBA shows the value on the system to be:

(DISK.VALUE/MEMORY.VALUE)*100

-----------------------------

.000942916

FormerMember

As a side note I upgraded the instantclient to 11.2.0.1 and it still has the same issue.