ORA-13857: Invalid module name

Cause : Module name is too long (exceeding 48 characters)

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

Supply correct name

update : 29-04-2017

ORA-13857 - Invalid module name
ORA-13857 - Invalid module name

  • ora-29395 : cannot set the initial consumer group to string
  • ora-02246 : missing EVENTS text
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-26515 : no master log available for 'string.string'
  • ora-27367 : program "string.string" associated with this job is disabled
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-12228 : TNS:protocol adapter not loadable
  • ora-31080 : type not specified for attribute or element "string"
  • ora-12457 : security label exceeded maximum allowable length
  • ora-30390 : the source statement is not equivalent to the destination statement
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-07471 : snclrd: name translation error of sgadef.dbf file name.
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-25443 : duplicate column value for table alias: string, column number: string
  • ora-19614 : archivelog thread string sequence string not found in backup set
  • ora-27432 : step string does not exist for chain string.string
  • ora-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-24202 : publisher does not exist for the queue
  • ora-04053 : error occurred when validating remote object stringstringstringstringstring
  • ora-03201 : the group number specification is invalid
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-00252 : log string of thread string is empty, cannot archive
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-13768 : Snapshot ID must be between string and string.
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-19268 : XQ0048 - namespace string does not match target namespace string
  • 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.