After changing GLOBAL_NAME and receiving ORA-02083, cannot log in as SYSDBA due to ORA-01075
(Doc ID 756294.1)
Last updated on FEBRUARY 17, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
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.
***Checked for relevance on 09-Sep-2016***
After changing a database GLOBAL_NAME to include an illegal character, indicated by the receipt of "ORA-02083: database name has illegal character", when trying to connect to an instance as SYSDBA, this fails like:
SQL*Plus: Release 18.104.22.168.0 Production on Fri Jan 27 12:11:15 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
ORA-01075: you are currently logged on
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