tag:blogger.com,1999:blog-11369382079453974952024-03-13T23:28:56.866-07:00CLASSY DBAClassy DBAhttp://www.blogger.com/profile/02961503193853080240noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1136938207945397495.post-50985012815220321412009-01-21T02:19:00.000-08:002009-01-21T02:35:26.432-08:00ORA-06553: PLS-213: package STANDARD not accessibleProblem Description:<br />====================<br /><br />You are doing any of the following activities<br /><br />1. Compiling PL/SQL<br />2. Running or executing a PL/SQL script or block<br />3. Connecting to SQL*Plus<br />4. Running "catproc.sql"<br /><br />Then you will receive an error as ora-6553 or PLS-213<br /><br />Cause: The PL/SQL compiler could not find package STANDARD in the current<br />Oracle database. To compile a program, PL/SQL needs package STANDARD.<br /><br />Action: Check that package STANDARD is available in the current Oracle<br />database, then retry the operation, Verify the status of package as its valid or not.<br /><br />select owner, object_name, object_type,status from dba_objects where object_name = 'STANDARD';<br /><br />If the find the status as INVALID then try compiling the package as<br />Alter package STANDARD compile;<br /><br />If the problem still persist try running the script<br />@$ORACLE_HOME/rdbms/admin/standard.sql<br /><br />This should solve your problem if not then Verify "$ORACLE_HOME/rdbms/admin/standard.sql" exists.<br /><br />If this file does not exist then:<br /><br />You probably did not install PL/SQL.<br />You must use the Installer to install PL/SQL.<br /><br />If the file does exist then:<br /><br />Verify that your ORACLE_SID is set correctly:<br /><br />SQL> connect sys/<password><br />SQL> @$ORACLE_HOME/rdbms/admin/catproc.sql<br /><br /><br />2) Verify that STANDARD is owned by SYS:<br /><br />SQL> SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = 'STANDARD';<br /><br />If OWNER != SYS then catproc.sql was not correctly executed<br />by SYS. You will have to drop these packages and rerun catproc<br />as SYS.<br /><br />3) Try running "catalog.sql" and "catproc.sql" while opening a spool file<br />to catch any errors that may have occurred.<br /><br />Look for Errors like:<br /><br />ORA-00604: error occurred at recursive SQL level 1<br />ORA-04031: unable to allocate 2192 bytes of shared memory ("shared pool,<br /><br />","PROCEDURE$","KQLS heap","KQLS MEM BLOCK")<br /><br />Create or Replace:<br />*<br />ORA-06553: PLS-213: package STANDARD not accessible<br />grant execute on STANDARD to public<br /><br />ORA-04042: procedure, function, package, or package body does not exist<br /><br />In this case, you would need to increase the "SHARED_POOL_SIZE" in the<br />"init<sid>.ora".<br /><br />Then re-execute CATALOG and CATPROC.<br /><br />Increasing "SHARED_POOL_SIZE" will allocate more resources and<br />allow the scripts to run successfully.<br /><br /><br />Explanation:<br />============<br /><br />The PL/SQL compiler could not find package STANDARD in the current<br />Oracle database. To compile a program, PL/SQL needs package STANDARD.<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /></sid></password>Classy DBAhttp://www.blogger.com/profile/02961503193853080240noreply@blogger.com0tag:blogger.com,1999:blog-1136938207945397495.post-85527288762590634282009-01-21T01:39:00.000-08:002009-01-21T01:46:53.672-08:00Dbconsole installation and repository configurationPlease find the steps to configure Sysman and DBconsole and Repsoitory configuration.<br /><br />Before that kindly check Os privilge and Oracle related folder permission.<br /><br />Steps:-<br /><br />Restore the DB and to check whether sysman and dbsnmp id available and it<br />should be unlock mode.Collect password for those accounts.<br /><br />1) Logon SQLPLUS as user SYSMAN<br />2) exec<br />DBMS_AQADM.DROP_QUEUE_TABLE(queue_table=>'MGMT_NOTIFY_QTABLE',force<br />=>TRUE);<br /><br />3) Logon SQLPLUS as user SYS or SYSTEM<br />4) SHUTDOWN IMMEDIATE;<br />5) STARTUP RESTRICT;<br />6) EXEC sysman.emd_maintenance.remove_em_dbms_jobs;<br />7) EXEC sysman.setEMUserContext('',5);<br />8) REVOKE dba FROM sysman;<br /><br />9)<br /><br />DECLARE<br />CURSOR c1 IS<br />SELECT owner, synonym_name name<br />FROM dba_synonyms<br />WHERE table_owner<br />= 'SYSMAN';<br />BEGIN<br />FOR r1 IN c1 LOOP<br />IF r1.owner = 'PUBLIC' THEN<br />EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;<br />ELSE<br />EXECUTE<br />IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name;<br />END IF;<br />END LOOP;<br />END;<br />/<br /><br />10) DROP USER mgmt_view CASCADE;<br />11) DROP ROLE mgmt_user;<br />12) DROP USER sysman CASCADE;<br />13) ALTER SYSTEM DISABLE RESTRICTED SESSION;<br />14) drop public synonym MGMT_TARGET_BLACKOUTS;<br />15) drop public synonym SETEMVIEWUSERCONTEXT;<br /><br />Delete DB Control Configuration Files and Repository Objects using<br />EMCA in Command prompt<br />================================================================<br />For DB Control 10.2.x,<br />16) <oracle_home>/bin/emca -deconfig dbcontrol db -repos drop<br /><br /><br />Create the DB Control Configuration Files<br />===================================<br />17) <oracle_home>bin/emca -config dbcontrol db -repos create<br /><br />Warning : - No New Connections or Operations Can Be Performed During<br />the DB Control Repository Creation.<br /><br />Finally restart the database.<br /></oracle_home></oracle_home>Classy DBAhttp://www.blogger.com/profile/02961503193853080240noreply@blogger.com0