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-06-2017
ORA-13857

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

  • ora-13780 : SQL statement does not exist.
  • ora-12558 : TNS:protocol adapter not loaded
  • ora-32835 : database user string does not exist
  • ora-31015 : Attempted to insert entry without name
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-12818 : invalid option in PARALLEL clause
  • ora-08321 : scnmin: NOT IMPLEMENTED YET
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-28507 : error in data dictionary view string
  • ora-16644 : apply instance not available
  • ora-07627 : smsfre: $CRETVA failure
  • ora-12445 : cannot change HIDDEN property of column
  • ora-28278 : No domain policy registered for password based GLOBAL users.
  • ora-08103 : object no longer exists
  • ora-16632 : instance being added to database profile
  • ora-39706 : schema 'string' not found
  • ora-27205 : skgfpcn: sbtpccancel returned error
  • ora-19697 : standby control file not found in backup set
  • ora-30342 : referenced level is not defined in this dimension
  • ora-15176 : file 'string' already has an alias associated with it
  • ora-13636 : The specified value provided for parameter string is not valid for this advisor.
  • ora-12632 : Role fetch failed
  • ora-02839 : Sync of blocks to disk failed.
  • ora-10943 : trace name context forever
  • ora-19113 : trace function called during evaluation: string
  • ora-38417 : attribute set string does not exist
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-13517 : Baseline (id = string) does not exist
  • 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.