We provide ORA-00600 12807 quick fix as a service . contact [email protected]
Bug 13781691 ORA-600 [12807] if CON$.CON# very high due to bug 13784384
Affects:
| Product (Component) | Oracle Server (Rdbms) |
| Range of versionsBelievedTo be affected | (Not specified) |
| VersionsConfirmedAs being affected | 11.2.0.311.2.0.211.1.0.710.2.0.5 |
| Platforms affected | Generic (all / most platforms affected) |
Fixed:
| The fix for 13781691 is first included in | 12.1.0.1 (Base Release)11.2.0.4 (Server Patch Set) |
| Symptoms: | Related To: |
| Internal Error May Occur (ORA-600)ORA-600 [12807] | Constraint Related |
Description
An ORA-600[12807] occurs if CON$.CON# reaches a very high value.
This typically can occur due to bug 13784384.
This fix raises the upper limit of CON$.CON# for cases where it has
hit the limit.
Note:
It is vital to also find the cause of CON$.CON# increasing so much and
ensure that cause is patched otherwise you may hit this new higher
limit.
Workaround
NoneDBRECOVER Recovery Options
For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.
When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.