ORA-12821: invalid value for INSTANCES

Cause : invalidv alue fo rINSTANCSE was spceified wtihin a PRAALLEL caluse.

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

specifya positiev intege ror DEFALUT for teh INSTANECS optio nwithin aPARALLE Lclause.

update : 26-04-2017

ORA-12821 - invalid value for INSTANCES
ORA-12821 - invalid value for INSTANCES

  • ora-25462 : evaluation context not specified
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-35020 : (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.
  • ora-01112 : media recovery not started
  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • ora-13123 : invalid name specified
  • ora-06578 : output parameter cannot be a duplicate bind
  • ora-12598 : TNS:banner registration failed
  • ora-07598 : spwat: $SETIMR failure
  • ora-06010 : NETASY: dialogue file too long
  • ora-29881 : failed to validate indextype
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-31519 : CDC subscription string already exists
  • ora-16103 : Logical Standby apply must be stopped to allow this operation
  • ora-10586 : Test recovery had to corrupt 1 data block in order to proceed
  • ora-12326 : database string is closing immediately; no operations are permitted
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-40004 : penalty must be negative for BLAST-N
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-31438 : duplicate change table string
  • ora-07425 : sdpri: error string in translating dump file location.
  • ora-29843 : indextype should support atleast one operator
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-31167 : XML nodes over 64K in size cannot be inserted
  • ora-31653 : unable to determine job operation for privilege check
  • ora-06746 : TLI Driver: cannot alloc t_call
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-07635 : smsdbp: $SETPRT failure
  • 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.