There are multiple options available for tracking down Oracle error mesages. Among the options are:
1) Documentation (including "Oracle Error Messages and Codes") should reside on db install CDs.
2) Oracle installations on Unix machines have a (2-stars-out-of-five) on-line facility for error-message descriptions. From the o/s prompt, in your case, type:
Code:
oerr ORA 920
The results are: error message confirmation, cause, and action. The reason I rate it "2-out-of-5" is because many of the error messages are without cause and action.
3) If you have Metalink, you can search by error number itself.
4) Copy and paste your erroneous code and error message(s) here on Tek-Tips, and we'll respond with the problem and the remedy.
Cheers,
Mufasa
(aka Dave of Sandy, Utah, USA @ 17:55 (10May04) UTC (aka "GMT" and "Zulu"), 10:55 (10May04) Mountain Time)
DEV> exec dbms_output.put_line('==> '||sqlerrm( &errno ) );
Enter value for errno: 100
old 1: begin dbms_output.put_line('==> '||sqlerrm( &errno ) ); end;
new 1: begin dbms_output.put_line('==> '||sqlerrm( 100 ) ); end;
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.