RE: Ever seen any of these errors?
STANDARD was not invalid (there were only two things invalid, both
'acceptable'). When I tried to compile STANDARD (actually I recreated it
altogether) it wored without errors but I still got the error when logging
into SQL*Plus. This whole thing was just really odd!
Linda
-Original Message-
Sent: Thursday, August 02, 2001 10:26 AM
To: Multiple recipients of list ORACLE-L
hi;
error: ORA-06553 : PLS-213 : package STANDARD not accessible.
I believe that you must connect as sys to do
SELECT * FROM DBA_OBJECTS WHERE OWNER = 'SYS' AND
OBJECT_NAME = 'STANDARD';
If you to find the status is "INVALID" and I believe that you try to
recompile it by use command
ALTER PACKAGE STANDARD COMPILE;
- Original Message -
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Sent: Thursday, August 02, 2001 12:10 PM
> Good point but no. I'm the only one who can get into this server, the
last
> time I ran anything like this was when I built it in September. H, I
> just checked the test environment, which is a clone, everything there is
> owned by sys.
>
> Thanks!
>
> Linda
>
> -Original Message-
> Sent: Wednesday, August 01, 2001 10:55 PM
> To: Multiple recipients of list ORACLE-L
>
>
> Any chance catalog or catproc was run by someone not logged in a "sys"?
>
> Ian MacGregor
> Stanford Linear Accelerator Center
> [EMAIL PROTECTED]
>
> -Original Message-
> Sent: Wednesday, August 01, 2001 1:52 PM
> To: Multiple recipients of list ORACLE-L
>
>
> Our Financials production database server crashed last week. When it came
> back up Oracle seemed to come up with no errors, everything connected
> properly, etc. That evening the SA rebooted the machine to turn on
> diagnostics for Sun. Oracle shutdown normally but after it came back up I
> started getting paged that some of the Financials processes weren't
working.
> I tried to start them and failed so I began poking around. When I logged
> into SQL*Plus I got errors. Unfortunately I didn't start writing things
> down until I had it 90% fixed :-{ but I *think* this was the order. I
> backed up before and after. Then, after each step, I recompiled any
invalid
> objects in the database. I ran sqlplus /nolog, then connect internal,
both
> for consistancy and to run the $ORACLE_HOME/rdbms/admin scripts.
>
> 1) ORA-06553: PLS-213: PACKAGE STANDARD not accessible
> Error accessing package DBMS_APPLICATION_INFO
> I checked for invalid objects, one _next_object (which appears to be a
bug)
> and a Financials package that is always invalid.
> 2) OK, let's try to recreate STANDARD. Ran the script, no errors
> SQL*Plus is still complaining.
> 3) Somewhere along the line I saw references to catalog and catproc on
> Metalink. After some more searching, I decided I didn't have anything to
> lose. Ran catalog without errors. Catproc had errors in a number of
> places. I got dbms_output errors:
> create or replace package dbms_output as
> *
> ERROR at line 1:
> ORA-00604: error occurred at recursive SQL level 1
> ORA-1: unique constraint (SYS.I_OBJ2) violated
> H, it's doing 'create or replace', something's fishy
> Got a 'ORA-00921: unexpected end of SQL command' when it was running
> catqueue.sql.
> Got the errors:
> create or replace type sys.aq$_dummy_t as object (data char(1));
> *
> ERROR at line 1:
> ORA-6545: PL/SQL: compilation error - compilation aborted
> ORA-06550: line 2, column 1:
> PLS-00103: Encountered the symbol "GRANT"
> ORA-06550: line 0, column 0:
> PLS-00565: AQ$_DUMMY_T must be completed as a potential REF target
> (object type)
> These were the only error messages (other than dropping non-existant
indexes
> and those type of messages).
> 4) I reran catproc, now the STANDARD errors are gone in SQL*Plus! But,
when
> I logged in then I got:
> PLS-00201: identifier DBMS_OUTPUT.DISABLE must be declared
> and
> Use of Oracle SQL feature not in SQL92 Entry Level
> 5) I changed catqueue.sql to get rid of a blank line and fixed the ORA-921
> error.
> 6) In prvtaq.plb I removed the ; at the end of the first line and inserted
a
> / on the second line to fix the sys.aq$_dummy_t error messages
> 7) Reran catproc again (I actually ran it twice, once after each script I
> changed). Finally, no errors, including the DBMS_OUTPUT.DISABLE!
> 8) Logged into SQL*Plus with no errors!
>
> Whew! So what could have caused the problems to begin with? There were
no
> errors in the alert log. I ran dbv on all the datafiles, everything was
> clean. The server crashed because of a bad processor, not because of a
bad
> disk (that was the development box on Sunday :-} ). No core dumps. I
> especially love the unique constraint violation on sys.i_obj2
>
> I count myself lucky, I didn't have to call Support, we didn't have
problems
> until after the reboot at 8:30 pm instead of during the middle of the day,
> and it's been a week without any other problems.
>
> Thanks!
>
> Linda
> --
> Please see the official ORAC
RE: Ever seen any of these errors?
Good point but no. I'm the only one who can get into this server, the last
time I ran anything like this was when I built it in September. H, I
just checked the test environment, which is a clone, everything there is
owned by sys.
Thanks!
Linda
-Original Message-
Sent: Wednesday, August 01, 2001 10:55 PM
To: Multiple recipients of list ORACLE-L
Any chance catalog or catproc was run by someone not logged in a "sys"?
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original Message-
Sent: Wednesday, August 01, 2001 1:52 PM
To: Multiple recipients of list ORACLE-L
Our Financials production database server crashed last week. When it came
back up Oracle seemed to come up with no errors, everything connected
properly, etc. That evening the SA rebooted the machine to turn on
diagnostics for Sun. Oracle shutdown normally but after it came back up I
started getting paged that some of the Financials processes weren't working.
I tried to start them and failed so I began poking around. When I logged
into SQL*Plus I got errors. Unfortunately I didn't start writing things
down until I had it 90% fixed :-{ but I *think* this was the order. I
backed up before and after. Then, after each step, I recompiled any invalid
objects in the database. I ran sqlplus /nolog, then connect internal, both
for consistancy and to run the $ORACLE_HOME/rdbms/admin scripts.
1) ORA-06553: PLS-213: PACKAGE STANDARD not accessible
Error accessing package DBMS_APPLICATION_INFO
I checked for invalid objects, one _next_object (which appears to be a bug)
and a Financials package that is always invalid.
2) OK, let's try to recreate STANDARD. Ran the script, no errors
SQL*Plus is still complaining.
3) Somewhere along the line I saw references to catalog and catproc on
Metalink. After some more searching, I decided I didn't have anything to
lose. Ran catalog without errors. Catproc had errors in a number of
places. I got dbms_output errors:
create or replace package dbms_output as
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-1: unique constraint (SYS.I_OBJ2) violated
H, it's doing 'create or replace', something's fishy
Got a 'ORA-00921: unexpected end of SQL command' when it was running
catqueue.sql.
Got the errors:
create or replace type sys.aq$_dummy_t as object (data char(1));
*
ERROR at line 1:
ORA-6545: PL/SQL: compilation error - compilation aborted
ORA-06550: line 2, column 1:
PLS-00103: Encountered the symbol "GRANT"
ORA-06550: line 0, column 0:
PLS-00565: AQ$_DUMMY_T must be completed as a potential REF target
(object type)
These were the only error messages (other than dropping non-existant indexes
and those type of messages).
4) I reran catproc, now the STANDARD errors are gone in SQL*Plus! But, when
I logged in then I got:
PLS-00201: identifier DBMS_OUTPUT.DISABLE must be declared
and
Use of Oracle SQL feature not in SQL92 Entry Level
5) I changed catqueue.sql to get rid of a blank line and fixed the ORA-921
error.
6) In prvtaq.plb I removed the ; at the end of the first line and inserted a
/ on the second line to fix the sys.aq$_dummy_t error messages
7) Reran catproc again (I actually ran it twice, once after each script I
changed). Finally, no errors, including the DBMS_OUTPUT.DISABLE!
8) Logged into SQL*Plus with no errors!
Whew! So what could have caused the problems to begin with? There were no
errors in the alert log. I ran dbv on all the datafiles, everything was
clean. The server crashed because of a bad processor, not because of a bad
disk (that was the development box on Sunday :-} ). No core dumps. I
especially love the unique constraint violation on sys.i_obj2
I count myself lucky, I didn't have to call Support, we didn't have problems
until after the reboot at 8:30 pm instead of during the middle of the day,
and it's been a week without any other problems.
Thanks!
Linda
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Seley, Linda
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: MacGregor, Ian A.
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
RE: Ever seen any of these errors?
Any chance catalog or catproc was run by someone not logged in a "sys"?
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original Message-
Sent: Wednesday, August 01, 2001 1:52 PM
To: Multiple recipients of list ORACLE-L
Our Financials production database server crashed last week. When it came
back up Oracle seemed to come up with no errors, everything connected
properly, etc. That evening the SA rebooted the machine to turn on
diagnostics for Sun. Oracle shutdown normally but after it came back up I
started getting paged that some of the Financials processes weren't working.
I tried to start them and failed so I began poking around. When I logged
into SQL*Plus I got errors. Unfortunately I didn't start writing things
down until I had it 90% fixed :-{ but I *think* this was the order. I
backed up before and after. Then, after each step, I recompiled any invalid
objects in the database. I ran sqlplus /nolog, then connect internal, both
for consistancy and to run the $ORACLE_HOME/rdbms/admin scripts.
1) ORA-06553: PLS-213: PACKAGE STANDARD not accessible
Error accessing package DBMS_APPLICATION_INFO
I checked for invalid objects, one _next_object (which appears to be a bug)
and a Financials package that is always invalid.
2) OK, let's try to recreate STANDARD. Ran the script, no errors
SQL*Plus is still complaining.
3) Somewhere along the line I saw references to catalog and catproc on
Metalink. After some more searching, I decided I didn't have anything to
lose. Ran catalog without errors. Catproc had errors in a number of
places. I got dbms_output errors:
create or replace package dbms_output as
*
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-1: unique constraint (SYS.I_OBJ2) violated
H, it's doing 'create or replace', something's fishy
Got a 'ORA-00921: unexpected end of SQL command' when it was running
catqueue.sql.
Got the errors:
create or replace type sys.aq$_dummy_t as object (data char(1));
*
ERROR at line 1:
ORA-6545: PL/SQL: compilation error - compilation aborted
ORA-06550: line 2, column 1:
PLS-00103: Encountered the symbol "GRANT"
ORA-06550: line 0, column 0:
PLS-00565: AQ$_DUMMY_T must be completed as a potential REF target
(object type)
These were the only error messages (other than dropping non-existant indexes
and those type of messages).
4) I reran catproc, now the STANDARD errors are gone in SQL*Plus! But, when
I logged in then I got:
PLS-00201: identifier DBMS_OUTPUT.DISABLE must be declared
and
Use of Oracle SQL feature not in SQL92 Entry Level
5) I changed catqueue.sql to get rid of a blank line and fixed the ORA-921
error.
6) In prvtaq.plb I removed the ; at the end of the first line and inserted a
/ on the second line to fix the sys.aq$_dummy_t error messages
7) Reran catproc again (I actually ran it twice, once after each script I
changed). Finally, no errors, including the DBMS_OUTPUT.DISABLE!
8) Logged into SQL*Plus with no errors!
Whew! So what could have caused the problems to begin with? There were no
errors in the alert log. I ran dbv on all the datafiles, everything was
clean. The server crashed because of a bad processor, not because of a bad
disk (that was the development box on Sunday :-} ). No core dumps. I
especially love the unique constraint violation on sys.i_obj2
I count myself lucky, I didn't have to call Support, we didn't have problems
until after the reboot at 8:30 pm instead of during the middle of the day,
and it's been a week without any other problems.
Thanks!
Linda
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Seley, Linda
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: MacGregor, Ian A.
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California-- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information
