000027884 - KB-1607 - ORA-600 error seen during collections. Internal error code  arguments: [13013]  [5001]?

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027884
Applies To6.x; 5.X
ORA-00600, ora 600, [13013], [5001], Opatch
RSA Identity Management and Governance
IssueORA-00600: internal error code, arguments: [13013], [5001]... are seen in the aveksaServer.log, often during failed Active Directory or LDAP collection runs.
KB-1607 - ORA-600 error seen during collections. Internal error code, arguments: [13013], [5001]?
ResolutionError Summary:
ORA-600 is an internal error generated by kernel code of the Oracle RDBMS software. ORA-600s are somewhat unique among oracle errors in that they have a series of arguments. The arguments are enclosed in square brackets and follow the error on the same line. For Example: ORA-00600 [14000][51202][1][51200][][]. Each argument has a specific meaning. This purpose of this article is to aid in the resolution of a specific ORA-600 error, the ORA-00600 [13013], [5001]...

The ORA-00600 [13013], [5001]... error in the Aveksa Server log is indicative of a known Oracle error that can be found on Oracle Linux-64bit servers. Some examples of this error that we have seen are:

ORA-00600: internal error code, arguments: [13013], [5001], [84496], [1701], [64], [1702], [17], [], [], [], [], [] 

ORA-00600: internal error code, arguments: [13013], [5001], [75912], [10967], [61], [11956], [17], [], [], [], [], [] 

ORA-00600: internal error code, arguments: [13013], [5001], [99485], [22537], [19], [56143], [17], [], [], [], [], []

There are other instances of ORA-00600's that are not covered by this patch, so if you have an ORA-00600 error which is not followed by [13013], [5001], then this article will not provide your solution.

If you are unsure whether you need to install this patch, please contact Aveksa Technical Support for advisement.


There is an Oracle-provided patch, p12345717, that may resolve this issue. This patch is exclusively for Oracle 11g environments, and should not be applied on 10g. If you are running an Appliance please follow the steps provided here, otherwise please alert your DBA as to the potential need for an Oracle patch.

Steps to install the Oracle Patch:

1) Log in to the machine as the Oracle user

2) Stop the ACM server

$ acm stop

3) Backup your Oracle database

$ cd /home/oracle/database/DBA/AVDB/scripts

$ ./AVDB_Export_Avuser.sh -t pre_oracle_patch

4) Stop the Oracle ACM instance

$ acm stopdb

5) Create a directory under $ORACLE_HOME and move the .zip file there


$ mkdir ora600patch

6) cd to that direcotory and unzip the patch file

$ cd $ORACLE_HOME/ora600patch

7) cd to the patch directory created by the unzip command

8) Add the Oracle OPatch directory in your $PATH environment variable:


9) Confirm you can find opatch and the Oracle inventory

$ opatch lsinventory

This will return current Oracle installation information. If this command fails, please contact Aveksa Support, as the environment the patch is being installed in is likely not setup correctly.

10) Apply the patch:

$ opatch apply

and answer 'y' to the prompt.

11) After completion of patch installation, restart the ACM Oracle Instance, followed by the ACM Server, and run your collections

$ acm startdb

$ acm start

NotesKB-1607 - ORA-600 error seen during collections. Internal error code, arguments: [13013], [5001]?
Legacy Article IDa67224