Customer Alert - bug 32669 - Custom Upload definition update

Flash (Alert)


Abstract

Customer Alert - bug 32669 - Custom Upload definition update.
There is a potential Issue with the Custom Upload definition update

Content

Technical Description:


    Guardium R&D have identified an issue with custom built “Custom Upload” definitions introduced during the previous GPU, where any customer defined upload definitions have been unintentionally removed.
      This issue only impacts customers using custom built “Custom Upload” definitions.


    How to verify whether your system is impacted:
      Manual validation:

        1. Login to Infosphere Guardium UI as admin user.

        2. Access Tools->Report Building->Custom Table Builder

        3. Find the manually added Custom Upload definition and highlight it

        4. Click Upload Data - is the “SQL statement” field is populated ?



        An empty SQL statement field would indicate a potential issue.


      Automated validati on:

        To verify Custom Upload data integrity, a new must_gather check has been added in v8.01p120 and v8.2p150 GPU fixpacks.

        Note:


          In a federated (Centrally Managed) environment, the steps below are required on Central Manager appliances only.

          In a non-federated (Non-Centrally Managed) environment, the steps below are required on all appliances.

        Steps to invoke the Custom Upload Integrity check:


          1. Access the Guardium appliance CLI interface.

          2. Run the following must_gather command

              support must_gather scheduler --debug_timeout=0

          3. Run the fileserver command from cli to access output file located in
              must_gather/scheduler_logs/scheduler_output.txt

        When the issue is detected, the resultant output may look like the following example


          ...

        ===2013-02-06 19:32:02 ... Output of the Custom Upload data integrity check:==

        ##################################################################

        Data integrity conflict has been found for Custom Upload functionality.

        CUSTOM_TABLE_NAME=table1, TABLE_DESC_ID=20000

        CUSTOM_TABLE_NAME=table2, TABLE_DESC_ID=20001

          the above shows a configuration discrepancy for 2 custom tables: table1 and table2.

      Remediation:


        To correct the custom definition integrity issue

          1. Login to Infosphere Guardium UI as admin user.

          2. Access Tools->Report Building->Custom Table Builder

          3. Choose the custom table reported by the must_gather command in scheduler_output.txt (above).

          4. Click the Upload Data button

          5. Populate the fields in the Import Data screen

          6. Click Apply


        Perform steps 2 - 6 for all tables reported by the Custom Upload data integrity check.

        Re-run the must_gather command above to verify that no more tables are reported as a discrepancy by the Custom Upload data integrity check.


        Note: Custom Upload Definitions could also be restored from export definition backups.


      Affected Appliances
      In Federated environment (CM) Central Manager Appliance only
      In non-Federated environment (no CM) All Appliances
      Affected Guardium versions v8.01 and v8.2
      Fixed in version v8.1p120 GPU fixpack
      v8.2p150 GPU fixpack

      If custom built "Custom Upload" functionality is used, customers are advised to verify and correct the issue if it exists using the above instructions

      Rate this page:

      (0 users)Average rating

      Add comments

      Document information


      More support for:

      InfoSphere Guardium

      Software version:

      8.0.1, 8.2

      Operating system(s):

      Linux

      Reference #:

      1624884

      Modified date:

      2013-02-07

      Translate my page

      Machine Translation

      Content navigation