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-06-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-14611 : Duplicate subpartition name string in template
  • ora-26029 : index string.string partition string initially in unusable state
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-16411 : ONDEMAND archival requires active managed recovery operation
  • ora-27146 : post/wait initialization failed
  • ora-00200 : control file could not be created
  • ora-12441 : policy string already exists
  • ora-02327 : cannot create index on expression with datatype string
  • ora-02339 : invalid column specification
  • ora-19606 : Cannot copy or restore to snapshot control file
  • ora-31162 : element or attribute "string" has no SQLType specified
  • ora-13119 : invalid edge_id [string]
  • ora-06918 : CMX: T_NOEVENT during wait for read event
  • ora-39090 : Cannot add devices to file oriented job.
  • ora-07593 : ssprprv: Error release privileges
  • ora-23313 : object group "string"."string" is not mastered at string
  • ora-28116 : insufficient privileges to do direct path access
  • ora-01240 : too many data files to add in one command
  • ora-01685 : max # extents (string) reached in index string.string partition string
  • ora-07234 : slemcw: fseek error.
  • ora-39124 : dump file name "string" contains an invalid substitution variable
  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-02083 : database name has illegal character 'string'
  • ora-02224 : EXECUTE privilege not allowed for tables
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-29827 : keyword USING is missing
  • ora-30432 : summary 'string.string' is in INVALID state
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • 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.