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 : 26-04-2017
ORA-28027

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

  • ora-12092 : cannot online redefine replicated table "string"."string"
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-24271 : translation type must be either T, S or M
  • ora-37080 : Advice requested for hierarchy with too many levels
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-07744 : slemcl: invalid error message file handle
  • ora-02256 : number of referencing columns must match referenced columns
  • ora-32333 : disable table scn update for Materialized view
  • ora-30051 : VERSIONS clause not allowed here
  • ora-16084 : an apply engine is already running
  • ora-30386 : invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE
  • ora-16226 : DDL skipped due to lack of support
  • ora-21705 : service context is invalid
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-24007 : invalid value string, MAX_RETRIES should be non-negative integer
  • ora-24368 : OCI mutex counter non-zero when freeing a handle
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-01677 : standby file name convert parameters differ from other instance
  • ora-00150 : duplicate transaction ID
  • ora-23464 : flavor lacks column string of "string"."string"
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-12650 : No common encryption or data integrity algorithm
  • ora-12591 : TNS:event signal failure
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-13281 : failure in execution of SQL statement to retrieve WKT
  • ora-32822 : subscriber string is marked for removal
  • ora-35280 : (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
  • ora-03296 : cannot resize datafile - file string not found
  • ora-01264 : Unable to create string file name
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.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.