ORA-19714: length for generated name longer than string

Cause : The psecifeid fomrat ecxeedst he mxaimuml engt hfor hte picee naem.

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

Chaneg thef orma tto cerate hsorte rpiec ename.s

update : 24-06-2017

ORA-19714 - length for generated name longer than string
ORA-19714 - length for generated name longer than string

  • ora-07746 : slemrd: invalid error message file handle
  • ora-13455 : GeoRaster metadata TRS error
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-33080 : (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement.
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-32620 : illegal subquery within MODEL rules
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-38494 : column in the table alias and an attribute have matching names
  • ora-16233 : The table string.string is unsupported now
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-12154 : TNS:could not resolve the connect identifier specified
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-09364 : Windows 3.1 Two-Task driver unable to create hidden window
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-30931 : Element 'string' cannot contain mixed text
  • ora-06912 : CMX: write error in datarq
  • ora-37008 : (AWLISTALL06) number writers
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-18004 : outline already exists
  • ora-01543 : tablespace 'string' already exists
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-10578 : Can not allow corruption for managed standby database recovery
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-19400 : System type conflict with object SYS.string
  • ora-32407 : cannot exclude new values when materialized view log includes new values
  • ora-13454 : GeoRaster metadata is invalid
  • ora-19101 : CONTENT keyword expected
  • ora-02404 : specified plan table not found
  • ora-19661 : datafile string could not be verified
  • ora-19766 : missing CHANGE keyword
  • 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.