SQL error

SQL error

Post by Tomas Rimste » Wed, 28 May 1997 04:00:00



When I start SQL*Plus 3.3 I get this
_____________________________________
SQL*Plus: Release 3.3.2.0.2 - Production on Tue May 27 13:23:31 1997

Copyright (c) Oracle Corporation 1979, 1994.  All rights reserved.

ERROR:
ORA-06553: PLS-213: package STANDARD not accessible

Error accessing package DBMS_APPLICATION_INFO
ERROR:
ORA-06553: PLS-213: package STANDARD not accessible

Error accessing package DBMS_APPLICATION_INFO
You may need to install the Oracle Procedural option
SET APPINFO requires Oracle Server Release 7.2 or later

Oracle7 Workgroup Server Release 7.3.2.3.1 - Production Release
With the distributed option
PL/SQL Release 2.3.2.3.0 - Production

____________________________________________________

What is wrong and how can I fix it ??

Tomas Rimsten
PPP

 
 
 

SQL error

Post by Mary Trav » Wed, 28 May 1997 04:00:00



>When I start SQL*Plus 3.3 I get this
>_____________________________________
>SQL*Plus: Release 3.3.2.0.2 - Production on Tue May 27 13:23:31 1997
>Copyright (c) Oracle Corporation 1979, 1994.  All rights reserved.
>ERROR:
>ORA-06553: PLS-213: package STANDARD not accessible
>Error accessing package DBMS_APPLICATION_INFO
>ERROR:
>ORA-06553: PLS-213: package STANDARD not accessible
>Error accessing package DBMS_APPLICATION_INFO
>You may need to install the Oracle Procedural option
>SET APPINFO requires Oracle Server Release 7.2 or later
>Oracle7 Workgroup Server Release 7.3.2.3.1 - Production Release
>With the distributed option
>PL/SQL Release 2.3.2.3.0 - Production
>____________________________________________________
>What is wrong and how can I fix it ??
>Tomas Rimsten
>PPP

Tomas,

Connect as sys or internal and run the catproc.sql script provided by
Oracle (on UNIX it's in the $ORACLE_HOME/rdbms/admin directory) to
install the Oracle procedural option.
Mary Travis
BellSouth Telecommunications


 
 
 

1. How to replace SQL Errors with custom Error messages

Hi,

I am trying to trap SQL Errors and replace them with custom error messages
from MS Access 97. Example: if a user tries to update or delete a records
where their have Select access only, he/she will my custom error message,
then "ODBC Call failed", follow by an Update Permission Denied on the table.
It is not nice at all.

Please help!

Thank you!

Yvel

2. Access hack needs advice for breaking into the VB / SQL platform!

3. HELP. Connection errors, SQL Error

4. Ask to close files

5. SP: Howto return own errors against sql errors

6. (no subject)

7. Trapping SQL error in VB before ADO raises run-time error

8. Programming Languages

9. Undocumented errors in SQL Error Log

10. error text of sql error 17805

11. Error in profiler not appearring in SQL error log

12. SQl error 823, with i/o error 59

13. SP: Howto return own errors against sql errors