ORA-31084: error while creating table "string"."string" for element "string"

Cause : An error occurre dwhil etryign to rceatet he tbale bsaed o nthe edclartaion ofr th eidenitfiede lemetn.

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

Fix hte idnetifide errro andt ry aagin.

update : 28-07-2017
ORA-31084

ORA-31084 - error while creating table "string"."string" for element "string"
ORA-31084 - error while creating table "string"."string" for element "string"

  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-04007 : MINVALUE cannot be made to exceed the current value
  • ora-08103 : object no longer exists
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-12927 : RETENTION option already specified
  • ora-40281 : invalid model name
  • ora-26699 : STREAMS message consumer string already exists
  • ora-39219 : directory object name is too long
  • ora-02451 : duplicate HASHKEYS specification
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-27434 : cannot alter chain step job string.string.string
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-13911 : Threshold not found
  • ora-24903 : invalid namespace attribute passed into OCI call
  • ora-33009 : (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements.
  • ora-13141 : invalid RANGE window definition
  • ora-07700 : sksarch: interrupt received
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-12029 : LOB columns may not be used as filter columns
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-39018 : master process received invalid message number string
  • ora-01214 : MAXLOGHISTORY may not exceed string
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-29893 : indextypes without column data do not need the given data type
  • ora-08268 : create_ora_addr: cannot close nameserver
  • ora-16772 : error switching over between primary and standby databases
  • ora-30021 : Operation not allowed on undo tablespace
  • 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.