Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Error in ETL Process: 'unable to extend table LIBR0.MRR_OPAC in tablespace ..'

    • Article Type: General
    • Product: Aleph
    • Product Version: 2

    Description:
    In our last ETL process we had the following error message. Nothing was changed in the configuration. Why is the space in the database not sufficient anymore? What has to be changed to avoid this problem?

    Sun Aug 27 01:03:02 2006
    ORA-1653: unable to extend table LIBR0.MRR_OPAC by 8192 in tablespace TS_ARC_D
    Sun Aug 27 01:03:16 2006
    ORA-1653: unable to extend table LIBR0.MRR_OPAC by 8192 in tablespace TS_ARC_D

    Resolution:
    The error message indicates, that the table space in ARC is full due to exceeding data amount. Probably related to a large table MRR_OPAC.
    Solution:
    a) Please check, how many records should be extracted of the so called OPAC Events (ARC target table mrr_opac) The table mrr_opac originates from the ALEPH table Z69 which is growing fast, depending on the configuration of table [bib_lib]/tab/tab_events.lng, switches 20 -30 in ALEPH. It is recommended to limit the extract to the required period. If you minimize the period of the extract, the error message will probably not occur anymore, since all the other records are not growing as fast.
    You can limit the period for the extract of the OPAC tables by defining the ALEPH table [adm_libs]/tab/arc_conf_table.conf
    Example
    [OPAC]
    from date = yyyymmdd
    b) If you want to extract all the OPAC events, you need to extend the table space TS_ARC_D. Please contact your system administrator for further details.

    Additional Information

    ARC, ETL, OPAC events, table space


    • Article last edited: 11/10/2014
    //doorbell.io feedback widged