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 : 29-04-2017

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-07249 : slsget: open error, unable to open /proc/pid.
  • ora-13211 : failed to tessellate the window object
  • ora-19007 : Schema string does not match expected string.
  • ora-38502 : invalid XML tag: string
  • ora-07490 : scgrcl: cannot convert lock.
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-09929 : GLB of two labels is invalid
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-23605 : invalid value "string" for STREAMS parameter string
  • ora-29826 : keyword FOR is missing
  • ora-25277 : cannot grant or revoke object privilege on release 8.0 compatible queues
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-23290 : This operation may not be combined with any other operation
  • ora-02458 : HASHKEYS must be specified for a HASH CLUSTER
  • ora-04940 : unsupported optimization of Oracle binary, check alert log for more info
  • ora-29528 : invalid Java call in trigger string
  • ora-30390 : the source statement is not equivalent to the destination statement
  • ora-19715 : invalid format string for generated name
  • ora-19811 : cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-01546 : tablespace contains active rollback segment 'string'
  • ora-00283 : recovery session canceled due to errors
  • ora-13260 : layer table string does not exist
  • ora-19109 : RETURNING keyword expected
  • ora-27035 : logical block size is invalid
  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-32842 : value for property string cannot be altered
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-36635 : (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.
  • 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.