|
|
Re: How to check procedure compiled warnings & errors [message #596726 is a reply to message #596724] |
Thu, 26 September 2013 00:57 |
|
deepak416
Messages: 63 Registered: January 2013 Location: Pune
|
Member |
|
|
like :
PACKAGE HEADER find_search_new
Warning: Package created with compilation errors.
Registering XML schemas
BEGIN
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kzxcInitLoadLocal-7], [64131], [ORA-64131:
XMLIndex Metadata: failure during the looking up of the dictionary
ORA-30966: error detected in the XML Index layer
ORA-31011: XML parsing failed
], [], [], [], [], [], [], [], [], []
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 3
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 14
ORA-06512: at line 8
creating v_user_modules
creating v_user_top_objects
Connecting to asdf schema and granting relevant privileges ON api objects
[Updated on: Thu, 26 September 2013 00:57] Report message to a moderator
|
|
|
|
|
Re: How to check procedure compiled warnings & errors [message #596729 is a reply to message #596723] |
Thu, 26 September 2013 01:21 |
|
Littlefoot
Messages: 21807 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
deepak416 wrote on Thu, 26 September 2013 07:41I have compiled some procedures, at the time of compilation i saw some warnings & errors but i did not notice, Now can we see that erros or warnings in dbconsole or any other way.
Thanks
Recompile that package once again; the same errors and warnings will appear.
Which tool do you use? If it is SQL*Plus, use SHOW command, such asSQL> help show
SHOW
----
Shows the value of a SQL*Plus system variable, or the current
SQL*Plus environment. SHOW SGA requires a DBA privileged login.
SHO[W] option
where option represents one of the following terms or clauses:
system_variable
ALL
BTI[TLE]
ERR[ORS] [{FUNCTION | PROCEDURE | PACKAGE | PACKAGE BODY | TRIGGER
| VIEW | TYPE | TYPE BODY | DIMENSION | JAVA CLASS} [schema.]name]
LNO
PARAMETERS [parameter_name]
PNO
RECYC[LEBIN] [original_name]
REL[EASE]
REPF[OOTER]
REPH[EADER]
SGA
SPOO[L]
SQLCODE
TT[ITLE]
USER
SHOW SPOOL is not available in iSQL*Plus
SQL> show err package your_package_name
No errors.
SQL> show err package body your_package_name
No errors.
SQL>
If you use one of GUI tools, you'll have to find that option somewhere (and if you specify which one it is, perhaps we could suggest where to look).
|
|
|
Re: How to check procedure compiled warnings & errors [message #596730 is a reply to message #596723] |
Thu, 26 September 2013 01:22 |
Lalit Kumar B
Messages: 3174 Registered: May 2013 Location: World Wide on the Web
|
Senior Member |
|
|
deepak416 wrote on Thu, 26 September 2013 11:11Now can we see that erros or warnings in dbconsole or any other way.
USER_ERRORS
SQL> CREATE OR REPLACE PROCEDURE TEST_ERRORS(V_IN NUMBER) AS
2 BEGIN
3 V_OUT := V_IN * V_IN;
4 DBMS_OUTPUT.PUT_LINE('output = ' || V_OUT);
5 END;
6 /
Warning: Procedure created with compilation errors
SQL> show errors;
Errors for PROCEDURE U208278.TEST_ERRORS:
LINE/COL ERROR
-------- ----------------------------------------------
3/4 PLS-00201: identifier 'V_OUT' must be declared
3/4 PL/SQL: Statement ignored
4/40 PLS-00201: identifier 'V_OUT' must be declared
4/4 PL/SQL: Statement ignored
SQL> select * from user_errors;
NAME TYPE SEQUENCE LINE POSITION TEXT ATTRIBUTE MESSAGE_NUMBER
------------------------------ ------------ ---------- ---------- ---------- -------------------------------------------------------------------------------- --------- --------------
TEST_ERRORS PROCEDURE 1 3 4 PLS-00201: identifier 'V_OUT' must be declared ERROR 201
TEST_ERRORS PROCEDURE 2 3 4 PL/SQL: Statement ignored ERROR 0
TEST_ERRORS PROCEDURE 3 4 40 PLS-00201: identifier 'V_OUT' must be declared ERROR 201
TEST_ERRORS PROCEDURE 4 4 4 PL/SQL: Statement ignored ERROR 0
SQL>
Regards,
Lalit
|
|
|
Re: How to check procedure compiled warnings & errors [message #596732 is a reply to message #596729] |
Thu, 26 September 2013 01:27 |
|
Littlefoot
Messages: 21807 Registered: June 2005 Location: Croatia, Europe
|
Senior Member Account Moderator |
|
|
While I was writing my message, you added some text to yours.
ORA-20001 error code suggests that it is a message written by you (or someone who created that script). These are probably not meant to be sent to Oracle Support; I believe that you should be able to sort them out. Either debug that code or talk to the author.
|
|
|