DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: SOURCE OF INVALID STANDARD.SQL

  1. #1
    Join Date
    Jun 2001
    Posts
    11
    I am trying to find what occured to make STANDARD.SQL invalid in one of our databases. We were not running an install, an upgrade or applying a patch.

    Somewhat before standard.sql became invalid I dropped some synonyms.

    THANKS

  2. #2
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185

    Question

    How do you know that it is invalid? What are the symptoms?
    David Knight
    OCP DBA 8i, 9i, 10g

  3. #3
    Join Date
    Jun 2001
    Posts
    11
    When logging into sql*plus I was getting error messages that package STANDARD was not available (ora-06553). I ran script to view all invalid_objects and then compiled standard. It corrected the problem, no longer were the errors coming up when I logged into sql*plus. Although now there are about 300 invalid 'sys' objects.

  4. #4
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185
    I had a related problem a few weeks ago during installation.

    Try this:

    1. run catalog.sql in $ORACLE_HOME/rdbms/admin
    2. run dbmsstdx.sql in $ORACLE_HOME/rdbms/admin
    3. run catproc.sql in $ORACLE_HOME/rdbms/admin

    I found that running only catalog and catproc did not successfully create and compile the DBMS_STANDARD package.

    You can view DBA_OBJECTS with owner='SYS' and object_type = 'PACKAGE' to see if the packages are valid.

    Good luck.

    David Knight
    OCP DBA 8i, 9i, 10g

  5. #5
    Join Date
    Jun 2001
    Posts
    11
    I was able to recompile the package standard. I am just curious how the package could have become invalid. We were not installing, upgrading or adding a patch.

    thanks

  6. #6
    Join Date
    Dec 2000
    Posts
    22
    I had experience the same question? but do not solve until now.
    The oracle version is 8.1.5. OS solarix 5.7.
    I have two database at the machine. a long time they can normal run. but one day, one database occur "ora-6553' at sqlplus, but other database can normal run, i could not find the find standard.sql directory ORACLE_HOME/rdbms/admin .
    i ask the question what action can bring on the error,
    how to solve the problem?

  7. #7
    Join Date
    Oct 2000
    Location
    Germany
    Posts
    1,185
    The STANDARD package is created with dbmsstdx.sql in $ORACLE_HOME/rdbms/admin.

    The package and the .sql are different things.

    David Knight
    OCP DBA 8i, 9i, 10g

  8. #8
    Join Date
    Dec 2000
    Posts
    22
    dknight , you say the PACKAGE STANDARD was created by dbmsstdx.sql, i could not find the syntax "create or replace package STANDARD " , only found the "create or replace package STANDARD" at standard.sql, i do not know your means. can you explain that?

  9. #9
    Join Date
    Jul 2000
    Posts
    243
    Hi guy's

    never ren into this (allways running into neww stuff on this forum), but, when i lokked at the metalink i found this doc id:
    132217.999

    there is a reference there to an official oracle note that i could not access. look into this, if you can not access metalink post your email.

  10. #10
    Join Date
    Nov 2000
    Posts
    245

    in metalink search, I typed 132217.999
    no match!!!

    where I can locate this doc? forums or tar?

    thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width