Hi,
The [15264] error occurs when we are attempting to lock an object in the row cache and find that the object does not exist. So it would make sense you are getting that error if the above is the case.

Every ORA-600 error creates a dump file in the user_dump_dest directory.

apperantly there is a bug in MetaLink on this issue
------------------------------------------------------------
Problem statement:

DROP PACKAGE ORA-600 [15264],DROP USER ORA-600 [15013],OBJECT_TYPE='NEXT OBJECT'
--------------------------------------------------------------------------------
PROBLEM:

Run "create package .body IS ... END;" will create an object named 'BODY'
with object_type= 'NEXT OBJECT' and user cannot drop object BODY or schema anymore.

drop package .body;
will give you ORA-00600 [15264]

drop user cascade;
will give you ORA-00600 [15013]

User schema is corrupted with orphan package left in data dictionary .
select object_name, object_type from user_objects;

OBJECT_NAME OBJECT_TYPE
------------------------------ ------------------
BODY PACKAGE
BODY NEXT OBJECT <-----

select obj#, owner#, name , type# from obj$ where name = 'BODY';
where name = 'BODY'
and owner# = ( select user_id from dba_users where username = '');

OBJ# OWNER# NAME TYPE#
---------- ---------- ------------------------------ ----------
2999 25 BODY 9
0 25 BODY 0 <---

'BODY' object with 'NEXT OBJECT' type always have object# = 0
and type# = 0


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

cheers,
R.