ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters.

Cause : hT esurea ttmetpdet orcaeeta n wet sa kroo jbce tsuni g aanemt ah tsit ool no.g

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

hSroet nht eanema dnr teyrt eho eparitno.

update : 26-04-2017

ORA-13615 - The task or object string is greater than the maximum allowable length of 30 characters.
ORA-13615 - The task or object string is greater than the maximum allowable length of 30 characters.

  • ora-12316 : syntax error in database link's connect string
  • ora-25265 : specified signature for a queue which does not support reciever non-repudiation
  • ora-12560 : TNS:protocol adapter error
  • ora-02349 : invalid user-defined type - type is incomplete
  • ora-06027 : NETASY: channel close failure
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-19675 : file string was modified during proxy copy
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-16530 : invalid buffer or length
  • ora-06596 : unsupported LOB operation in RPC call
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-32628 : invalid nesting of MODEL cell reference
  • ora-01698 : a clone database may only have SYSTEM rollback segment online
  • ora-37080 : Advice requested for hierarchy with too many levels
  • ora-01769 : duplicate CLUSTER option specifications
  • ora-24379 : invalid user callback type
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-28652 : overflow segment attributes cannot be specified
  • ora-02170 : FREELIST GROUPS storage option not allowed
  • ora-29893 : indextypes without column data do not need the given data type
  • ora-30109 : could not open parameter file 'string'
  • ora-01590 : number of segment free list (string) exceeds maximum of string
  • ora-27454 : argument name and position cannot be NULL
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-01671 : control file is a backup, cannot make a standby control file
  • ora-06568 : obsolete ICD procedure called
  • ora-36266 : (XSCGMDLAGG00) Invalid context for the AGGREGATION function
  • ora-16805 : change of LogXptMode property violates overall protection mode
  • ora-02271 : table does not have such constraint
  • ora-36834 : (XSLMGEN04) Column tag is greater than 30 bytes
  • 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.