Results 1 to 5 of 5
  1. #1
    Join Date
    Mar 2004
    Posts
    6

    Angry Unanswered: "Deadlock detected" trying to export

    Hi all-
    Loaded Oracle 9.2.0.4 on RHEL AS 3.0, created a test database, tried to do an export and received a deadlock. I've included the initial text followed by the beginning of the trace file. Where am I going wrong??
    tks for looking, Bill Edison

    Initial text:


    SQL> [Email address protected]
    create or replace
    *
    ERROR at line 1:
    ORA-04045: errors during recompilation/revalidation of
    SYS.CDC_CREATE_CTABLE_AFTER
    ORA-00060: deadlock detected while waiting for resource


    create or replace
    *
    ERROR at line 1:
    ORA-04045: errors during recompilation/revalidation of
    SYS.CDC_CREATE_CTABLE_BEFORE
    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package body "LBACSYS.LBAC_EVENTS" has been
    invalidated
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2



    trace entries:

    *** 2004-05-13 11:40:36.448
    *** SESSION ID10.14) 2004-05-13 11:40:36.447
    DEADLOCK DETECTED
    Current SQL statement for this session:
    delete from dependency$ where d_obj#=:1
    The following deadlock is not an ORACLE error. It is a
    deadlock due to user error in the design of an application
    or from issuing incorrect ad-hoc SQL. The following
    information may aid in determining the deadlock:
    Deadlock graph:
    ---------Blocker(s)--------
    ---------Waiter(s)---------
    Resource Name process session holds waits process session
    holds waits
    TX-0006002d-000000d5 12 10 X 12
    10 X
    session 10: DID 0001-000C-00000010 session 10: DID 0001-000C-00000010
    Rows waited on:
    Session 10: no row
    Information on the OTHER waiting sessions:
    End of information on OTHER waiting sessions.

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    HUH?
    EXACTLY how are you initiating this "export"?
    Here is a free clue, "SQL>" (SQL*Plus) is not used to "export"
    You showed use what messages where displayed for you.
    You did not show us EXACTLY what you did to generate them.
    Plz share!
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Mar 2004
    Posts
    6

    Angry

    Sorry- you've guess that I have no clue when it comes to SQL or Oracle as I'm the lowly systems guy and my job doesn't often venture into this area, although maybe it should. The offending statement was I believe blocked out by a
    well-intentioned but [at least this time] innaccurate, security 'feature'.
    I passed it along hoping to help the dba out with what is turning into a long standing problem, maybe due to a faulty setup/or install on my part, but the
    reinstall seemed to go ok.

    The very first line should have been:

    "SQL> @./product/9.2.0/rdbms/admin/catalog.sql"

    don't know what it does, but whatever it was supposed to do, it didn't.

    thanks for looking.

  4. #4
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >"SQL> @./product/9.2.0/rdbms/admin/catalog.sql"
    get back to the command line & be logged into the OS as user "oracle" or who ever owns all the Oracle directory tree

    $ cd $ORACLE_HOME
    $ sqlplus
    / as sysdba
    @rdbms/admin/catalog.sql
    @rdbms/admin/catproc.sql
    @rdbms/admin/catexp.sql
    -- the above are various "catalog" scripts which populate the data dictionary
    exit

    # They are like giving chicken soup to a dead man.
    # they might make things better & won't hurt anything.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  5. #5
    Join Date
    Mar 2004
    Posts
    6

    Angry

    here is the result from the first line. It goes on for quite a while. Sorry I'm so lame with this. . .


    SQL> @rdbms/admin/catalog.sql
    create or replace
    *
    ERROR at line 1:
    ORA-04045: errors during recompilation/revalidation of
    SYS.CDC_CREATE_CTABLE_BEFORE
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2



    create or replace
    *
    ERROR at line 1:
    ORA-04045: errors during recompilation/revalidation of
    SYS.CDC_CREATE_CTABLE_BEFORE
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2



    Grant succeeded.

    create or replace package dbms_standard is
    *
    ERROR at line 1:
    ORA-04045: errors during recompilation/revalidation of
    SYS.CDC_CREATE_CTABLE_BEFORE
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 2

    .

    .

    .

    tks again for looking...
    bill

Posting Permissions

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