PL/SQL re-installation
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 5 123 ... LastLast
Results 1 to 10 of 42

Thread: PL/SQL re-installation

  1. #1
    Join Date
    Sep 2005
    Posts
    278

    PL/SQL re-installation

    Something happen few days ago which i dont want reveal and some of the views and packages become invalid, so i tried to reinstall PL/SQL.

    Before reinstalling what is my mistake is to delete all the packages
    and types including the Standard package.

    Now iam trying to reinstall PL/SQL, but i got following errors.

    Please help me out.

    The following are the series of steps i followed for reinstallation

    SQL> @\\Ed10\c_oracle\ora92\rdbms\admin\catalog.sql
    create or replace
    *
    ERROR at line 1:
    ORA-04045: errors during recompilation/revalidation of
    SYS.CDC_CREATE_CTABLE_BEFORE
    ORA-06554: package DBMS_STANDARD must be created before using PL/SQL
    ORA-06553: PLS-213: package STANDARD not accessible

    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.

    "after the above error i added the following parameter in init.ora file
    _system_trig_enabled=false
    and rerun the script"

    SQL> startup pfile="C:\Documents and Settings\Administrator\Desktop\init.ora"
    ORACLE instance started.

    Total System Global Area 655433488 bytes
    Fixed Size 454416 bytes
    Variable Size 603979776 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    Database opened.

    SQL> @\\Ed10\c_oracle\ora92\rdbms\admin\catalog.sql
    create or replace
    *
    ERROR at line 1:
    ORA-00955: name is already used by an existing object


    create or replace
    *
    ERROR at line 1:
    ORA-06553: PLS-213: package STANDARD not accessible

    The database is running know but for only queries and DML statements but
    I cant able to run PL/SQL stuff.

    I can't even able to export the data.

  2. #2
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    May I ask why you set _system_trig_enabled=false? That is onlyused when you are upgrading or downgrading

  3. #3
    Join Date
    Sep 2005
    Posts
    278
    to disable any triggers which are raised during creation of oracle objects in the database

  4. #4
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    And thatīs what you think or you have been told...? Or read from somewhere :-?

  5. #5
    Join Date
    Sep 2005
    Posts
    278
    I have read on internet.

    If u knw wat to do,specify that...dont ask cross questions plz

  6. #6
    Join Date
    Nov 2002
    Location
    New Delhi, INDIA
    Posts
    1,796
    Quote Originally Posted by tabreaz
    I have read on internet.

    If u knw wat to do,specify that...dont ask cross questions plz
    First things first... do not get offended when some one is asking you question. They are trying to help you here and trying to understand why you are doing what you are doing. They do not know what situation you are in and the cannot understand the gravity of the problem. So without understanding your problem they cannot simply say run this and see, run that and see.

    Be polite to someone who is trying to help you...

    And run catproc.sql not catalog.sql to get back all the procedures and packages. Catalog creates the data dictionary. Catproc creates all structures required for PL/SQL.

    HTH
    Amar
    "There is a difference between knowing the path and walking the path."

    Amar's Blog  Get Firefox!

  7. #7
    Join Date
    Sep 2005
    Posts
    278
    Thanks for ur reply,

    Again same problem even if i run catproc.sql without catalog.sql

    Actually STANDARD PACKAGE is not getting created.
    SQL> @X:\admin\catproc.sql
    BEGIN
    *
    ERROR at line 1:
    ORA-06553: PLS-213: package STANDARD not accessible

  8. #8
    Join Date
    Feb 2003
    Location
    London
    Posts
    170
    Are you running catproc.sql as user 'SYS'. You need to run this when connect to 'SYS' as sysdba
    thomasp

  9. #9
    Join Date
    Sep 2005
    Posts
    278
    Thanks for ur replay thomasp,
    yes iam running the script through SYS user.

    I did not lost any data, as with previous exports and w/ some other stuff & the database is up on other system. I think the only solution is to reinstall total oracle software but i want to know how the problem comes and wat is the solution for the problem.

  10. #10
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,003
    Quote Originally Posted by tabreaz
    Thanks for ur replay thomasp,
    yes iam running the script through SYS user.

    I did not lost any data, as with previous exports and w/ some other stuff & the database is up on other system. I think the only solution is to reinstall total oracle software but i want to know how the problem comes and wat is the solution for the problem.
    You have a problem with the data dictionary, you should not have deleted sys objects. You may need to rerun the catalog.sql script depending on what you deleted. Look at the following link to see how the data dictionary is created.

    Step 8: Run Scripts to Build Data Dictionary Views

    In the future look before you leap. If you are doing something to the database and you aren't sure, make sure you know what you are doing before you do it.
    this space intentionally left blank

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