-
Hi,
I created a new 8i database, i wanted to run catalog.sql, but it gave the error ora-06553, PLS-213 package STANDARD not accessible
i recreated the database and ran standard.sql first, again the got the same error
pls help
thanks
-
Is your system tablespace is set to autoextend. who was the owner when you ran the catalog.sql? you have to run it as sys and not system.
Sam
Thanx
Sam
Life is a journey, not a destination!
-
Hi Sam,
i guess i have made a mistake, go thro' this first part of the script, i just have created a datafile system01.dbf,not system tablespace, i think this is the problem, pls let me know
connect internal
startup nomount pfile=/u02/oracle/proddb/8.1.7/dbs/initPROD.ora
create database PROD
controlfile reuse
logfile
group 1 '/u03/oracle/proddata/log01a.dbf' size 2M ,
group 2 '/u04/oracle/proddata/log02a.dbf' size 2M ,
group 3 '/u05/oracle/proddata/log03a.dbf' size 2M
datafile '/u04/oracle/proddata/system01.dbf' size 1000M reuse autoextend on
next 10M maxsize 2000M
character set WE8ISO8859P1;
.i have not creat3ed system tablespace,but i have created all other tablespaces.....
thanks
-
login to your database as SYS and run catproc.sql , standard.sql is in catproc.sql.
-
What is the output for the following code
Code:
select owner,object_name,object_type,status
from dba_objects
where owner='SYS'
and object_name=?STANDARD? ;
Sam
Thanx
Sam
Life is a journey, not a destination!
-
i also ran to see catproc.sql, it also could not access standard package
also dba_objects is not available to check the owner and object_name
can u check the script that i sent, i guess i have to create system tablespace as well
-
-
Your script seems to be o.k. One other way to reconfirm/recreate the script is invoke the database configuration assistant (dbassist) and specify your parameters there and at the end it would come out with the option whether you want the save the script or would want to create the database. You can choose the save option and view the script
need more time to research into it.
Sam
Thanx
Sam
Life is a journey, not a destination!
-
Sam,
i recreated the database, ran sql.bsq first
next i ran catalog.sql
i get the error - package STANDARD not accessible
i checked dba_objects and owner is sys and status is invalid
i tried to compile STANDARD, it compiles with compilation errors
what to do?
-
Curtesy of oracle metalink
=================
Code:
Problem Description:
====================
You are doing any of the following activities
1. Compiling PL/SQL
2. Running or executing a PL/SQL script or block
3. Connecting to SQL*Plus
4. Running "catproc.sql"
and receive:
PLS-213: Package standard not accessible
Cause: The PL/SQL compiler could not find package STANDARD in the current
Oracle database. To compile a program, PL/SQL needs package STANDARD.
Action: Check that package STANDARD is available in the current Oracle
database, then retry the operation.
--AND/OR--
ORA-06553: PLS-213: package STANDARD not accessible
You may also receive the following error:
ORA-01933: cannot create a stored object using privileges from a role
running catproc.sql.
Cause: An attempt was made to create a stored object using privileges
from a role. Stored objects cannot use privileges from roles.
Action: Grant the required privileges to the user directly.
Solution Description:
=====================
You need to verify the package STANDARD is valid and owned by SYS. Do the
following:
1) Check the status of the package STANDARD using:
connect sys/
SQL> SELECT * FROM DBA_OBJECTS WHERE OWNER = 'SYS'
AND OBJECT_NAME = 'STANDARD';
If you find the status is 'INVALID' then:
SQL> ALTER PACKAGE STANDARD COMPILE;
You may also find that a number of other packages are in 'INVALID'
state. They should ALL be (re)compiled.
If you find STANDARD does not exist then:
Verify "$ORACLE_HOME/rdbms/admin/standard.sql" exists.
If this file does not exist then:
You probably did not install PL/SQL.
You must use the Installer to install PL/SQL.
If the file does exist then:
Verify that your ORACLE_SID is set correctly:
SQL> connect sys/
SQL> @$ORACLE_HOME/rdbms/admin/catproc.sql
2) Verify that STANDARD is owned by SYS:
SQL> SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = 'STANDARD';
If OWNER != SYS then catproc.sql was not correctly executed
by SYS. You will have to drop these packages and rerun catproc
as SYS.
3) Try running "catalog.sql" and "catproc.sql" while opening a spool file
to catch any errors that may have occurred.
Look for Errors like:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 2192 bytes of shared memory ("shared pool,
","PROCEDURE$","KQLS heap","KQLS MEM BLOCK")
Create or Replace:
*
ORA-06553: PLS-213: package STANDARD not accessible
grant execute on STANDARD to public
ORA-04042: procedure, function, package, or package body does not exist
In this case, you would need to increase the "SHARED_POOL_SIZE" in the
"init.ora".
Then re-execute CATALOG and CATPROC.
Increasing "SHARED_POOL_SIZE" will allocate more resources and
allow the scripts to run successfully.
Explanation:
============
The PL/SQL compiler could not find package STANDARD in the current
Oracle database. To compile a program, PL/SQL needs package STANDARD.
Troubleshoot the PLS-213 by verifying the information above.
Sam
Thanx
Sam
Life is a journey, not a destination!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|