-
Title
ORA-06502: PL/SQL: numeric or value error: character to number conversion error -
Description
We recently upgraded one of our databases from Oracle 9 to Oracle 10. The connection to this database from the Spotlight monitor causes the following trace to be generated over and over:
----------------------------------------*** ACTION NAME:() 2011-01-31 09:27:17.765
*** MODULE NAME:(Spotlight.exe) 2011-01-31 09:27:17.765
*** SERVICE NAME:(SYS$USERS) 2011-01-31 09:27:17.765
*** SESSION ID:(511.1966) 2011-01-31 09:27:17.765
*** 2011-01-31 09:27:17.765
ksedmp: internal or fatal error
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
Current SQL statement for this session:
SELECT p.name, --CloseCursor (1856332)
SUBSTR(quest_soo_pkg.translate_parameter(value),1,200) value,
NVL(quest_soo_pkg.translate_parameter(value), 0) num_value,
p.isdefault
FROM v$system_parameter p
UNION ALL
SELECT 'log_mode',
TO_CHAR(DECODE(log_mode,'ARCHIVELOG',1,0)) log_mode,
'' num_value,
'TRUE'
FROM v$database
-
Cause
That database has the event initialization parameter set to "4030 trace name errorstack forever, level 10:6502 trace name errorstack forever, level 12:3113 trace name errorstack level 3:3114 trace name errorstack level 3" which is causing Oracle to create a trace file every time an ORA-06502 error is generated.
-
Resolution
WORKAROUND
Try putting the following in the spotlight.ora (located at C:\Program Files\Quest Software\Spotlight\Plug-ins\SoO)...
alter session set events '6502 trace name errorstack off'...this will override that setting just for Spotlight.
-
Additional Information
Note: May need to re-evaluate whether this setting in the initialization parameter file is intentional as this is normally something set to track down an issue rather than permanently having it on. If it is required, then the workaround mentioned in this solution should resolve the issue.