Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-21818

Inefficient AGS DB query runs multiple times when any doclib or file plan is loaded in Share

    Details

    • Type: Hot Fix Request
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: AGS 3.2
    • Fix Version/s: AGS 3.2.0.9
    • Component/s: Records Management
    • Labels:
      None
    • Environment:
      ACS 6.1.1.1, AGS 3.2.0, Postgres 10.14
    • Bug Priority:
      Category 2
    • Escalated By:
      CSO
    • Hot Fix Version:
      AGS 3.2.0.9
    • ACT Numbers:

      01013774, 01014770

    • Delivery Team:
      Customer Excellence

      Description

      When clicking into a doclib or file plan, the same inefficient query is run, resulting in a long load time.

      Steps to Reproduce

      1. Install ACS 6.1.1
      2. Enable query statement logging in Postgres (or use p6spy)
      3. Click into the swsdp site doclib and note the queries made to the DB
      4. Now, install AGS 3.2.0, create the RM site, and import the test data.
      5. Click into the swsdp site doclib and note the queries
      6. Click into the RM site File Plan and note the queries

      Expected Results

      In step 3 we would not expect to see any RM-related queries, and we don't. In steps 5 and 6, we would expect to see a single, efficient query for node aspects.

      Observed Results

      In steps 5 and 6, we see the following query with the same params run 5 times at each step:

      select
          node.id as id,
          store.protocol as protocol,
          store.identifier as identifier,
          node.uuid as uuid
      from
          alf_node_aspects na
          join alf_node node on (na.node_id = node.id)
          join alf_store store on (store.id = node.store_id)
      where
          na.node_id >= -9223372036854775808
          and na.node_id < 9223372036854775807
          and na.qname_id in
              ( 289 ) 

      This query returns the noderef of the recordsManagementRoot node.

      In customer's environment, this query takes from 1.8-2.2secs to return, so it is on average adding at least 10s to the load time of doclibs and file plan.

      Customer's DBA feels this is an inefficient query in the first place, and also it should only need to run once.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedbugs Closed Bugs (Inactive)
                  Reporter:
                  sashcraft Scott Ashcraft
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  17 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel