ORA-28027: privileged database links may be used by global users

Cause : Only users IDENTIFIED GLOBALLY may use a privileged database link.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Either change the user to a global user or try to use a different database link.

update : 24-05-2017

ORA-28027 - privileged database links may be used by global users
ORA-28027 - privileged database links may be used by global users

  • ora-26716 : message limit reached
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-32109 : invalid column or parameter position
  • ora-00600 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-16188 : LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-13415 : invalid or out of scope point specification
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-14607 : Tablespace was not specified for previous subpartitions in template but is specified for string
  • ora-26690 : datatype not supported at non-Oracle system
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-01636 : rollback segment 'string' is already online
  • ora-12902 : default temporary tablespace must be SYSTEM or of TEMPORARY type
  • ora-16512 : parameter exceeded maximum size limit
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-33064 : (XSAGDNGL31) In AGGMAP workspace object, the hierarchy dimension QDR workspace object cannot refer to the related dimension of the relation.
  • ora-19657 : cannot inspect current datafile string
  • ora-31113 : XDB configuration may not be updated with non-schema compliant data
  • ora-16216 : Log stream sequence error
  • ora-22982 : cannot create sub-view under this view
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-18009 : one or more outline system tables do not exist
  • ora-31012 : Given XPATH expression not supported
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-15077 : could not locate ASM instance serving a required diskgroup
  • ora-13155 : invalid number of dimensions specified
  • ora-37128 : (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.
  • ora-02305 : only EXECUTE, DEBUG, and UNDER privileges are valid for types
  • ora-23342 : invalid parameter column string
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.