ora-06553, PLS-213 package STANDARD not accessible

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

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

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

any help?

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

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

Sam,

I happened to check my initPROD.ora file

#shared_pool_size=300000000
shared_pool_reserved_size=300000000

I think i have to comment out shared_pool_reserved_size and then uncomment shared_pool_size

RIght?

then i will bounce the database and again run the catalog.sql

correct me

OH YES!!!

Sam

Thanks Sam,

So, do i have to recreate the database and run sql.bsq,followd by catalog.sql
or just correct the shared_pool_size and then run catalog.sql again ?

First just fix the shared_pool and try to open the database. Then try running the catalog.sql script and see the results. If that succeds procced with the rest.

Else start from square one. But doubt that you got to run the sql.bsq

Sam

Sam,
fixing shared_pool_size did not have any effect. the problem still exists.

Dont know what to do.

Could you please post your init.ora file? May I know why you were trying to create the database through the scripts? Is there any reason behind it? Did you try the database configuration assistant "dbassist" and try?

Looking forward to hear from you.

Sam

Sam,
Thanks for responding. I will post the init.ora tomorrow. I am doing an upgrade of oracle applications 10.7SC to 11.5.5
so after installing the 11.5.5, 8.1.7 database wont be there,we have to create it,so, I manually created it.
I have to check if 'dbassist' utility is available.

thanks

Hi, never heard who need to manually run sql.bsq. it's called by oracle automatically during creation of db. This script creates actural objects while catalog.sql create views/synonms of these objects. Your script look ok, pls try re-create db by running your script and login as sys to run catalog.sql and catproc.sql. Hope this can help.

Most of the oracle installations would have the dbassist installed on the server. Make sure that you have that. Next confirm that your ORACLE_HOME, LD_LIBRARY_PATH, TNS_ADMIN, and PATH and ORACLE_SID set correctly before you start the db creation.

Sam

Sam, here it is
###########################################################################
#
# Oracle Applications 11i - init.ora
#
# This file contains a listing of init.ora parameters for 8.1.6
#
# This is a reference file and contains the major initialisation
# parameters used in Oracle Applications. It is intended to provide
# a guide to the required parameters, but the actual values chosen
# will be specific to each customer site, depending on the number
# of OLTP users. This is in contrast to the CBO parameters
# (ifilecbo.ora ), which are mandatory.
#
###########################################################################


db_name = PROD
control_files = /u03/oracle/proddata/cntrl01.dbf,
/u04/oracle/proddata/cntrl02.dbf,
/u05/oracle/proddata/cntrl03.dbf

db_block_size = 8192

compatible = 8.1.7

_system_trig_enabled = TRUE

row_locking = always

nls_date_format = DD-MON-RR # Is this still true with 11.5 ?

nls_numeric_characters = ".,"
nls_sort = binary
nls_language = american
nls_territory = america


#audit_trail = true # if you want auditing

max_enabled_roles = 40 # Some modules depend on
# this feature.
ifile = ?/dbs/ifilecbo.ora


user_dump_dest = /u02/oracle/proddb/8.1.7/admin/udump
background_dump_dest = /u02/oracle/proddb/8.1.7/admin/bdump
core_dump_dest = /u02/oracle/proddb/8.1.7/admin/cdump

max_dump_file_size = 10240 # trace file size

timed_statistics = true

# _trace_files_public
_trace_files_public = TRUE

processes = 75 # Max. no. of users x 2

db_files = 500 # Max. no. of database files
dml_locks = 500
open_cursors = 500 # Consumes process memory, unless
# using MTS.
session_cached_cursors = 100
enqueue_resources = 5000 # Max. no of concurrent database locks.

db_block_buffers = 5000

log_checkpoint_timeout = 72000 # Checkpoint at least every 20 mins.
log_checkpoint_interval = 100000
log_buffer = 1048576
log_checkpoints_to_alert = TRUE


rollback_segments = (rb1,rb2,rb3,rb4,rb5,rb6,rb7,rb8,rb9,rb10,rb11,rb12,rb13,rb14,rb15,rb16)
#rollback_segments = (rbs1,rbs2)

sort_area_size = 256000

hash_area_size= 6000000

#shared_pool_size = 300000000
shared_pool_reserved_size = 30000000
_shared_pool_reserved_min_alloc = 4100

shared_pool_size = 300000000

#java_pool_size = 50000000

utl_file_dir = /usr/tmp

aq_tm_processes = 1

# log_archive_start = true # if you want automatic archiving

parallel_max_servers = 8
parallel_min_servers = 0

optimizer_mode= choose
_sqlexec_progression_cost= 0

Quote:

---

db_files = 500 # Max. no. of database files

---

DB_FILES is not the no. of database files, it is the max number of files associated with this instance of the DB!

I am now creating a database using dbassist,lets see what happens.

dbassist was simple and easy, no errors !

Julian,


quote:
--------------------------------------------------------------------------------
db_files = 500 # Max. no. of database files

--------------------------------------------------------------------------------


DB_FILES is not the no. of database files, it is the max number of files associated with this instance of the DB!


Then if I am running a single instance database then db_files will be max number of datafiles I can create right?

Nizar