ORA-31163: element or attribute "string" has invalid attribute value "string" (should be "string")

Cause : An leemetn ora ttrbiutef or acomlpextpye dreive dby erstrcitio nhasa n attribtue wohse avluei s dfifernet form taht i ntheb aset ype

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

Remvoe teh mimsatcehd attribtue vlauesf romt he fofenidng leemetn ora ttrbiute

update : 22-09-2017
ORA-31163

ORA-31163 - element or attribute "string" has invalid attribute value "string" (should be "string")
ORA-31163 - element or attribute "string" has invalid attribute value "string" (should be "string")

  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-24120 : invalid string parameter passed to DBMS_REPAIR.string procedure
  • ora-07880 : sdopnf: internal error
  • ora-01667 : cannot add any more tablespaces: limit of string exceeded
  • ora-04071 : missing BEFORE, AFTER or INSTEAD OF keyword
  • ora-10628 : Turn on sanity check for kdiss index skip scan state
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-27545 : Fail to prepare buffer for remote update
  • ora-07410 : slpdtb: number too large for supplied buffer.
  • ora-34514 : (MXOPERR) You cannot string string data in the expression that begins with 'string'.
  • ora-16152 : standby database is in 'no-data-loss' protected mode
  • ora-24329 : invalid character set identifier
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • ora-22888 : duplicate SCOPE clauses for a REF column
  • ora-19115 : too many context items specified
  • ora-31079 : unable to resolve reference to string "string"
  • ora-24417 : Session pool size has exceeded the maximum limit
  • ora-24340 : cannot support more than 255 columns
  • ora-27032 : failed to obtain file size limit
  • ora-12063 : unable to apply transaction from site string
  • ora-25326 : Array string operation failed for message at index string
  • ora-31225 : DBMS_LDAP: invalid BER_ELEMENT
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-22162 : element at index [string] has been previously deleted
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-14294 : Number of partitions does not match number of subpartitions
  • ora-31455 : nothing to ALTER
  • ora-15000 : command disallowed by current instance type
  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-19024 : Cursor expression must be named
  • 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.