ORA-19712: table name exceeds maximum length of string

Cause : The table name string exceeds maximum length.

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

Retry the operation with a shorter table name.

update : 24-06-2017
ORA-19712

ORA-19712 - table name exceeds maximum length of string
ORA-19712 - table name exceeds maximum length of string

  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-15117 : command only operates on one diskgroup
  • ora-24143 : invalid evaluation context name
  • ora-09840 : soacon: Name translation failure.
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-06117 : NETTCP: unable to create ORASRV: quota exceeded
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-13702 : Snapshot IDs specified by the range [string, string] are equal.
  • ora-09959 : IMON: deletion of a process failed.
  • ora-02848 : Asynchronous I/O package is not running
  • ora-09801 : Unable to get user ID from connection
  • ora-06127 : NETTCP: unable to change username
  • ora-33448 : (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-12548 : TNS:incomplete read or write
  • ora-32032 : free temporary object number not available
  • ora-23341 : user function required
  • ora-32315 : REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
  • ora-07621 : smscre: illegal redo block size
  • ora-19913 : unable to decrypt backup
  • ora-25230 : invalid value string, WAIT should be non-negative
  • ora-39114 : Dump files are not supported for network jobs.
  • ora-01936 : cannot specify owner when creating users or roles
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-07490 : scgrcl: cannot convert lock.
  • ora-30572 : AUTO segment space management not valid with DICTIONARY extent management
  • ora-14298 : LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • 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.