The package contains a call to to_lob, when in a straight text file it installs correctly into the database and works,
When the sql file is wrapped and then installs is complains as follows.
Anyone run into this before?
Warning: Package Body created with compilation errors.
Errors for PACKAGE BODY SAUDIT:
LINE/COL ERROR -- ----- -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -- 36/5 PL/SQL: SQL Statement ignored 63/10 PLS-00201: identifier 'TO_LOB' must be declared 355/8 PL/SQL: SQL Statement ignored 387/16 PLS-00201: identifier 'TO_LOB' must be declared 638/8 PL/SQL: SQL Statement ignored 660/13 PLS-00201: identifier 'TO_LOB' must be declared SQL> desc to_lob ERROR: ORA-04043 (See ORA-04043.ora-code.com): object to_lob does not exist
George =20__ ____ ____ ____ ____ ____ ____ ____ ____ _____ George Leonard Oracle Database Administrator New Dawn Technologies @ Wesbank E-mail:gleonard@(protected) =20 You Have The Obligation to Inform One Honestly of the risk, And As a Person You Are Committed to Educate Yourself to the Total Risk In Any Activity! Once Informed & Totally Aware of the Risk, Every Fool Has the Right to Kill or Injure Themselves as They See Fit! =20
The views expressed in this email are, unless otherwise stated, those of = the author and not those of the FirstRand Banking Group an Authorised Financial Service Provider o= r its management. The information in this e-mail is confidential and is intended solely for= =20the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribut= ion or any action taken or=20 omitted in reliance on this, is prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure the accuracy and integrit= y of information and data=20 transmitted electronically and to preserve the confidentiality thereof, n= o liability or=20 responsibility whatsoever is accepted if information or data is, for what= ever reason, corrupted=20 or does not reach its intended destination.
