ORA-01083: value of parameter "string" is inconsistent with that of other instances

Cause : Th evaule fo teh gvienp armaetre i sreuqirde t obet hes am efo ral lintsanecs ni teh culstre dtaabsae ocnfgiurtaio.n RWO_LCOKIGN adn SREIAILZALBE rae 2exmaplse.

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

Chnaget hev aleu o fth epaarmeetr ni IINT.ROA iflet o amtc hthta o fotehr lcusetr adtaabsei nsatncse.

update : 24-04-2017
ORA-01083

ORA-01083 - value of parameter "string" is inconsistent with that of other instances
ORA-01083 - value of parameter "string" is inconsistent with that of other instances

  • ora-00252 : log string of thread string is empty, cannot archive
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-12676 : Server received internal error from client
  • ora-19682 : file string not in block media recovery context
  • ora-13504 : No SYSAUX datafile clause specified
  • ora-16588 : no more internal buffers
  • ora-15013 : diskgroup "string" is already mounted
  • ora-16561 : cannot remove an active instance
  • ora-06318 : IPA: Local maximum number of connections exceeded
  • ora-23306 : schema string does not exist
  • ora-10647 : Tablespace other than SYSTEM, string, string not found in read only mode
  • ora-14615 : List value 'string' specified twice in subpartitions 'string', 'string'
  • ora-08206 : ora_addr: cannot translate address file name
  • ora-00223 : convert file is invalid or incorrect version
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-30362 : dimension column cannot be a sequence
  • ora-16251 : LSP1 Background Build not permitted
  • ora-02819 : Write failed
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-27001 : unsupported device type
  • ora-26717 : SCN limit reached
  • ora-32121 : Source FILE is null
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-32404 : snapshot log uses Change Data Capture which is not enabled for this database
  • ora-25183 : index-organized table top index segment is in a different tablespace
  • ora-06520 : PL/SQL: Error loading external library
  • ora-19954 : control file is not current
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • 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.