ORA-00600: internal error code, arguments: [2116], [900], [], [], [], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [2116], [900], [], [], [], [], [], [], [], [], [], []

There is a metalink note ( see below ) about a timeout on opening the controlfile.

The same error can happen if you use DNFS ( direct NFS ) , and somehow... you modify the IP the storage or server.

Until you don't modify oranfstab, you can not mount/open the database, and the same misleading error you have is ORA-00600: internal error code, arguments: [2116], [900], [], [], [], [], [], [], [], [], [], []

Applies to:

Oracle Server - Enterprise Edition - Version: 11.2.0.2 and later   [Release: 11.2 and later ]
Information in this document applies to any platform.

Symptoms

ORA-00600: internal error code, arguments: [2116], [900], [], [], [], [], [], [], [], [], [], [] In the alert log and DISKMON logs show dskm_slave_thrd_creat1: no more slave table slots left!

Changes

Trying to start up more than 15 database instances on Exadata 11.2.0.2

Cause

This is caused by a combination of following unpublished defects that are corrected in the latest patch bundle

unpublished bug:9842238
and
unpublished bug:11719062

Solution

Apply 11.2.0.2 Exadata Patch Bundle 4
This can be downloaded with Patch:11668495