SP2-0809: Warning: Package Body created with compilation errors. [message #592308] |
Tue, 06 August 2013 07:45 |
amit.pandey
Messages: 64 Registered: August 2006 Location: Bangalore, India
|
Member |
|
|
Hello Everyone,
I've compiled a package with warnings ON.
Getting message SP2-0809: Package Body Created with Compilation Errors.
When I checked the errors by issuing "Show Errors", it shows "No error".
SQL> ALTER PACKAGE PKG_ABC COMPILE PLSQL_WARNINGS = 'ENABLE:ALL';
SP2-0809: Package Body Created with Compilation Errors
SQL> SHOW ERRORS
No Errors
Can anyone please tell me how to check errors for that, or oracle simply pointing that package might have performance issue.
Any help will be much appreciated.
Thanks
Amit P
|
|
|
|
|
|
Re: SP2-0809: Warning: Package Body created with compilation errors. [message #592325 is a reply to message #592308] |
Tue, 06 August 2013 09:39 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
[oracle@localhost ~]$ oerr sp2 809
00809, 0, "Package altered with compilation warnings"
// *Cause: The PL/SQL package has been altered, but has one or more
// warnings, informational messages or performance messages
// that may help you to improve your PL/SQL package.
// *Action: Use the SQL*Plus SHOW ERR[ORS] command to display
// the warnings and messages.
which USER owns the code?
which USER is trying to compile the code?
[Updated on: Tue, 06 August 2013 09:39] Report message to a moderator
|
|
|
|
Re: SP2-0809: Warning: Package Body created with compilation errors. [message #592368 is a reply to message #592326] |
Wed, 07 August 2013 03:43 |
|
Michel Cadot
Messages: 68651 Registered: March 2007 Location: Nanterre, France, http://...
|
Senior Member Account Moderator |
|
|
PLW-07205: SIMPLE_INTEGER is mixed with BINARY_INTEGER or PLS_INTEGER
MANUAL: PL/SQL
INDEX:
RELEASE: 11.0.0
CAUSE: Using SIMPLE_INTEGER and BINARY_INTEGER or PLS_INTEGER arguments
in the same arithmetic expression may inhibit certain optimizations.
ACTION: Try using SIMPLE_INTEGER values only if the expression is
computed on a performance critical path.
|
|
|