Skip to Content
If the large table is not already in a separate tablespace option 2 might be the better alternative. Needless to say that both option are ‘workarounds’ to cope with the situation. It would be much better if LRIDs would be enabled on all tables _before_ the tables in the tablespace come close to the old table size limit.  h5. The Large RID Tool  With SAP note 1108956  (https://service.sap.com/sap/support/notes/1108956) an ABAP based tool is available for all SAP customers with SAP Releases starting at 4.6. The tool comes as a transport which is attached to the note together with the documentation. Refer to the note for installation instructions. The tool can be started via transaction /isis/zlargerid (enter /n/isis/zlargerid in the command field of the SAPGui). It holds information about the current LRID status of all tables in its own table /isis/zlrgtabinf. To fill this table initially you need to schedule a background job upon first start (‘Refresh Catalog Information’ button) and wait until it finishes.  The tool basically consist of two screens: one for tablespaces and – after selecting one tablespace and pressing the ‘REORG Indexes/Tables’ button – one for showing all tables within the selected tablespace. The following picture shows the first screen:LRIDTool1The icon in the first column designates the LRID status of tables in that tablespace. A green icon indicates that all tables are enabled for LRIDs, a yellow icons says that at least 75 percent of the tables in that tablespace are using LRIDs and a red icon means that so far no table in that tablespace employs LRIDs. Note that is possible to sort the tablespaces by a selected column. If you for example sort by the ‘% of Max pages’ column you will see the tablespace with the most used pages (in percent) at the top. Tables can be only enabled for LRIDs once their tablespace is converted to LARGE (the ‘Content Type’ is LARGE). Converting a tablespace to LARGE is done by selecting the tablespace and using the ‘Convert to LARGE’ button. The conversion takes just a few seconds. SAP recommends converting all tablespaces to LARGE because then newly created tables in these tablespaces are using LRIDs automatically. Notice that the SYSCATSPACE cannot be converted to LARGE (SQL1234N), it is therefore not listed here. To enable existing tables for LRIDs select a tablespace which is not marked with a green icon and hit the ‘REORG Indexes/Tables’ button. The following screen shows the table information collected in /isis/zlrgtabinf:LRIDTool2
To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member
    Hi Johannes,

    The documentation indicates this tool is released for ABAP and ABAP+JAVA systems only. Stand-alone JAVA stacks are often monitored remotely using DBACOCKPIT, are there any plans to integrate this tool into DBACOCKPIT and support databases for remote stand-alone JAVA stack systems?

    Best regards, Walter

    (0) 
    1. Johannes Heinrich Post author
      Hello Walter,

      yes, there are plans to inlcude the functionality of the ABAP based compression tool into the DBACOCKPIT. As of SAP NetWeaver 7.0 SP12, you can use DBACOCKPIT to identify compression candidates and perform the compression on a single-table basis. This will be extended so that a set of tables candidates can be compressed in a batch job. And it will also work for the database of an AS Java via a remote DB connection.

      Regards,
                             Johannes

      Regards,
                                       Johannes

      (0) 
    2. Johannes Heinrich Post author
      Hello Walter,

      yes, there are plans to inlcude the functionality of the ABAP based compression tool into the DBACOCKPIT. As of SAP NetWeaver 7.0 SP12, you can use DBACOCKPIT to identify compression candidates and perform the compression on a single-table basis. This will be extended so that a set of tables candidates can be compressed in a batch job. And it will also work for the database of an AS Java via a remote DB connection.

      Regards,
      Johannes

      (0) 

Leave a Reply