Custom Search . . .

Wednesday, September 10, 2008

ORA-00600: internal error code, arguments: [kxspoac : EXL 1]

Today we are faced the below error in our one of production database.


ORA-00600: internal error code, arguments: [kxspoac : EXL 1]


Database Version: 10.2.0.1

OS Version: Windows


This is database bug in 10.2.0.1 to 10.2.0.3. Due to this error if a SQL statement fails with Ora-600 [kxspoac : EXL 1] when executed by a parallel execution slave and that SQL statement has numeric binds then you are probably seeing this bug.


Solution:


This bug fixed in oracle 10.2.0.4 & 11.1

Refer more details in : Metalink document: 389438.1

3 comments:

Mohammed Taj said...

Thanks for sharing with us.

Regards,
Taj

Babu B said...

Thanks a lot taj..

Babu

Mortinke said...

We got this error "ORA-00600: internal error code, arguments: [kxspoac : EXL 1], [2000], [128], [], [], [], [], [], [], [], [], []" after executed
"ALTER SYSTEM SET EVENTS '10503 trace name context forever, level 2000';" with oracle 11.2.0.3.

We identify the statement in the dump file from the trace file.

----- Current SQL Statement for this session (sql_id=dqbhc9r7gz0a5) -----
SELECT DECODE(COUNT(CLIENT_INFO), 0, 'down','up') FROM GV$SESSION WHERE CLIENT_INFO = :B1

Only remove this statement from shared pool didn resolve the problem.

We executed the Event 10503 with a smaller value again:

ALTER SYSTEM SET EVENTS '10503 trace name context forever, level 128';

Afterwards we removed the statement from the shared pool:

select inst_id,address,hash_value from gv$sqlarea where sql_id='dqbhc9r7gz0a5';

BEGIN
DBMS_SHARED_POOL.PURGE ('00000005C4BE2940,3472851269','C');
end;

After that, the problem no longer occured.