ORA-24230: input to DBMS_DDL.WRAP is not a legal PL/SQL unit

Cause : The input supplied to DBMS_DDL.WRAP or DBMS_DDL.CREATE_WRAPPED did not specify a legal PL/SQL package specification, package body, type specification, type body, function or procedure. This error can occur if you used incorrect syntax in the CREATE OR REPLACE statement or specified a unit that cannot be wrapped (e.g., a trigger or anonymous block).

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

Provide a legal PL/SQL unit as input.

update : 24-08-2017
ORA-24230

ORA-24230 - input to DBMS_DDL.WRAP is not a legal PL/SQL unit
ORA-24230 - input to DBMS_DDL.WRAP is not a legal PL/SQL unit

  • ora-25453 : invalid iterator: string
  • ora-27084 : unable to get/set file status flags
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-13338 : failure in reversing LRS polygon/collection geometry
  • ora-30377 : table string.MV_CAPABILITIES_TABLE not found
  • ora-22804 : remote operations not permitted on object tables or user-defined type columns
  • ora-22875 : cannot drop primary key of an object table whose object identifier is primary key based
  • ora-30182 : invalid precision specifier
  • ora-33082 : (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
  • ora-21503 : program terminated by fatal error
  • ora-39078 : unable to dequeue message for agent string from queue "string"
  • ora-14186 : number of sub-partitions of LOCAL index must equal that of the underlying table
  • ora-24404 : connection pool does not exist
  • ora-15163 : cluster not in rolling downgrade
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-29884 : domain index is defined on the column to be dropped
  • ora-16060 : Log file is current
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-02377 : invalid resource limit
  • ora-24300 : bad value for mode
  • ora-13215 : window object is out of range
  • ora-14111 : creation of a GLOBAL partitioned index on clustered tables is not supported
  • ora-10970 : backout event for bug 2133357
  • ora-30357 : this PL/SQL function cannot be supported for query rewrite
  • ora-29500 : NAMED keyword is invalid in CREATE JAVA CLASS
  • ora-28153 : Invalid client initial role specified: 'string'
  • ora-02053 : transaction string committed, some remote DBs may be in-doubt
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-16700 : the standby database has diverged from the primary database
  • ora-39128 : unexpected DbmsJava error number from statement 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.