Cannot Restart Oracle After Setting Global Name to NULL
Last updated on DECEMBER 24, 2013
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]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
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms