ora -229516 - urgent
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: ora -229516 - urgent

  1. #1
    Join Date
    Apr 2001
    Posts
    47

    Thumbs up

    Hi DBA's,

    I'm facing a unique problem.

    The Database is of Oracle 8.1.6 running in SUN Solaris platform. When doing a full database export or incremental export I'm getting the following error.

    "ORA-29516 Aurora assertion failure:Assertion failure at eox.c:187. Uncaught exception root of all java exception."

    I don't know how to solve this problem.

    This is the export cmd i have used:-

    exp system/manager file= "file_name" log="path of log" inctype = complete full=y direct=y compress=y

    I have also tried by giving direct=n;then also the same problem exixts.

    So anyone can help me out? I have browsed net also, no useful information....?


  2. #2
    Join Date
    Sep 2001
    Location
    SWEDEN
    Posts
    70
    ORA-29516 Aurora assertion failure: string

    Cause: An internal error occurred in the Aurora module.

    Action: Contact Oracle Customer Support.
    Action: Contact Oracle Customer Support.
    Action: Contact Oracle Customer Support.

  3. #3
    Join Date
    Sep 2001
    Location
    SWEDEN
    Posts
    70
    There are som bugs. You can find them on http:\\metalink.oracle.com

  4. #4
    Join Date
    Apr 2001
    Posts
    47
    hi,

    Any body faced same kind of issues before.? Could give some valuable suggestions in the above problem?

  5. #5
    Join Date
    Apr 2001
    Posts
    47

    ORA-29516

    Any useful suggestion...?

  6. #6
    Join Date
    Sep 2001
    Location
    Fort Smith
    Posts
    184


    Bookmark Fixed font Go to End

    Doc ID: Note:130080.1
    Subject: Problem/Solution: Problems with EXPORT after upgrading from 8.1.5 to 8.1.6
    Type: BULLETIN
    Status: PUBLISHED
    Content Type: TEXT/PLAIN
    Creation Date: 04-DEC-2000
    Last Revision Date: 31-AUG-2001


    *************************************************************
    This article is being delivered in Draft form and may contain
    errors. Please use the MetaLink "Feedback" button to advise
    Oracle of any issues related to this article.
    *************************************************************

    PURPOSE
    -------

    You followed online documentation steps to upgrade your 8.1.5 database to 8.1.6 release.
    Everything looks OK, but, when you try to make an EXPORT, some of the errors below are reported:

    EXP-00008: ORACLE error 29516 encountered
    ORA-29516: Aurora assertion failure: Assertion failure at eox.c:187
    Uncaught exception Root of all Java exceptions:
    EXP-00000: Export terminated unsuccessfully
    ORA-00904: invalid column name
    EXP-00008: ORACLE error 0 encountered
    ORA-00000: normal, successful completion
    EXP-00078: Error exporting metadata for index IMT. Index creation will be skipped
    EXP-00008: ORACLE error 20000 encountered
    ORA-20000: interMedia Text error:
    DRG-10502: index "CTXTEST"."QUICK_TEXT" does not exist
    ORA-06512: at"SYS.DBMS_EXPORT_EXTENSION", line 208
    ORA-06512: at line 1
    EXP-00078: Error exporting metadata for index QUICK_TEXT. Index creation will be skipped

    Some steps to complete specific components upgrade are missing.


    SCOPE & APPLICATION
    -------------------

    Anyone who has just upgraded database from 8.1.5 to 8.1.6 release.


    SOLUTION
    --------

    If you chose to upgrade database manually, make sure you followed all the steps discussed in "Upgrading Specific Components".

    When performing an export on Oracle database after the upgrade, the following errors can be returned while exporting synonyms:

    Exp-00008: Oracle error 29516 encountered.
    ORA-29516: Aurora assertion failure: Assertion failure at eox.c:187
    Uncaught exception Root of all Java exceptions:
    EXP-00000: Export terminated unsuccessfully

    There are three possible solutions for this errors:

    1. First, run CATEXP as INTERNAL. Then retry the export. Often times this will fix
    the problem and then export will run without error.
    2. If running CATEXP as INTERNAL does not fix the errors, you may be hitting a resource
    issue for export. Try increasing DB_BLOCK_BUFFERS and size of your rollback segments. Then try the export.
    3. If it still fails, it appears that the errors relate to a bad or incomplete installation
    of JAVAVM, which stands for Java Virtual Machine. This is installed using INITJVM.SQL.
    If using this, then verify whether or not its installation was successful.

    ORA-29516 means that something failed in JAVAVM when export tried to call into it,
    probably attempting to translate a synonym from short to long form. It may be that
    there are cases where export decides to do this when Java has not been loaded, in
    which case the error here might result. To verify what is currently in your database, please run the following queries:

    SELECT owner, synonym_name, table_owner, table_name
    FROM all_synonyms
    WHERE table_owner = 'DLC535'
    OR owner = 'DLC535';

    SELECT COUNT(*)
    FROM all_objects
    WHERE object_type LIKE 'JAVA%';

    If JVM was installed, you should find about 8000 objects.

    Trying another export, you may get these error messages while exporting synonyms:

    . exporting referential integrity constraints
    . exporting synonyms
    EXP-00008: ORACLE error 904 encountered
    ORA-00904: invalid column name
    EXP-00000: Export terminated unsuccessfully

    If JAVA is enabled, make sure that both DBMS_JAVA synonym and DBMS_JAVA package are
    created and valid. If a synonym named DBMS_JAVA exists without a corresponding package,
    run script $ORACLE_HOME/javavm/install/initdbj.sql as INTERNAL, in order to create
    package DBMS_JAVA, which is required if Java is enabled.

    If you do not intend on using JAVAVM, please deinstall it running RMJVM.SQL as INTERNAL,
    located in $ORACLE_HOME/javavm/install directory.
    However, every time you try to run RMJVM.SQL, the following error message is generated:

    call rmjvm.run(true)
    *
    ORA-06576: not a valid function or procedure name

    In script RMJVM.SQL, one of the last commands is "call rmjvm.run(true)" which generates
    an ORA-6576. The error occurs because the command "call" cannot be used to execute
    PL/SQL procedures with boolean arguments. The command "execute" needs to be used
    instead. So the line should read "execute rmjvm.run(true)".
    To run the script you will need to edit RMJVM.SQL and change "call rmjvm.run(true)" to "execute rmjvm.run(true)".
    On Oracle8i 8.1.6 for Windows NT, the file RMJVM.SQL does NOT exist. Create file RMJVM.SQL with the following statements:

    . SET SERVEROUTPUT ON
    . VARIABLE jvmrmaction VARCHAR2(30)
    . EXECUTE :jvmrmaction := ‘FULL_REMOVAL’;
    . @@jvmrm
    . execute rmjvm.run(true);

    This issue was fixed in 8.1.7.

    After fixing JAVAVM problems successfully, export can be done with the following errors:

    EXP-00008: ORACLE error 0 encountered
    ORA-00000: normal, successful completion
    EXP-00078: Error exporting metadata for index IMT. Index creation will be skipped
    EXP-00008: ORACLE error 20000 encountered
    ORA-20000: interMedia Text error:
    DRG-10502: index "CTXTEST"."QUICK_TEXT" does not exist
    ORA-06512: at"SYS.DBMS_EXPORT_EXTENSION", line 208
    ORA-06512: at line 1
    EXP-00078: Error exporting metadata for index QUICK_TEXT. Index creation will be skipped

    This is [BUG:1060587], found in 8.1.5 and fixed in 8.1.6. This occurs only if interMedia
    option is installed. The DMP file can be imported, but import will skip over the
    failed index creation. You can do a successful export of the schema, using a User Level Export/Import.
    This issue shouldn’t be found in 8.1.6. InterMedia objects weren’t migrated from
    8.1.5. To upgrade interMedia Spatial Data objects, run the following scripts, as INTERNAL:

    $ORACLE_HOME/ord/im/admin/imuphelp.sql
    $ORACLE_HOME/ord/im/admin/u0801050.sql

    To upgrade interMedia Text (Context) objects, follow the next steps, in this order:

    1. Connect as INTERNAL and run the script:
    $ORACLE_HOME/ctx/admin/upgrade/s0801060.sql
    2. Connect as CTXSYS and run these scripts:
    $ORACLE_HOME/ctx/admin/upgrade/u0801060.sql
    $ORACLE_HOME/ctx/admin/dr0pkh.sql
    $ORACLE_HOME/ctx/admin/dr0plb.sql
    $ORACLE_HOME/ctx/admin/dr0type.plb
    3. Check for any invalid object in CTXSYS schema.
    4. Verify if the path for library libctxx8.so for UNIX (or oractxx8.dll for NT) is right in DR$LIBX:
    SVRMGR> connect ctxsys
    SVRMGR> desc dr$libx
    library dr$libx as '/u01/app/oracle/product/8.1.6/ctx/lib/libctxx8.so'
    If the path isn’t right, then:
    SVRMGR> create or replace library dr$libx as '/lib/libctxx8.so';
    (or ':\Bin\oractxx8.dll' on NT)
    Use the complete absolute path for ORACLE_HOME (do not use the environment variable).
    Note that the file extension could be either ".so" or ".sl" for UNIX, depending on the platform.
    5. Recompile every possible invalid object in CTXSYS. This can be done by the command:
    SVRMGR> exec dbms_utility.compile_schema('CTXSYS')
    6. Check if the new version is 8.1.6:
    SVRMGR> select * from ctx_version;
    7. Recreate and rebuild all indexes that appeared in the error messages. Recreating
    all context indexes is recommended. On the above example, you should do:
    SVRMGR> connect ctxtest
    Password:
    Connected.
    SVRMGR> drop index quick_text;
    Statement processed.
    SVRMGR> create index quick_text on quick(text) indextype is ctxsys.context;
    Statement processed.
    SVRMGR> alter index quick_text rebuild parameters('SYNC');
    Statement processed.

    Finally, recompile all PL/SQL modules in the format required by the new database.
    To do that, run script UTLIRP.SQL, located in $ORACLE_HOME/rdbms/admin.
    Now, you can run EXPORT in this 8.1.6 database without problems.


    RELATED DOCUMENTS
    -----------------

    When making an export of a database recently upgrade from 8.1.5, the error 29516
    [NOTE:114356.1] Export fails with ORA-29516 Aurora Assertion Failure EXP-8
    [NOTE:119155.1] ORA-904 EXP-8 and ORA-1003 on 8.1.6
    [NOTE:121338.1] Oracle8i R2 Export Fails on Synonym export
    [NOTE:116090.1] RUNNING RMJVM.SQL IN 8.1.6 FAILS WITH ORA-6576
    [NOTE:101616.1] SDO 8.1.5: EXP-8 EXP-78 ERRORS EXPORTING SPATIAL METADATA FOR INDEXES
    [NOTE:121868.1] ORA-20000 icx_por_ctx_desc ORA-29863 icx_por_intermedia_index odciindexcreate
    [NOTE:112035.1] ORA-29855 ORA-20000 ORA-6520 ORA-6522 when creating/sync'ing intermedia indexes
    [NOTE:2065798.102] CORRECT LOCATION OF LIBRARY LIBCTXX8.SO IN DR$LIBX
    [NOTE:112200.1] How To Upgrade InterMedia Text 8.1.5 to 8.1.6
    [BUG:1318864] CRM 11.5.1: ORA-29863 IN DOM1151 WHEN REBUILD INTERMEDIA INDEX
    "Oracle8i Migration Release 2 (8.1.6)" (A76957-01)
    .



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

    Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.

    sonofsita
    http://www.ordba.net

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