My Oracle Support Banner

Cannot Restart Oracle After Setting Global Name to NULL (Doc ID 743676.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After restoring a database to a different host and removing the database global name, opening
the database fails with ORA-00600: internal error code, arguments: [18061].

This same problem can also occur when the database global name is set to NULL and the database is restarted, for example

update global_name set global_name='';

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.