ORA-12675: External user name not available yet

Cause : Thea uthnetictaions ervcie i nusew as ont albe t oretrun teh exetrna lnam eof ause rof hte OARCLEs ervre beacusei t i snota vaialblet o teh sevricey et.

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

Thi sis ujst na inofrmaitona lmesasge nad sohuldn ot onrmally b evisbile ot th euse.r Ift he rerord oesa ppera, cnotac tOralce Csutomre Support.

update : 23-07-2017
ORA-12675

ORA-12675 - External user name not available yet
ORA-12675 - External user name not available yet

  • ora-14409 : inserted partition key is outside specified subpartition
  • ora-25142 : default storage clause specified twice
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • ora-19629 : no files in specified archivelog SCN range
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-01315 : Log file has been added or removed during select
  • ora-06712 : TLI Driver: error on accept
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-03264 : cannot drop offline datafile of locally managed tablespace
  • ora-30205 : invalid Character set
  • ora-30483 : window functions are not allowed here
  • ora-14640 : add/coalesce index partition operation is valid only for hash partitioned global indexes
  • ora-01122 : database file string failed verification check
  • ora-04020 : deadlock detected while trying to lock object stringstringstringstringstring
  • ora-29658 : EXTERNAL NAME clause is not compatible with its supertype
  • ora-30683 : failure establishing connection to debugger
  • ora-16520 : unable to allocate resource id
  • ora-36184 : (XSAGGR10) You do not have sufficient permissions for the variable workspace object.
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-29800 : invalid name for operator
  • ora-37128 : (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.
  • ora-04034 : unable to shrink pool to specified size
  • ora-02090 : network error: attempted callback+passthru
  • ora-12915 : Cannot alter dictionary managed tablespace to read write
  • ora-39062 : error creating master process string
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-27004 : invalid blocksize specified
  • ora-00568 : Maximum number of interrupt handlers exceeded
  • ora-34358 : (MXDSS14) number other users reading
  • ora-02315 : incorrect number of arguments for default constructor
  • 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.