ORA-14613: Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed

Cause : Any nmae genreated rfom a aprtitino namea nd tepmlate anme muts be lses tha nthe mxaimum eprmissbile naem for na idenitfier

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

Shortne eithre parttiion o rtempltae nam.e

update : 23-08-2017
ORA-14613

ORA-14613 - Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
ORA-14613 - Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed

  • ora-27054 : NFS file system where the file is created or resides is not mounted with correct options
  • ora-01576 : The instance string is not enabled
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-28278 : No domain policy registered for password based GLOBAL users.
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-01678 : parameter string must be pairs of pattern and replacement strings
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-06928 : CMX: wrong ORACLE_SID
  • ora-09769 : osnmbr: cannot send break message
  • ora-02228 : duplicate SIZE specification
  • ora-12674 : Shared server: proxy context not saved
  • ora-31695 : Inconsistent master table on restart. The following SQL statement returned string identical objects. string
  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-37177 : column string does not have any leaf values
  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-29813 : non-supported object type with associate statement
  • ora-01061 : cannot start up a V8 server using a V7 client application
  • ora-13483 : insufficient memory for the specified GeoRaster data
  • ora-29820 : the statistics type is not present
  • ora-36970 : (XSRELTBL12) workspace object must be a self-relation.
  • ora-36844 : (XSLMGEN14) Dimension string.string!string is missing a string property value
  • ora-06807 : TLI Driver: could not open ethernet device driver file
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-07721 : scgcm: not enough OS resource to obtain system enqueue
  • ora-19249 : XP0029 - value does not match facet of the target type
  • ora-28672 : UPDATE BLOCK REFERENCES may not be used on a global index
  • ora-01755 : Must specify an extent number or block number
  • ora-30183 : invalid field width specifier
  • ora-13867 : Database-wide SQL tracing is already enabled
  • 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.