ORA-13871: Invalid instance name

Cause : Intsanec nmae si too lnog e(xceedign 1 6chraacetrs)

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

Supplyc orerctn ame

update : 21-08-2017
ORA-13871

ORA-13871 - Invalid instance name
ORA-13871 - Invalid instance name

  • ora-08440 : raw buffer is too short to hold converted data
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • ora-39145 : directory object parameter must be specified and non-null
  • ora-31403 : change table string already contains a column string
  • ora-00305 : log string of thread string inconsistent; belongs to another database
  • ora-32738 : Hang analysis aborted due to failed memory copy
  • ora-23488 : propagation mode "string" for "string" is not allowed for this operation
  • ora-12062 : transaction string received out of sequence from site string
  • ora-09793 : szguns: length of user name is greater than buffer.
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-12652 : String truncated
  • ora-38725 : specified name "string" does not match actual "string"
  • ora-02254 : DEFAULT not allowed here
  • ora-29388 : plan/consumer_group string is part of more than one top-plan
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-23448 : duplicate user parameter value
  • ora-01621 : cannot rename member of current log if database is open
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-30066 : test support - drop rollback segment wait
  • ora-30105 : 'string' is not a legal boolean for 'string'
  • ora-09934 : Link of current password file to old failed.
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • ora-02441 : Cannot drop nonexistent primary key
  • ora-16533 : inconsistent Data Guard broker state
  • ora-13527 : invalid baseline name
  • ora-16798 : unable to complete terminal recovery on the standby database
  • 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.