Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph
    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Non critical error ORA-48913 caught while writing to trace file ...

    Non critical error ORA-48913 caught while writing to trace file ...

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Problem Symptoms:
    The following appears in the Oracle alert log:

    Non critical error ORA-48913 caught while writing to trace file "/exlibris/app/oracle/diag/rdbms/aleph20/aleph20/trace/aleph20_ora_30945.trc"

    Cause:
    Max dump file size needed to be increased.

    Resolution:
    Increased MAX_DUMP_FILE_SIZE to 500M.

    Additional Information

    See also article " Oracle: remove large alert / trace files "  (KB 16384-61297).

    Category: System Management (500)

    Subject: Oracle (500)


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • No. of Recs wrongly appears as 999
      • NON unique keys in Z501 and Z20
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      2. contype:kba
      3. Oracle (500)
      4. Prod:Aleph
      5. System Management (500)
      6. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved