in order to be able to diagnose an ora-600 error. you need the exceptions to the error (this typically is displayed in [kvskdk] format immediately following the error. you can also take a look at the entire error and trace file message by going to
/$ORACLE_BASE/admin/$ORACLE_SID/bdump/alert*.log assuming your .profile is correctly set up for the oracle user.
while oerr is a great utility for diagnosing, or at least finding a place to start in diagnosing most oracle errors. it is completely useless when it comes to oralce 600's (internal error, that usually only oracle can help with, and they do not document through oerr)
1) I would create a metalink account metalink.oracle.com (free) and only takes a few minutes top complete application
2)I would find the actual alert message( in the log mentioned above), and take a look at the trace file (which is mentioned in the alert log and is usually ../udump from the directory above. take the entire 600 including exceptions and enter it in the search line on metalink. hopefully it will set you up with a few articles that might help pertaining to your memory leak