Warning: Undefined array key "id" in C:\xampp\htdocs\kb-dsource\kb-home-details.php on line 4
SRMS ONLINE
  • CASE NUMBER:
    2018-00001
  • STATUS:
    CLOSE
  • SPOC:
    ROWELL ALONZO MAGNO
    • CASE NUMBER:
      2020-00001
    • STATUS:
      CLOSE
    • SPOC:
      CHRIS QUILANG DELGADO
      • CASE NUMBER:
        2020-00002
      • STATUS:
        CLOSE
      • SPOC:
        FLORENCIO B CORTEZ
        • CASE NUMBER:
          2020-00003
        • STATUS:
          CLOSE
        • SPOC:
          EDGAR D CAALIM
          • CASE NUMBER:
            2020-00004
          • STATUS:
            CLOSE
          • SPOC:
            FLORENCIO B CORTEZ
            • CASE NUMBER:
              2020-00005
            • STATUS:
              CLOSE
            • SPOC:
              MARINELA N ALINDOG
              • CASE NUMBER:
                2020-00006
              • STATUS:
                CLOSE
              • SPOC:
                FLORENCIO B CORTEZ
                • CASE NUMBER:
                  2020-00007
                • STATUS:
                  CLOSE
                • SPOC:
                  SHERWIN N ASTORGA
                  • CASE NUMBER:
                    2020-00008
                  • STATUS:
                    CLOSE
                  • SPOC:
                    SHERWIN N ASTORGA
                    • CASE NUMBER:
                      2020-00009
                    • STATUS:
                      CLOSE
                    • SPOC:
                      EDGAR D CAALIM
                      • CASE NUMBER:
                        2020-00010
                      • STATUS:
                        CLOSE
                      • SPOC:
                        FLORENCIO B CORTEZ
                        • CASE NUMBER:
                          2020-00011
                        • STATUS:
                          CLOSE
                        • SPOC:
                          FLORENCIO B CORTEZ
                          • CASE NUMBER:
                            2020-00012
                          • STATUS:
                            CLOSE
                          • SPOC:
                            FLORENCIO B CORTEZ
                            • CASE NUMBER:
                              2020-00013
                            • STATUS:
                              CLOSE
                            • SPOC:
                              SHERWIN N ASTORGA
                              • CASE NUMBER:
                                2020-00014
                              • STATUS:
                                CLOSE
                              • SPOC:
                                SHERWIN N ASTORGA
                                • CASE NUMBER:
                                  2020-00015
                                • STATUS:
                                  CLOSE
                                • SPOC:
                                  SHERWIN N ASTORGA
                                  • CASE NUMBER:
                                    2020-00016
                                  • STATUS:
                                    CLOSE
                                  • SPOC:
                                    FLORENCIO B CORTEZ
                                    • CASE NUMBER:
                                      2020-00017
                                    • STATUS:
                                      CLOSE
                                    • SPOC:
                                      FLORENCIO B CORTEZ
                                      • CASE NUMBER:
                                        2020-00018
                                      • STATUS:
                                        CLOSE
                                      • SPOC:
                                        FLORENCIO B CORTEZ
                                        • CASE NUMBER:
                                          2020-00019
                                        • STATUS:
                                          CLOSE
                                        • SPOC:
                                          MARINELA N ALINDOG
                                          • CASE NUMBER:
                                            2020-00020
                                          • STATUS:
                                            CLOSE
                                          • SPOC:
                                            FLORENCIO B CORTEZ
                                            • CASE NUMBER:
                                              2020-00021
                                            • STATUS:
                                              CLOSE
                                            • SPOC:
                                              SHERWIN N ASTORGA
                                              • CASE NUMBER:
                                                2020-00022
                                              • STATUS:
                                                CLOSE
                                              • SPOC:
                                                SHERWIN N ASTORGA
                                                • CASE NUMBER:
                                                  2020-00023
                                                • STATUS:
                                                  CLOSE
                                                • SPOC:
                                                  HDMF HDMF
                                                  • CASE NUMBER:
                                                    2020-00024
                                                  • STATUS:
                                                    CLOSE
                                                  • SPOC:
                                                    FLORENCIO B CORTEZ
                                                    • CASE NUMBER:
                                                      2020-00025
                                                    • STATUS:
                                                      CLOSE
                                                    • SPOC:
                                                      FLORENCIO B CORTEZ
                                                      • CASE NUMBER:
                                                        2020-00026
                                                      • STATUS:
                                                        CLOSE
                                                      • SPOC:
                                                        HDMF HDMF
                                                        • CASE NUMBER:
                                                          2020-00027
                                                        • STATUS:
                                                          CLOSE
                                                        • SPOC:
                                                          FLORENCIO B CORTEZ
                                                          • CASE NUMBER:
                                                            2020-00028
                                                          • STATUS:
                                                            CLOSE
                                                          • SPOC:
                                                            FLORENCIO B CORTEZ
                                                            • CASE NUMBER:
                                                              2020-00029
                                                            • STATUS:
                                                              CLOSE
                                                            • SPOC:
                                                              JOSE MARIE SANDOVAL
                                                              • CASE NUMBER:
                                                                2020-00030
                                                              • STATUS:
                                                                CLOSE
                                                              • SPOC:
                                                                FLORENCIO B CORTEZ
                                                                • CASE NUMBER:
                                                                  2020-00031
                                                                • STATUS:
                                                                  CLOSE
                                                                • SPOC:
                                                                  SHERWIN N ASTORGA
                                                                  • CASE NUMBER:
                                                                    2020-00032
                                                                  • STATUS:
                                                                    CLOSE
                                                                  • SPOC:
                                                                    FLORENCIO B CORTEZ
                                                                    • CASE NUMBER:
                                                                      2020-00033
                                                                    • STATUS:
                                                                      CLOSE
                                                                    • SPOC:
                                                                      FLORENCIO B CORTEZ
                                                                      • CASE NUMBER:
                                                                        2020-00034
                                                                      • STATUS:
                                                                        CLOSE
                                                                      • SPOC:
                                                                        FLORENCIO B CORTEZ
                                                                        • CASE NUMBER:
                                                                          2020-00035
                                                                        • STATUS:
                                                                          CLOSE
                                                                        • SPOC:
                                                                          STEPHEN N QUIAMNO
                                                                          • CASE NUMBER:
                                                                            2020-00036
                                                                          • STATUS:
                                                                            CLOSE
                                                                          • SPOC:
                                                                            STEPHEN N QUIAMNO
                                                                            • CASE NUMBER:
                                                                              2020-00037
                                                                            • STATUS:
                                                                              CLOSE
                                                                            • SPOC:
                                                                              FLORENCIO B CORTEZ
                                                                              • CASE NUMBER:
                                                                                2020-00038
                                                                              • STATUS:
                                                                                CLOSE
                                                                              • SPOC:
                                                                                ALVIN T TABARREJO
                                                                                • CASE NUMBER:
                                                                                  2020-00039
                                                                                • STATUS:
                                                                                  CLOSE
                                                                                • SPOC:
                                                                                  ALVIN T TABARREJO
                                                                                  • CASE NUMBER:
                                                                                    2020-00040
                                                                                  • STATUS:
                                                                                    CLOSE
                                                                                  • SPOC:
                                                                                    ALVIN T TABARREJO
                                                                                    • CASE NUMBER:
                                                                                      2020-00041
                                                                                    • STATUS:
                                                                                      CLOSE
                                                                                    • SPOC:
                                                                                      STEPHEN N QUIAMNO
                                                                                      • CASE NUMBER:
                                                                                        2020-00042
                                                                                      • STATUS:
                                                                                        CLOSE
                                                                                      • SPOC:
                                                                                        FLORENCIO B CORTEZ
                                                                                        • CASE NUMBER:
                                                                                          2020-00043
                                                                                        • STATUS:
                                                                                          CLOSE
                                                                                        • SPOC:
                                                                                          FLORENCIO B CORTEZ
                                                                                          • CASE NUMBER:
                                                                                            2020-00044
                                                                                          • STATUS:
                                                                                            CLOSE
                                                                                          • SPOC:
                                                                                            ALVIN T TABARREJO
                                                                                            • CASE NUMBER:
                                                                                              2020-00045
                                                                                            • STATUS:
                                                                                              CLOSE
                                                                                            • SPOC:
                                                                                              ALVIN T TABARREJO
                                                                                              • CASE NUMBER:
                                                                                                2020-00046
                                                                                              • STATUS:
                                                                                                CLOSE
                                                                                              • SPOC:
                                                                                                JUN SEPNIO
                                                                                                • CASE NUMBER:
                                                                                                  2020-00047
                                                                                                • STATUS:
                                                                                                  CLOSE
                                                                                                • SPOC:
                                                                                                  FLORENCIO B CORTEZ
                                                                                                  • CASE NUMBER:
                                                                                                    2020-00048
                                                                                                  • STATUS:
                                                                                                    CLOSE
                                                                                                  • SPOC:
                                                                                                    FLORENCIO B CORTEZ
                                                                                                    • CASE NUMBER:
                                                                                                      2020-00049
                                                                                                    • STATUS:
                                                                                                      CLOSE
                                                                                                    • SPOC:
                                                                                                      FLORENCIO B CORTEZ
                                                                                                      • CASE NUMBER:
                                                                                                        2020-00050
                                                                                                      • STATUS:
                                                                                                        CLOSE
                                                                                                      • SPOC:
                                                                                                        FLORENCIO B CORTEZ
                                                                                                        • CASE NUMBER:
                                                                                                          2020-00051
                                                                                                        • STATUS:
                                                                                                          CLOSE
                                                                                                        • SPOC:
                                                                                                          FLORENCIO B CORTEZ
                                                                                                          • CASE NUMBER:
                                                                                                            2020-00052
                                                                                                          • STATUS:
                                                                                                            CLOSE
                                                                                                          • SPOC:
                                                                                                            SHERWIN N ASTORGA
                                                                                                            • CASE NUMBER:
                                                                                                              2020-00053
                                                                                                            • STATUS:
                                                                                                              CLOSE
                                                                                                            • SPOC:
                                                                                                              FLORENCIO B CORTEZ
                                                                                                              • CASE NUMBER:
                                                                                                                2020-00054
                                                                                                              • STATUS:
                                                                                                                CLOSE
                                                                                                              • SPOC:
                                                                                                                FLORENCIO B CORTEZ
                                                                                                                • CASE NUMBER:
                                                                                                                  2020-00055
                                                                                                                • STATUS:
                                                                                                                  CLOSE
                                                                                                                • SPOC:
                                                                                                                  FLORENCIO B CORTEZ
                                                                                                                  • CASE NUMBER:
                                                                                                                    2020-00056
                                                                                                                  • STATUS:
                                                                                                                    CLOSE
                                                                                                                  • SPOC:
                                                                                                                    SHERWIN N ASTORGA
                                                                                                                    • CASE NUMBER:
                                                                                                                      2020-00057
                                                                                                                    • STATUS:
                                                                                                                      CLOSE
                                                                                                                    • SPOC:
                                                                                                                      FLORENCIO B CORTEZ
                                                                                                                      • CASE NUMBER:
                                                                                                                        2020-00058
                                                                                                                      • STATUS:
                                                                                                                        CLOSE
                                                                                                                      • SPOC:
                                                                                                                        SHERWIN N ASTORGA
                                                                                                                        • CASE NUMBER:
                                                                                                                          2020-00059
                                                                                                                        • STATUS:
                                                                                                                          CLOSE
                                                                                                                        • SPOC:
                                                                                                                          FLORENCIO B CORTEZ
                                                                                                                          • CASE NUMBER:
                                                                                                                            2020-00060
                                                                                                                          • STATUS:
                                                                                                                            CLOSE
                                                                                                                          • SPOC:
                                                                                                                            FLORENCIO B CORTEZ
                                                                                                                            • CASE NUMBER:
                                                                                                                              2020-00061
                                                                                                                            • STATUS:
                                                                                                                              CLOSE
                                                                                                                            • SPOC:
                                                                                                                              MANILYN GOMEZ PALEC
                                                                                                                              • CASE NUMBER:
                                                                                                                                2020-00062
                                                                                                                              • STATUS:
                                                                                                                                CLOSE
                                                                                                                              • SPOC:
                                                                                                                                ALVIN T TABARREJO
                                                                                                                                • CASE NUMBER:
                                                                                                                                  2020-00063
                                                                                                                                • STATUS:
                                                                                                                                  CLOSE
                                                                                                                                • SPOC:
                                                                                                                                  FLORENCIO B CORTEZ
                                                                                                                                  • CASE NUMBER:
                                                                                                                                    2020-00064
                                                                                                                                  • STATUS:
                                                                                                                                    CLOSE
                                                                                                                                  • SPOC:
                                                                                                                                    SHERWIN N ASTORGA
                                                                                                                                    • CASE NUMBER:
                                                                                                                                      2020-00065
                                                                                                                                    • STATUS:
                                                                                                                                      CLOSE
                                                                                                                                    • SPOC:
                                                                                                                                      MANILYN GOMEZ PALEC
                                                                                                                                      • CASE NUMBER:
                                                                                                                                        2020-00066
                                                                                                                                      • STATUS:
                                                                                                                                        CLOSE
                                                                                                                                      • SPOC:
                                                                                                                                        MANILYN GOMEZ PALEC
                                                                                                                                        • CASE NUMBER:
                                                                                                                                          2020-00067
                                                                                                                                        • STATUS:
                                                                                                                                          CLOSE
                                                                                                                                        • SPOC:
                                                                                                                                          ROWELL ALONZO MAGNO
                                                                                                                                          • CASE NUMBER:
                                                                                                                                            2020-00068
                                                                                                                                          • STATUS:
                                                                                                                                            CLOSE
                                                                                                                                          • SPOC:
                                                                                                                                            ALVIN T TABARREJO
                                                                                                                                            • CASE NUMBER:
                                                                                                                                              2020-00069
                                                                                                                                            • STATUS:
                                                                                                                                              CLOSE
                                                                                                                                            • SPOC:
                                                                                                                                              JUN SEPNIO
                                                                                                                                              • CASE NUMBER:
                                                                                                                                                2021-00001
                                                                                                                                              • STATUS:
                                                                                                                                                CLOSE
                                                                                                                                              • SPOC:
                                                                                                                                                SHERWIN N ASTORGA
                                                                                                                                                • CASE NUMBER:
                                                                                                                                                  2021-00002
                                                                                                                                                • STATUS:
                                                                                                                                                  CLOSE
                                                                                                                                                • SPOC:
                                                                                                                                                  ARIANE V MAGALLANES
                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                    2021-00003
                                                                                                                                                  • STATUS:
                                                                                                                                                    CLOSE
                                                                                                                                                  • SPOC:
                                                                                                                                                    SHERWIN N ASTORGA
                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                      2021-00004
                                                                                                                                                    • STATUS:
                                                                                                                                                      CLOSE
                                                                                                                                                    • SPOC:
                                                                                                                                                      SHERWIN N ASTORGA
                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                        2021-00005
                                                                                                                                                      • STATUS:
                                                                                                                                                        CLOSE
                                                                                                                                                      • SPOC:
                                                                                                                                                        SHERWIN N ASTORGA
                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                          2021-00006
                                                                                                                                                        • STATUS:
                                                                                                                                                          CLOSE
                                                                                                                                                        • SPOC:
                                                                                                                                                          ALVIN T TABARREJO
                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                            2021-00007
                                                                                                                                                          • STATUS:
                                                                                                                                                            CLOSE
                                                                                                                                                          • SPOC:
                                                                                                                                                            ALVIN T TABARREJO
                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                              2021-00008
                                                                                                                                                            • STATUS:
                                                                                                                                                              CLOSE
                                                                                                                                                            • SPOC:
                                                                                                                                                              MANILYN GOMEZ PALEC
                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                2021-00009
                                                                                                                                                              • STATUS:
                                                                                                                                                                CLOSE
                                                                                                                                                              • SPOC:
                                                                                                                                                                CHRIS QUILANG DELGADO
                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                  2021-00010
                                                                                                                                                                • STATUS:
                                                                                                                                                                  CLOSE
                                                                                                                                                                • SPOC:
                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                    2021-00011
                                                                                                                                                                  • STATUS:
                                                                                                                                                                    CLOSE
                                                                                                                                                                  • SPOC:
                                                                                                                                                                    FLORENCIO B CORTEZ
                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                      2021-00012
                                                                                                                                                                    • STATUS:
                                                                                                                                                                      CLOSE
                                                                                                                                                                    • SPOC:
                                                                                                                                                                      FLORENCIO B CORTEZ
                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                        2021-00013
                                                                                                                                                                      • STATUS:
                                                                                                                                                                        CLOSE
                                                                                                                                                                      • SPOC:
                                                                                                                                                                        MANILYN GOMEZ PALEC
                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                          2021-00014
                                                                                                                                                                        • STATUS:
                                                                                                                                                                          CLOSE
                                                                                                                                                                        • SPOC:
                                                                                                                                                                          ALVIN T TABARREJO
                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                            2021-00015
                                                                                                                                                                          • STATUS:
                                                                                                                                                                            CLOSE
                                                                                                                                                                          • SPOC:
                                                                                                                                                                            CHRIS QUILANG DELGADO
                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                              2021-00016
                                                                                                                                                                            • STATUS:
                                                                                                                                                                              CLOSE
                                                                                                                                                                            • SPOC:
                                                                                                                                                                              FLORENCIO B CORTEZ
                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                2021-00017
                                                                                                                                                                              • STATUS:
                                                                                                                                                                                CLOSE
                                                                                                                                                                              • SPOC:
                                                                                                                                                                                CHRIS QUILANG DELGADO
                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                  2021-00018
                                                                                                                                                                                • STATUS:
                                                                                                                                                                                  CLOSE
                                                                                                                                                                                • SPOC:
                                                                                                                                                                                  ROWELL ALONZO MAGNO
                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                    2021-00019
                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                    CLOSE
                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                    SHERWIN N ASTORGA
                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                      2021-00020
                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                      CLOSE
                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                      ROWELL ALONZO MAGNO
                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                        2021-00021
                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                        CLOSE
                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                        ALVIN T TABARREJO
                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                          2021-00022
                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                          CLOSE
                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                          MANILYN GOMEZ PALEC
                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                            2021-00023
                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                            CLOSE
                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                            MARINELA N ALINDOG
                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                              2021-00024
                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                              CLOSE
                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                              FLORENCIO B CORTEZ
                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                2021-00025
                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                CLOSE
                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                SHERWIN N ASTORGA
                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                  2021-00026
                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                  EDGAR D CAALIM
                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                    2021-00027
                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                    STEPHEN N QUIAMNO
                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                      2021-00028
                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                      CHRIS QUILANG DELGADO
                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                        2021-00029
                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                        MARINELA N ALINDOG
                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                          2021-00030
                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                          ALVIN T TABARREJO
                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                            2021-00031
                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                            ROWELL ALONZO MAGNO
                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                              2021-00032
                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                              FLORENCIO B CORTEZ
                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                2021-00033
                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                MANILYN GOMEZ PALEC
                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                  2021-00034
                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                  ROWELL ALONZO MAGNO
                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                    2021-00035
                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                      2021-00036
                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                      ON HOLD
                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                      SHERWIN N ASTORGA
                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                        2021-00037
                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                        MANILYN GOMEZ PALEC
                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                          2021-00038
                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                          FLORENCIO B CORTEZ
                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                            2021-00039
                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                            ALVIN T TABARREJO
                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                              2021-00040
                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                              ROWELL ALONZO MAGNO
                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                2021-00041
                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                SHERWIN N ASTORGA
                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                  2021-00042
                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                  ROWELL ALONZO MAGNO
                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                    2021-00043
                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                      2021-00044
                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                      ALVIN T TABARREJO
                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                        2021-00045
                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                        ALVIN T TABARREJO
                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                          2021-00046
                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                          SHERWIN N ASTORGA
                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                            2021-00047
                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                            SHERWIN N ASTORGA
                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                              2021-00048
                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                              ALVIN T TABARREJO
                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                2021-00049
                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                ROY P URBINA
                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                  2021-00050
                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                  ON HOLD
                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                  DIANNE GARCIA CABANGBANG
                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                    2021-00051
                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                    JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                      2022-00001
                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                      ALVIN T TABARREJO
                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                        2022-00002
                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                        DIANNE GARCIA CABANGBANG
                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                          2022-00003
                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                          ON HOLD
                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                          DIANNE GARCIA CABANGBANG
                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                            2022-00004
                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                            ALVIN T TABARREJO
                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                              2022-00005
                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                              ALVIN T TABARREJO
                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                2022-00006
                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                ALVIN T TABARREJO
                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                  2022-00007
                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                    2022-00008
                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                    ELEXIE LABERINTO
                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                      2022-00009
                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                      BENJELIN M DALICUN
                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                        2022-00010
                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                        ALVIN T TABARREJO
                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                          2022-00011
                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                          ROY P URBINA
                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                            2022-00012
                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                            EDGAR D CAALIM
                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                              2022-00013
                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                              ALVIN T TABARREJO
                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                2022-00014
                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                  2022-00015
                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                  FLORENCIO B CORTEZ
                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                    2022-00016
                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                      2022-00017
                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                      ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                        2022-00018
                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                        FLORENCIO B CORTEZ
                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                          2022-00019
                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                          FLORENCIO B CORTEZ
                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                            2022-00020
                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                            FLORENCIO B CORTEZ
                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                              2022-00021
                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                              ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                2022-00022
                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                SHERWIN N ASTORGA
                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                  2022-00023
                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                    2022-00024
                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                      2022-00025
                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                      ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                        2022-00026
                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                        CHRIS QUILANG DELGADO
                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                          2022-00027
                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                          ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                            2022-00028
                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                            ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                              2022-00029
                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                              ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                2022-00030
                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                  2022-00031
                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                    2022-00032
                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                    ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                      2022-00033
                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                      ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                        2022-00034
                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                        OPEN
                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                        ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                          2022-00035
                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                          OPEN
                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                          ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                            2022-00036
                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                            OPEN
                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                            ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                              2022-00037
                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                              ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                2022-00038
                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                  2022-00039
                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                  ROY P URBINA
                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                    2022-00040
                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                    ON HOLD
                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                      2022-00041
                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                      ON HOLD
                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                      ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                        2023-00001
                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                        ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                          2023-00002
                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                          ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                            2023-00003
                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                            ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                              2023-00004
                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                              ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                2023-00005
                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                FOLLOW UP
                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                  2023-00006
                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                    2023-00007
                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                      2023-00008
                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                      OPEN
                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                      ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                        2023-00009
                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                        ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                          2023-00010
                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                          ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                            2023-00011
                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                            ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                              2023-00012
                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                              OPEN
                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                              ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                2023-00013
                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                FOLLOW UP
                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                SHERWIN N ASTORGA
                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                  2023-00014
                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                  ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                    2023-00015
                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                    SHERWIN N ASTORGA
                                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                      2023-00016
                                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                                      ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                        2023-00017
                                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                                        SHERWIN N ASTORGA
                                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                          2023-00018
                                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                                          ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                            2023-00019
                                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                                            ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                              2023-00020
                                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                                              MARINELA N ALINDOG
                                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                2023-00021
                                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                  2023-00022
                                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                  ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                    2023-00023
                                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                    ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                      2023-00024
                                                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                      MARINELA N ALINDOG
                                                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                        2023-00025
                                                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                        ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                          2023-00026
                                                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                          ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                            2023-00027
                                                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                            JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                              2023-00028
                                                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                              CLOSE
                                                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                              REYMART C GO
                                                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                2023-00029
                                                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                ROWELL ALONZO MAGNO
                                                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                  2023-00030
                                                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                  STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                    2023-00031
                                                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                    OPEN
                                                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                    ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                      2023-00032
                                                                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                      SPENCER EDSEL T MANAHAN
                                                                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                        2023-00033
                                                                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                        ENRIQUE S SAN ANDRES
                                                                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                          2023-00034
                                                                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                          JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                            2023-00035
                                                                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                            SHERWIN N ASTORGA
                                                                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                              2023-00036
                                                                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                              OPEN
                                                                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                              ELEXIE LABERINTO
                                                                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                2023-00037
                                                                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                DANIEL A CATALAN
                                                                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                  2024-00001
                                                                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                    2024-00002
                                                                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                    STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                      2024-00003
                                                                                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                      STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                        2024-00004
                                                                                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                        CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                        ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                          2024-00005
                                                                                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                          OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                          ANTHONY BRYAN C CRISTOBAL
                                                                                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                            2024-00006
                                                                                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                            STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                              2024-00007
                                                                                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                              OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                              JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                2024-00008
                                                                                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                SHERWIN N ASTORGA
                                                                                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                  2024-00009
                                                                                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                  ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                    2024-00010
                                                                                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                    OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                    ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                      2024-00011
                                                                                                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                      ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                        2024-00012
                                                                                                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                        OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                        STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                          2024-00013
                                                                                                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                          CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                          STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                            2024-00014
                                                                                                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                            CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                            ROWELL ALONZO MAGNO
                                                                                                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                              2024-00015
                                                                                                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                              OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                              ROY P URBINA
                                                                                                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                2024-00016
                                                                                                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                  2024-00017
                                                                                                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                  CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                  JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                    2024-00018
                                                                                                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                    CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                    JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                    • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                      2024-00019
                                                                                                                                                                                                                                                                                                                                                                                                                                                    • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                      CLOSE
                                                                                                                                                                                                                                                                                                                                                                                                                                                    • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                      JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                      • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                        2024-00020
                                                                                                                                                                                                                                                                                                                                                                                                                                                      • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                        OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                      • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                        JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                        • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                          2024-00021
                                                                                                                                                                                                                                                                                                                                                                                                                                                        • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                          OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                        • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                          STEPHEN O MOLINA
                                                                                                                                                                                                                                                                                                                                                                                                                                                          • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                            2024-00022
                                                                                                                                                                                                                                                                                                                                                                                                                                                          • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                            OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                          • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                            SPENCER EDSEL T MANAHAN
                                                                                                                                                                                                                                                                                                                                                                                                                                                            • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                              2024-00023
                                                                                                                                                                                                                                                                                                                                                                                                                                                            • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                              OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                            • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                              ALVIN T TABARREJO
                                                                                                                                                                                                                                                                                                                                                                                                                                                              • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                2024-00024
                                                                                                                                                                                                                                                                                                                                                                                                                                                              • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                              • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                SPENCER EDSEL T MANAHAN
                                                                                                                                                                                                                                                                                                                                                                                                                                                                • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  2025-00001
                                                                                                                                                                                                                                                                                                                                                                                                                                                                • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                                • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  JAN EDMOND NUÑEZ DE VERA
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • CASE NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    2025-00002
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • STATUS:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    OPEN
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • SPOC:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • OWNER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    JUNEL PERALTA GARCIA
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • SEVERITY:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1 - CRITICAL
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • CASE TYPE:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    QUESTION
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • PRODUCT:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    OPENROAD
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • SUBJECT:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    TEST
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • OPERATING SYSTEM:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    LINUX 32-bit
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • PATCH NUMBER:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    0
                                                                                                                                                                                                                                                                                                                                                                                                                                                                  • VERSION:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    11.2
                                                                                                                                                                                                                                                                                                                                                                                                                                                                    • DETAILS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/11/2024 22:56:05

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Is there a method to properly size a server for OpenROAD AppServer? Would it be based on number of active users?

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/19/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1110771.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 22:52:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI asked if there will be a problem if the DB Server uses Asia-Manila time zone and OpernROAD application uses Philipines as time zone. Actian sain, if using OpenROAD Application, you should NOT use IANA time zone. Ingres continues to support own time zone tables. OpenROAD doesn’t yet support the IANA time zone.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/25/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1111517.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 22:53:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/24/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1116237.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 22:53:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Chain of errors and issues which together caused the server crashed. Recommended to rebuild these two indexes: xconv_endorsdate and xconv_psdate. Also modify CBF: online_error_action TO stop and offline_error_action to continue_ignore_table

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/26/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1116702.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 22:58:39

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    SQL returning different result with date('now') command. Actian reccommends to change the timezone to TZ=Asia/Manila

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/03/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1122791.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 22:59:16

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Ext4 is supported on Ingres however RHEL6 ext4 uses a default setting of barrier=1 which causes poor performance on Ingres. Actian recommend a barrier=0 setting.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/09/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1118844.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:00:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can remove/edit specific column for replication using ColumnProperties. Just check /Absent and /Name then add the names of columns you want to remove on target DB

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/09/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number RAM0001.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:02:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSOURCE conduct an installation support for Openroad 6.2 on Linux Machine and provides a Installation guide to help HDMF replicate the procedure.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/09/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1118647.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:02:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon installation of OpenROAD App Server on RHEL 6.9 we've got the "Error registering library .." but Actian thinks that it was just an ownership issue. It work on other VM installation

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/10/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1119181.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:10:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Some DBMS went down so the client restarted the Ingres. Upon checking the inglogs, one of the DBMS server died silently and Ingres didn't handle it properly which cause high performance of CPU. Actian asked to change the CBF Configurations: online_error action to stop and offline_error_action to continue_ignore_table.]

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/15/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1120073.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:10:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon initial checkpoint, the client had some error stating that vectorwise directory is missing, which upgradedb should create automatically. When the client manually created those directory, the checkpoint ran successfully. As per Actian, some directories were missing because someone ran destroydb

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/15/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1120072.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:12:56

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Select query running very slow on Ingres 11.1 but quite fast on Ingres 10.2. Found out that it was a bug (#136662) and was fixed on patch 15562.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/16/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1120081.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:13:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    On testing for upgrading from 10.2 to 11.1 (upgradedb), some db procedures were gone and were not recreated successfully. Upon investigation it was beacuse of the date format set to MULTINATIONAL4 instead of US

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/17/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1120493.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:14:13

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Asked Actian if there is a counterpart on Linux of using DLL on Microsoft Active Directory to authenticate OR users. Linux authentication was set via appserver portal VOSA. Opened case 1121449 for further discussion of vosa.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/23/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1121449.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:15:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Further discussion of inquiry in case 1120493. Asked Actian what is the counter-part of the windows registry on Linux, if there is also a registry file being used by VOSA. Applications can be registered via command line using regedit in silent mode. Though after the next patch, application are not registered in Windows registry but rather registered apps are written pm JSON file. VOSA will still be used to add application but you can also write script that add 'apps' on JSON file.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/23/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number RAM0002.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:16:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Mr Sherwin Astorga requested an assistance support to register images to OpenROAD VOSA on LINUX Machine.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/12/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1127683

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:16:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    To use 'tables' command on Ingres 11.1 make sure that the 'Query and Reorting Runtime' package is installed

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/13/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1127943.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:17:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    I have encountered this error: Check sum differences encountered. "<": values in install area: /II_SYSTEM/ingres ">": values in patch area: /II_SYSTEM/patch15562 267a268,269 > ./lib/thirdparty/lp32/libcrypto.so 00031,2706 > ./lib/thirdparty/lp32/libssl.so 23996,573 Error occurred during install. The install program failed to complete. I am currently testing the newest patch 15562 on my Ingres 11.1 VM when I got this error upon installation of the patch. What I did before this is that I reinstalled other packages such as Query and Reporting Tool/Runtime then I reinstalled the patch 15550 as advised by Kristoff, then when I install this patch I am getting this error. Will attach the inglogs for your reference.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/18/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1128760.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:18:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hope someone could help me with this, we are trying to setup LoadNRun for our client. We already have an OpenROAD App Server installation on a Windows VM and a sample image loaded through VOSA. Is there a step-by-step guide/ instruction to set this up and what are required for us to have to have this work on a client machine.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/18/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1128858.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:18:42

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Just a follow up question on my case number 01122791, is it OK to install Ingres on RHEL 7 with ext4 file system? If ever what are the pros and cons?

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/19/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1129206.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:19:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After an upgrade from Ingres 10.2 to 11.1, we are getting this error. It seems that simple upgradedb wont work and we have to manually run usermod to all the databases until I found this article stating that this could be an alternative command. I would just like to confirm if it is though. upgradedb dbname -modify or upgradedb -all -tree -modify

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/20/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number RAM0004.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:19:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Mr Sherwin Astorga requested an assistance support to find-out how to run comtestrso from a windows machine to an existing Linux OpenROAD App Server.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/22/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1129809.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:20:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    We are having problem running comtestrso from a window workstation. This server can be pinged and running comtestrso directly on it or through putty works, but not from another machine testing the app server. hr = 0x800706ba Releasing interface IRun4GLrs. On other Windows OpenROAD server, we have no problem. We may be doing something wrong, or something have to be done on the server to resolve this.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/25/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number MGP0002.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:21:14

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSOURCE conduct the First Batch of ONLINE TRAINING for INGRES SQL. The Training was participated by 13 HDMF personel.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/27/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1130725.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:21:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    We created this DB Procedure and is running in Ingres 10.2, Unfortunately, during our test upgrade in Ingres 11.1, we are hanging on the execute of this. create procedure dbp_virtual_sel_pf_ledger ( p_pagibigid varchar(25) not null, p_account_no varchar(25) not null, p_program_code varchar(10) not null, p_cyear varchar(13) not null ) result row( varchar(25), ingresdate, varchar(6), varchar(13), money, money, money, varchar(25), varchar(250)) as declare v_trans_code varchar(10); v_refno varchar(25); v_trans_date ingresdate; v_percov varchar(6); v_cyear varchar(13); v_ee money; v_er money; v_div money; v_pagibig_erid varchar(25); v_eyername varchar(250); begin for select trans_code, refno, trans_date, percov, cyear, sum(ee), sum(er), sum(div), pagibig_erid, eyername into :v_trans_code, :v_refno, :v_trans_date, :v_percov, :v_cyear, :v_ee, :v_er, :v_div, :v_pagibig_erid, :v_eyername from vw_virtual_branch_pf_ledger where pagibigid = :p_pagibigid and account_no = :p_account_no and program_code = :p_program_code and cyear = :p_cyear group by trans_code, refno, trans_date, percov, cyear, pagibig_erid, eyername having sum(ee) <> 0 or sum(er) <> 0 or sum(div) <> 0 order by trans_date desc, percov desc do return row(:v_refno, :v_trans_date, :v_percov, :v_cyear, :v_ee, :v_er, :v_div, :v_pagibig_erid,

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/27/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1130808.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:22:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After the version upgrade from 10.2 to 11.1 We ran this upgradedb -all -tree -modify assuming that we can upgrade all the old table formats to the new one used by 11.1. Unfortunately, we are still getting this error on IMADB database even if we run upgradedb imadb -tree -modify after shutting down the rmcmd. We also cannot usermod imadb -u$ingres remote.. because it is returning an error. We also did a check via select a.relid, a relowner from iirelation a, iitables b where a.relowner ... but it shows nothing in imadb.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/27/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number RAM0003.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:23:08

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSOURCE conduct the First Batch of ONLINE TRAINING for OpenROAD APPLICATION DEVELOPMENT. The Training was participated by 13 HDMF personel.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/03/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1132489.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:25:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSOURCE conduct the First Batch of ONLINE TRAINING for OpenROAD APPLICATION DEVELOPMENT. The Training was participated by 13 HDMF personel.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/14/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1134866.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:26:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    While realoding data from 10.2 to 11 client got this error: E_PS042C GRANT: You may not grant permit on database procedure 'ropa_sp_get_installsched'. As an alternative solution, you may add : flag -uropa_user when running the SQL or alternatively include 'set session authorization ropa_user'.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/15/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1134866.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:27:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Housing group is trying to reload their hdmf_ropa database to Ingres 11.1, unfortunately they stumbled a E_PS042C GRANT error which stop database procedures from running

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/25/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1137471.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:27:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    With the help of Actian, DSOURCE set up and tested Ingres Replicator for future use. See document HVR and Ingres Replicator for more detailed comparison.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/28/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1137846.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:28:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Clarify some information about LoadNRun. Loadnrun is a simple solution for non-privileged users on Windows machines to deploy OpenROAD eClient applications. It is identical to eClient applications that run in mode 2. Yumiko Oura of Actian attached some knowledge base on how to set up LoadNRun.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/30/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1138248.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:28:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Clarify some information about the limitations of Ingres Replicator. Aside from additonal for the database server, one of the cons of Ingres Replicator is that x100 tables are not and supported and might marked as deprecated in the near future.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/02/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1138619.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:29:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource set up and test the use of Incremental Rollforward. This is of the options considered by HDMF for the replication of their data from production server to their data warehouse. See document Ingres Rollforward KB for more details.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/08/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1140020.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:30:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Clarify some questions in running OpenROAD 11.1 on top of Ingres 11.1. OpenROAD 11.1 requires Ingres 11.1 client installation even on developer workstation. You cannot install OpenROAD 11.1 on top of Client Runtime 11.1 media.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/12/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1140819.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:30:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Had license error on OpenROAD 11.1, apparently the newest version of OpenROAD requires license.xml now. As a resolution Yumiko of Actian provides a trial license of OpenROAD 11.1. Aside from Ingres, license.xml should also include license for OpenROAD when using version 11.1.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/13/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1141038.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:31:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A single corrupted frame is preventing the application to export an image. But as the client tries to delete the frame. It gives him "Cannot fetch source" error. Please __ KB for the resolution.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/14/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1141246.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:31:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Question was raised as RHEL 6 uses PHT +08:00 (Philippine Timezone) while RHEL 7 or hight uses +08:00 PST as in Pacifics Standard Time. This may cause some problems when client upgrade the OS to much newer version of RHEL.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/23/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1143206.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 23:32:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After upgrading the RHL6_MID to Ingres 11.1 and run the ‘upgradedb’ command on the database, it had some errors like E_DU2417_NODROP_SYSCAT and E_DU241A_SYSCAT_UPGRADE_FAILED. As a resolution, the client uses the unloaddb backup files to reload and fix the database. Actian however suggest to run verifydb command (verifydb -mreport -sdbname -odbms_catalogs) to ensure that no problem exist in the database before upgrading to the newer version.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/23/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1143207.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:40:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    During upgrade of HO6 server from Ingres 10.2 to Ingres 11 some components like DBMS Server, Ingres Networking etc. could not be installed. Upon checking, there are 2 hostnames declared on config.dat, to solve the problem the client deleted on of the hostname.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/23/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1143210.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:41:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    During upgrade of HO6 server we've included the C2 Security component but had some problems while installing it. Upon checking of the config.dat C2 Security was installed. As of this moment, we are still verifying of C2 was already installed, if not, we'll schedule the installation of the said component.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/28/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number RAM0005.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:41:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Mr. Quiamno requested assistance on how to export query result to CVS file. With exchange of research and testing, Mr Quiamno came-up with a solution somewhat identical to DSOURCE's findings.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/28/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number MGP0001.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:42:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSOURCE conduct a POC of HVR and tested various INGRES versions replicating data across servers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/28/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1144172.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:53:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Confirming sequence of activity during Database Upgrade. Client is running optimizedb, sysmod, usermod.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/10/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1144649.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:54:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The upgrade of the production database server to Ingres 11 was immediately aborted. The error says that the files was owned by 10.2 package.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/01/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1144995.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:55:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    While upgrading the DR server to Ingres 11.1, the process stopped while upgrading the iidbdbd.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/01/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1144997.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:55:47

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Problem connecting PowerBi to ActianX, resolved by installing latest version of PowerBi 64-bit.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/02/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145338.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:56:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    SIGSEGV error encountered causing database crash after upgrade.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/02/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145349.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:57:14

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Experiencing performance issues after Database Upgrade.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/02/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145353.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:57:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_UL0009_MEM_SEMWAIT Error attempting to set semaphore and E_UL0004_CORRUPT ULM has detected a corrupted memory pool errors encountered leading to crash.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145360.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:58:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_UL0004_CORRUPT ULM has detected a corrupted memory pool keeps reoccuring.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145450.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:58:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Experienced another server crash related to previous cases.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145604.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:59:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    running optimizedb -zf fname where in fname the flag we use is -zk -zns -zfq. Unfortunately statistics where created even in the non-keyed columns.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145622.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:00:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Experienced another server crash related to previous cases.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/04/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145719.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:01:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Performance issue running specific query comparing results to 10.2 installation.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/04/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1145918.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:01:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Experienced another server crash related to previous cases. E_SO0215_PSF_ERROR E_RD0041_BAD_FCB E_PS0904_BAD_RDF_GETDESC E_PS0007_INT_OTHER_FAC_ERR

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/05/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1146129.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:02:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Tables on upgraded 11.1 database shows 10.0 versions.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/06/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1146141.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:02:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Showing very slow performance on queries with 'AND STATUS' . Bug ID II-6715,137187 fixed on Patch 15599

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/06/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1146142.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:03:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Identified the specific query causing SIGSEGV error. Using REPEATED SELECT vs EXECUTE IMMEDIATELY

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/08/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1146898.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:04:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Another query showing very poor performance using 'LIKE%'.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/09/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1146909.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:05:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Case Description statdump -zc -o filename -rtablename gives W_OP0976 WARNING: Table 'tablename0, column 'columname' value for rows 0 and 1 have the same value ( -2147483648). II_CHARSETII=ISO88591

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/09/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1146992.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:05:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Request of Installer of Patch 15587

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/09/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1147391.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:06:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Could not connect to the server. Specified server may not exist or is not allowing connects. INGRES error message is E_CLFE07_BS_READ_ERR. It might be due to CPU overload. Fixed on patch 15595.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/11/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1147889.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:07:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Performance issue running specific query select * from vw_esrs_stl_listing where pagibigid = '158001251275' and status = '10010'

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/10/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number MGP0003.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:08:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    It is found out that the error might be caused by the Disk not available.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/19/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1150874.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:09:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    /ii_database/ingres/data/default/pf/aaaaabbb.t00 file couldn't be found. The select statement used was not valid for partitioned table. KB on how to find physical files for partitioned table was attached to the case.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/19/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1150989.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:11:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_GC4807_CONN_ABORT Aborting client connection with host '::ffff:192.168.1.43' port '56136', reason follows. read() failed with operating system error 104 (Connection reset by peer) occuring after 15595 patch. This error was sue to Java program(application) exited or was aborted for other reasons such as network connection or alike.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/02/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1156446.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:12:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI requested for license file of OpenROAD for testing.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/02/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1156458.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:12:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF had some error while doing some rollforward on close server (inghsg1). DSI recommends to copy the checkpoint files and do the rollforward again. Checpoint files may be corrupted.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/17/2020 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1159673.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 16:13:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF installed the latest version of PowerBI and used the provided MEZ file to connect and make a direct query.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/11/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1166656.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:32:56

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Generating statistics, as mentioned earlier, is quite important for X100, in some cases even more important than for Ingres tables to ensure optimal memory management while executing queries.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/17/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1168159.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:35:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Below functions can be used for x100 tables. * select TIMESTAMPDIFF(day, col1, DATE '2021-12-31') from idatex\g Executing . . . lqqqqqqqqqqqqqqqqqqqqqqk xcol1 x tqqqqqqqqqqqqqqqqqqqqqqu x 365x mqqqqqqqqqqqqqqqqqqqqqqj (1 row) continue * Where col1 contains "2020-12-31" and idatex is an x100 table.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/19/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1168843.000.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:36:55

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Problem fixed after database restart.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/24/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1170204.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:37:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF had the 'Bad Data' error while loading the .trl file into global temporary table. Apparently, there are some discrepancy on the declared columns on Global Temporary Table that result of mismatch of data from audit trail file.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/25/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1170551.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:38:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Some transctions were included on the transation prior to the start date/time (-e flag) declared on auditdb. Apparently, '-e' flag on auditdb gives all transactions that were committed after the specified date and time no matter when they began. The date column on audit trail records the start of the query, not when they were committed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/02/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number MGP0004.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:40:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Error E_QS0001 and E_OP0886_QSF_PALLOC occurred while running help command on certain table. Recommends to double the value of qsf_memory on CBF. Run CBF > DBMS Server > Derived > Configure.Make sure to save the changes and ingstop/ingstart Ingres to take effect.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/01/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1172158.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:49:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon confirming that LoadNinja only works for web-based applicaions, DSI asked Actian if there is a Performance Testing tool that could be use for OpenROAD applications. They suggest to use Jmeter, but it doesn't work for OpenROAD as well.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/03/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1172828.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:56:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI had a few clarification on using ANSIDATE for date-only data and TIMESTAMP for date-and-time format. Also the difference of using TIMESTAMP WITH TIMEZONE and TIMESTAMP WITH LOCAL TIMEZONE.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/04/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1173159.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:57:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    While doing an incremental rollforwarddb on test server, DSI had this E_DM1306_RFP_APPLY_RECORD error. Initial investigations show that there were some files deleted on II_WORK location that caused rollforward to fail. Further investigation stopped because the server was used for something else.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/07/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1173608.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:58:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Created a temporary session table and use the data to insert into heap and x100 table. Upon doing a select statement, it gives E_US10D7 error and looks like the inserted value was an invalid date, however the value on temporary session table was valid. Apparently, it’s a bug with ID II-7036, 137473 and solved with Ingres 11.1 Patch 15615.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/09/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1174080.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 12:00:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Squeeze() function gives different output for a btree and x100 tables whenever used to convert a data from character to money type. Actian declare this a bug with ID B137471, II-7034 and still waiting for patch to fix this.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/09/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1174237.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 12:01:16

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The client encountered a wrong output from two tables with IN SELECT statement, where table 1 = lo_stl_frontend has a column name called pagibigid, and table 2 = lms_stl_master doesn't have any column name called pagibigid but is returning a result. It turned out that this behavior works as per design and is SQL standards compliant. If a column does not exist in the table referenced in the FROM clause of a subquery but exists in a table referenced by the outer query's FROM clause, it is implicitly qualified by the table referenced in the FROM clause of the outer query.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/10/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1174252.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 12:02:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Just a few clarification on Chapter 4: Sizing x100 System on System Administration Guide of Ingres 11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/10/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1174346.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:03:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    One of the client’s server has been experiencing some slow down and some DBMS server shutdown. Some memory free problems have seen on the error log, E_SC0224 MEMORY_FREE Unable to deallocate SCF memory. Actian’s recommendation is to unprotect and recalculate Ingres locking parameters such as lock_limit and resource_limit.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/10/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1174456.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:04:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    An inquiry about different ways on how to do the data encryption on Ingres. There are two ways to do the encryption; through DBMS server-level encryption and Application-level encryption. Check Security Guide Documentation for more information.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/14/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1175304.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:05:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Converting a blank ('') or null ingresdate to ansidate gives a current date result. Bug ID II-7070 was created and waiting for a patch. For the meantime, HDMF is using the script that Keith Bolam created to convert tables from ingres to x100.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/14/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1175305

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:07:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Declaring a global temporary doesn't return error even if it doesn't include required ON COMMIT PRESERVE ROWS and WITH NO RECOVERY. For ease of use, it is no longer needed to mandatorily mention the parameter. Actian raised a documentation bug for thisand will update on the upoming releases.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/16/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1175707.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:07:47

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Getting "Component cannot be saved. The Object encoding could not be flushed.” error. It turned out a certain bitmap was associated with Windolcon in one of the frames. Deleting the bitmap solved the problem.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/16/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1175712.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:09:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI tested to relocate x100 table to another using MODIFY statement but giving E_US15B9 error. As per Actian, the right way to relocate the x100 table is to use CTAS, create and new table with new location then drop the old one. Also tested MODIFY to RECONSTRUCT, apparently the system updated the location, but files are not actually relocated. Actian create a bug for this II-7099, II-3803.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/18/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1176136.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:10:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Ken Lindner opened a case to send training files to DSI.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/03/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1179283.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:15:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The client forgot to include quote '' on the #m12 flag that's why it ran on individual locations separately and caused the checkpoint to slow down.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/08/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1180506.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:16:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    During testing DSI noticed that mask/unmask privilege of the user will depend on the user ‘ingres’ privilege. As per Actian, the best way to effectively authenticate and login to database is by using +user flag. Sample: sql +user=username,password database_name. Apparently when using ‘-u’ flag, it inherits some properties from the OS. This option is only available for users who have DB_ADMIN privilege.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/09/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1180787.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:17:16

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A few clarification on the sample computation of x100 sizing on Chapter 4 of System Administration Guide of Ingres 11. Ken Lindner had a zoom meeting to clarify and explain further the sample computation.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/09/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1180790.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:20:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A certain database procedure caused SIGSEVG on the server. Actian advised to set opf_autostats to x100 on CBF and restart Ingres to take effect.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1184998.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:20:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The client encountered E_VW1142_WRITEAGGR after creating an x100 table from another x100 table. Actian able to replicate the problem and created JIRA number II-7456 and waiting for engineering team’s update.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/25/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1185204.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:22:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The DBMS and Archiver suddenly shut down, due to several errors. Unfortunately, Actian could not drill down to specific point where the crashed because the DBMS logs was not enabled yet. The client took three to enable the DBMS logs. Four weeks later, crashed happen again. The problem appears to have been caused by a lock escalation to table level locks to free locks up in the transaction that was accompanied by DEADLOCKS and finally when there were no more locks available to the transaction the DBMS and Recovery servers were not able to roll the transaction back and the database was then marked inconsistent. Actian recommended to increase the system_maxlocks on CBF and restart Ingres to take effect.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/08/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1187564.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:23:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF asked for the source code of one of the OpenROAD's sample demo. Actian, sent the link for the source as well as the link to the demo application.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/04/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1194864.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:23:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI asked for a copy of installer of Actian X 11.1 Patch 15633 for Linux 64-bit.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/04/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1194867.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:24:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    For the future version upgrade of some servers, DSI asked Actian if there's way to verify whether an instance was installed using RPM or Ingbuild installer. You can run >rpm -qai |grep ingres and >rpm -qai |grep dbms to check.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/09/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1196162.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:25:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI asked for a copy of licensing utility that could work on Windows 7 32-bit. Apparently, the latest version uploaded on ESD doesn't work on older version of Windows.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/14/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1197249.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:26:15

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI asked Actian if there is a Basic Troubleshooting Guide documentation for Ingres. Apparently there's no guide available.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/17/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1197843.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:26:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Client noticed that Stored Procedures are not updating immediately after a drop/create. It needs ingstop/ingstart to take effect on all DBMS Severs. Actian this is an old bug, II-7617, a complicated one and Engineering are still checking the feasiblity to resolve. Actian gave a workaround while they are still studying the bug. You can do "set trace point qs506" in all DBMS server that might need the DB procedure. This will fkush the QSF cache and forces each DBMS server to rebuild QEP from the DB procedure definition.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/25/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1200257.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:27:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI asked Actian if there's a command or certain method to check when the last usermod was ran. As usermod does reorganize the tables and recreate secondary indexes, just like sysmod, we can use this query to check when was the last time the table was modified: select varchar(table_name,32) as "tablename",varchar(table_owner,32) as "table_owner",create_date,modify_date from iitables.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/14/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1200286.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:28:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    OpenROAD workbench was not loading properly and days after it worked again. Actian and DSI believed that this may be because of the Windows Update applied on the machine

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/07/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1203588.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:29:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    One of the production server of the client (ingdba1) suddenly shut down. As per checking of the Ingres error log, transaction log became full and leads the Ingres to shutdown. Possible causes are long running queries that possibly were uncommited, long DB procedures that involved unoptimized table and QSF out of memory caused by these uncommited queries. Actian recommends to double the value of qef_hash_mem on CBF and do housekepping chores regularly.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/02/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1215683.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:38:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Database became inconsistent after a failed rollback due to deadlocks encountered on iisequence table. Actian said that its hitting Bug II-2545 and currently in Engineering for patch creation

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/07/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1220146.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:39:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Just a few clarification with Actian on how to properly calculate width of an encrypted column for both transparent and application-based encryption.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/15/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1227009.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:40:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Tellering Server having some SIGSEGV due to QSF Meemory Pool errors. Actian recommends to change qsf_quideline to "LARGE" and increase the value of qsf_memory.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/15/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1227018.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:42:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The same error in Case 01174346 occurred again even after updating the configuration. Recovery Server failed to recover the same indexes in the previous case and shut down itself. Actian recommends to regularly recreate xled_pfrdate and xledext_transdate, also to upgrade the server to Actian X 11.1.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/25/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1249256.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 13:43:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Server can be accesed via Putty by setting up IP to static and setting Forwarding Port 22 but cannot established connection via netutil from a remote machine. Testing wasn't pushed through because of server's hardware problem.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/01/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1262317.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:56:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    There are some E_VW1059_WRITESORT on error log that appeared October 2021 but information says that it was run August 2021 and couldn’t find it on IPM anymore. Another error is that the client is running an SQL Script to modify pf_ledger_16_20 except session.pf_ledger_16_20_tmp to combine. Running this on OR6.2 thru Execute Immediate gives an error, but via SQL Monitor or via Terminal it runs smoothly without any error. Unfortunately, the client could not reproduce the error, therefore thorough testing/investigation could not push through.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/17/2022 16:51:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1263196.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:57:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI requested for current product availability and software compatibility of Actian X

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/04/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1263626.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:33:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per investigation, E_AD2062_NO_FUNC_FOUND was caused by not providing the right parameters to the data dependent procedure.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/10/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1266352.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:34:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    newdcddb01 crashed due to SIGSEGV simliar to bug II-6256 which has something to do with inner joins. There are a lot E_US0001 error seen on log. Actian recommends to increase the value of connect_limit and upgrade the server to Actian X 11.1

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 14:59:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/12/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1267038.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:41:42

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Several E_VW1006_GENERIC, E_DM9848_BACKUP_DB and E_DM9847_X100_BACKUP errors founf on error log. As per Actian, it seems that some of the directory is missing/corrupted. They recommend to disable and then renable the journaling of pfmdb database.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 15:02:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/01/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1274607.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:42:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is with regards to bug that was fixed on case 1175712 (II-7099, II-3803). The said patch was to fix the bug on 'modify to reconstruct' not on the 'modify to relocate'. Still 'modfiy to relocate' was not supprted on x100 tables yet.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 15:04:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/01/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1274608.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:43:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is with regards to bug that was fixed on case 1175712 (II-7099, II-3803). The said patch works for 'modiy to reconstrcut' ONLY with SINGLE location, NOT with MULTIPLE locations.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 15:06:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1275167.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:44:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    One of the server (Ingres 10.2 ver) has been experiencing crash/hang. Looking at the error logs, there are some deadlocks on one of the database. HDMF upgraded the version of Ingres to 11.1.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 15:07:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/02/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource recommended and was approved by HDMF to conduct a test migration for OpenROAD 3.1 Application to the latest version (OpenROAD 11.12)

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 17:09:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A test credential was provided and DSI is able to access the application through login. Gathered screenhots to compare visual differences between OR 5.1 and 11.2 with Property Changer applied. No functional error found yet though all that's done is navigating between frames. A meeting was requested to discuss next step (i.e. Functional Testing). On-site visit Testing and Application Access 1:30pm to 2:30pm

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/04/2022 16:07:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource changed the database connection from the DR server to the Test Server (Actiansvr). Minor testing are done to make sure everything still works after changing database. This Testing Database is currently on Ingres Version 11.1. The previous database being used is on version 10.2. Site-visit configuration 1:00pm to 2:00pm

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/05/2022 16:13:13

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A Manual Functional Testing has been done with the help of Sir Chris Manalo and supervision of Sir Roy Urbina. End-to-end testing on migrated version 5.1 was a success with no functional or visual issues encountered. On the other hand, testing on migrated version 11.2 was almost fault-free but an issue with date verification occured. Upon checking, date format of MM-DD-YYYY sends an error but format DD-MM-YYYY works fine. This is an issue since version 5.1 doesn't have a problem with this. Further investigation will be done to identify the specifics of this issue and to specify the most efficient fix for this. Site-visit testing and debugging 1:30pm to 3:30pm

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/06/2022 16:52:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date format error was fixed, apparently the OpenROAD 11.2 environment has its II_DATE_FORMAT set to MULTINATIONAL4. Changing this to US same as the OR 5.1 installation fixed the problem, no changes on the codes was done.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/11/2022 16:31:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Futher tested Image of the AUT to determine compatibility with different Client Runtime. This test was conducted to identify possible options for future application to be migrated. Options includes migrating to the latest version (11.2) and running all images thourhg Client Runtime 11.2 OR migrating to specific versions then re-imaging application to run on Client Runtime 6.2. Here are the Findings: Migrating to either versions 5.1, 6.2 and 11.2 and running on thier respective Client Runtime definitely works. Migrating to version 5.1 then re-imaging to OR 6.2 to use Client Runtime 6.2 also works. Definitely re-imaging to a higher version works, 5.1 re-image to 6.2, 5.1 re-image to 11.2, 6.2 re-image to 11.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/22/2022 16:57:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A digital copy of the documentation for OPENROAD MIGRATION FROM 3.1 to 11.2 was sent to Sir Roy Urbina for review and acceptance. This document details the process and results of the activity.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/20/2021 10:56:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF provided DSI with the exported source code to test migrate from OpenROAD 3.1 to 11.2. This Application Under Test that is currently on version 3.1 is called Funding Commitment Line. Provided with the help of Sir Chris Manalo.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/03/2022 08:42:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Due to older versions of OpenROAD are already out of support, these are not available for download on the ACTIAN Portal. DSI also aren't able to get our hands with old versions. alternatively, DSI requested HDMF for their installers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/24/2022 12:17:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Installers are provided by HDMF namely versions 3.5, 4.1 and 5.1 through the help of Sir Rosel Tagorio and Ma'am Bernadette Angeles. Internal testing and research was done to identify proper steps to migrate old applications on 3.5 to 11.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/07/2022 16:26:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Test environment setup - DSi tried to install Virtual Machines to simulate separate environments for version 5.1 and 11.2. This setup deemed not efficient since the installation on VMwares and too slow. DSI decided to install OpenROAD 5.1 directly to the machine provided. On-site visit and installation run from 1:00pm to 4:00pm.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/09/2022 16:30:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI have successfully loaded the Test Application on OpenROAD 5.1 connected to Sir Alvin's preferred database for connection testing. There are still included applications that are part of the application suite that need to be converted. The following are the applications being used in conjunction with the AUT: common origcommon orig_class dbaccess printapi2 A request for the said applications have been submitted. On-site visit and installation run from 2:00pm to 4:00pm.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/17/2022 17:35:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Site visit to check on the progress on the request for the missing applicatons, also to discuss the progress of the test. Missing applications provided by Sir Chris Manalo. Site-visit and follow-up from 1:30pm to 2:30pm.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 16:44:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon loading and testing the missing applications, it is later found out that there are other applications needed to complete the test. The following prerequisite applications are requested and immediately provided by Sir Chris Manalo: idletimer fileexist rdbaaccess The application is completely loaded to OpenROAD 5.1 and is running. Though DSI do not have an access to the application to further test it. A request to test-run the application on OpenROAD 5.1 was sent so both party can identify changes and possible errors on the Migration. Next step is to load the exported 5.1 app to 11.2. Site-visit and testing from 1:30pm to 3:30pm.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 17:29:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Still waiting for credentials on the FCA system. Meanwhile, a test migration to 11.2 from 5.1 exported files was successful. Further testing is still pending. Also, upon test migrating to 11.2, DSI manage to test the Property Changer Tool on the imported 11.2 application. The property change was done but changes here are all aesthetic.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/12/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1284977.000.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:46:08

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    LoadNRun could not successfully install because of error “Ingres Net XW failed to start.”, also it seems that the installer cannot detect the runtime client that was installed before the LoadNRun installation. Actian said that it was a bug and gave us a workaround for the mean time. Use orsmsiexec11.bat with loadnrun112_x64_nonet.rsp. From the command prompt run ormsiexec11 loadnrun112_x64_nonet.rsp /install

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/22/2021 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Migration from DSI Support Log. Refer to case number 1287497.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/18/2022 22:47:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI is requesting to Actian for a copy on installer of OpenROAD 3.5 and 4.1.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/03/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Server reports E_CL1613 PC_SP_PROCPC[f][s]spawn:System Process Table is Temporarily Full error which most probably caused the DB crashed. As a resolution DSI asked HDMF to increase the soft and hard limits of the OS. vi /etc/security/limits.conf * soft nofile 32000 * hard nofile 63696.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/23/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI asked what External Class should use when using SAP Crystal Report 2020 Application. Actian said that it will need an external userclass with an ActiveX viewer component but unfortunately it wasn’t delivered with Crystal Report. Actian sent this links for some readings and help: Deprecated and Removed Featureshttps://help.sap.com/viewer/09fe9f205ee047d48d58665649fc4fae/4.3/en-US/a63659eb71074d2b8fcca84db88fe204.html , Standalone viewer application https://www.sap.com/products/crystal-reports-viewer.html

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 11:14:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/15/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per reported, you are experiencing slow down of the server upon execution of the following query. select payrefno as payrefno, msb_code as msb_code, hub_code as hub_code, date_created as date_created, pay_source as pay_source, payor_id as payor_id, payor_name as payor_name, payor_address as payor_address, currency_code as currency_code, payment_mode as payment_mode, is_value_dated as is_value_dated, amount as amount, orig_refno as orig_refno, orig_refdate as orig_refdate, old_payrefno as oldpayrefno, status as status, status_date as status_date, membership_category as membership_category, user_branch_code as user_branch_code from pof_payscreenheader where payrefno= ~V

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:08:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The following errors could be due to the following reasons: E_CL2539_THREAD_CREATE_FAIL CSMTadd_thread 1. Insufficient resources to create another thread 2. System-imposed limit on the number of threads was encountered 3. No permission to set the scheduling policy and parameters specified during thread creation

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:09:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_DMA011_LK_NO_LLBS 1. More lock list blocks are available. It could be that locking shared memory has been exhausted, or that the configured limit (ii.*.rcp.lock.list_limit) has been exceeded

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:10:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_DM9C07_OUT_OF_LOCKLISTS 1. You have exceeded the maximum number of lock lists allocated for this installation. Either reduce the number of sessions in the installation or increase the number of lock lists in the locking system. Use the lockstat utility to show the current quota settings in the locking system

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:11:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is similar with the case number 01174346 dated Feb 2021, whereas the following: 1. ii.iisp_tellering.rcp.lock.lock_limit: 100000 (Protected) 2. ii.iisp_tellering.rcp.lock.per_tx_limit: 3000 In addition, you might want to check your Memory before running the said query. You only have a total of 32GB RAM and available memory during the time of the error is only 252MB.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:12:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Therefore, we would like to continue checking the status of this sever provided that you do the following: 1. Check for any session that is potentially hugging your memory resources if there’s any. 2. Usermod the concerned tables on the payrefno query. 3. Ingstop the instance 4. Recalculate parameters a. Open CBF b. Click on Locking System > Configure > Derived c. Select lock_limit d. If protected column states “yes”, select protect to unprotect it e. Select recalculate f. Do steps c,d,e for resource_limit parameter g. Save changes h. Exit CBF 5. Ingstart the instance 6. Check if you have sufficient memory (Take note of this before step #7) 7. Run the payrefno query (On an isolated environment, no users) 8. Check if the memory status (Take note of this) 9. Check if this SQL still hugs memory resources 10. Increase memory, redo steps #s 3-5.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:16:42

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon checking the status of your Ingres instance on IISP_TELLERING via inglogs_20220218_133831_pid86335. Date 18_Feb 2022 1338H, I have not seen any critical errors. The lock_limit of 100,000 was recalculated to 150,000. Although, we are still running on low RAM as shown on the statistics below: total used free shared buffers cached Mem: 32868348 32646244 222104 745324 163736 30437360 -/+ buffers/cache: 2045148 30823200 Swap: 16506876 345028 16161848 I would suggest increasing the RAM, recalculate again and check if it still hugging memory. In addition, please see any already terminated sessions that might still locks memory.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/14/2022 15:24:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. DSI suggested to unprotect and recalculate the lock_limit to ITID team. 2. ITID team already requested for an additional memory for IISP_TELLERING server, if the additional memory already installed we suggest to perform solution #1. 3. Data Center team created external indexes for the tables involving the payref SQL. As of 28-Feb 2022 and upon confirmation of the requestor, no error/s have encountered.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 15:12:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Emergency 2-hour remote assistance via FB messenger · Client called around February 26, 2022 8:18 AM asking for assistance on their error while upgrading from Ingres 10.2 to Actian X Ingres 11.1 version · II_DATABASE doesn’t seem to be writeable due to the following: II_SYSTEM’s original location is /ii_database/ingres Cannot find /ii_database/ingres location /ii_database was changed to /II_DATABASE (take note of case sensitive) · DSI asked client to run ‘chmod 777’ and ‘chown ingres:ingres’ on II_SYSTEM, II_DATABASE and II_CKPT – DONE, No effect · DSI asked the client to run ‘echo $II_SYSTEM’ and ‘ingprenv’ to check whether the $II_SYSTEM is /II_SYSTEM – NOT EXECUTED · Client said the issue was resolved by rebooting the server at 10:00AM Product: Ingres Version: 11.1 Patch: 15633 OS: Linux x86 64-bit Server: NEWDCDB01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/10/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF experienced this error while running auditdb on IISP ROPA Server: Thu Mar 10 22:08:32 2022 E_DM1212_ATP_DISPLAY Error writing display record during Auditdb processing. The command run successfully for dates March 7 - 11, but for March 1 - 5 it returned E_DM1212_ATP_DISPLAY error.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2022 16:13:08

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    These are the purchase_id that has multiple pfr_dates +--------------------+-------------+ |purchase_id |id_cnt | +--------------------+-------------+ |PO8220200214001 | 2| |PO1520180716018 | 2| |PO1520180920069 | 2| |PO1520190214019 | 2| |PO8220180803006 | 2| |PO1520180327049 | 2| |PO8220200110001 | 2| |PO2820190620001 | 2| |PO1520191218024 | 2| |PO2820191210002 | 2| |PO8220201001001 | 2| |PO1520180723014 | 2| |PO1520180327005 | 2| |PO1520190228008 | 2| |PO6420201019003 | 2| |PO1520200108002 | 2| |PO1520180720067 | 2| |PO1520190219034 | 2| |PO8820190422002 | 2| |PO4020191121004 | 2| |PO1520191220001 | 2| |PO5320191119014 | 2| |PO1520190711049 | 2| |PO3420181019001 | 2| |PO4020200116003 | 2| |PO4720190621002 | 2| |PO1520190313022 | 2| |PO8220180803007 | 2| |PO1520190912007 | 2| |PO1520191223010 | 2| |PO1520190918072 | 2| |PO1520180308045 | 2| |PO6420191106059 | 2| |PO6420191227006 | 2| |PO1520191226007 | 2| |PO1520191217009 | 2| |PO1520180604025 | 2| |PO4720190108001 | 2| |PO1520191017005 | 2| |PO1520180619039 | 2| |PO1520181219005 | 2| |PO4020181016001 | 2| |PO1520180613008 | 2| |PO4020190723002 | 2| |PO1520190117070 | 2| |PO4020191121005 | 2| |PO1520180529037 | 2| |PO1520180720076 | 2| |PO1520181016023 | 2|

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2022 16:14:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    +--------------------+-------------+ |purchase_id |id_cnt | +--------------------+-------------+ |PO1520180712057 | 2| |PO1520191220020 | 2| |PO1520181122051 | 2| |PO1520181206043 | 3| |PO1520191126059 | 3| |PO1520190220116 | 3| |PO7620181112001 | 3| |PO1520190131050 | 3| |PO1520180907042 | 3| |PO1520180420027 | 3| |PO8220190215002 | 4| |PO8820190116001 | 4| |PO8820181218002 | 6| |PO1520210414009 | 14| +--------------------+-------------+

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/20/2022 14:20:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    We created a small sample of the concerned tables. We cleaned up the SQL script provided by Sir Jomar of HDMF for it to run without any more E_US125D Ambiguous replace error. We ran the SQL script multiple times enough to generate a new jnl entry on the said test database. We ran the auditdb without any E_DM1212_ATP_DISPLAY error. We are running on II 11.1.0 (a64.lnx/100) 15744. We cannot create a test case.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/20/2022 14:26:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After numerous attempt to simulate and reproduce the problem encountered, we failed to create a test case of this error. Recommendations: 1. After running an alter table make sure to run the following a. usermod dbname [-uusername][{table1 table2 table3 ...}] [-noint] [-repmod [+w|-w]] [-online]. This is to modify the table/s being altered. b. ckpdb dbname. This is so that the physical structure of the table match the journals. 2. We also strongly recommend to update the patch on this server and on any other production servers to avoid these kind of problems happening in the future. We are currently on II 11.1.0 (a64.lnx/100) 15744 as of April 2022.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/11/2022 15:20:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    March 11, 2022 - DSI asked Sir Alvin to enable II_DBMS_LOG of the server - DSI asked HDMF if theres any changes or modification on the involed tables: ropa_lti_evaluation ropa_lt_masterr ropa_masterr ropa_notary ropa_purchase as per Sir Jomar, ropa_purchased was altered last January 8

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/30/2022 15:22:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    March 30, 2022 - DSI follow up the status of this logged case to HDMF

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/06/2022 16:58:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Gather few data and run testing to check the following: 1. Ran auditdb on individual tables. Found out that table ropa_purchase is the one causing the E_DM1212 error. Command: auditdb hdmf_ropa -table=ropa_purchase -file -b01-mar-2022:23:00:00 -e05-mar-2022:01:00:00 2. Find out that the affected dates are not 1-Mar to 5-Mar. It is 1-Mar to 4-Mar. 3. Checked that latest alter date, it is not Jan 2022. It is 6-Mar 2022 11:27:01 GMT. 4. No checkpoint on 6-Mar because it is Sunday.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/08/2022 12:13:13

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional information gathered and further testing to isolate the case: 1. Created a pseudo ropa_purchase table. 2. Alter table add column to the table. 3. Run modify. 4. Auditdb -- OK! 5. KB attached re: Schema changes vs Auditdb with results to E_DM1212 error. Facts: 1. Saying that the alteration of the table is 6-Mar 2022 and they did not run a checkpoint on the same date, hence the cause of the inconsistency on the physical structure of the table as against the journals. 2. The iitables shows the latest alter date, hence we did not know if they did an alteration prior to 6-Mar i.e., 1-Mar to 5-Mar 3. They ran a checkpoint 7-Mar. Questions: 1.. Apparently, 6-Mar is the latest alter without any checkpoint but how come when I ran auditdb on these dates we are not getting any E_DM1212_ATP_DISPLAY error. Command ran: auditdb hdmf_ropa -table=ropa_purchase -file -b06-mar-2022:23:00:00 -e10-mar-2022:01:00:00 2. We are NOT getting any errors on or before 28-Feb and after 5-Mar. We are getting errors on 1-Mar to 4-Mar wherein they have checkpoints. 3. If fact#2 is true and they have checkpoint on the same dates, we shouldn't have any errors on those dates. We should have error on 6-Mar date where there was an alteration and NO checkpoint.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/08/2022 12:25:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    We have to simulate the actual step-by-step procedure to further understand the cause. Additional request and clarification to HDMF: 1. What is the actual alteration they did on ropa_purchase table? If they have the actual script or SQL used that would be great. 2. What is the complete step-by-step procedure they did after the alteration? Action plan: 1. Replicate the above procedure with the pseudo ropa_purchase table. 2. Rollforward hdmf_ropa database to test server and see if error still occurs.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/11/2022 15:37:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF gave us the sample SQL that they run during the alter table on ropa_purchase. Although we are getting sequence problem and minor error due to update part. See actual test result below: INGRES TERMINAL MONITOR Copyright 2019 Actian Corporation Ingres Linux Version II 11.1.0 (a64.lnx/100) login Mon Apr 11 15:42:41 2022 Enter \g to execute commands, "help help\g" for general help, "help tm\g" for terminal monitor help, \q to quit continue * * /* SQL Startup File */ alter table ropa_purchase add column fp_date date Executing . . . continue * * * * * create table purchase_fpdate as select a.purchase_id , a.ropa_id, b.pfrdate from ropa_purchase a LEFT JOIN ropa_payment b ON a.ropa_id = b.ropa_id where a.paymode = 1 and a.stat_cd NOT IN (3,4,5) and a.fp_date IS NULL and b.pay_type = 19 Executing . . . (3550 rows) continue * * * * * * update ropa_purchase as rp from purchase_fpdate as pf set rp.fp_date = pf.pfrdate where rp.purchase_id = pf.purchase_id Executing . . . E_US125D Ambiguous replace: you have specified several replacements for the same row. (Mon Apr 11 15:42:42 2022) continue * * * DROP TABLE purchase_fpdate; Executing . . . continue * * * Your SQL statement(s) have been committed. Ingres Version II 11.1.0 (a64.lnx/100) logout

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 10:58:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Made a follow up email for our concerns last 11-Apr. Found out that patch are not updated. They are still in patch 15683, whereas we provided patch 15726 last January. Two patch release were also missed out for February 15730 and March 15738. Already sent an email for the April patch 15744.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2022 15:26:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Seeing errors while running the provided update script: update ropa_purchase as rp from purchase_fpdate as pf set rp.fp_date = pf.pfrdate where rp.purchase_id = pf.purchase_id Executing . . . E_US125D Ambiguous replace: you have specified several replacements for the same row. (Tue Apr 19 15:35:12 2022) Its where you try to update one row more than once i.e., ropa_purchase as rp has two fields, purchase_id and fp_date so a row might be purchase_id='1001' and fp_date='04/01/2022' purchase_fpdate as pf is where the updates will be coming from if rp.purchase_id = pf.purchase_id so it may have rows that have purchase_id='1001' and pfr_date='04/02/2022' purchase_id='1001' and pfr_date='04/03/2022' purchase_id='1001' and pfr_date='04/04/2022' It seems that during a deferred update statement, ambiguous replace errors will occur if the same row is updated more than once. This is the correct action as specified in the "INGRES/SQL reference manual". Queries that hadn't shown the error "E_US125D Ambiguous Replace error" before and now give this error were always incorrect. This error is now correctly trapped. The usual cause of this error are tables that allow duplicate rows being use in the query. You should check on this error first and consistency of the tables ropa_purchase and ropa_payment; and the SQL statements.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/17/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF requested another Data Encryption and Data Masking Proof of Concept for their future projects.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/10/2022 13:51:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of June 10, 2022: June 1, 2022 10:15-11:15AM, 2:15-4:15PM June 2, 2022 10:00-11:00AM, 2:00-4:00PM June 3, 2022 10:15-11:15AM, 1:30-2:30PM June 6, 2022 2:00-3:00PM June 7 – 8, 2022 – 1hr * June 9, 2022 10:00-11:00AM, 1:30-4:00PM June 10, 2022 9:30 – 10:AM - DAR Data at Rest Encryption of tables pf_employer_master and pf_member master with HEAP structure - Indexing, optimizing and usermod for tables: - pf_member_master_enc_aes_niv - pf_employer_master_enc_aes_niv - pf_ledger_21_25_enc_aes_niv - pf_tav_balance_enc_aes_niv - pf_membership_info_enc_aes_niv - Benchmarking of SQL tables with AES_ENCRYPT encryption

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/20/2022 11:20:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sent an email last Wednesday, 15-June 2022 for the request of presentation of the result of testing. No feedback as of Monday, 20-June 2022.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/28/2022 11:43:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Documentation and presentation preparation

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/06/2022 14:15:55

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Data Encryption Presentation | 06-July 2022 | 9AM-11AM PHT Zoom recording link: https://www.dropbox.com/s/6k7pz5e1fy5xh0l/2022-07-06%2008.40.27%20ingres%20data%20encryption.zip?dl=0 Attendees: HDMF: Teresa M. Manabat - VP for Computer Operations and Support Services Group, Florencio B. Cortez - VP for Information Systems Group, Arlene M. Chu - Manager for Electronic Data Processing Department (ITID), Maricris Pajo - CEO of VP for COSSG, Alvin Tabarrejo, Sherwin Astorga, Marinella Alindog, Elexie Laberinto, Actian and DSource: Ken Lindner - Director of Professional Services APAC, Juan Miguel Cruz - Director for Sales and Marketing, Rowell Magno - Managing Supervisor, Manilyn Palec - Head for Technical and Support Group, Junel Garcia, Mylene Gabay, Kit Vizcarra, Additional Testing: 1. Include squeeze/trim during encryption table conversion; 2. Where condition with values; a. like, b. equal, Approach: AES_DECRYPT_IV(col1,'Passphrase') = or like % Deliverables: 1. Minutes of Meeting 2. POC Documentation with the following revisions: a. Include results of additional testing, b. Testing/POC Environment and Hardware specifications, c. "Disk sizing formula" on how to estimate size for identified tables and columns to be partitioned - c/o Ken, d. Questionnaire / Survey for Data Encryption Implementation (if available) - c/o Ken, e. Recommended "Pass Phrase" location.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/08/2022 14:37:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Minutes of Meeting (MoM) can be downloaded here https://www.dropbox.com/s/3opmw9b71ws9tk1/MoM%206-Jul%202022%20Data%20Encryption%20-%20HDMF.pdf?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/19/2022 13:33:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of July 19, 2022: 3 July 7, 2022 2:30-3:30PM (2hrs CQD & MGP) July 8, 2022 10:30 - 11:00AM July 19, 2022 10:30 - 11:30AM -Run initial benchmark of SQL #2 -Conversion of pf_member_master_aes2 with encrypted First, Middle and Last Name

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/22/2022 11:28:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additonal ManHrs as of July 22, 2022: 4 July 21, 2022: 10:15-11:15AM, 2:30-4:00PM (CQD&MGP) July 22, 2022: 10:05-11:05AM - Run additional SQLs (decrypted/true value) approach - On going conversion of pf_member_master_enc with AES_ENCRYPT_IV() encryption. Last, first and middle name of each record was encrypted for SEARCH testing

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/22/2022 14:04:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    First release of Data Encryption Proof of Concept documentation can be downloaded on this link: https://www.dropbox.com/sh/1aoksoyegrssd07/AABPX8kfr5Bkw7oSA7XhBvZfa?dl=0 Ken Linder’s Encryption Calculator (to compute column width) can also be downloaded on the link above. Please take note that there is still on-going conversion of pf_member_master_enc where we encrypted first, last and middle name with AES_ENCRYPT_IV() for future SEARCH testing using WHERE and LIKE clauses with decrypted/true value of data.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/29/2022 14:20:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additonal ManHrs as of July 29, 2022: 2 July 25, 2022: 02:15-03:15PM July 26, 2022: 15min July 27, 2022: 15min July 28, 2022: 15min July 29, 2022: 15min - Create indexes for table pf_member_master_enc_aes2 - Run usermod and optimizedb on pf_member_master_enc_aes2 - Run additional SQL against pf_member_master_enc_aes2

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/29/2022 14:35:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Version 3 release of the documentation can be downloaded on this link: https://www.dropbox.com/s/136d61xnj3vak74/HDMF%20-%20Data%20Encryption%20and%20Data%20Masking%202022%20v3.pdf?dl=0 Version 2: July 22, 2022 -Complete Table Conversion -Complete Table Disk Size -Complete SQL Benchmark with encrypted data approach -Partial SQL Benchmark with decrypted data approach Version 3: July 29, 2022 -Completed all SQL Benchmark

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/21/2022 10:43:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    ManHrs as of March 21, 2022: 1hr March 18, 2022 02:00PM - 03:00PM Data gathering of table structures and copy.in of pfmdb_encrypted DB

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/22/2022 15:13:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Presented the Data Encryption Proof of Concept results to HDMF

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/25/2022 15:09:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of March 25, 2022 :5 March 18, 2022 01:30PM - 03:00PM March 21, 2022 03:00PM - 04:30PM March 23, 2022 02:00PM - 03:00PM March 24, 2022 10:00AM - 11:30AM March 25, 2022 10:00AM - 11:00AM, 02:00PM - 02:30PM - Script Editing - Encrypted table pfmdb_employer_master_enc to both Transparent (pfmdb_employer_master_enc_dar) and Function-Based (pfmdb_employer_master_enc_aes) - Encrytted table pfmdb_member_master_enc to Transparent )pf_member_master_enc_dar - Get the physical table files and computed note the table sizes - Function-based encryption for table pf_member_master_enc_aes is still running as of the momment

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/01/2022 09:19:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of March 31, 2022 : 10 March 28, 2022 10:00 - 11:00 AM, 02:00 - 04:00 PM Chris Delgado - 02:00 - 03:00 March 29, 2022 10:00 - 11:00 AM, 01:30 - 02:30 P< March 30, 2022 02:00 - 04:00 PM March 31, 2022 10:00 - 11:00 AM, 01:30 - 02:30 PM - Finished loading pf_member_master_enc_aes - Tested encypting key columns, modifying btree tables with help of Chris Delgado - Encrypted table pf_member_tav_balance_enc to Transparent (pf_member_tav_balance_enc_dar) - Get the physical table files and computed note the table sizes - Function-based encryption for table pf_member_tav_balance_enc_aes is still running as of the moment

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/07/2022 12:28:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of April 7, 2022: 9 April 1, 2022 10:00 – 11:00 AM April 4, 2022 10:00 – 11:30 AM, 02:30 – 04:00 PM April 5, 2002 10:30 – 11:30 AM, 01:30 – 04:00 PM April 6, 2022 10:00 – 11:00 AM, 02:00 – 03:00 PM April 7, 2022 10:00 – 11: 30 AM - Finished loading pf_member_tav_balance_enc_aes - Run some SQL commands for benchmarking - Optimizedb pfmdb_encrypted - Usermod pfmdb_encrypted - Checkpoint pfmdb_encrypted - Finished loading pf_membership_info_enc_dar - Run some SQLs decrypting AES encrypted tables - Function-based encryption for table pf_ledger_21_25_enbc_aes is still running as of the moment

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/18/2022 13:45:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of April 13, 2022: 3 April 12, 2022 10:00AM - 11:00AM, 2:00 - 3:00PM April 13, 2022 1:30 - 2:30 PM - Loading of pf_membership_info_enc_aes finished April 14, 2022 - Preparing script for pf_ledger_21_25_enc_dar to be load on April 16 or 17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/28/2022 15:09:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of April 28, 2022: 9 April 18, 2022 10:00AM - 11:00AM, 2:00 - 3:00PM April 20, 2022 1:30PM - 2:30 PM April 21, 2022 10:30AM - 11:30 AM April 22, 2022 2:00PM - 3:00 PM April 26, 2022 2:00PM – 3:30PM April 27, 2022 10:30AM – 11:30 AM, 1:30 – 3:00 PM April 28, 2022 1:30PM -3:00PM - Index creation for the encrypted tables - Optimize pfmdb_encyrpted database - Run usermod on all the tables (including baste tables) - Record table physical sizes

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 12:41:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of May 11, 2022: 9 May 5, 2022 2:00 - 3:00PM May 10, 2022 10:00 - 11:00AM May 11, 2022 1:00 - 2:0PM Script editing and benchmarking.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/27/2022 15:06:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Additional ManHrs as of May 27, 2022: 8 May 16, 2022 2:00–3:00PM May 23, 2022 10:00-11:00AM, 2:00 - 3:00PM May 25, 2022 2:00-3:00PM May 26, 2022 9:30-11:00AM, 2:30-4:00PM May 27, 2022 9:30-10:00AM, 1:30-2:30 PM - Converted pf_member_master_enc_aes_niv, pf_employer_master_enc_aes_niv and pf_membership_info_enc_aes_niv using AES_ENCRYPT - Run some testing on AES_ENCRYPT encrypted data (pf_member_master_enc_aes_niv, pf_employer_master_enc_aes_niv) - Index creation of pf_employer_master_enc_aes_niv - Run optimizeddb and usermod pf_employer_master_enc_aes_niv - Index creation for pf_member_master_enc_aes_niv - Conversion of pf_ledger_21_25_enc_aes_niv using AES_ENCRYPT on going - Conversion of pf_ledger_21_25_enc_aes_niv using AES_ENCRYPT on going

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/17/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Implementation Enterprise Monitoring Appliance (EMA) of HDMF's various database systems.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/21/2022 12:10:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    First batch of servers that were added. 1. ingdb1a 2. onlinesvr 3. ingdb1b but with error Remote command execution failed: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). 4. NEWDCDDB01 but with error Remote command execution failed: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/21/2022 12:16:16

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Troubleshooting of the error: Remote command execution failed: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). SSH Failed Permission Denied on linux system. Findings: Other server does not have a standard home location for ingres user i.e., /home/ingres instead ingres home directory is in /II_SYSTEM/ingres which should be the ingres installation directory and not the user ingres directory. Action: 1. Removed all servers that shows errors -- ingdb1b and NEWDCDDB01 servers. Second batch of server that was added. 3. LEGACYSVR

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/21/2022 16:32:05

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Removed the authorized_keys from the user directory/.ssh, pushed the ssh from docker to target database server again and it worked. Third batch of servers that were added: 1. ingdb1b 2. NEWDCDDB01 3. IISP_TELLERING 4. NEWCMSSVR 5. NEWDCDDB03 6. bidb3 7. iispropa Last problematic server: 1. NEWHDMFSERVER

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:35:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sent a request to provide the following files from the two (2) working DB servers: NEWCMSSVR NEWDCDDB01 and from the one (1) problematic server NEWHDMFSERVER 1. /etc/ssh/sshd_config 2. ls -ltr /II_SYSTEM/ingres/ 3. ls -ltr /II_SYSTEM/ingres/.ssh 4. hostnamectl 5. cat /etc/redhat-release

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:40:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Find out that the /etc/ssh/sshd_config from NEWDCDDB01 and NEWCMSSVR DB servers are both identical, whereas the NEWHDMFSERVER's /etc/ssh/sshd_config file is different. sshd_config,v 1.80 2008/07/02 02:24:18 ssh_config,v 1.25 2009/02/17 01:28:32 and there's lacking line from the sshd_config of NEWHDMFSERVER

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/24/2022 13:58:13

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Troubleshoot the /etc/ssh/sshd_config files and compared it with other server's sshd_config, but still no luck in fixing the ssh error. Client schedule a server restart on Sunday 27-March 2022.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2022 15:21:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After a scheduled restart of the server, NEWHDMFSERVER was successfully included in the EMA Server. We will now close this Service Request.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/07/2022 14:20:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Troubleshooting of the error: Obviously after a server change, RSA/SSH key will be different from the old server. Removed the old server name from the EMA server. /home/emauser/.ssh/known_hosts /home/ingres/.ssh/known_hosts /home/ingres/ema/ema/nagios/etc/ssh/known_hosts /root/.ssh/known_hosts /var/lib/docker/overlay/bef351a0712328c65702314fa6c6ba5a7b47a6043a1651ad8d76914bd415c4b2/upper/root/.ssh /known_hosts Push the RSA/SSH Key again from docker to EMA server -- SUCCESS!

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Mr Benjielin Dalicun raised a concern regarding an ingres driver for Microsoft Visual Studio 2019 .Net Core. They are getting the error when using the provided Actian DotNetProvider-2.1.84.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 11:40:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI have posted an inquiry to Actian Portal about the compatibility of Actian DotNetDataProvider-2.1.84 to Visual Studio 2019 .Net Core Although upon doing research, this error seems to be a Microsoft .NET Framework error message. This error message may display on computers where Microsoft .NET Framework 2.0, Service Pack 2 is installed. A Microsoft .NET Framework file System.EnterpriseServices.dll assembly is missing or corrupted in the Global Assembly Cache (GAC) folder (\Windows\Assembly). Or, the file in the Global Assembly Cache (GAC) does not match with the Microsoft.NET 2.0 Framework version. The Following steps are advised to try to fix the problem: Run Windows Update on your computer, ensure that you have not rejected and hidden any Windows Updates. Complete the update process for all Critical and Recommended updates. This links to Microsoft website may help: https://support.microsoft.com/kb/12373 Download and reinstall Microsoft .Net Framework 2.0 and higher from Microsoft Website. https://www.microsoft.com/en-us/download/details.aspx?id=1639 If you are using Windows 7 or Windows 8: Repair the .NET 2.0 Framework installation. Click Start - All Programs - Accessories - Command prompt Right click on command prompt and select 'Run as Administrator' In the Command Prompt, type: "sfc /scannow" (with the quote marks) System File Checker - SFC - will scan your system and (hopefully) fix some of your system files. Restart your computer Details on how to repair an existing installation of the.NET Framework are provided in Microsoft web site: https://support.microsoft.com/kb/306160 Microsoft provides a .NET Framework Repair Tool which can be downloaded from: https://www.microsoft.com/en-gb/download/details.aspx?id=30135

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2022 17:03:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A response came from Actian Support Portal: it is advaised to download Actian .NET Driver 3.0.1 (Actian.Client.3.0.1.nupkg). Reference links are also provided: https://docs.microsoft.com/en-us/visualstudio/releases/2019/compatibility https://esd.actian.com/product/drivers/.Net_Data_Provider/Windows_64-Bit/.Net_Data_Provider_GA/Actian.Client.3.0.1.nupkg/readme

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/31/2022 11:27:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This error is a common Microsoft Visual Studio Code error. Some fixes posted online might be of help. https://appuals.com/object-reference-not-set-to-an-instance-of-an-object-microsoft-visual-studio/?fbclid=IwAR3B_HtgEysCJwZpJ3FlHxA9wv0TXUBgmNQI8HougId6nRhTJ1l7JLEt7N8

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/31/2022 11:28:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI visited Sir Benjie Dalicun to investigate further the cause of the error. Sir Benjie were able to make it work by extracting the nupkg file and manually calling the extracted DLL file on the source code. Apparently, the nupkg file cannot be detected by Microsoft Visual Studio 2019 and giving an error "Object reference not set to an instance of an object" This is a common error for Microsoft Visual Studio Code and DSI found some fixes online that might be of help. https://docs.microsoft.com/en-us/answers/questions/126187/microsoft-visual-studio-object-reference-not-set-t.html https://appuals.com/object-reference-not-set-to-an-instance-of-an-object-microsoft-visual-studio/?fbclid=IwAR3B_HtgEysCJwZpJ3FlHxA9wv0TXUBgmNQI8HougId6nRhTJ1l7JLEt7N8

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/12/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    2.0 April 1, 2022 - New Bug Fixes for Patch 15744 Bug 135405 (IIMGMTSVR) Management server is crashing regularly on Avalanche. Failure seems to be in the calls to ERlookup from multiple threads at the same time. Bug 138120 II-7603 (GENERIC) Prepared query information(PQTXT line) missing in trace files with server_trace,SC930 for FETCH and CLOSE cursor statements using prepared query. Bug 138593 II-8017 (GENERIC) verifydb modifies extended table even in REPORT mode. Also, etabs part was not getting verified for extended tables. Bug 138681 II-8106 (GENERIC) Details(database, table owner, table name etc.,) missing in BLOB related error messages E_DM9B0B_DMPE_LENGTH_MISMATCH,E_AD7004_BAD_BLOB. The new follow up error message E_AD7FFF_ADP_INFO_BAD_BLOB prints the missing details. Bug 139477 II-9017 (GENERIC) E_VW1027 error with X100 UNION query involving REUSE Bug 139490 II-9032 (GENERIC) verifydb adds journalling entries even in REPORT mode. Bug 139493 II-9036 (GENERIC) With configuration parameter 'opf_literal_transitive' being set to ON, a query may take longer time to run. Bug 139589 II-9128 (GENERIC) A select query could fail with E_OP0082 error. Error log shows an E_OP0901_UNKNOWN_EXCEPTION happened, and the function name on the top of the stack printed in errlog.log is opn_eqtamp(). Bug 139667 II-9212 (GENERIC) A query may fail with E_DM0138 error. 3.0 March 21, 2022 - New Bug Fixes for Patch 15738 Bug 133296 II-2615 (GENERIC) 'usermod -online' (which does a modify with concurrent_updates) sets the allocation_size for the modified tables to 0. Bug 136686 II-6166 (ENHANCEMENT, GENERIC) 'set date format' is not applied to values retrieved from an x100 table. After the application of this patch "set date format" will also apply to date retrieved from x100 tables. Bug 137326 II-6870 (GENERIC) Differing query results with 'not exists' if query flattening is on or off with a correlated anti-join subselect

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/12/2022 13:48:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    I would like to inform you that latest patch 15744 is already available for your testing. You can download it here https://www.dropbox.com/s/hlhx33g18r9attm/actianx-11.1.0-100-linux-x86_64-p15744.tar.Z?dl=0 Though upon checking earlier it seems that production servers are still in patch 15683. The last January 2022 patch that we gave you 15726 has not yet deployed. Following this January 2022 we have February 15730 and March 15738 releases. I would suggest for you to test immediately and once the testing passed, upgrade the production environments.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/26/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As part of the OpenROAD Version Migration effort. A request was sent to migrate the application LOANS ORIGINATION. A list of requirements are sent to initiate the process. EXP file export of the application to be migrated with all the included applications. Database Environment to test connect the application. Test Database to load the OR Codes (preferably ActianSVR) Test Login Credential to test the functionality of the AUT.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/16/2022 15:11:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Installation of OpenROAD 11.2 with license was succesfully installed on requested machine for testing of migrated HLOS. Image shortcuts are also created for HLOS 11.2 image and and another instance that run-though Property Changer. Site-visit: Installation and configuration 2 man-hours

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/26/2022 17:14:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This case will be closed since the testing part was transferred to HDMF. It may also take some time to complete testing since Loans Origination is a large application. Any findings and error that might occur will still be catered and forwarded to a new case. Attached here is the documentation for the Migration Activity for Loans Origination from OpenROAD version 3.5 to 11.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/26/2022 17:24:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is Migration guide for OpenROAD 3.5 to 11.2. Information from this document was derived from the documentation from Actian Corporation but filtered to cater the steps specifically needed for this activity. This document also covers the migration activity for Funding Commitment Line and Loans Origination Application.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/02/2022 09:37:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The following files was sent by Sir Chris Manalo. dbaccess.app gl_shlf.app maintenance.app orig_class.app origination_462t.app origreports.app printapi2.app proj_util.app as part of the Loans Origination Migration

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/05/2022 15:45:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    An initial loading of the exported applications from 3.5 to 5.1 was started. Found out that the following included applications are still missing. origdbsess conversionretentioncomputatios Origcommon A request was sent for the files. Site-visit: Loading Applications 1 man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/06/2022 15:18:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Missing Included applications are provided and loaded to OpenROAD 5.1. Dsource tried to use the same login credential from the Migration Test and it also works. Running the application with the test login credential shows positive output, but still to be tested for it's Functionality. All migrated 5.1 applications was then exported to EXP files. Next step is to migrate it to OpenROAD version 11.2. Site-visit: Loading Applications 1 man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/10/2022 17:05:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Initial migration from exported OpenROAD version 5.1 to OpenROAD 11.2. At first shows some code error pertaining to Procedure declared as non-returning value, but upon checking it does and was working with the 5.1 version. It is then checked that upon importing/migrating applications, a restart or a refresh is necessary since there are a lot of included applcations intertwined with each other. Further testing is required. Site-visit: Loading Applications 2 man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/25/2022 16:27:56

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Was not able to perform basic test with 11.2 Migrated application since Dsource found out that the testing Database they are using have been removed from the Test Server to clear out some space for other testing activities. In the meantime, Dsource managed to create migration from 5.1 to 6.2 for reference. Site Visit: Migration - 1 man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/02/2022 15:53:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The Databse for the Application Under Test was restored on the test server. A new set of Login Credentials was requested. Site-visit: reconfiuration of the application to the database 1 Man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/07/2022 16:55:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Test Log-in credentials was checked and working though an error message was detected that wasn't showing before: "Your version is outdated, Current image version is Version 4.6.2u. Please coordinate with your System Administrator to get the latest version." This might be caused by a new version of the application has been rolled-out or this has something to do with the Database reload that happened. This needs to be fixed for the testing to move forward. Site-visit: Login-credential testing and reconfiguration 1 man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/15/2022 10:16:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The application message showing that the version was outdated was removed by modifying the database entry of the latest version on table orig_version. HDMF requested to install a 11.2 OpenROAD on one of their workstation to test the application migrated to 11.2 Site-visit: reconfiguration 1 man-hour

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/10/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF called to report a case with their HLMS production server that has stopped accepting user connection due to deadlocks. Upon investigation, I found few causes of the said problem. 1. E_OP04C0_NEWENUMFAILURE which may be the cause of deadlocks because the query execution plan fails. We will have to check if this is a bug. 2. Numerous E_DM9045_TABLE_DEADLOCK on the system. 3. Still running an old version of patch -- 15683. We already have 15744 for April 2022 patch update.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/10/2022 16:46:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_DM9045_TABLE_DEADLOCK Deadlock encountered locking table ingres.appr_master_ext in database hsgcentral with mode 3. Resource held by session [37098 7f4386fce780] Mode 2. Avoid deadlocks on system catalogs by doing frequent sysmod, increasing number of locks in locking system, and avoiding use of READLOCK=NOLOCK and DLL when other sessions are in.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 13:57:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, ulx.c:300 ]: Tue May 10 12:01:54 2022 E_QE0002_INTERNAL_ERROR A QEF internal error occurred. Associated error messages which provide more detailed information about the problem can be found in the error log (errlog.log) INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, scssvc.c:979 ]: An error occurred in the following session: INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: >>>>>Session 00007F0468AB8E00:1480677120<<<<< INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: DB Name: hsgcentral (Owned by: ingres ) INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: User: rfpineda (real: rfpineda ) INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Session started at 10-May-2022 08:13:22 as user rfpineda INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Terminal: batch INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Group Id: mcrorig

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 13:58:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Role Id: INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Application Code: 00000000 Current Facility: QEF (00000006) INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Session Unique Number: 9628674 INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Client user: rfpineda INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Client host: PAM12-11809 INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Client tty: PAM12-11809 INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Client pid: 7516 INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Client connection target: centraldb::HSGCENTRAL INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Client information: user='rfpineda',host='PAM12-11809',tty='PAM12-11809', pid=7516,conn='centraldb::HSGCENTRAL'

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 13:58:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Modes: DB: RW Sess: RW Txn: multi,rw Onerror-rollback: stmt INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Description: INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Query: Execute ChkDevsWnoGB INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: PQTXT: INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Last Query: define query ~Q is select n.guidelines as guidelines, n.shlf as shlf, n.program as program, d.name as devname, n.dev_code as dev_code, n.entrydate as entrydate, n.par as par from devswnogb n, dev_bank d where d.code=n.dev_code and guidelines= $0= ~V and shlf= $1= ~V and program= $2= ~V and n.dev_code= $3= ~V order by guidelines, shlf, program, devname INGDB1B ::[47292 , 36777 , 0000000000000000:00007f0468ab8e00, sc0e.c:717 ]: Last recorded query start time: 10-May-2022 12:01:54 ingdb1b ::[47292 , 68ab8e00]: Tue May 10 12:01:54 2022 Segmentation Violation (SIGSEGV) @PC 00000000007fa77c RSP 00007f055840c330 RBP 00007f055840c390 RSI 00007f0774336068 RDI 00007f07743360b0 RAX 3030393933313133 RBX 00007f055840c440 RCX 000000364f0094a8 RDX 0000000000000000

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 13:59:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The E_OP04C0 error is trying to take advantage if Greedy Optimization method fails. The query will continue but use alternate query optimization (non-greedy). You can hide this error message but I am recommending not to. CBF > DBMS Server > opf_new_enum=OFF > ingstop,ingstart

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 14:05:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. E_OP04C0_NEWENUMFAILURE which may be the cause of deadlocks because the query execution plan fails. We will have to check if this is a bug. Answer #1: The E_OP04C0 error is trying to take advantage if Greedy Optimization method fails. This is not the actual cause of the error but this is the notification error that the query execution is already failing. 2. Numerous E_DM9045_TABLE_DEADLOCK on the system. 3. E_QE0002_INTERNAL_ERROR. A QEF inter error occured. Answer #2 and #3: Table deadlocks and efficiency of the query execution relies on proper housekeeping. Always run optimizedb -zk -zfq, usermod at least every week. Last run 14-Apr 2022. The server is already running 287 days, please schedule a server reboot once in a while. 4. E_US0010. Database does not exist: 'mrddocs'. Answer #4. Multiple users are trying to access this mrddocs table but does not exist. Check on this as well. 5. Still running an old version of patch -- 15683. We already have 15744 for April 2022 patch update. Answer #5: Patch 15744 was superceded by Patch 15753 released May 9, 2022. I would suggest to test this patch and apply to production environment once tested ok.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    I would like to inform you that latest patch 15753 is already available for your testing. You can download it here https://www.dropbox.com/s/hlhx33g18r9attm/actianx-11.1.0-100-linux-x86_64-p15744.tar.Z?dl=0 Though upon checking earlier it seems that production servers are still in patch 15683. This patch supercedes the previous releases as follows: 15726 January 2022 15730 February 2022 15738 March 2022 15744 April 2022 I suggest for you to test immediately and once the testing passed, upgrade the production environments.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/12/2022 15:44:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    2.0 May 9, 2022 - New Bug Fixes for Patch 15753 Bug 135096 II-4342 (GENERIC) Cross table update query between table and view fails with error: E_US125D Ambiguous replace: you have specified several replacements for the same row. Bug 136054 II-5554 (GENERIC) infodb shows "X100 supported : Yes" in user databases on platforms with no x100 support (Solaris, AIX, HP-UX, VMS) Bug 136714 II-6190 (GENERIC) The resulting datatype of date('string') within the procedure changes after clearing the cache using tracepoint qs506. the procedure recompile and uses current date_alias. It is not using the date_alias when the procedure created for the first time Bug 139324 II-8671 (VMS, CLUSTER) Following a node failure, lock requests on remaining nodes are stalled and never granted. Bug 139353 II-8850 (VMS) E_SC033D_TZNAME_INVALID is not displaying the timezone name. Bug 139406 II-8926 (VMS) The DBMS server may hang. PSTACK trace show that the ast_thread is stalled waiting for IO AST to complete. Bug 139509 II-9053 (ENHANCEMENT) Add support for the ipv4, ipv6 and uuid datatype to QBF utilities. A default display format for ipv4, ipv6, and uuid is c15, c39, and c36 respectively. A maximum of 15, 39, 36 character is required to apply inserts and/or updates as valid values in ipv4, ipv6, and uuid. Bug 139625 II-9170 (GENERIC) A query that does a cross table update with a view runs slow due to the view is being materialized.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/25/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A gentle reminder that upon our annual audit of Ingres / OpenROAD servers, we find out that there are still servers that are running on lower product and patch version. Such as the following: 1. GEN_ACCT, LEGACYSVR, onlinesvr, orataf2 - Ingres 10.2 patch 15049 2. HO6 - Actian 11.1 patch 15580 3. ingdb2a, LEGACYPDCSVR, RHL6_MID - Actian 11.1 patch 15619 4. NEWISDDSVR - Actian 11.1 patch 15644 5. bidb3, hloutsourcing, hsgdrdb, IISP_TELLERING, iispropa, ingdb1a, ingdb1b, ingdb2b, ingdrdb, inghsg1, NEWCMSSVR, NEWDCDDB01, NEWDCDDB03, NEWHDMFSVR - Actian 11.1 patch 15683 6. ActianSvr, dcdsvr, newisqadsvr - Actian 11.1 patch 15726 7. isddsvr - Actian 11.1 patch 15744 For 2022, please be advised that there will no longer have license keys for 10.2 versions. We highly recommend to upgrade the remaining four (4) servers on or before 15-July 2022. For servers running Actian 11.1 with patch lower than patch release May 2022 -- 15753, we suggest to upgrade it to the latest patch to avoid any already-fixed bug/s. In addition, Actian 11.1 will soon end its Enterprise Support and patch. We highly recommend to test Actian 11.2 as soon as possible.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/06/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As part of our services to you, we would also like to implement the Load and Run on you your OpenROAD 6.2 Applications. For us to properly implement the Proof of Concept, we will be needing the below installers to be installed on one of your servers. We would like to request for the following items: 1. Server where the Load and Run Server will be installed. Windows OS. 2. Login credentials of the Load and Run Server e.g., Username and Password, IP Address. 3. OpenROAD Application (.img) that will be deployed using LoadAndRun Server. 4. Client workstation that can access #3 OpenROAD Application to test. In addition, we would like to know when is the best time to start this service. Applications needed for setting up LoadNRun 6.2 on windows: 1. Java JDK and JRE 2. OR Server 6.2 3. LoadNRun 6.2 4. Apache Tomcat v8.5 installer 5. Application to be deployed Numbers 1, 3, & 4 installers are provided in the link below.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/30/2022 09:26:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource will now close case number 2022-00015: Setting Up LoadNrun 6.2. Included in the POC documentation are this case's activities, results, and findings. Below is the link for the soft copy of the LNR POC documentation. https://www.dropbox.com/s/vpeb2pdzhkxut1s/HDMF%20-%20LNR%20PoC%20Documentation%20V1.pdf?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/16/2022 11:20:15

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    June 15, 2022: - DSI setup and configure the workstation to be used for loadnrun.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/21/2022 10:56:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    June 20, 2022: - Testing Loadnrun 6.2 build: 15216 (latest LNR 6.2 version) with OR server 6.2 build: 15074 (HDMF OR 6.2 version) provided by Actian. Result: Failed - OR 6.2 build: 15074 does not contain the following files: 1. Loadnrun image (must have) 2. Loadnrun demos 3. Gatekeeper 3 - DSI used the loadnrun image from the Loadnrun 6.2 build: 15216 and register it to OR Server. Connecting to loadnrun via VOSA results to an error code: 0x800706BE. - loadnrun.log contains the following error message: OpenROAD OR 6.2.0 (int.w32/00) BLD: 6.2.0/15074 p15119 [20-jun-2022 13:52:27] ghostexec for 'server': Loadnrun Server Started E_WT0067 The interpreter found an invalid intermediate language operation (141). Contact technical support. Try recompiling the program.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/21/2022 16:48:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    June 21, 2022: Loadnrun Setup and Configuration - DSI installed and configured the following: 1. Java JDK and JRE 2. OR 6.2 bld:15216 complete installation 3. Apache Tomcat v. 8.5 4. Loadnrun 6.2 bld:15216 - DSI deployed two thick applications (FCA and Loans Origination) using the LNR launcher. Result: Successful - Note: Setup LNR netutil on the client-side for applications with database connections to work.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/07/2022 15:40:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    July 6, 2022: Research and configuration for LNR settings. - You could set ASO & SPO to either CONNECT or PACKET_PRIVACY. - It is recommended to use Tomcat 8.5 for OR Server 6.2 - Run this command to OR Administrative window to check if tomcat is running. sc qc tomcat8 - To call new applications to the from the sample Launcher, edit its install4gl.txt file. - Verify that II_W4GLAPPS_DIR has been set at the System level - Sample demos and launcher for LNR set up is located at %II_SYSTEM%\eclient\62demox64. But it should be placed as to where II_LOADNRUN62X64_W4GLAPPS_DIR points.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/07/2022 16:38:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    July 7, 20222: - Deploying and running both Thin and Think applications on a client machine. - Demonstration on how to setup and configure new images to LoadNRun on both Server and Client side. - We also verified that some nuances may still occur when running an old build application on a new LoadNRun installation. These concerns were raised during the demonstration: • Network performance if multiple users simultaneously download images. • Transferring folder over LoadNRun • Enabling decompression of compressed files through OpenROAD (to limit transfer load) • Checking running window processes to disable multiple instance of an Application • Triggering LoadNRun download if the application image is non-existence.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/11/2022 15:54:56

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    July 8, 2022: Additional LoadNrun testing - Deploying zipped file including the image are automatically unzipped on the client side. - Previously we noticed that deploying a Folder thru loadnrun turns it into a file once it is downloaded by the client. This can be fixed by Zipping the folder. - Loadnrun 11.2 downloads the file faster than loadnrun 6.2. - LNR has a 1200 seconds limit on the download time.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/11/2022 17:38:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    July 9, 2022: Additional LoadNRun Testing Dsource have created codes to automatically decompress zip files through OpenROAD code. This code will render moot since Dsource discovered that a zipped file transfered through LoadNRun will automatically decompress it once it reach the client machine. Also included to this script is a code to check if a specific file is non-existense on a location, that can be use to trigger a LoadNRun Download. (Please refer to the Attached File). Another Code is provided to check is an instance of an application is already running on the machine, this will determine if another instance of the image will be allowed to run. Please see attached file.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/20/2022 09:11:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    July 11, 2022: More information from Actian Engineering Team: The main factors that could influence the download performance during Loadnrun are • network speed • size of downloaded files (images, config files, etc.) • contention when several downloads are due to be executed at the same time A contention could happen if multiple users perform a download at the same time as: • The Loadnrun server is run as OpenROAD server application (oraso process on the server). • Only one remote procedure call is served at a time for each oraso process -downloading via Loadnrun is using remote procedure calls • The default configuration for the Loadnrun server uses one slave process (means one oraso process), • therefore it would only allow to process one download at a time (all others are queued, so they will wait). The default configuration for the “Loadnrun” server application can be amended to provide parallel downloads by the following changes in VOSA (or in the orserver.json configuration file): • Increase the number in the “Max. Slaves” option ("maxslaves" member in orserver.json) • Change the “-L” flag within the “Flags” setting ("cmdflags" member in orserver.json) to include the Slave ID: • from -Lloadnrun.log to -Lloadnrun_%s.log • This is done in order to prevent conflicts when different processes write to the same log file. This will (after an OpenROAD Server restart) allow to run multiple downloads in parallel by using multiple oraso processes (up to the configured number).

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/10/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You have requested a license file for 1x Actian X 11.1 Custom Evaluation License ; Multiple OS,cores: 64 ; Exp:2022-07-10 Download the license file here https://www.dropbox.com/s/0u9f4s4bs1cf24j/license.xml?dl=0 Please save the attached XML license file as license.xml in a directory that can be accessed by the Ingres Installations you wish to use it for. The ii.HOSTNAME.config.license_dir in the config.dat (where HOSTNAME is the hostname as it appears in other config.dat entries for the host) will need to reference this location. Please ensure the file owner and/or permissions of the license.xml file allow the Ingres installation owner to read the file. The license.xml file can be verified by copying it to any directory on the host and running: cilicchk /path/to/license_directory

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/21/2022 09:58:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You have requested a license file for 1x Ingres Multi-Core 11.1 Runtime License ; Linux X86 64-bit ,cores: 32 ; HostId:8a62c3a00069 ; Exp:2022-06-29 . Download the license file here https://www.dropbox.com/s/xur5wylpe4f0e5t/license.xml?dl=0 Please save the attached XML license file as license.xml in a directory that can be accessed by the Ingres Installations you wish to use it for. The ii.HOSTNAME.config.license_dir in the config.dat (where HOSTNAME is the hostname as it appears in other config.dat entries for the host) will need to reference this location. Please ensure the file owner and/or permissions of the license.xml file allow the Ingres installation owner to read the file. The license.xml file can be verified by copying it to any directory on the host and running: cilicchk /path/to/license_directory

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/07/2022 15:38:15

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF have encounter a Visual Bug on Tablefields when using Property Changer on an Application. The Tablefield's Header Button changes color during Mouse Hover, but won't turn back once hover was done. Done some testing and apparently, this can be fixed by: 1. checking the "ignore Fieldstyle-unique fields" option on Property Changer 2. changing the Header Button's BgDisplayPolicy to BDP_CORNERED 3. Applying the readily made Field style 2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/07/2022 15:45:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. checking the "ignore Fieldstyle-unique fields" option on Property Changer 2. changing the Header Button's BgDisplayPolicy to BDP_CORNERED 3. Applying the readily made Field style 2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/19/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Request sent to conduct training to a new set of participants.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/18/2022 12:00:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Training commenced August 8 to 9 2022 for 16 hours. The training was attended by: Prince Ryan B. Monte Jullienne L. Ramos Alexis P. Espejo Harry M. Cayanan Reymart C. Go Christian D. Cobrado Zysa V. Rosales Roy Urbina Bryan Exequiel E. Pineda Rosel M. Tagorio Kevin Jerome A. Cruz Kim Jonnathan R. Parianes Lloyd B. Tobias Rheyarie Ross G. Espinol Crisanta H. Rance

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/19/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Request sent to conduct training to a new set of participants.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/18/2022 12:10:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Training commenced August 10 to 12 2022 for 24 hours. The training was attended by: Prince Ryan B. Monte Jullienne L. Ramos Alexis P. Espejo Harry M. Cayanan Reymart C. Go Christian D. Cobrado Zysa V. Rosales Roy Urbina Bryan Exequiel E. Pineda Rosel M. Tagorio Kevin Jerome A. Cruz Kim Jonnathan R. Parianes Lloyd B. Tobias Rheyarie Ross G. Espinol Crisanta H. Rance

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/20/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the license keys for all your ActianX 11.1 database servers on this link: https://www.dropbox.com/s/l7v5w1mxwpqrpx0/Ingres%20license%20files%202022-2023.zip?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/21/2022 11:05:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    New .zip file https://www.dropbox.com/s/83olf5do617m32j/ActianX%20License%20Files%202022-2023.zip?dl=0 for the license keys 2022-2023 with the following inclusions: 1. onlinesvr is on ActianX 11.1 version 2. Temporary license keys until 21-Aug 2022 for old linux servers of ingdb1a (PFMDS and STLMS) and ingdb1b (HLMS) 3. Temporary license keys until 21-Aug 2022 for old windows server of gen_acctg

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/20/2022 16:51:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    For the deployment of OpenROAD Loadnrun 6.2 (OR LNR), we would like to request for the following items: 1. Server where the OR LNR and App Server will be installed. Windows OS 64-bit. 2. Login credentials of the OR LNR and App Server e.g., Username and Password, IP Address. 3. OpenROAD Application (.img) that will be deployed using LoadAndRun Server. 4. Client workstation that can access #3 OpenROAD Application to test. Below are applications needed for setting up OR LNR 6.2 on windows: 1. Java JDK and JRE 2. OpenROAD Server 6.2 build: 15216 patch:15707 3. LoadNRun 6.2 build: 15216 patch:15707 4. Apache Tomcat v8.5 installer 5. Application to be deployed (created/imaged using OR 6.2 build: 15216 patch:15707) We would like to ask your permission for installing Java JDK and JRE, and Apache Tomcat on the server machine that you'll provide. In addition, we would also like to know when is the best time to start this service.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/04/2022 12:24:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A gentle follow-up for case number 2022-00022: OPENROAD LOADNRUN 6.2 DEPLOYMENT. The following requested requirements are essential to start the service. • Requested items 1. Server where the OR LNR and App Server will be installed. Windows OS 64-bit. 2. Login credentials of the OR LNR and App Server e.g., Username and Password, IP Address. 3. OpenROAD Application (.img) that will be deployed using LoadAndRun Server. 4. Client workstation that can access #3 OpenROAD Application to test. 5. Applications to be deployed (created/imaged using OR 6.2 build: 15216 patch:15707) • Permission to install the following apps (server side) 1. Java JDK and JRE 2. Apache Tomcat v8.5

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/22/2022 16:15:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This case is for prioritization.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/21/2022 00:00:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the latest patch release for 5-July 2022. https://www.dropbox.com/s/6l1m8jvrlrqiqb8/actianx-11.1.0-100-linux-x86_64-p15773.tar.Z?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/21/2022 11:37:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bugs addressed with this patch: Bug 126709 II-203 (GENERIC) SELECT CAST(MY_SEQ.NEXTVAL AS INTEGER) fails with E_US18AF whilst SELECT INTEGER(MY_SEQ.NEXTVAL) works as expected. Bug 130442 (ATTENTION,GENERIC) COMMIT or ROLLBACK are incorrectly allowed inside a DBP procedure FOR LOOP. This causes the error E_QE001D_FAIL in the front end and the errors E_DM002B_BAD_RECORD_ID and E_QE001D_FAIL in the errlog. COMMIT and ROLLBACK should not be allowed inside FOR LOOP. Bug 135587 II-5004 (GENERIC) DBMSINFO needs to be able to return more than 64 characters for some DBMSINFO functions such as returning the DBMS log file path. The DBMSINFO return maximum size is now the larger of 64, or the maximum size needed for the dbmsinfo item. All DBMSINFO requests prior to this change return 64 characters max. New DBMSINFO requests may be sized at more than 64 characters when necessary to contain the full returned value. For compatibility, DBMSINFO('dbms_log') continues to return 64 characters max. The new DBMSINFO('full_dbms_log') returns the full path up to the internal server max of 255 characters. Bug 135696 II-5132 (GENERIC) The query: 'select CURRENT_TIMESTAMP' fails with the error_E_US09C5 when connected to a Star database. Bug 136072 II-5564 (GENERIC) AES_ENCRYPT(CONST, PASS_COLL) FROM MYTAB leads to incorrect results for every other row prcessed. Bug 136464 II-5968 (WINDOWS) Changes made in the Visual SQL preferences are not saved on exit. Bug 136806 II-6280 (WINDOWS) On Windows abf building binary fails with error LNK1104 and E_AB0020 but there is no hint about target directory has no write or read permission. Bug 137401 II-6952 (GENERIC) json_arrayagg(), json_objectagg(), json_array(), json_object() calls can give E_AD1082 errors with no useful context info when should run clean or give E_AD5708 error instead. Bug 138963 II-8457 (LINUX) CLONEDB fails with "export: Command not found." errors if a remote host login has a default shell of csh.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/21/2022 11:38:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bug 139643 II-9186 (GENERIC) Support untyped NULL values in certain scenarios. Bug 139754 II-9280 (GENERIC) Doing "alterdb -readonly" to a database which was created with "createdb ... -d ..." results in connections to that database getting: "E_DM012A The database configuration file was not found" Bug 139786 II-9318 (GENERIC) aes_encrypt_iv()/aes_encrypt()/aes_decrypt_iv()/aes_decrypt() returning NULL incase 'passphrase' is NULL Bug 139805 II-9338 (WINDOWS) Support zlib 1.2.12. Bug 139858 II-9388 (GENERIC) Wrong result from query that groups by on scalar string function. Bug 139894 II-9419 (GENERIC) Wrong result when using windows function count() in an outer join. Bug 139900 II-9427 (GENERIC) set date_alias - - value without quotes followed by ';' gives error message. Bug 139907 II-9437 (GENERIC) set date_alias - - date_alias is not taking NONE as valid value. - Same error message is displayed twice in case of invalid value. - Error message is not showing NONE as valid value Bug 139914 II-9450 (GENERIC) dbmsinfo('date_type_alias') - Does not display session specific value. Bug 139942 II-9480 (WINDOWS) iisuitz.bat -update fails with C:No CSI structure available Bug 139948 II-9490 (GENERIC) PREPARE statement fails with internal errors causing unexpected results if the placeholder is used as column expression within subquery E_SC0206, E_PS0C03, E_PS0002, E_SC0215, E_SC0220 Bug 139965 II-9520 (GENERIC) A correlated NOT EXISTS WHERE clause can produce wrong results when the correlation includes the inner side of a LEFT OUTER JOIN. Bug 140029 II-9608 (GENERIC) 'cilicchk -Q' can SIGSEGV if the license file does not contain a valid license for the host.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/21/2022 11:39:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bug 140067 II-9640 (GENERIC) Invalid/wrong date value returned for least-function on data columns, if a date column was all NULLs

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/05/2022 12:15:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the latest patch release for 2-August 2022. https://www.dropbox.com/s/m68ph9mo1gn5tx5/actianx-11.1.0-100-linux-x86_64-p15779.tar.Z?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/05/2022 12:10:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bugs addressed with this patch: Bug 130174 II-169 (GENERIC) A union query that has an order-by clause which contains a function such as rand() or lower() causes E_SC0206/E_QE009C error. Bug 132638 II-1985 (GENERIC) In a multi DBMS server environment if the recovery process dies for whatever reason one DBMS server does not shut down, spins reporting E_CL2517_CS_SMPR_DEADLOCK and E_DMA42E_LG_MUTEX and fills the errlog.log until the process is killed. Happens with 4 and more servers. Bug 135208 II-4515 (GENERIC) Incorrect SQL syntax using OVER without PARTITION BY causes E_OP0082 consistency check error. Bug 135511 II-4923 (GENERIC) Wrong flags set in iiprocedure.dbp_mask1 for procedure A when A calls procedure B and B is recreated - depending on who is executing A. Verifydb then reports S_DU16E9_UNEXPECTED_DBP_PERMS and S_DU0251_MARK_DBP_DORMANT. Bug 136823 II-6290 (GENERIC) View creation fails with E_QS000F_BAD_HANDLE when created from python and JDBC. Bug 137084 II-6596 (GENERIC) Server returns wrong result for queries with restrictions on a table's key column. Bug 139654 II-9197 (X100) A query that has a mixture of distinct and non-distinct aggregate fails with E_OP08C1 Consistency check error. Bug 139946 II-9449 (GENERIC) With config parameter 'ambig_replace_64compat' being set to ON, in a cross table update query, a view that contains ifnull() in its select list is being materialized instead of being flattened Bug 140028 II-9607 (X100) An outer join query on x100 tables returns wrong result. QEP contains an outer join hash join node, and the hash join type in such node is not HashJoin01 or HashJoinN type. Bug 140066 II-9639 (GENERIC) Updating the current row of a cursor will abort if any of the columns being updated are part of an Integrity constraint. Bug 140080 II-9651 (GENERIC,VECTORWISE) ISO Ingres sends padding characters to x100 when inserting non-ASCII strings into char(n) column

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/05/2022 12:11:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bug 140115 II-9441 (DIRECTOR) Update JAR files in view of security vulnerabilities Bug 140223 II-9826 (GENERIC) 'CREATE TABLE IF NOT EXISTS' fails with E_US13EE when a table (or other db object if applicable) exists with the same name. Bug 140261 II-9865 (GENERIC) A query that has a window function with named over clause fails with E_US2548.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2022 10:22:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    AFTER THE DISK COPY/SYNC THE ONLINE APPLICATION VIRTUAL PAG-IBIG CANNOT FULLY ACCESS THE PFMDB.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2022 10:27:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Requested additional result files of the following. 1. verifydb -mreport -sdbname -odbms 2. check if you can access the location ingres/data/default/ and do an ls -ltra

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2022 11:55:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Background: The database was being backed-up thru a process of disk copy/syncing from a working, live production database server. Hence, the state log of the database was marked consistent, see infodb.log Errors from errlog.log: 1. E_DM930C_DM0P_PAGE_CHKSUM_FAIL Page Checksum failure detected. Database pfmdb, Table iiattribute. This is because of a corrupted system catalog. 2. E_RD0060_DMT_SHOW Cannot access table information due to a non-recoverable DMT_SHOW error. This happens when the underlying physical files for the tables do not exist anymore or is corrupted. Steps taken: If the database is inconsistent due to operation, we tried to force it consistent thru the following commands: 1. sql -A10 pfmdb -- This returns E_QE007C Error trying to get a record. This happens if the said database is inconsistent but unfortunately the -A10 should force it consistent already. 2. verifydb -mrun -sdbname pfmdb -oforce_consistent. This command will flag the state of the database consistent for access but also failed. 3. sysmod pfmdb -- Failed with errors. Findings: 1. Prior to this incident, a corrupted database and system file was seen, files with priviledge, ownership and group with (?). 2. The database is corrupted and NOT inconsistent due to a corrupted system / database file. Resolution: Try to recover the database using rollforwarddb from an existing checkpoint file/s: 1. destroydb pfmdb 2. rollforwarddb pfmdb 3. sysmod

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/12/2022 10:51:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Update: 1. HDMF is having a hardtime destroying the existing database due to corrupted data files. 2. Virtual Pag-IBIG App connection will be transfered to another database server until ingdrdb server was restored. Action: 1. HDMF is manually removing all data files in the server and will perform destroydb once cleared. 2. We recommend to check disk integrity for rollforwarddb. 3. HDMF will perform rollforwarddb which usually takes around 5-6 hours. 4. DSource will close the ticket now since we have already identified the problem, we will create another case if incase HDMF needs further assistance on the restoration.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2022 10:18:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This case is related to case number 2022-00019: DSOURCE ONLINE TRAINING - "INTRODUCTION TO ACTIAN X AND INGRES SQL" - BATCH 5 During the training one of the HDMF participants asks if ingres has a GROUP_CONCAT() function just like in MySQL. GROUP_CONCAT() SYNTAX: GROUP_CONCAT(expr); SAMPLE: SELECT pub_id, GROUP_CONCAT(DISTINCT cate_id) FROM book_mast GROUP BY pub_id ORDER BY GROUP_CONCAT(DISTINCT cate_id) ASC; For more information about GROUP_CONCAT() go to this link: https://www.w3resource.com/mysql/aggregate-functions-and-grouping/aggregate-functions-and-grouping-group_concat.php

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2022 10:32:28

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    AUGUST 9, 2022: WORKAROUND FOR GROUP_CONCAT() USING OPENROAD Code: declare i = integer not null; x = integer not null; vConcat = varchar(500) not null; vText = varchar(100) not null; enddeclare { ///////workaround i = 1; SELECT DISTINCT (al_ccode) as tbl[i].txt_code from airline begin i = i + 1; end; for x = 1 to tbl.lastrow() do select concat(al_name, ' (',al_icaocode,')') as vText from airline where al_ccode = :tbl[x].txt_code begin vConcat = vConcat + ' ' + vText + ' | '; end; tbl[x].txt_con = vConcat; vconcat = ''; endfor; }

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2022 10:46:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    August 10, 2022; Resolution: LISTAGG() function is the counterpart of GROUP_CONCAT() SYNTAX: LISTAGG ([DISTINCT] value_expr [, 'delimiter']) [WITHIN GROUP (order-by-clause)] SAMPLE: SELECT al_ccode, LISTAGG(concat(al_name, ' (',al_icaocode,')'), ' | ') within group (order by al_name) AS name FROM airline group by al_ccode; commit; Note: The table used for this example is included in demodb. Actian reference #: 01368379

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/20/2022 10:58:39

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF (Sir Alvin Tabarrejo) informed DSI on August 20, 2022 that the production server went down last August 18, 2022. Client run ingstop/ingstart as their resolution. The server goes up and the operation went back to normal. Upon checking on the inglogs uploaded August 18, 2022 (inglogs_20220818_145342_pid60351), there are too many locks recorded and exceeded the quota which probably the main reason the server crashed. DSI recommends to increase per_tx_limit for the maximum number of locks per transaction and system_maxlocks for the maximum number of locks in locking system.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/25/2022 14:37:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Attached a KB related to this case. File Name: Increasing MAXLOCKS and Involved INGRES Paramaters.pdf

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/07/2022 14:11:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the latest patch release for 1-September 2022. https://www.dropbox.com/s/mjlfl2udn696l6q/actianx-11.1.0-100-linux-x86_64-p15790.tar.Z?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/07/2022 14:15:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bugs addressed with this patch: Bug 133639 II-2964 (GENERIC) The error return for SQL using an invalid paramter name when executing a TPROC causes subsequent, valid calls to the procedure to report "E_US0965 Procedure '' not found". Bug 134456 II-3744 (LINUX) Provide OCF compliant resource agent script so instance can be managed as part of a failover cluster. This will support such software as Pacemaker. Bug 134892 II-3232 (GENERIC) Cardinality estimate inaccuracies for joins can be much too low, resulting in poor query plans and/or poor performance. Bug 139807 II-9340 (GENERIC) DBMS server prints only addresses of function stack not the corresponding names in the log file when a crash occurs. Bug 139960 II-9517 (GENERIC) The RCP log file can fill with 'License returned' messages. Bug 140260 II-9864 (WINDOWS) Name Server becomes unresponsive when a bad client connects to the Name Server listen port (named pipe).

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/15/2022 13:16:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF got some of these error codes E_DM93AF E_DM9006 E_DM9335 E_CL0603 while trying to insert 82M records on session table.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/19/2022 13:24:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    - Inglogs was uploaded upon creation of case on portal last September 15, 2022. - Query of the session table as well as the table definition of table involved on the sessionn table was uploaded last September 16, 2022. - First follow-up was sent to Pravat today September 19, 2022. Still waiting for his response.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2022 11:21:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Alvin did some testing to monitor II_WORK 1. Open a command prompt and run: > du -sh /II_WORK/WKLOC1/ingres/work/default/data_warehouse /II_WORK/WKLOC2/ingres/work/default/data_warehouse *This is to check the base size of II_WORK 2. Open another command prompt and run: NOTE: DO NOT CLOSE THE SESSION > iisql data_warehouse * Please next comment for the query 3. Go back to another command prompt and run this again: > du -sh /II_WORK/WKLOC1/ingres/work/default/data_warehouse /II_WORK/WKLOC2/ingres/work/default/data_warehouse *This is to check the difference made on size of II_WORK Please screenshot the du -sh commands.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2022 11:24:16

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    drop table if exists session.tmp_corplan_report_ml; declare global temporary table session.tmp_corplan_report_ml ( seqno integer8 not null not default, pagibigid varchar(25) not null not default, account_no varchar(25) not null not default, lname varchar(60) not null not default, fname varchar(60) not null not default, mid varchar(60), name_ext varchar(10), birthdate ansidate not null not default, civil_status char(2), gender char(1), basic money, program_code varchar(10) not null not default, membership_category varchar(5) not null not default, employerid varchar(25) not null not default, branch_code varchar(10) not null not default, init_percov char(6) not null with default, last_percov char(6) not null with default, init_remit ansidate not null not default, last_remit ansidate not null not default, occupationcode varchar(10) not null with default, ee money not null not default, er money not null not default, div money not null not default, country varchar(100) not null with default, mobile_no varchar(30) not null with default, with_final_claim integer2 not null with default, paymentcount integer not null with default, cutdate ansidate not null not default, rundate ansidate not null not default ) with page_size = 16384 ; insert into session.tmp_corplan_report_ml select first 1000000 a.seqno, a.pagibigid, a.account_no, a.lname, a.fname, a.mid, a.name_ext, a.birthdate, a.civil_status, a.gender, a.basic, a.program_code, a.membership_category, a.employerid, a.branch_code, a.init_percov, a.last_percov, a.init_remit, a.last_remit, a.occupationcode, a.ee, a.er, a.div, a.country, a.mobile_no, a.with_final_claim, Int2(-1), AnsiDate(b.cutdate), AnsiDate('today') as rundate from cpr_memberlist a inner join report_parameters b on b.cutdate <> Date('') left join stg_corplan_report_ml c on a.pagibigid = c.pagibigid and a.account_no = c.account_no and a.program_code = c.program_code where c.pagibigid is null; modify session.tmp_corplan_report_ml to btree unique on seqno;

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2022 11:27:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per Actian, Engineering is working on bug II-10201 for this case.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2022 11:34:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per Actian: This case could be related to case 2022-00036 wherein the II_WORK was unnsupportedly set on ingprenv. Actian recommends to look for all the possible remaining references to /II_WORK/ingres* 1.Database configuration file aaaaaaaa.cnf in /II_DATABASE/ingres/data/default/data_warehouse 2. Database configuration file aaaaaaaa.cnf in /II_CKPT/ingres/dmp/default/data_warehouse # use ls -l / cksum and make sure these two are identical 3.The aaaaaaaa.ext in /II_CKPT/ingres/dmp/default/data_warehouse 4.The X100 location_map file in /II_DATABASE/ingres/data/default/data_warehouse/wal 5. Connect to iidbdb and check all system catalogs that might be related. For checking , use SELECT VARCHAR(table_name,32) FROM iitables WHERE table_name LIKE '%loc%' OR table_name LIKE '%ext%'\g and check every single one of them. To update you if you find one, you need to connect using "sql +U -u'$ingres' iidbdb". In particular, check iilocation_info, iiextend_info, iiextend, iilocations and modify/correct any reference to the old (supposedly unused) location.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2022 11:44:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF performed another testing to monitor II_WORK DSI asked HDMF to run the sql for iidbdb to verify locations: | 16|ii_work2 |/II_WORK/WKLOC2 | 16|ii_work |II_WORK |ii_work2 |N |N |N |Y |N |N |/II_WORK/WKLOC2 |ii_work |N |N |N |Y |N |N |II_WORK | | 0| 16| +--------------------------------+--------------------------------+-------------+-------------+-------------+ |location_name |database_name |status |raw_start |raw_blocks | +--------------------------------+--------------------------------+-------------+-------------+-------------+ |ii_work |b132169 | 5| 0| 0| |ii_database |b132169 | 3| 0| 0| |ii_work |stlos_prod | 5| 0| 0| |ii_database |stlos_prod | 3| 0| 0| |ii_work |snastorga | 5| 0| 0| |ii_database |sna

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2022 11:47:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per Actian, locations on iidbdb looks good and theres no need to change anything. The entries in iilocations and iilocation_info state that ii_work is using the area specified by II_WORK (the installation primary work location) which is set to /II_WORK/WKLOC1 so that is fine. Actian recommends to: 1. Run "infodb data_warehouse" and check if II_WORK locations are corrent 2. ingstop 3. Rename /II_WORK/ingres/work/default/data_warehouse to /II_WORK/ingres/work/default/dwh 4. Rename /.../dmp/default/data_warehouse/aaaaaaaa.cnf to /.../dmp/default/data_warehouse/aaaaaaaa.cnf.old 5. ingstart 6. Create a dummy table in database data_warehouse 7. Echo "create table dropme as select * from iitables\g" | sql data_warehouse This will create a new aaaaaaaa.cnf in the dmp directory If all works fine and confirmed that correct two /II_WORK/WKLOC1 and /II_WORK/WKLOC2 are shown by infodb in step1, run the original INSERT SELECT statement to create the 82 million rows table While this is running: 1. execute $II_SYSTEM/ingres/sig/inglogs/inglogs 2. cd to the inglogs directory and open pfiles_iidbms* and search for II_WORK. 3. Double check and make sure only files in /II_WORK/WKLOC1 and /II_WORK/WKLOC2 are open and there is no reference to files in /II_WORK/ingres/work/default/*.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/20/2022 15:03:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After migration to the new server, checkpoint could not perform on iidbdb database.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/20/2022 15:19:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, Kindly run the following before running ckpdb +j on iidbdb: 1. As user ingres: > copy cktmpl_wrap to $II_SYSTEM/ingres/bin > chmod 755 $II_SYSTEM/ingres/bin/cktmpl_wrap > copy cktmpl_wrap.def to $II_SYSTEM/ingres/files 2. Run: > ingsetenv II_CKTMPL_FILE $II_SYSTEM/ingres/files/cktmpl_wrap.def 3. ingstop/ingstart to take effect

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/20/2022 15:34:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    To checkpoint IIDBDBD: 1. ingstop/ingstart -dmfacp 2. alterdb -disable_journaling iidbdb 3. ckpdb -d +j iidbdb

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/21/2022 15:05:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per our site visit earlier, iidbdb is now journaled and was checkpointed last night. Closing this case now.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/21/2022 11:07:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    $ingres VS ingres • $ingres user is a special type of user ID that used internally for system catalogs (e.g., iiusers, iidatabase_info, iilocation_info) • ingres user is the owner and administrator of Ingres RDBMS, and it was set up during installation Each Ingres user has different privileges given: audit_all - the privilege to security audit all user activities. Since user ingres was the administrator, this privilege was granted to ingres user unmask – the privilege to unmask masked columns defined during CREATE TABLE audit_query_text - the privilege of user to see query text, enabled if security_audit=(query_text) was specified when creating or altering the user Other privileges can be seen on DatabaseAdmin.pdf Guide attached.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/22/2022 11:08:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per Sir Alvin, his inquiry were already answered. Closing this case now.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/27/2022 14:39:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After a patch upgrade from 15683 to 15726, 15744, 15753, 15779 and 15790 last Saturday, 24-Sep-2022, HDMF has experienced a Segmentation Violation error pertaining to a permission to set the scheduling policy and parameters specified during thread creation.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/27/2022 17:13:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Requesting for a series of inglogs in 4 hours interval starting tomorrow 28-Sep-2022 0800H.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/30/2022 15:14:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon investigation, there's an error before the Segmentation Violation (SIGSEGV) error. Tue Sep 27 09:21:15 2022 E_CL2539_THREAD_CREATE_FAIL CSMTadd_thread: The request to the operating system to create a new thread failed with error status 11. Depending on the error status code, it could happen because: a) Insufficient resources to create another thread. b) A system-imposed limit on the number of threads was encountered. c) No permission to set the scheduling policy and parameters specified during thread creation. The possible cause of this is because the soft limit was set to the default minimum of 1024. Please perform the following during weekend: 1. Re-apply patch 15790 2. Run iisetres ii.iisp_tellering.createdb.iidbdb_page_size 8192 3. Increase the OS' soft limit to 4096 4. Re-run the application that runs this SQL: select payrefno as payrefno, msb_code as msb_code, hub_code as hub_code, date_created as date_created, pay_source as pay_source, payor_id as payor_id, payor_name as payor_name, payor_address as payor_address, currency_code as currency_code, payment_mode as payment_mode, is_value_dated as is_value_dated, amount as amount, orig_refno as orig_refno, orig_refdate as orig_refdate, old_payrefno as oldpayrefno, status as status, status_date as status_date, membership_category as membership_category, user_branch_code as user_branch_code from pof_payscreenheader where payrefno= ~V

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/30/2022 15:29:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_CL1030_LK_EXPAND_LIST_FAILED. (1) ingstop (2) Start CBF (3) Scroll down to Locking system (4) Choose Configure from the menu at the bottom (5) Choose Derived from the menu at the bottom (6) Scroll down to lock_lists (7) Choose E dit from the menu at the bottom --- double the current value. (8) Scroll down to lock_limit (9) Choose Edit from the menu at the bottom --- and enter 101000, if there is a value above 1 000 000. (10) choose protect from the menu at the bottom (11) Choose E nd from the menu at the bottom (12) Choose Edit from the menu at the bottom and enter double the current value for the per_tx_limit. (13) Choose End from the menu at the bottom (14) Select Yes to save the changes (15) Quit from CBF (16) ingstart

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2022 14:00:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Client already did the following: 1. Run iisetres ii.iisp_tellering.createdb.iidbdb_page_size 8192 2. Increase the OS' soft limit to 4096 Unfortunately, they haven't had the chance to do the following due to operation: 1. Re-apply patch 15790 2. Re-run the application that runs this SQL: select payrefno as payrefno, msb_code as msb_code, hub_code as hub_code, date_created as date_created, pay_source as pay_source, payor_id as payor_id, payor_name as payor_name, payor_address as payor_address, currency_code as currency_code, payment_mode as payment_mode, is_value_dated as is_value_dated, amount as amount, orig_refno as orig_refno, orig_refdate as orig_refdate, old_payrefno as oldpayrefno, status as status, status_date as status_date, membership_category as membership_category, user_branch_code as user_branch_code from pof_payscreenheader where payrefno= ~V For follow up next week 25-Oct 2022

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/28/2022 14:07:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Enterprise Access is a middle-ware that makes other databases look like an Ingres database. In other words, it is an Ingres connectivity option that allows Ingres/OpenROAD applications to run against non-Ingres databases such as Oracle. Enterprise Access allows a single application to run against multiple databases without needing to know or use host specific syntax or data types. EDBC is a Mainframe based product similar to Enterprise Access that offers access to mainframe databases (both relational and non-relational databases). You can download documentation on this link https://www.dropbox.com/sh/exchwp3b2jxmvh7/AAB-6-DXkPOXyO56b10qBHw7a?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/07/2022 10:55:55

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Lex reported at 8AM that NEWDCDDB01 could not start.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/07/2022 11:18:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF rename /II_SYSTEM/ingres/files/audit.1 and audit.2 to /II_SYSTEM/ingres/files/audit.11 and audit.22 The DBMS Server then started. DSI requested another inglogs after ingstart for further investigation as tons of E_CL1613_PC_SP_PROC error have seen on the inglogs.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/07/2022 11:25:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Link for I_SX1056_CHANGE_AUDIT_LOG error KB: https://communities.actian.com/s/article/Ingres-fails-to-start-with-AUDIT-errors https://communities.actian.com/s/article/Managing-Security-Auditing-Files-Via-ON-SWITCH-LOG-Option

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/07/2022 17:50:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Good day! May I request for a copy of /var/log/messages to further investigate the E_CL1613_PC_SP_PROC error. Also, Actian's initial recommendation is to increase max user processes to 240000 on /etc/security/limits.conf and observe the servers behavior. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/10/2022 10:09:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Yes as per Actian last recommendation please set soft limit to 8192 and hard limit to 128336. Just add the following line on /etc/security/limits.conf: ingres nproc 8192 ingres nproc 128336 After server restart you can run ulimit -a and ulimit -aH to check.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/10/2022 10:11:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    From Actian: Security Auditing has been switchen ON on "Thu Sep 8 15:46:23 2022" (included in both inglogs you've provided'. However, on_switch_log has not been specified how to manage the two audit log files so once they are filled security auditing gets susoendet (as per your on_log_full=suspend). However, the next restart attempts writing to the log files and finds them full and refuses to start with "E_SX104C_SXAP_NEED_LOGFILES All security audit logfiles are used." and "2022 E_SX101A_SXAP_STARTUP Because of previous errors, the low level auditing system could not start up". You either need to switch OFF security auditing OR if you needed security auditing, implement a script that manages the files when switching. The best approach is described in KB doc "Managing Security Audit Files". The "E_CL1613_PC_SP_PROC PCspawn: system process table is temporarily full" is because the installation exceeds the soft "max user processes" (we are using the soft limit and don't expand). As of ulimit-a.out, the soft limit is set to 1024 and as of ulimit-aH.out the hard limit is set to 128336. The 1024 setting is ways too low. I would increase at least to 8192 if not 165384.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/12/2022 14:50:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    NEWDCDDB01 ::[II_ACP , 31312 , 0000000000000000:00007f03b9fec200, dmfx100.c:1847 ]: Wed Oct 12 09:47:39 2022 E_VW1006_GENERIC Generic internal error in X100 server NEWDCDDB01 ::[II_ACP , 31312 , 0000000000000000:00007f03b9fec200, dmfx100.c:1856 ]: Wed Oct 12 09:47:39 2022 E_DM9848_BACKUP_DB Error occurred archiving database bayadcenter_ws_db NEWDCDDB01 ::[II_ACP , 31312 , 0000000000000000:00007f03b9fec200, ]: Wed Oct 12 09:47:39 2022 E_VW1006_GENERIC Generic internal error in X100 server NEWDCDDB01 ::[II_ACP , 31312 , 0000000000000000:00007f03b9fec200, ]: Wed Oct 12 09:47:39 2022 E_DM9847_X100_BACKUP Error occurred during x100 archive processing.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/12/2022 14:57:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    With the fix for both bugs in place the x100 server is not called in any of the following cases: The database was created without x100 support at all (createdb -no_x100, you can see X100 supported: No in the infodb output) The database was created with x100 support, but x100 support was disabled later and there was no x100 table created. (The Status line in the infodb output (infodb -get_status) contains X100_DISABLED but does not contain X100_EXIST. The x100 support was re-enabled for the database after the last checkpoint, i.e. that checkpoint was taken while x100 was disabled. (In the infodb output the mode column in the Checkpoint History for Journal section for the last checkpoint contains NOX100 (infodb -get_ckp_mode). Please note that this status is added to the last and already existing checkpoint when the x100 support is re-enabled with alterdb) Please note that 2) implies that the x100 server wakes up even if the x100 support was disabled, but the X100_EXIST flag is set. This flag is set when the very first x100 table is created, but isn't unset when the last x100 table is dropped. To get the X100_EXIST flag removed run sysmod after the last x100 table was dropped.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2022 13:23:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Found some inconsistencies between journaling and main.wal upon checking the vectorwise.log. 022-10-08 08:17:06.127658 PID 10665:TID 139714790233856:SID 3:TXID 7:ERROR:BACKUP:Incremental backup is ahead of transaction log. Aborting backup. last_commit_id = 1, end_transaction_commit_id = 35 2022-10-08 08:17:06.127698 PID 10665:TID 139714790233856:SID 3:TXID 7:ERROR:BACKUP:incremental_backup_copy_LOG failed with error = -1 2022-10-08 08:17:06.127709 PID 10665:TID 139714790233856:SID 3:TXID 7:ERROR:BACKUP:Failed copying main.wal

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2022 13:26:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Disable journaling and re-enable it: 1. alterdb -disable_journaling dbname 2. ckpdb +j dbname

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/12/2022 15:12:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, vwerror.c:910 ]: Sat Oct 8 10:28:47 2022 E_VW1099_SERVER_START Cannot start X100 server. ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfx100.c:1648 ]: Sat Oct 8 10:28:47 2022 E_VW1198_JSP_INFO Database: data_warehouse ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfx100.c:1652 ]: Sat Oct 8 10:28:47 2022 E_VW1198_JSP_INFO Database: data_warehouse ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfx100.c:1656 ]: Sat Oct 8 10:28:47 2022 E_VW1199_VW_RESTORE_ERROR Error starting server for data_warehouse (255) ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfrfp.c:2140 ]: Sat Oct 8 10:28:47 2022 E_DM0100_DB_INCONSISTENT Database is inconsistent. ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfrfp.c:14628 ]: Sat Oct 8 10:28:47 2022 E_DM1371_RFP_INFO Database data_warehouse has been marked inconsistent. ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfjsf.c:3672 ]: Sat Oct 8 10:28:47 2022 I_DM1061_JSP_INFO A user has run rollforwarddb data_warehouse +c -j #x #c211 #m12. Now completed. ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, dmfrfp.c:2260 ]: Sat Oct 8 10:28:47 2022 E_DM1301_RFP_ROLL_FORWARD An error occurred that prevents further processing.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/25/2022 13:55:56

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Successfully rollforward data_warehouse #211 by running: - verifydb -mrun -sdbname data_warehouse -oforce_consistent - sql -A10 Another error occured when the client tried to rollforward #221: !ingdb1a ::[II_JSP , 10396 , 0000000000000000:00007fdb99140200, dmfrfp.c:6826 ]: Fri Oct 21 10:51:52 2022 E_DM1327_RFP_INV_CHECKPOINT Error trying to apply incomplete checkpoint. !ingdb1a ::[II_JSP , 10396 , 0000000000000000:00007fdb99140200, dmfrfp.c:6827 ]: Fri Oct 21 10:51:52 2022 E_DM133C_RFP_UNUSABLE_CKP Client destroy the database and did steps 1-7 and successfully rollforward to 221

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/25/2022 14:00:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Directories/files we know that has reference to locations: 1.Database configuration file aaaaaaaa.cnf /II_DATABASE/ingres/data/default/data_warehouse 2.Database configuration file aaaaaaaa.cnf in /II_CKPT/ingres/dmp/default/data_warehouse # use ls -l / cksum and make sure these two are identical 3.The aaaaaaaa.ext in /II_CKPT/ingres/dmp/default/data_warehouse 4.The X100 location_map file in /II_DATABASE/ingres/data/default/data_warehouse/wal Remove or modify any information you find related to II_WORK/ingres. 5.Connect to iidbdb and check all system catalogs that might be related. sql +U -u'$ingres' iidbdb SELECT VARCHAR(table_name,32) FROM iitables WHERE table_name LIKE '%loc%' OR table_name LIKE '%ext%'\g +--------------------------------+ ¦col1 ¦ +--------------------------------¦ ¦iiextended_relation ¦ ¦iilocation_info ¦ ¦iimulti_locations ¦ ¦iiextend_info ¦ ¦iiextend ¦ ¦iilocations ¦ ¦iiexternal ¦ ¦ii_locks ¦ ¦ii_dbd_locations ¦ ¦iiqrytext ¦ ¦iiget_table_locations ¦ ¦iicolumn_locations ¦ +--------------------------------+ In particular, check iilocation_info, iiextend_info, iiextend, iilocations and modify/correct any reference to the old (/II_WORK/ingres/) location.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2022 10:10:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of the rollforwarddb log file you have provided, we see that we start (obviously) with the 12 locations checkpoint files andf restore them successfully (both the Ingres and Vectorwise part): beginning restore of disk /II_CKPT/ingres/ckp/default/data_warehouse of 12 locations Fri Oct 7 21:04:23 2022 RFP: Deleting files at root location : ii_database: Fri Oct 7 21:04:23 2022 RFP: Start restore of location: ii_database from disk: path = '/II_CKPT/ingres/ckp/default/data_warehouse' file = 'c0211001.ckp' executing restore to disk /II_CKPT/ingres/ckp/default/data_warehouse of 12 locations deleting files in location /II_DATA/DBLOC1/ingres/data/default/data_warehouse Fri Oct 7 21:04:23 2022 RFP: Start restore of location: ii_dbloc1 from disk: path = '/II_CKPT/ingres/ckp/default/data_warehouse' file = 'c0211002.ckp' executing restore to disk /II_CKPT/ingres/ckp/default/data_warehouse of 12 locations deleting files in location /II_DATA/DBLOC2/ingres/data/default/data_warehouse . . . executing restore to disk /II_CKPT/ingres/ckp/default/data_warehouse of 12 locations beginning restore of disk /II_CKPT/ingres/ckp/vectorwise/data_warehouse of 12 locations deleting files in location /II_DATABASE/ingres/data/vectorwise/data_warehouse Fri Oct 7 21:04:23 2022 RFP: Start restore of location: ii_database from disk: path = '/II_CKPT/ingres/ckp/vectorwise/data_warehouse' file = 'x0211001.ckp' executing restore to disk /II_CKPT/ingres/ckp/vectorwise/data_warehouse of 12 locations deleting files in location /II_DATA/DBLOC1/ingres/data/vectorwise/data_warehouse . . . executing restore to disk /II_CKPT/ingres/ckp/vectorwise/data_warehouse of 12 locations deleting files in location /II_DATA/DBLOC11/ingres/data/vectorwise/data_warehouse Fri Oct 7 21:56:17 2022 RFP: Start restore of location: ii_dbloc11 from disk: path = '/II_CKPT/ingres/ckp/vectorwise/data_warehouse' file = 'x0211012.ckp' executing restore to disk /II_CKPT/ingres/ckp/vectorwise/data_warehouse of 12 locations done with disk opera

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2022 10:15:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Then we start dump and journals (this always need to be done for online checkpoints even if the database is not journaled as it is here). Apparently the X100/Vectorwise server fails to do this step Fri Oct 7 22:58:05 2022 RFP: Begin restore of Vectorwise journals Fri Oct 7 22:58:35 2022 RFP: Cannot restore incremental checkpoints Database data_warehouse has been marked inconsistent. We see this exact behavior in all three attempts witch c208, c209 and c211. The rfpdb.dbg file you've provided gives a bit more information about the failing step !Sat Oct 8 10:28:19 2022 RFP: Begin restore of Vectorwise journals !Sat Oct 8 10:28:19 2022 [55716,7fbe7e383740] Starting restore X100 server for data_warehouse !Sat Oct 8 10:28:19 2022 [55716,7fbe7e383740] X100 --restore ckps "211" id 11382466 !Sat Oct 8 10:28:47 2022 [55716,7fbe7e383740] Waiting for restore x100_server pid 60860 to exit !Sat Oct 8 10:28:47 2022 X100[1] ended from state STARTING, pid 60860 status 255 !Sat Oct 8 10:28:47 2022 [55716,7fbe7e383740] x100_server wait status 255 !Sat Oct 8 10:28:47 2022 Clearing X100 server[1] entry !ingdb1a ::[II_JSP , 55716 , 0000000000000000:00007fbe77b1a200, vwerror.c:910 ]: Sat Oct 8 10:28:47 2022 E_VW1099_SERVER_START Cannot start X100 server.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2022 10:15:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of that, it is apparent that the X100 / Vectorwise server fails to start for database data_warehouse. Looking at vectorwise.log to check if we can see more details of why the X100 / Vectorwise server fails to start, the corresponding messages are as follows: 2022-10-08 10:28:19.813572 PID 60860:TID 140472906872640: INFO:SYSTEM:X100 Server version x100-gcc-OPTXPROF-64-r21029 (branches/ingres11r1) built on Jun 28 2022 15:46:28 with GCC 4.9.2 20150212 (Red Hat 4.9.2-6) 2022-10-08 10:28:19.868576 PID 60860:TID 140472906872640: INFO:SYSTEM:Started for database 'data_warehouse' in '/II_DATABASE/ingres/data/vectorwise' with vectorsize = 1024 2022-10-08 10:28:19.868673 PID 60860:TID 140472906872640: INFO:SYSTEM:Setting the query memory limit to 271055847424 bytes 2022-10-08 10:28:19.868689 PID 60860:TID 140472906872640: INFO:SYSTEM:rank = 0, num_nodes = 1 2022-10-08 10:28:20.030629 PID 60860:TID 140472906872640: INFO:SYSTEM:Vector nodes: (0, inghsg1) 2022-10-08 10:28:20.075605 PID 60860:TID 140472906872640: WARN:BACKUP:Restoring main.wal using backup sets file /II_CKPT/ingres/jnl/vectorwise/data_warehouse/ckp_211 2022-10-08 10:28:22.413354 PID 60860:TID 140472906872640: INFO:CBM:columnspace_create: nrblks 128 . . . 2022-10-08 10:28:22.414044 PID 60860:TID 140472906872640: INFO:CBM:columnspace_create: nrblks 128 2022-10-08 10:28:45.930745 PID 60860:TID 140472906872640: INFO:CBM:Setting the bufferpool limit to 135528448000 bytes 2022-10-08 10:28:45.930800 PID 60860:TID 140472906872640: INFO:CBM:iobp_create: blksz=524288 nrblks=258500 2022-10-08 10:28:45.930807 PID 60860:TID 140472906872640: INFO:CBM:NUMA interleave bufferpool memory. 2022-10-08 10:28:45.951781 PID 60860:TID 140472906872640: WARN:CBM:verify_auth_file: '1C98E3FD4A16C45D5531BBF76C84CD540B2B7BCD396923871E63588C2CACEB6C' does not match '234D37CF5604166C2544E9DC0FBF250303F2240E2871F42326505FB65F60CEF9' in '/II_WORK/ingres/work/vectorwise/data_warehouse/db_key'

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2022 10:16:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1) Please check the content of /II_DATABASE/ingres/data/vectorwise/data_warehouse/wal/location_map on the source and on the target system? 2) What is the output of "infodb data_warehouse" on the source and on the target system (afrter copying the relevant files from source to target)? Note, infodb.log doesn't show details of the data_warehouse database since it stops when it fails at some point with Wed Oct 12 09:48:08 2022 E_DM012A_CONFIG_NOT_FOUND The database configuration file was not found. This is because of a database called hdmf_zamboanga for which the cnf file is missing since Oct 2021. 3) What locations and files have been copied from the source to the target system? See KB "Cloning Vector / Ingres Database Using Rollforwarddb" attached to this case for requirement.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2022 10:17:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1) Setup the database destroydb data_warehouse createdb data_warehouse extenddb -lii_dbloc1 . . . extenddb -lii_dbloc2 . . . extenddb -lii_dbloc3 . . . extenddb -lii_dbloc4 . . . extenddb -lii_dbloc5 . . . extenddb -lii_dbloc6 . . . extenddb -lii_dbloc7 . . . extenddb -lii_dbloc8 . . . extenddb -lii_dbloc9 . . . extenddb -lii_dbloc10 . . . extenddb -lii_dbloc11 . . . extenddb -lii_work2 . . . ckpdb data_warehouse 2) Run infodb and verify all alternate locations are shown for both Ingres and vectorwise. 3) Make sure all directories exist. 4) Check the content of /...//vectorwise/data_warehouse/wal/location_map and verify it has all the locations listed as the file is in your source system. 5) Connect to the database using "sql data_warehouse" and create/drop a dummy X100 table to make sure the X100 / Vectorwise server starts successfully. Note, this is because, as of vectorwise.log, it appears that since 2020-11-26 no X100 / Vectorwise server was ever successfully started for any database. sql data_warehouse * commit\p\g * create table dummy as select * from iitables with structure=x100\p\g 6) Copy the required files from source (as per the KB doc "Cloning Vector / Ingres Database Using Rollforwarddb") to the target. 7) Run rollforwarddb as you have done before

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2022 13:36:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    2022-10-08 10:28:45.951781 PID 60860:TID 140472906872640: WARN:CBM:verify_auth_file: '1C98E3FD4A16C45D5531BBF76C84CD540B2B7BCD396923871E63588C2CACEB6C' does not match '234D37CF5604166C2544E9DC0FBF250303F2240E2871F42326505FB65F60CEF9' in '/II_WORK/ingres/work/vectorwise/data_warehouse/db_key' The above warning could be the reason for the issue. The database auth file (db_key) is stored in the default data location (here "/II_DATABASE/ingres/data/vectorwise/data_warehouse/CBM/") and there should be an identical copy of the file in the two locations. As the infodb output these are supposed to be: /II_WORK/WKLOC1/ingres/work/vectorwise/data_warehouse /II_WORK/WKLOC2/ingres/work/vectorwise/data_warehouse

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2022 13:39:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI/Actian needs to find out where this information about /II_WORK comes from (it is in the location_map file of the source DB). Actian assumed /II_WORK/ingres still exists, otherwise HDMF wouldn't be able to do anything related to X100 (the X100 engine get details of locations out of this file and not out of aaaaaaaa.cnf). DSI/Actian have to fix the inconsistency on the source system first.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/19/2022 16:34:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    From the logs we have seen that all checkpoint tar files were successfully restored. It fails just when it comes to starting the X100 server to check for any possible journal records. I would consider the database to be consistent from data point of view. Based on that I'd suggest simply patching the database consistent using verifydb: verifydb -mrun -sdbname data_warehouse -oforce_consistent and check if you can open the database using SQL and access the X100 objects. Before connecting check the database using infodb and ensure the locations listed are correct. Check the location_map file and ensure it has the right locations, if it has not, manually modify I.e. changing /II_WORK/ingres/work/vectorwise/data_warehouse to /II_WORK/WKLOC1/ingres/work/vectorwise/data_warehouse Correct the db_key file as well, i.e. remove the db_key file in /II_WORK/ingres/work/vectorwise/data_warehouse and copy the db_key file from /II_DATABASE/ingres/data/vectorwise/data_warehouse/CBM into /II_WORK/ingres/work/vectorwise/data_warehouse.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2022 10:20:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF could not connect to the server and upon checking with ingstatus, Ingres services have stopped. They have to manually ingstart the server to up the services. This happened twice already (October 10 & 17).

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/27/2022 14:41:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Good day! As per observation earlier: 1. Inglogs was run at around 11:25 AM. 2. Uptime.out shows that the server was up for 6mins. 3. Errorlog.log shows that Ingres starts at 11:21 AM (Sir Alvin confirmed that he ran ingstart). 4. The last entry on the errorlog.log was around 11:14 AM, followed by the start up at 11:21. Therefore, the server was down from 11:14AM up to 11:21AM (which is more or less 6mins before running inglogs). Server could not be ping, also third-party software Bitvise could not connect to the server. 5. Errorlog.log did not log any major error or shutdown messages before 11:14AM. Looking at the previous inglogs sent last October 18, it was also the same case: 1. Inglogs was run at Oct 18 07:50AM. 2. Uptime.out shows that the server was up for 14hrs. 3. Errlog.log shows that the Ingres starts Oct 17 07:40PM. 4. The last entry on the errorlog.log was Oct 17: 05:46PM, 14hrs after running the inglogs. Also, errlog.log did not log any major error or shutdown messages before the Oct 17 05:46 PM. Our initial assumption was that the server automatically rebooted. Please run the following: 1. last -x | grep reboot | less > reboot_log.out 2. last -x | grep shutdown | less > shutdown_log.out and send us the result files. Also please send us /var/log/messages. Thank you!

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/27/2022 15:52:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As we checked on the inglogs and reboot log you have sent, those Ingres crashed/shutdown you have reported on dates October 17 and 13, were actually system reboot. reboot system boot 4.18.0-147.el8.x Mon Oct 17 17:51 - 09:16 (4+15:25) ingdb1b ::[40625 IIGCD, 7137 , 0000000000000003]: Mon Oct 17 17:46:21 2022 E_CLFE07_BS_READ_ERR Read from peer process failed; it may have exited. ingdb1b ::[38505 IIGCN, 4207 , 0000000000000000]: Mon Oct 17 19:48:38 2022 E_GC0151_GCN_STARTUP Name Server normal startup. reboot system boot 4.18.0-147.el8.x Thu Oct 13 16:21 - 09:16 (8+16:55) ingdb1b ::[40387 IIGCD, 10131 , 000000000000000b]: Thu Oct 13 16:14:56 2022 E_CLFE07_BS_READ_ERR Read from peer process failed; it may have exited. ingdb1b ::[40387 IIGCD, 10131 , 000000000000000b]: read() failed with operating system error 104 (Connection reset by peer) ingdb1b ::[38589 IIGCN, 6907 , 0000000000000000]: Thu Oct 13 16:22:23 2022 E_GC0151_GCN_STARTUP Name Server normal startup. Notice how the error log shows minutes up to hours gap on recorded logs on these reboots: reboot system boot 4.18.0-147.el8.x Thu Oct 27 11:20 still running reboot system boot 4.18.0-147.el8.x Sat Oct 22 14:47 still running reboot system boot 4.18.0-147.el8.x Sat Oct 22 10:07 still running reboot system boot 4.18.0-147.el8.x Sat Oct 22 09:19 still running reboot system boot 4.18.0-147.el8.x Fri Oct 21 08:36 - 09:16 (1+00:39) reboot system boot 4.18.0-147.el8.x Thu Oct 20 11:11 - 09:16 (1+22:04) reboot system boot 4.18.0-147.el8.x Mon Oct 17 17:51 - 09:16 (4+15:25) reboot system boot 4.18.0-147.el8.x Sun Oct 16 09:23 - 09:16 (5+23:53) Please ask assistance on your hardware/OS supplier regarding this sudden reboot.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/27/2022 19:20:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Closing this case now.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/22/2022 15:17:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As we checked on the inglogs and reboot log you have sent, those Ingres crashed/shutdown you have reported on dates October 17 and 13, were actually system reboot. reboot system boot 4.18.0-147.el8.x Mon Oct 17 17:51 - 09:16 (4+15:25) ingdb1b ::[40625 IIGCD, 7137 , 0000000000000003]: Mon Oct 17 17:46:21 2022 E_CLFE07_BS_READ_ERR Read from peer process failed; it may have exited. ingdb1b ::[38505 IIGCN, 4207 , 0000000000000000]: Mon Oct 17 19:48:38 2022 E_GC0151_GCN_STARTUP Name Server normal startup. reboot system boot 4.18.0-147.el8.x Thu Oct 13 16:21 - 09:16 (8+16:55) ingdb1b ::[40387 IIGCD, 10131 , 000000000000000b]: Thu Oct 13 16:14:56 2022 E_CLFE07_BS_READ_ERR Read from peer process failed; it may have exited. ingdb1b ::[40387 IIGCD, 10131 , 000000000000000b]: read() failed with operating system error 104 (Connection reset by peer) ingdb1b ::[38589 IIGCN, 6907 , 0000000000000000]: Thu Oct 13 16:22:23 2022 E_GC0151_GCN_STARTUP Name Server normal startup. Notice how the error log shows minutes up to hours gap on recorded logs on these reboots: reboot system boot 4.18.0-147.el8.x Thu Oct 27 11:20 still running reboot system boot 4.18.0-147.el8.x Sat Oct 22 14:47 still running reboot system boot 4.18.0-147.el8.x Sat Oct 22 10:07 still running reboot system boot 4.18.0-147.el8.x Sat Oct 22 09:19 still running reboot system boot 4.18.0-147.el8.x Fri Oct 21 08:36 - 09:16 (1+00:39) reboot system boot 4.18.0-147.el8.x Thu Oct 20 11:11 - 09:16 (1+22:04) reboot system boot 4.18.0-147.el8.x Mon Oct 17 17:51 - 09:16 (4+15:25) reboot system boot 4.18.0-147.el8.x Sun Oct 16 09:23 - 09:16 (5+23:53) Please ask assistance on your hardware/OS supplier regarding this sudden reboot.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/31/2022 17:15:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    - /II_DATA/DBLOC1/INGRES/DATA/DEFAULT/PFMDB was accidentally deleted on ingdb1a last October 31, 2022 18:00H - HDMF asked if we could rollforwarddb a multiple-location checkpoint on a single location, which is not possible. - HDMF asked if we could rollforwarddb with +j (journaling) while excluding the last journal because it may be corrupted

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/02/2022 20:14:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    To properly run the rollforwarddb on a deleted database location 1. Re-create the pfmdb directory on /II_DATA/DBLOC1/ingres/data/default/ 2. chmod 700 3. Run rollforward with +j -e31-Oct-2022:14:59:00 Note: DSource recommend not to remove the "corrupted" journal as it might cause improper recovery due to a missing file. HDMF run a test rollforward on inghsg1 and actiansvr before the actual recovery on the production server

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/02/2022 20:22:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF successfully ran the rollforwarddb with +j -e to ingdb1a. PFMS production database is now live at around 13:00H, 1-Nov-2022. HDMF ran checkpoint at around 17:00H, 1-Nov-2022.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/22/2022 10:45:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A problem was raise during the Tips and Tricks 2022 by Sir Roy Urbina. The problem was when an OpenROAD computation change its connection to a newer Ingres Database version, it's changed. No change on the code or the database structure, just the version. Some information is needed to further investigate this case.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/01/2022 15:46:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    In compliance of the Housekeeping guidelines for Optimization of critical Ingres Databases and Tables for Production servers, this activity will cover the following: 1. Identify which production database to be used for pilot implementation. 2. Identify fast growing and critical tables in production database. 3. Rollforwarddb the production database into the test server. 4. Benchmark the identified tables in the test server. 5. Create a plan and schedule of the optimization activity base on the result of the benchmark. 6. Propose the plan and schedule which will be subject for approval of all concerned department. 7. Implementation of the plan and schedule in the staging / reporting / test server. 8. Implementation of the plan and schedule in the production database.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/12/2022 15:23:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    First follow up emailed today, 12-Dec-2022

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/20/2023 15:43:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Follow up 20-Mar-23. Tables that needs usermod in daily basis, optimizedb on a weekly, semi-monthly, monthly running.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/01/2022 15:57:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is in compliance with the monitoring of critical and security events of the production databases. Enable for ITID to proceed with the implementation of the Ingres C2 Security Auditing, we will have to perform the following activities to identify the requirement/s and features to successfully implement the said feature. 1. Identify the location of the audit files. DSI Recommend to remove the existing audit file from /II_SYSTEM and place it to another separate partition. 2. Identify the appropriate size of the audit files. 3. Identify the critical table/s to be monitored. 4. Identify the user/s to be monitored. 5. Identify the appropriate configuration for the security auditing. 6. Identify the security alarm statements.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/12/2022 15:24:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    First follow up emailed today, 12-Dec-2022

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/16/2023 14:08:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the latest patch release for 13-December 2022. https://www.dropbox.com/s/hy9ks2fgvepljys/actianx-11.1.0-100-linux-x86_64-p15829.tar.Z?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/16/2023 14:10:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    2.0 December 13, 2022 - New Bug Fixes for Patch 15829 Bug 137372 (GENERIC) An 'isnull' predicate in the where clause being applied on a not-nullable column that is inner to an outer join makes optimizer underestimate the tuple being produced by the outer join, which could make server choose an in-efficient qep, and make query take longer time to run. Bug 139729 II-9257 (GENERIC) For UTF8 installaion, aes_decrypt_iv() is not working for NCHAR type Bug 140491 II-10090 (GENERIC) A query that has an aggregate subselect under an OR clause takes longer time to run. Bug 140557 II-10151 (GENERIC) Query may incorrectly return duplicated/more rows. Bug 140696 II-9993 (GENERIC) Number of allowed connections are one less/more than the actual allowed value. Bug 140767 II-10365 (UNIX) inglogs may fail to collect vectorwise log files.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/16/2023 14:11:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    3.0 November 21, 2022 - New Bug Fixes for Patch 15825 Bug 138494 II-7931 (GENERIC) Nulls ordered wrongly sometimes - e.g. ordering DESC with NULLS LAST can leave them first, and ordering ASC with NULLS FIRST can leave them last Bug 138754 II-8195 (GENERIC) help is missing for create/drop function statements. Bug 140244 II-9848 (GENERIC) Transaction UNDO fails with E_DM968E/E_DM968F for a table with compressed btree secondary index and the DBMS server crashes. Bug 140319 II-9923 (ATTENTION, GENERIC) Updating a 2D Geospatial column which has a RTREE secondary index may fail with 'E_US120E An error occurred while updating a record.'. The errlog contains additional messages 'E_DM9385_NO_INDEX_TUPLE', 'E_DM9386_SEC_INDEX_ERROR', 'E_DM9387_INDEX_UPDATE_ERROR', 'E_DM008C_ERROR_REPLACING_RECORD' and 'E_QE007E_ERROR_REPLACING_RECORD'. Existing RTREE indices on 2D Geospatial columns must be recreated. Bug 140551 II-10145 (GENERIC) Outer join query returns wrong result. Bug 140580 II-10174 (GENERIC) Outer join query returns less rows than expected. Bug 140610 II-10197 (GENERIC) Query that contains an ifnull() and other aggregates may take longer time to run. Bug 140723 II-10299 (DIRECTOR,IIMGMTSVR) protobuf-java.jar 2.5.0 has high vulnerability risk

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/16/2023 14:12:39

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    4.0 October 14, 2022 - New Bug Fixes for Patch 15812 Bug 134456 II-3744 (LINUX) Provide OCF compliant resource agent script so instance can be managed as part of a failover cluster. This will support such software as Pacemaker. Bug 137795 II-7345 (ATTENTION, LINUX) Support Xerces 3.2. Important: Xerces 3.2 requires libnsl to be installed. Bug 139085 II-8588 (CLUSTERED, VMS) upgradedb may report '%SYSTEM-F-ABORT, abort' after reloading the query tree objects. The Database was updated. Bug 139233 II-8736 (GENERIC) Decimal display as garbage in TM when selecting derived dec(39, 17) column Bug 139859 II-9389 (GENERIC) 'mm-dd-yyyy' is supported for FINLAND/SWEDEN and YMD date_format Bug 140288 II-9836 (GENERIC) Query output suppressed in sql tm caused by use of comment in query. Bug 140351 II-9957 (WINDOWS) GCN exits abruptly using TCP_IP for local I/O and referencing an inactive port. Bug 140401 II-1765 (GENERIC) Error in Database procedure throws extra "E_FORMAT" error. E_FORMAT : Couldn't look up message 1905 (reason: ER error 10903) Bug 140406 II-10002 (GENERIC) Users may see E_CL2514, E_QS001E, E_QS0014, segmentation violation using update cursors. Bug 140409 II-10006 (VMS) Iana timezone files may not be download completely leading to ZIC compilation errors and/or missing Timezone files. Bug 140452 II-10012 (GENERIC) Correlated subquery containing IFNULL() gives wrong results Bug 140489 II-10087 (GENERIC) An insert query that has a group by clause appends more rows than expected into the target table. In the case where the affected tables have many rows, the query may either take longer time to run or may fail with disk full error.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/31/2023 11:49:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF reported some segmentation violations seen on production server. Checking on the privsp_get_mc_record procedure which was common on these segmentation violations.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/31/2023 17:43:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, Can we ask for the schema of the following tables: pf_member_tav_balance pf_membership_info program_type currency_code Also, can we try to run the privsp_get_mc_record DB procedure on test server? Thanks. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2023 16:15:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, This case has been reported to Actian engineering with Jira (II-10351, 140760). Actian Engineering come up with a fix already. Once the patch is ready, will let you know, Sir ASAP. Thank you.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/08/2023 11:56:14

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This bug has been addressed with the latest patch 15854. Please conduct a test for this patch and apply with Production once tested working and do not conflict with other applications. 2.0 March 7, 2023 - New Bug Fixes for Patch 15854 Bug 139878 II-9403 (ENHANCEMENT) Added ELEMENT() and ELEMENT_COUNT() sql functions. Bug 140760 II-10351 (GENERIC) During concurrent sessions perform the same procedure following error can occur: E_PS0004 SIGSEGV at stack psq_recreate Bug 141256 II-11014 (GENERIC) Sending email fails silently

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/31/2023 14:13:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF reported SIGSEGV on Tellering Service. Procedure spgetpospfrdateamountfp has to be checked to further investigate.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2023 16:12:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The client unable to provide the details of the getpospfrdateamountfp procedure, therefore the case was closed last February 14, 2023

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/07/2023 15:14:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The server crashed due to several E_US0001 error. The Ingres was restarted (insgtop/ingstart) and was restored successfully.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/09/2023 12:37:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_US0001 error occurs when more users are trying to connect to the DBMS than the maximum number of users allowed (through configuration). The following are the steps to increase the number of allowed connections: Check to see how many users/ sessions are connected to the database. The DBMS parameter connect_limit controls that value. Increase 'connect_limit' if user connections are getting more or close to that value. It can be increased using one of the two following methods: Run cbf to start the configuration utility (CBF). Go to DBMS Server (Configure) > connect_limit (Edit) or Run iisetres to change the connect limit parameter to the new value iisetres ii..dbms.*.connect_limit new_value Restart the installation to bring that into effect

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/14/2023 11:51:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Elexie updated the connect_limit from 600 to 1000. They haven't had E_US0001 error since then. Closing this case now.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2023 16:36:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As discussed earlier, HDMF is asking to test Actian X 11.2 on their system. HDMF will provide a server with RHEL 7 operating system (as it is the OS requirement for version 11.2) to proceed with the testing. As of March 20: HDMF will provide VM server (with RHEL 8 version) as well as the lichost for license request.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/23/2023 15:26:08

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Successfully upgraded actiansvr to Actian X 11.2 - Done upgradedb for both hsgcentral, pfrstest06302023 - Done sysmod pfrstest06302023 - Currently running usermod againts pfrstest06302023 Next step: 1. sysmod and usermod hsgcentral 2. upgradedb, sysmod and usermod pfmdb

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/25/2023 10:11:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Done running upgradedb for the following databases: bms2023 cis12312022 consoecollection crmsws_db dsi_testapp dsi_testapp_2 dsi_testapp_3 dsi_testapp_4 dsi_testapp_5 dsi_testapp_6 ecollection_esrs ecollection_indi edisbursement enc_test esrsdb hdmf_provident hdmf_ropa hdmf_ropadevph2 hfdcs hfdcs_test hldv_central insclaim_central match_online_collection_paymaya oracle_integ_uat osca07262023 pdc_region_demo2020 pdc_region31_demo2020 pencon pfmdb pfmdb_test pfmdb2 redirectingmidintegdb rfpdb_err stloshelpsreference stlosv2 travel_order2 sysmod, usermod and optimizedb: pfmdb and hsgcentral

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/28/2023 17:46:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of November 28, 2023: - Benchmarked the SQLs for the upgraded version. - Recreated remaining DB procedures for pfmdb and hsgcentral - Record DB Procedures and/or Views that has errors while recreating on the upgraded version

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/21/2024 16:07:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of February 20 1. Backup all necessary files and folders before the upgrade. •inglogs •copy.in •config.dat •ingprenv •Checkpoint files (aaa*.cnf, ckp, jnl, dmp, etc.) •version.rel •OS release ( /etc/redhat-release) •df -k $II_SYSTEM/ingres/files $II_SYSTEM/ingres/bin $II_SYSTEM/ingres/utility Run sysmod and verifydb for upgrade

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/21/2024 16:10:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of February 21 1. Download and install all the required 32-bit RHEL libraries and packages for the upgrade. 2. Started the upgrade but had some errors, turns out other disk location wasn't mounted yet.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/29/2024 19:43:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of February 22 Finished installing on Actian X 11.2 Run upgradedb on: - audit_pfmdb - b132169 - hdmfrecon - pfmdb_test - pfmdb Run optimizeddb on: - pfmdb

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/29/2024 19:47:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of February 23 Due to service disruption on ingdb1a, the test server ingdrdbclone was downgraded to Actian X 11.1 as one of the back up servers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/22/2024 15:33:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Began upgrading the ingdrproclone to Actian X 11.2. This server was already upgraded to 11.2 but downgraded again to 11.1 when PFMS crashed last February 22 2024. As of May 22 2024 DSI already backed up the following: - inglogs - copy.in - config.dat - ingprenv - version.rel - OS release - df-kh DSI also run SQLs to benchmark on 11.1 Currently running sysmod on databases

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/12/2023 16:11:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI perform some pre-upgrade activities and back-up some files: inglogs copy.in config.dat version.rel os-release infodb ingprenv df -k output users.sql Also, earlier DSI discovered that the OS version of ACTIANSVR is RHEL 6.3. Actian X 11.2 is only compatible with RHEL version 7 and up. DSI recommended to upgrade the OS version to continue the testing.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2023 17:20:15

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As pre-upgrade activities, Sir Chris gathered some SQLs and did some benchmark. DSI will wait SQL commands from Sir Edgar Caalim to check and benchmark SQL on Housing DB. Manilyn check the necessary libraries needed to install Actian X 11.2 on RHEL. Sir Ron will still need to update other 32bit libraries as it is required for installation October 19, 2023 Edit and benchmark SQLs for Housing System c/o Sir Edgar Caalim. Check 32bit required libraries for Actian X 11.2 Upgrade.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/19/2023 17:45:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Initial creation and update of Actian X 11.2 Upgrade Plan document.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/25/2023 09:09:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The testing server actiansvr, was installed with RHEL 9.1 with Actian X 11.1 and is loaded with data. For 11.2 upgrade, the installer is asking for the required 32bit libraries to support 32bit applications. Unfortunately those librares are still missing. HDMF System Administrators installed and upgraded the libraries, but still, upon installation, it says that there are 32bit libraries missing. We tried to run 'ldd iiarchtst' to check the 32bit libraries but its just giving 'not dynamic executable' error.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/25/2023 09:16:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    On DSI testing server, we tried to upgrade an Actian X 11.1 installation installed using ingbuild to 11.2 with rpm installer. With the required 32bit libraries alrady installed, the installation was successful.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/26/2023 14:40:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, Good day! To resolve the problem we have on upgrading the actiansvr to 11.2, we set up a virtual machine and install it with RHEL 9.1 to somehow simulate the server's environment: 1. Install Actian X 11.1 and load it with sample data 2. Run “ldd iiarchtst” to check the missing 32bit libraries: a.To solve the “not a dynamic executable” error, we installed glibc-2.34-83.el9.7.i686.rpm to have the /lib/ld.linux.so.2 that we could run the “ldd iiarchtst” command b.Upon running “ldd iiarchtst”, we discovered that the following libraries are still missing: •libcrypt.so.1 •libstdc++.so.6 •libgcc_s.so.1 c. We, then install the missing libraries using the following rpm commands: •libcrypt.so.1: rpm -ivh –-nodeps libxcrypt-compat-4.4.18-3.el9.i686.rpm •libstdc++.so.6: rpm -ivh –replacefiles –nodeps libstdc++-11.4.1-2.1.el9.i686.rpm •libgcc_s.so.1: rpm -ivh –nodeps libgcc-11.4.1-2.1.el9.i686.rpm 3. Run “ldd iiarchtst” again to confirm all the 32bit libraries required were installed: linux-gate.so.1 (0xf7f6b000) librt.so.1 => /lib/librt.so.1 (0xf7f60000) libm.so.6 => /lib/libm.so.6 (0xf7e95000) libc.so.6 => /lib/libc.so.6 (0xf7c9e000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xf7c60000) libdl.so.2 => /lib/libdl.so.2 (0xf7c5b000) libstdc++.so.6 => /lib/libstdc++.so.6 (0xf7a2e000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7a10000) libpthread.so.0 => /lib/libpthread.so.0 (0xf7a0b000) /lib/ld-linux.so.2 (0xf7f6d000) 4. As all the libraries required now complete, we install Actian X 11.2 and upgrade all existing databases. As per my observation, some i686 rpms are still required to be installed to have the other 32bit libraries. I have downloaded the all the required rpm files just in case we need to update the actiansvr. Hopefully it would work and we could eventually upgrade the server to Actian X 11.2 next week. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/10/2023 14:07:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, Just an update for activities done this week: 1. We have already installed and updated 32-bit libraries needed to install Actian X 11.2 on ActianSvr 2. As discussed, pfmdb and hsgcentral are the chosen databases to be upgraded on 11.2 (FYI edisbursement is empty and ropa doesn't exist) 3. Completed the following pre-upgrade activities: - inglogs - copy.in - config.dat - ingprenv - version.rel - RedHat release - df -k - infodb - usermod (hsgcentral, on-going for pfmdb) - sysmod (hsgcentral) 4. Backed up the following files: - $II_SYSTEM/ingres/files - $II_SYSTEM/ingres/bin - $II_SYSTEM/ingres/utility - $II_SYSTEM/ingres/fileslib 5. Remaining pre-upgrade activities: - sysmod (pfmdb) - verifydb (hsgcentral, pfmdb) Hopefully #5 could all be done by Monday so that we could start the upgrade on Tuesday. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/21/2023 11:06:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of Nov 21, 2023: - Both hsgcentral and pfmdb are already done with usermod, sysmod and verifydb - All necessary files have already been backed-up - All set for actiansvr upgrade to Actian X 11.2

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/08/2023 11:29:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the latest patch release for 7-March 2023. https://www.dropbox.com/s/9u7e6rydi5vdnq3/actianx-11.1.0-100-linux-x86_64-p15854.tar.Z?dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/08/2023 11:32:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bugs addressed with this patch: 2.0 March 7, 2023 - New Bug Fixes for Patch 15854 Bug 139878 II-9403 (ENHANCEMENT) Added ELEMENT() and ELEMENT_COUNT() sql functions. Bug 140760 II-10351 (GENERIC) During concurrent sessions perform the same procedure following error can occur: E_PS0004 SIGSEGV at stack psq_recreate Bug 141256 II-11014 (GENERIC) Sending email fails silently

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/08/2023 11:32:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    3.0 February 17, 2023 - New Bug Fixes for Patch 15846 Bug 135659 II-5094 (GENERIC) Following an unsuccessful attempt to open a database, an ALTERDB command could cause the DBMS's 'LK Callback Thread' to report an E_CL250A_CS_NO_SEMAPHORE and terminate the DBMS via the server with an E_DM9449_DMD_CHECK error. Bug 140538 II-10141 (ATTENTION,GENERIC) Statistics generated on CHAR class column with length greater than 8 does not represent the data characteristics well, and may make the optimizer produce sub-optimal query plan. Existing statistics on affected columns needs to be deleted and re-generated in order to apply the fix. Bug 140749 II-10297 (GENERIC) Support OpenSSL version 1.1.1n to fix CVE-2022-077. Bug 140803 II-10428 (GENERIC) X100 aggregate query fails with E_VW1027 error. Bug 140836 II-10466 (GENERIC) The Patch level of the DBMS server can now be obtained using select DBMSINFO( '_patch' ) Bug 140871 II-10500 (GENERIC) The DBMS reports spurious PSF, RDF and/or ULM errors when one or more sessions is creating and/or recreating database procedures. With ulm_pad_bytes set to an odd number the DBMS will report a SEGV in uld_marshal( ). Bug 140892 II-10522 (GENERIC) The upgradedb command doesn't create the iiexternal catalog table. Therefore a CREATE EXTERNAL TABLE statement fails with the error E_US0091_NONEXISTENT_CATALOG. Bug 140935 II-10573 (GENERIC) Server returns wrong result for an union query that has an outer join in one of its sub-query. Bug 140938 II-10576 (ACTIANX) A running installation will stall if the license.xml file being used is updated so that it does not contain a license for the same product that was being used. Restarting ActianX, the new licenses in the license.xml will be accepted. Bug 140947 II-10586 (GENERIC) Server returns wrong result for a query that joins on a table that is keyed on boolean type column(s). Bug 141021 II-10684 (UNIX,WINDOWS) upgradedb creates the iiexternal table on configurations w/o X100 support

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2023 14:25:16

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    While performing a penetration testing on the system, some server slowed down. Third party (provider of Pen Testing) is asking what are the ports used by Ingres so that they could exemp them on the next scan.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/09/2023 14:39:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, You could check errorlog to see what ports are used by Ingres.You can also see it when you ingstart. For the LEGACYPDCSVR its 21064 and 21071. EGACYPDCSVR ::[45824 IIGCC, 10819 , 00000000ffffffff]: Sun Jan 29 07:18:40 2023 E_GC2815_NTWK_OPEN Network open complete for protocol TCP_IP, port II (21064). LEGACYPDCSVR ::[45824 IIGCC, 10819 , 00000000ffffffff]: Sun Jan 29 07:18:40 2023 E_GC2A10_LOAD_CONFIG Finished loading configuration parameters for configuration '(DEFAULT)' of server type 'GCC'. LEGACYPDCSVR ::[45824 IIGCC, 10819 , 00000000ffffffff]: Sun Jan 29 07:18:40 2023 E_GC2006_STARTUP Communication Server normal startup: server rev. level II 11.1. LEGACYPDCSVR ::[34081 IIGCN, 10677 , 0000000000000004]: Sun Jan 29 07:18:41 2023 E_GC0153_GCN_SRV_STARTUP Server Registration: class DASVR, address 38417 LEGACYPDCSVR ::[38417 IIGCD, 10838 , 00000000ffffffff]: Sun Jan 29 07:18:41 2023 E_GC4803_NTWK_OPEN Network open complete for protocol TCP_IP, port II7 (21071). Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/09/2023 14:44:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Both the net server and jdbc one, report: LEGACYPDCSVR ::[38417 IIGCD, 10838 , 00000000ffffffff]: Fri Mar 3 16:15:15 2023 E_GC001E_ACCEPT_FAIL Connecting client failed to perform all actions required for a successful connection. This may indicate a problem with the client, a foreign client that does not conform to the correct IPC protocol, or a malicious client attempting to disrupt the server. LEGACYPDCSVR ::[45824 IIGCC, 10819 , 0000000000000008]: Fri Mar 3 16:15:15 2023 E_GC001E_ACCEPT_FAIL Connecting client failed to perform all actions required for a successful connection. This may indicate a problem with the client, a foreign client that does not conform to the correct IPC protocol, or a malicious client attempting to disrupt the server. Slow down may caused by the overwhelemed GCC/GCD. Kindly exclude ports 21064 and 21071 and let us know what will happen. Thank you.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/15/2023 11:09:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, Any udpate on Pen Testing? We'll be closing this case in 2 days. Thank you. Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/27/2023 16:29:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    No reported slow downs on LEGACYPDCSERVER since they have filtered the ports 21064 and 21071 as well as other ports from 5000+ and up. HDMF will pen test bigger server next and will report if there's any slow down or similar problem. Closing this case now.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/20/2023 09:41:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is a support case for HDMF's Re-engineering project for old OpenROAD Application versions of Housing Department.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 11:34:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The Project was renamed to "Housing Revitalization Project"

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 17:58:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The re-engineering project is at full swing and as per Sir Roy Urbina, they are deploying a small module of the program soon. It is currently being tested with the QA Dept.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/20/2023 15:10:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A request was made for a Functional Testing Tool that can accomodate and identify OpenROAD forms and fields. Attached to this case are the documentions for the previous Proof-of-Concept for SmartBear TestComplete. The POC was conducted last 2021 for the purpose of testing TestComplete's compatibility with OpenROAD applicatons. The POC shows a positive result and demostrate its use with an OpenROAD Application.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/25/2023 10:11:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A product presentation was requested last August 18 by Sir Kit Navia for the whole ISQAD. The actual presentation was commenced last Sept 19 on Meeting Room 1 from 1pm to 3pm. The presentation was attended by Sir Kit Navia, Ms Lily Ambal, Sir Bhoy Cortez and the whole ISQAD Team. The Following topics was discusssed: •What is Automated Functional Testing Tool? •What are the benefits of utilizing an Automated Testing Tool? •What sets TESTCOMPLETE apart? •Setting Expectations •Do's and Don't s for Automated Testing •A little demonstration for TestComplete •Next Step on Using TestComplete.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/25/2023 10:37:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Kit Navia mentioned that a Desktop was set for their team to host a TestComplete installation last October 20. They are now free to use the 6-months Trial License Dsource provided them for testing and learning.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/08/2023 16:39:08

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI had a quick discussion with Sir Kit Navia with regards to the usage of TestComplete. They have requested to coordinate with DSOURCE to facilitate a workshop to kickstart their team's activity to use TestComplete. They will have a meeting on Friday (Nov 10) to discuss the team's schedule so we can set-up the workshop.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/21/2023 12:04:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A date was set for the Workshop to be attended by ISQAD team on Nov 24 at 9am to 12nn. To be conducted at 15th floor Jelp Building HDMF Office.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/24/2023 15:15:43

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A successful workshop was concluded on Nov 24, 2023 from 9am-12nn. The team will now start their individual testings. Some inquiry are raised: -Adding breakpoints to the script to stop the running of script on a specific line. -Tracing( step by step manually) -Append text to a variable for checkpoint -Saving test results for reporting -Test mobile application in testcomplete -Documentation for Delay and Waitfor in testcomplete.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/03/2024 15:48:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A guided testing was requested by Sir Kit Navia. This activity is will include the whole QA Testing Team and will take 2 whole days and will be conducted on HDMF premises. Every team member will have their own application to test and DSOURCE will be there to accomodate questions and inquiries of every member. The goal of this activity is for every team to have at least one application to test through Smartbear TestComplete for them to have their feedback on the tool. The agreed dates are April 2 and 3 from 8:00AM to 5:00PM.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/01/2024 16:08:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    In preparation for the Guided Testing. Dsource requested five 14-day trial license from Smartbear and a Bitbar license to test Bitbar with HDMF's Mobile Application.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/04/2024 16:20:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The Guided Testing activity was a success. Everyone from the QA Testing team was able to perform automated testing on various applications. Some challenges were encountered and needed to be addressed after the activity. Results: Successfully created test scripts and run multiple Data Loop on the Application Under Tests each QA team selected. Application varies from: OpenROAD Applications Web Based Application Successfully connected and run a Mobile Application for test with the use of TestComplete and Bitbar. Unfortunately, the QA Team and Dsource did not proceed with the test due to: Requirement of the Application Under Test to connect to HDMF’s infrastructure. This cannot be done since this will expose HDMF’s network to outside. With no connection to their test environment, Dsource and QA Team decided not to proceed with the Mobile Testing using Bitbar. Alternatively, the QA team decided to use their development team’s tool to simulate the mobile application, unfortunately it did not succeed due to slow performance of the machine. Dsource and HDMF QA Team successfully showcased some features of SmartBear TestComplete like: Test Script Creation using Keyword Testing Data Loop on whole script Data Loop on a segment of a script Test Runs and Debugging Variable creation and test script modification If Else Conditions Test Replay from Test Application running. Failed test on a Web-based ASP.Net application. Successful test recording but replaying causes different selection on DropDown Options. This case was raised to Smartbear Support and identified as existing behavioral bug. Awaiting response to fix this error. Next Step: The HDMF QA Team will conduct an internal assessment of their experience on using an Automated Testing Tool. Dsource will await HDMF QA Team’s assessment and will further assist on any help they will need. Dsource will follow-through on the Failed Test for the ASP.Net Application

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/20/2023 15:48:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Advance Training for OpenROAD developers who have attended the online or face-to-face "Introduction to OpenROAD Development training". As of the moment, there is still no available training offerings from Actian Education. A list of prospective candicate for the advance Training will be requested from HDMF as well as particular training topics that we could request to be discussed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/25/2023 10:23:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A Training was set to commence with 2 batches to accomodate more participants. The Advance Training will commence on the following date: Batch 1 - Oct 9 to 13, 2023 Batch 2 - Oct 23 to 27, 2023 The following are the participants who will attend the training: Batch 1: • Sandoval, Jose Marie Sales • Ramos, Jullienne Lising • Angeles, Ma. Bernadette Merogenia • Bagatua, Floyd Tenorio • Manalo, Christopher Del Rosario • Salazar, Richard Jeffrey Maquinto • Cobrado, Christian Noel Dural • Go, Reymart Cabanos • Martin, Michael A. • Simon, Ramonato A Batch 2: • Alindog, Marinella N. • Manahan, Spencer Edsel T. • Burgonio, Crisaldo B. • Sepnio, Virgilio Jr V. • Raposon, Loida F. • Laberinto, Elexie C. • Caalim, Edgar C. • Labastida, Neil Ryan E. • Dalicun, Benjelin Mabborang • Antonio, Brian Buen Jose • Onayan, Jeneses Balat • Dimaculangan, Marco Katimbang • Policarpio, Jomar Gaytano • Cayanan, Harry Mora • Lapuz, Dyojie L. • Gregorio, Jennifer P. • Tabarrejo, Alvin T. • Tobias, Lloyd B. • Beltejar, Ronald Leo R. • Molina, Stephen O.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2023 10:27:28

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    2nd batch of OpenROAD Advance Training was successfully fulfilled with the updated set of Participants: Brian Buen Antonio Ronald Leo Beltejar Jeneses B. Onayan Loida Raposon Kim Antonio Jullienne Ramos Stephen O. Molina Neil Ryan E. Labastida Harry M Cayanan BENJIE DALICUN Virgilio Sepnio Jr. Alvin Tabarrejo LLOYD B. TOBIAS Elexie Laberinto Crisaldo B. Burgonio Spencer Edsel T. Manahan Marinella Alindog MARCO K. DIMACULANGAN Edgar C. Caalim Jennifer Gregorio Jomar G. Policarpio Dyojie Lapuz Hazar b. Buensalida Robert E. Pilapil

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/20/2023 15:55:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    There are newly hired developers coming in around mid-2023 that will require basic training for both Ingres and OpenROAD development. Minimum of 10 participants are anticipated to take this training. The Introduction to OpenROAD development might require a longer session than the previous 3-day setup. This will also be a Face-to-face session for better comprehension of the lessons.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/25/2023 10:19:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Batch 6 commenced from Sept 25 to 29 at Edsa Shangri-la Hotel. The training was attended the following people: • Apring, Mary Joy Lara • Quimzon, Bernard Ongonion • Ureta, Marycho Altamia • Antonio, Kim Sagala • Pedrera, Norelyn • Canales, Jomel • Doza, John Paul • Gabrentina, Michael • Tiamzon, Niesser • Rayela, Aizelle Ann B • Nolasco, Nathaniel M. • Sante, Rialen F. • Torio, Alben B.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/24/2023 17:01:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF testing server (actiansvr) just applied the recent patch (15854) to test the previous SIGSEGV experienced on the production server. Unfortunately another segmentation violation occurred while they are still testing the latest patch.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/27/2023 16:34:28

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Alvin, As per Actian the SIGSEGV error on ActianSvr, seems to be different from the production error which was patched on 15854. It could have happened due to ungraceful shutdown of the server during patch installation. I have attached a KB on this case, though it covers only a portion of the error message which appeared in the errorlog, but it looks relevant. Please take a look and apply the resolution on KB. Also, there's a lot of logical locks recorded on errorlog. Please consider updating the per_tx_limit. Thank you. Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/03/2023 16:03:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Good day! The SIGSEGV error on the latest inglogs sent today, April 3, was really similar to the previous one. Please see the attached KB and try apply the suggested solution (recreate transaction logs), and let us know what will happpen. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/11/2023 14:28:06

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Good day! As per discussion with Sir Sherwin earlier, he agreed to run again the auditdb script on actiansvr. If the SIGSEGV error will still occur, you will provide us the test case that will be submitted to Actian to further investigate. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2023 13:59:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Unfortunately, Actian cannot recreate the error on their side. They are still analyzing the case. They are asking to turn off the "security_auditing" on CBF (this needs a restart) and then rerun the auditdb command and let us know how it goes. Kindly send us screenshot and inglogs after. Please do it when nobody is accessing the database. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/28/2023 14:32:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Good day! Just an update on this case, it is suspected to be related on Jira II-9902,140296 which is currently in Engineering for fix. We'll keep you posted Sir. Thank you.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/29/2023 13:54:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As part of our services to you and in relation to our previous OpenROAD Loadnrun (OR LNR) 6.2 POC (reffer to case number 2022-00015) we would like to request for the following items for the deployment of OR LNR 6.2 : 1. Server where the OR LNR and App Server will be installed. - Please prepare any of this Windows OS 64-bit: Windows 2008 R2, Windows 7, Windows 8, 8.1, Windows 10, Windows 2012 R2, Windows Server 2016 (64-bit) - On our previous POC, Windows Server 2012 R2 Standard 64-bit was used. 2. Login credentials of the OR LNR and App Server e.g., Username and Password, IP Address. 3. OpenROAD Application (.img) that will be deployed using LoadAndRun Server. 4. Client workstation that can access #3 OpenROAD Application to test. Below are applications needed for setting up OR LNR 6.2 on windows: 1. Java JDK and JRE 2. OpenROAD Server 6.2 build: 15216 patch:15707 3. LoadNRun 6.2 build: 15216 patch:15707 4. Apache Tomcat v8.5 installer 5. Application to be deployed (created/imaged using OR 6.2 build: 15216 patch:15707) We would like to ask your permission for installing Java JDK and JRE, and Apache Tomcat on the server machine that you'll provide. In addition, we would also like to know when is the best time to start this service. Note: During our Tips and Tricks 2022 session, Ms. Manabat asked us if it's possible to use IIS instead of Apache Tomcat to set up the gatekeeper so that there's no need for third-party software. Our team conducted research on this matter and tested it on our side, and we were able to set up the gatekeeper using IIS. If you would like to use IIS over Apache Tomcat, we suggest that we perform a POC using IIS in your environment before deploying OR LNR 6.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/01/2023 15:56:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI presents the LNR to HDMF to show the current status of the project and to also discuss the next move. Activity list: 1. Upgrade LNR 6.2 to LNR 11.2 2. Use IIS as webserver 3. Launcher Restriction 4. Security options for LNR config files 5. Set OR 11.2 on another machine to check 6.2 images 6. Design a Launcher 7. Create an LNR user manual for client

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/02/2023 15:38:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI installed the following for the testing of LNR 11.2: OR 11.2 LNR 11.2 (Client and Server side) IIS DSI also get the lichostinfo of the server so that they can provide a trial license for the OR App Server 11.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/04/2023 17:03:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI starts to setup the following: IIS OR App Server 11.2 (License activation) LNR 11.2 (Client and Server) LNR Gatekeeper 2 After the setup, DSI test to launch the demo application of LNR. Launcher: Sucessfully downloaded Jigfall: Successfully downloaded

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/10/2023 15:52:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As requested, Dsource created 3 templates for the LNR Launcher. This is to show the possibilities for the design we can use for the Launcher instead of using the Default Simple Launcher. Included to the attachments are: > The exported XML of the Launcher template already tested working for LNR 11.2. > RAR file composing of images used for the template. MUST be extracted and loaded to C:\ Directory (C:\DSISystem|....) > 3 Images per each template.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 18:26:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI and HDMF had a meeting regarding the Following: 1. Download speed of LNR. 2. Testing one Loadnrun client in Cubao branch. Result: Download time is aroung 15-20 seconds. 3. Date for LNR deployment at Cubao branch. Tentative date: September

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 18:32:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Set up LNR Client to Sir Michael Martin. Gave a copy and present the launcher created by DSI. Gave the xml file of Openroad Sample Launcher so HDMF could check and modifiy the Launcher.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 18:49:03

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Transfer of knowledge on the creation of LNR launcher to Sir Michael Martin –install4gl.txt. DSI and Sir Michael Martin checkout the codes of the Launcher. - Locate and compare the environment variable from install4gl.txt and Launcher's code.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/06/2023 14:45:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Martin asked DSI for assistance in developing the LNR Launcher for HDMF's use. He envisions an application that can modify the list of applications executed by their Launcher without the need to manually edit the 'install4gl.txt' file on the server side.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/08/2023 15:06:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI and Sir Mike discussed their plan and process on how they will modify the HDMF's Launcher application. Objective: Make a dynamic launcher where it can filter the applications that the user can only use.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/13/2023 15:08:13

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Update from last discussion: DSI has created a sample Launcher with access control by utilizing a set of information from a Database. This Database consists of information of users and the applications assigned to them. The created launcher will check the database for a specific user and will fetch all the applications assigned. It will then load the menu on the Launcher based on what is allowed for the specific user. NOTE: The process used on this Launcher bypassed the normal way of reading from the Config File. The Config File is still relevant for other variables like version number. But the application details was directly fetched from Database. Attached are the files generated.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/13/2023 16:35:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    - DSI has successfully set up a Loadnrun Client and confirmed connectivity with the Loadnrun Server, with a successful result. - DSI has made a request to deploy an application through Loadnrun to test its functionality. - Sir Sherwin has indicated that modifications to the application's code are necessary to access its associated templates before they can deploy it using Loadnrun. During this phase, Sir Sherwin has requested support from DSI.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2023 12:23:14

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As part of LNR deployment, all applications that uses external files must be recoded to accomodate the change in file location. As per Sir Sherwin Astorga, local files used by the image are store on a specific location, thus the location path was hard coded. LoadNRun, as presented on the previous P.O.C. can transfer supporting external files along with the Image. But these files will be stored with the Image's location defined by LoadNRun. A simple code can be done to adjust this and make it dynamic. Cursession.WorkingDirectory This function will return the current location of the Image being run. Concatenating additional text to represent a sub-folder location. e.g. vPath = Cursession.WorkingDirectory + '\files\config.ini';

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2023 15:57:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Stephen will recode the images to accomodate the change in file location. We instructed him on how to use the CurSession.WorkingDirectory function.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2023 11:56:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI together with Sir Stephen test the new image with Cursession.Workingdirectory function. It is working.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2023 16:06:21

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After re-coding and testing of the Cursession.WorkingDirectory function to accomodate the change of location of the supporting files (Excel Templates). A functionality test was done to check the following: > Auto Downloading of Image along with the Supporting files. > Testing of download speed through VPN connection. > This shows a very slow download though the result was expected. > Auto download for Deleted/Non-existing application on client machine. > Version change for both Launcher and Application to trigger download. > Removal of Trace Window for both Launcher and Application AUT. > Testing of application behaviour on missing supporting files. > Application functioned as designed. Next step is deploying on a clean (no prior installation of any OpenROAD related product) to test/check the completeness of deployment. Clients also seek assistance to check for setting/adding environment upon installation to reduce installation effort when deployed to client machines. Dsource will also send a sample launcher source code for their modification and testing.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/03/2023 09:44:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    During our search for information on how to set and add environment variables during the LNR installation process, we discovered that only a limited set of environments can be changed, including II_INSTALLATION, II_CHARSET, II_DATE_FORMAT, II_DECIMAL, II_MONEY_FORMAT, and II_TERM_INGRES. However, it's worth noting that II_TIMEZONE_NAME can be set after the installation, and new environment variables can be added as well. To simplify the installation process, we recommend using the silent installation method, which involves using ormsiexec.bat to install LNR. We suggest conducting a trial run first to ensure that the process runs smoothly. This method can potentially reduce installation effort.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/05/2023 14:17:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF was interested in deploying and using an OR 6.2 image in an LNR 11.2 server/client environment. To test this, DSource conducted a simple image test and found that it was successful.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Aug/01/2023 15:52:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Re-testing of LNR server and LNR Client. Checking LNR connection with client Deploying new image Updating image Testing of LNR Launcher DSI tried to deploy an 11.2 image using the LNR 6.2. Result: Failed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/13/2023 18:15:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Integrity error while running the below SQL Statements on ingdrdb DR Server. select pagibigid, account_no, lname, fname, mid, name_ext, birthdate, branch_code, branch_name, hub_code, hub_name, pagibig_erid, employerid, eyername, eyeraddr, membership_category, membership_category_desc, program_code, program_code_desc, init_percov, last_percov, init_remit, last_remit, maturity_counter, total_ee, total_er, total_div, total_savings, membership_status, membership_status_desc from vw_virtual_branch_member_master where pagibigid = '109003740170' order by lname, fname, mid, account_no, membership_status, last_remit desc; commit; select max(percov), count(distinct(percov)) from vw_virtual_branch_pf_ledger where pagibigid = '109003740170' and account_no = '109003740170' and program_code = 'F1' and ifnull(percov, '') <> '' and ifnull(ee,0.00) > 0.00; COMMIT;

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/13/2023 18:25:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A potential backup error resulting to inconsistent data integrity. Tested the same query on the following servers: 1. inghsg1 (Reporting Server) - SUCCESSFUL 2. actiansvr (Testing Server) - SUCCESSFUL 3. ingdrdb (DR Server) - FAIL The apparent difference on those three servers are the way of restoring the back-up. 1. inghsg1 (Reporting Server) - rollforwarddb 2. actiansvr (Testing Server) - rollforwarddb 3. ingdrdb (DR Server) - 3par synching For further investigation.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/13/2023 18:43:30

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Requesting for a table definition of the following: 1. vw_virtual_branch_member_master 2. vw_virtual_branch_pf_ledger from ingdrdb, inghsg1, actiansvr

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/14/2023 12:02:24

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon checking the table definition of the views are all similar. One problem to check is the more evident cause--the 3par synching. We will request for a trial license for a temporary DR Server and redo the synching of the DR Server to fix this issue. Take note that the trial license is for strict one (1) month use only. Will close this case now as this is not an Ingres related case but more of a third-party software problem.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2023 16:19:28

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. Download the Actian licensing utility on the dropbox link below. 2. Unzip the file 3. Run the lichostinfo batch file 4. Please send us the result of the lichostinfo in text format with the following naming format: .ORDev.lichostinfo Example: ChrisDelgado.ORDev.lihostinfo

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/04/2023 16:39:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Follow up submission of lichostinfo today 04-May-23.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/22/2023 14:22:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Greetings Sir Sherwin, Gentle follow up of the lichostinfo of the development user's workstations so we can size up how many allocated licenses per development.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/14/2023 14:50:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Gentle follow up on the lichostinfo of all the OpenROAD Development user, so we could issue an OpenROAD 11.2 license.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2023 16:25:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, We would like to request for the following: 1. lichostinfo of all the Database servers (Production, DR, HA, Testing, Development). 2. version.rel of all the Database servers. 3. lichostinfo of all the OpenROAD Application servers. 4. version.rel of all the OpenROAD Application servers. Special instructions: 1. Please have all the lichostinfo and version.rel in one folder per server. Folder name will be the server name. 2. Please have all the files in text format. 3. Please include a short description and usage of the server on a separate text file within the folder. Deadline is on or before May 2, 2023.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/19/2023 16:25:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The client have upgraded their servers to Windows Server 2019 R2 which is hosting their OpenROAD Appication Server. Everything is working good on the previous Servers but they are having some problems with the current setup. > User Credentials for their DCOM connection sometimes does'nt work. A server reset was necessary to have their users accomodated to the servers. > A specific application is hogging the CPU resources of the Application Server which is not happening on the old servers. Since there are no apparent error message or specific diagnosis that the cause of this is the Compatibility of OpenROAD to Windows Server 2019 R2, an invistigation will be done to track what might be causing this problem.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/26/2023 11:17:05

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Apparently, OpenROAD 6.2 was not tested on Windows Server 2019. The latest version of OpenROAD 11.2 is the one that has been tested and certified on Windows 2019. Also, since OpenROAD 6.2 is on extended support since 2021, there are no new fixes. It is highly recommended to upgrade to OpenROAD 11.2. We will be closing this case.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/24/2023 10:35:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    An Error occured when using .NET upon saving to a new table. "Could not open the iirelation table."

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/24/2023 17:57:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The following information was requested for assessing the problem: 1) From where the source table is coming (ddl) ? 2) Is there any difference/modification done in the structure of the target table which is being saved via stored procedure? If yes what is it? 3) What exactly the procedure does ? 4) Please provide the errlog.log and the Ingres patch # in use ? 5)What connection type is being used i.e (jdbc/odbc)?

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/26/2023 10:59:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The problem was resolved. Apparently, it was caused by a coding error resulting a "Null Date" argument. "As per Sir RJs findings, the Ingres Version 10.2 returns an error “IIRelation Error”. Then he runs the same script (run and develop in vb .net) connecting to Ingres Version 11.1 then the returning error pertains to “null date”. So he just make adjustment to his script and run it again in Version 10.2 and the problem is resolved." This case will be closed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/15/2023 14:30:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This will serve as a reminder that Patch 15854 which was released last 7-Mar-23 will probably the last patch for ActianX version 11.1. Kindly take note also of your servers that has obsolete version (10.2) i.e., orataf and LEGACYSVR. There will be no license for Ingres 10.2 version anymore. Furthermore, kindly check the attached link for .pdf file so you can see the list of servers that needs patch updating. Legends: RED - NEEDS IMMEDIATE VERSION OR PATCH UPDATE (Patches released 31-Dec-21 or older) ORANGE - NEEDS IMMEDIATE PATCH UPDATE (Patches released 31-Dec-22 or older) GREEN - ON THE LATEST PATCH

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/30/2023 10:42:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A request to setup an OpenROAD Server Farm Administration for HDMF's OR Application Servers. The request was sent by Ms Marinella Alindog.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/02/2023 11:23:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The server and client have different timezones, which causes discrepancies in the saved time. Ideally, the saved time should reflect the server's time, but in this scenario, the time is obtained from the client instead.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/02/2023 11:40:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This is the code we use to get the time from the server side. "SELECT date('now') as server_date;" Please give this code a try and let us know if it resolves the problem you encountered. Thank you Sir.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/02/2023 15:53:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After the consultaion earlier with HDMF, it has been identified that the II_TIMEZONE_NAME obtained from the client is being used instead of the server's timezone. To address the issue at hand, DSource will replicate the case in order to understand the problem thoroughly and provide an appropriate solution.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/05/2023 10:30:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    We conducted several scenarios to replicate the timezone problem. These scenarios were performed on the client side with II_TIMEZONE_NAME set to GMT2, while the server used II_TIMEZONE_NAME PHILIPPINES. 1. Directly inserting the current date('now') into the database via ISQL. 2. Inserting the actual date and time value (e.g., 05-jun-2023 12:00:00) into the database via ISQL. 3. Running the SELECT date('now') query via ISQL and comparing it to the server. 4. Using OpenROAD, passing the value of SELECT date('now') to a variable and using that variable to insert into the database. The data type of the variable was set to date, and we also tried setting it to varchar. RESULT: On the client side, the date and time values are displayed in GMT2. When compared to the server side, the date and time values are in the PHILIPPINE timezone, resulting in the correct time being posted.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/07/2023 15:23:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After conducting a testing on OpenROAD 6.2 p15707, we found out that the server-side accurately saves the date and time, even when the client has a different II_TIMEZONE_NAME. We highly recommend trying out and applying the mentioned patch (p15707) to resolve the problem you have encountered.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/16/2023 09:34:05

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    This case was fixed using the OR 6.2 p15707. When saving date and time from a Client with a different II_TIMEZONE_NAME from the Server, it will still use the II_TIMEZONE_NAME of the Server. However, by default, when viewing the date and time from the Client, it will be displayed based on its II_TIMEZONE_NAME. If the Client wants to view the actual date and time from the Server, the Client's II_TIMEZONE_NAME must be the same as the Server's. Please use the link below to get a copy of OR 6.2 p15707.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/14/2023 12:26:12

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Showed signs of performance slowdown then it went down. No further test to be performed because inglogs is not yet available.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/14/2023 14:48:42

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of now, no clear cause of the production server failure. It is speculated to caused by some network adaptor while HP is pointing out that the cause is the Operating System.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/23/2023 17:16:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    No further update from the client regarding the real cause of the crash. Either Operating System or Hardware failure.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/16/2023 10:04:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. Query Tool Crashes every time a wrong query is done. 2. "SELECT FIRST 10 * FROM insclaim_master;" produce an error.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 10:59:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Transaction UNDO fails with E_DM968E / E_DM968F for a table with compressed btree secondary index and the DBMS server crashes and becomes unaccessible.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 11:46:42

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Ms Nheng, Good day! Upon checking the inglogs of ingdb1b, this error was caused by bug II-9848 (140244) where in UNDO fails with secondary indexes with BTree table structure leading to crashing of DBMS servers. This bug was fixed with patch 15829 last November. Please patch the server to avoid this error again. Thank you! Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 15:07:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    You can download the latest patch release for 31-May 2023. https://www.dropbox.com/scl/fi/ulcnly8hzxraamawd2ab8/actianx-11.1.0-100-linux-x86_64-p15872.tar.Z?rlkey=fxtnuq87ftnay0wvp2zd2ckei&dl=0

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 15:14:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bug 135025 II-4321 (ATTENTION, GENERIC) timestampadd() function is not considering 'interval' field as Integer. Now decimal part from 'interval' would be truncated, hence it will result different value in case 'interval' is decimal. Bug 139633 II-9177 (GENERIC) SIGSEGV occurs when autostats is on. Stack shows rdu_statistics(), rdf_getinfo(). Bug 139928 II-9466 (WINDOWS) The Visual Manager icon on the taskbar does not show the Exit option. Bug 141112 II-10785 (GENERIC) Handle '-0.0' in comparisons consistently with '0.0'. Bug 141185 II-10899 (GENERIC) OPTIMIZEDB leads to a SIGSEGV in the DBMS when server tracing is enabled. The SIGSEGV occurs in scu_qtrace_dataval(). The same exception may happen when tracing any query that has varbyte query parameters. Bug 141208 II-10945 (GENERIC) Comments on views are lost when running upgradedb -tree. Bug 141209 II-223 (GENERIC) Fix quotes in SQL and QUEL macros. Bug 141256 II-11014 (GENERIC) Sending email fails silently

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/18/2023 15:15:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Bug 141270 II-11020 (ATTENTION, UNIX) Upgradedb fails with "Unable to create subdirectory 'upgradedb' in II_FILES:upgrade" if run as a user other the installation owner. This patch contains a fix for new installations, to manually fix existing installations run as the installation owner: $ upgradedb -tree iidbdb Bug 141350 II-11122 (ATTENTION,ENHANCEMENT,GENERIC) Enhance optimizedb by building statistics that uses all exact histogram (vs mixture of exact and inexact) if space is allowed. This solution requires the derived configuration parameter 'opf_memory' in config.dat to be recalculated. This can be done by using ingres utility 'cbf', then navigate to 'DBMS Server' -> 'Derived' -> 'opf memory', then choose 'Recalculate' option. Bug 141369 II-11145 (LINUX) The inglogs helper script inglogs_gdb_stacks is not shipped. This script is useful in cases where a process owner is not allowed to determine the stacks. By using the -stackdmd flag, inglogs can be advised to call that script via sudo to collect the stacks. Run "inglogs --help" to get more details. Bug 141426 II-11217 (GENERIC) User provided schema is ignored while "rename" / "alter rename" table. Also error message is not correct. Bug 141443 II-11233 (GENERIC) An outer join query that fetches a BLOB type column fails with E_SC0206. Bug 141448 II-11237 (GENERIC) Uncorrect behaving of quotes in macro mode in SQL tm. Fixed by limiting quotes only for macro parameters. Bug 141454 II-11248 (GENERIC) Optimizer picks an inefficient qep and makes query take longer time to run. Bug 141515 II-11339 (GENERIC) Server returns wrong result for an outer join query that contains an 'is null' predicate on its ON clauses. Bug 141612 II-11446 (GENERIC) Sometimes dbms server crashes when update/modify and drop is done parallelly on x100 table. Bug 141688 II-11545 (VMS) Iana 2023c fails to compile.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/25/2023 10:06:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    There is a slow response of the Open Road Workbench when saving objects or code. Currently, it takes an average of 1-2 minutes to complete, causing delays in system development. Additionally, they are using the same code server for applications built in versions 3.5 and 4.1, but with a different database name for version 6.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/25/2023 15:07:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon reviewing the system performance of the server where the codes are currently stored, we have noticed that the CPU and disk usage spike when multiple (3) developers save their work simultaneously. In response to this, HDMF will migrate their codes to a server with better specifications. If the problem still persists, our next step will be to patch/update the OpenROAD workbench used by the developers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/06/2023 15:02:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF identified the cause of the slow saving time of their applications on OpenROAD. After removing all Image Trim fields on their application development, a significant change on the saving speed was apparent. The slow saving may be caused by the large size of the application due to the amount of images inserted on the imagetrim. DSI suggest of limiting the use of ImageTrim especially if inserting large image file size. This will cause the application to be larger in file size and may cause a corruption of the component with the ImageTrim. In replacement, you could use ImageField instead and then using the "FileHandle" method to load the image to the ImageField from a specific location. You could also utelize "Cursession.WorkingDirectory" to specify the location where the IMG(image file) is located.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/06/2023 13:08:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    When using "Insert Field from Database Table" functionality in tables with long names (e.g., insti_proponent_officer_techstaff) an error occurs stating "Table "insti_proponent_officer_techstaf" does not exist".

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/06/2023 14:55:46

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    According to Actian this is because OpenROAD only supports shorter object names (for tables, columns, etc.) - up to 32 characters.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/06/2023 13:38:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A problem was raised about OpenROAD components that cannot be deleted and is giving an error message that it is corrupted. This case was encountered before by Dsource Develoment Team before and a documentation was created to fix this problem. PLEASE NOTE: that the solution provided was given directly from Actian BUT is not supported. Meaning that precaution should be taken before doing this and this should be done on your own risk. Dsource encountered this problem before with using large icon image on our application or using large image on Image Trim fields. We suggest limiting the use of image trim since it will also increase the size of your application. In replacement of Image Trim, you could use Image Field instead and calling the image using FileHandle Method. Please see attached file for the solution on removing corrupted components.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/09/2023 13:36:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. Identify the Entity ID of the locked component. > SELECT * FROM II_LOCKS; 2. Confirm Component Name. > SELECT ENTITY_ID, ENTITY_NAME FROM II_ENTITIES WHERE ENTITY_ID = ; 3. Delete the LOCKED component from the II_LOCKS Table. > DELETE FROM II_LOCKS WHERE ENTITY_ID = ;

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/11/2023 12:54:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Checkpoint of production server (ingdb1a) last night failed. Looking at the log files to further investigate the problem.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/11/2023 15:53:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF sent checkpoint log and dbg file

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/12/2023 11:21:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per Actian, they could only see that the checkpoint process died and there are no further details pertaining to the database session which started the checkpoint in the errlog.log. They suspect the checkpoint process was terminated at the OS level. ingdb1a ::[II_JSP , 422 , 0000000000000000:00007fd7da180200, dmfjsf.c:3672 ]: Tue Oct 10 18:47:01 2023 I_DM105D_JSP_INFO A user is running ckpdb -v #x #m12 pfmdb ingdb1a ::[II_JSP , 422 , 0000000000000000:00007fd7da180200, dmfx100.c:1821 ]: Tue Oct 10 18:56:12 2023 E_VW1198_JSP_INFO Database: pfmdb, backup '2041' They are also looking at the checkpoint log warnings during the tar operation on the checkpoint that might have failed the process. I’m still clarifying the issue with regards to checkpoint template file. I will get back to you as soon as I have confirmed it. I was informed by Sir Alvin that the checkpoint last night was successful. Could you please send me the logs and dbg file. Thank you. Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/13/2023 10:39:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Stephen, Good day! Actian cannot really find anything on all the log files on why the checkpoint process failed last October 10. All they could see is the II_JSP process was spawned for the checkpoint and it got terminate/died. Later the Dead Process Detector(DPD) reported that the checkpoint process has died. Please check from OS end if there was something else running on the system which could have terminated the checkpoint process. Also please monitor the checkpoints, should the issue repeat again, please let us know. Thanks. Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2023 17:18:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_DM9055_AUDITDB_PRESCAN_FAIL and E_DM9034_BAD_JNL_NOT_FOUND errors while running an auditdb on production server. One possible cause for this sequence of errors is that one of the journal files to be read by the auditdb utility is missing from the database JNL location or compressed. Inglogs already sent to Actian for further analysis.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2023 17:28:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Noticed something peculiar with the journal files. Aside from j1506278.jnl is missing: -rw-------. 1 ingres ingres 5308928 Oct 13 19:41 j1506277.jnl -rw-------. 1 ingres ingres 10928640 Oct 13 19:35 j1506279.jnl Other journal files was written earlier than expected: -rw-------. 1 ingres ingres 15450624 Oct 13 19:41 j1506276.jnl -rw-------. 1 ingres ingres 5308928 Oct 13 19:41 j1506277.jnl -rw-------. 1 ingres ingres 10928640 Oct 13 19:35 j1506279.jnl -rw-------. 1 ingres ingres 10945024 Oct 13 19:35 j1506280.jnl -rw-------. 1 ingres ingres 9486848 Oct 13 19:36 j1506281.jnl -rw-------. 1 ingres ingres 17629696 Oct 13 19:38 j1506282.jnl -rw-------. 1 ingres ingres 9765376 Oct 13 19:39 j1506283.jnl -rw-------. 1 ingres ingres 9044480 Oct 13 19:40 j1506284.jnl -rw-------. 1 ingres ingres 17957376 Oct 13 19:42 j1506285.jnl -rw-------. 1 ingres ingres 8569344 Oct 13 19:44 j1506286.jnl -rw-------. 1 ingres ingres 12288512 Oct 13 19:53 j1506287.jnl -rw-------. 1 ingres ingres 12222976 Oct 13 19:58 j1506288.jnl Noticed that j1506277.jnl file was written on Oct 13 19:41 then journal files after that was written on Oct 13 19:35, 19:36 (much earlier time).

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/19/2023 12:55:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, Good day! With regards to your observation yesterday, about the missing journal file 1506278. It definitely has something to do with the auditdb error. On the archiver log file, $II_SYSTEM/ingres/files/iiacp.log, line 1125062, journal 1506276 is created at 19:24:49 line 1125236, journal 1506277 is created at 19:29:18 line 1125389, journal 1506278 is created at 19:33:17 One of the reason why the auditdb command failed, is certainly because the file 1506278 is missing. Thank you. Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/09/2023 14:06:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Lex, The main reason why E_DM9034 error happened while running auditdb is because the 1506278.jnl was missing. But then, Archiver process shows that the 1506278.jnl was created on October 19:33:17. Unfortunately, we have no trace on log files on what happened to the journal file, whether it was deleted or moved. I will be closing this case, please let me know if you need more help. Thank you. Regards, Manilyn

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/17/2023 09:47:39

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF requested a demo on how to install the openroad 11.2. They wanted to know how to use the license file to activate the openroad workbench upon installation.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2023 09:53:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    DSI conducted a demo at HDMF office to show how to use the license file upon installing openroad 11.2.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2023 13:31:38

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The discussion transpired yesterday 17-Oct-23. This is regarding the architecture and behavior of PFMDB tables schema across multiple database location that might help with the effective implementation of HPE Alletra's asynchronous replication a snapshot based data replication. Implementation has the following success criterias: 1. Consistent data replication on a storage level from PFMS/STLMS production server to interim Disaster Recovery Server. 2. Implementation of compression and data deduplication. 3. Optimum SQL performance. 4. Successful database backup using ckpdb and recovery via rollforwarddb on different database server/s. Action items: 1. HDMF will provide the SQL statement used for data consistency and performance testing to DSI. 2. DSI will determine the database location/s of the affected tables for testing. 3. HDMF will proceed with asynchronous replication on the specific database location/s. 4. HDMF will test the data consistency and performance. 5. DSI will create a use case on the implementation of quiescing during asynchronous snapshot.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2023 17:42:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The asynchronous data replication will be done on all database locations. Provided SQL scripts to be used for testing. runslow.pf_member_master01.sql https://www.dropbox.com/scl/fi/yt9fznr29d4783923dtbm/runslow.pf_member_master01.sql?rlkey=w1tfr5z62d5upkrcd5tuxrj1o&dl=0 runslow.pf_member_master03.sql https://www.dropbox.com/scl/fi/6c846euolwukc58lwyp58/runslow.pf_member_master03.sql?rlkey=pvp127bhx7tv1qe734biorq67&dl=0 Already benchmarked the above SQLs. We strongly suggest to at least run each SQL twice per scenario.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/18/2023 18:05:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF environment and replication diagram

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/23/2023 16:05:32

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    There's a good news and not-so-good news. Good news is that Ingres/Actian X 11.x has a quiesce function. "Quiesce" function in Ingres stops the Communications Servers (iigcc) after all current sessions have terminated or disconnected. Whereas, "Stop" function force stop all the iigcn in an instant. Syntax: Netutil -file- stop | quiesce The not-so-good news is that the use the quiesce function will prove challenging in HDMF's scenario due to the following reasons: 1. The behavior of quiesce is that it will temporarily block all new and incoming connections by restricting the iigcc. 2. Meaning, all users who terminated and/or disconnected all their connections to the server, cannot go back until the iigcc has started again. 3. Meanwhile, if a certain user did not terminated and/or disconnected his/her connection, iigcc cannot continue to stop and will be stalled until all user/s disconnects. 4. In addition, while the iigcc is at stall, rules still apply that all new and incoming connections are temporarily blocked. Possible resolution: 1. Test the use case of quiesce carefully and create a policy supporting this approach 2. Once a day, prior to the issuance of quiesce, help desk will announce an of calm/quiet time for operation 3. DBA will issue a quiesce command 4. DBA will check all active connections without current transaction/s, and force disconnect until quiesce completely stops the iigcc 5. of calm/quiet time will be used for HPE Alletra's asynchronous replication 6. After item# 5, restart iigcc by issuing an ingstart -iigcc 7. Check if all users can already connect to the database server

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/08/2023 14:46:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Will be closing this case now. Should you have any other concern, please feel free to contact us.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2023 10:06:55

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Question raised during the 2nd Batch of Advanced Training by Sir Robert Pilapil. On how to manage and limit developer access to certain components or application to set a restrictive approach on shared development.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2023 10:12:36

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Comments from Actian Support regarding this question: Basically, when users have access to a development repository, they can also access all the applications/components in the repository. Even components that are “Saved Private” can be viewed (but not edited) – at least the version that has last been checked in. If you want to prevent the View, you’d have to provide developers all other components in included application(s) that reside in image file(s), thus the source is stripped from the component. But this will of course make development harder, i.e. as a “Step Into” in the Debugger cannot step into any components residing in an image file.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/03/2023 10:16:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    For effective teamwork we prefer the following approach (which we use internally): > Every developer has its (his/her) own repository database – this can be a local database or a “private” database on a shared DBMS. > Thus, the developers are not restricted in their work and several developers are able to work in parallel (even on the same component). > Once developers are ready to submit a change (which can involve several components – also from several applications), the components are exported into XML export files: > One directory for each application containing: > one XML export file for each component > one XML export file for the application properties (using “- appsource” flag of “w4gldev backupapp out) > The export files are under control of an SCM (Software Configuration Management) like “git” (Bitbucket) > Once the developer wants to submit the changes to the repository of the SCM (changed/added/deleted files), there is a “Code Review” process going on. > The file submission into the central repository will only happen after reviews and approval by peers/authorized users (“Pull Request” in git/Bitbucket). > Other developers can get the new component versions from the SCM repositiory after the change has been merged. > The build of a daily build or release of the application(s) will be done using the applications/component export files contained in the SCM repository > This could even be done using a newly created database, into which all the required export files are imported before doing makeimage.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/06/2023 17:11:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As part of the project of migrating OpenROAD applications to the latest version. An update also surfaced that the Appserver/DCOM setup might be decommision in the future and a move to Appserver/JSON setup is imminent. To start identifying all the changes to be done, Sir Sherwin Astorga with the Go-signal of Sir Florencio Cortez provided DSOURCE with a sample program that utilizes DCOM connection to migrate it to JSON connection.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/20/2024 15:32:56

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Answers from previous concerns and questions raised during the presentation of the converted application to JSON-RPC setup. - Verify the length of StringObject Value attribute • The "value" attribute is indeed can only contain 2000 characters but the StringObject System Class doesn't have a limit. This will not be a problem since the only procedure that's using "value" attribute is the RPC-Request which may not reach 2000 characters. The RPC-result on the otherhand will definitely reach more than 2000 characters but the "value" attribute was never used. - Use the JsonObject to Object function to eliminate looping to get values from the reply string • This was done successfully (please refer to the PDF file attached). This process will require a UserClass on the Client-Side to hold the data parsed from the RPC-Response. - Populate the database to test response time from the server. • The database was loaded with three thousand rows of record and there was a little delay experienced (This is on a Client-Server setup on a single laptop. Further testing are being done to check the response time from the server. - Create additional table to test nested array behaviour on JSON • As expected, there was no problem encountered on this kind of setup. the RPC-Response just created an array within the array that's already on the original setup. (Please refer to the PDF attached)

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 17:56:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource presented their findings on the added testing requested by Sir Sherwin Astorga. The concern about security and performance is still there so Dsource will do testing and research with regards to this matter.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/12/2024 12:22:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    A POC was triggered to convert an existing OpenROAD application to JSON-rpc setup. A new case was created to monitor this POC. Please refer to Case No. 2024-0008.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/08/2023 17:13:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource was provided with a sample application, Appserver Image and a database schema. Dsource were able to setup the AppServer and running the UI trigger's a session on the app server. Though a message appears "Connection is unsuccessful, please try again." It is still unclear if this is because of a connection problem or because there are no record on the database. Dsource is still asking to verify this message and if possible, have a sample test data to populate the database.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/21/2023 12:06:29

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HDMF configuration was succesfully set-up at Dsource Office and the process of learning and conversion of the current setup has started. Dsource has also succesfully setup a http-jsonrpc routing to be use for this activity.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/29/2023 18:17:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Succesful creation of sample application with Application Server Image registered to VOSA and JSON configuration files setup. Successful call from Client UI sending and receiving request via JSON. Next Step - application of changes to HDMF-provided sample DCOM application to make it JSON compliant.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/08/2023 16:09:14

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Change of plan due to complication. Dsource development team has to fix the sample application created to work as a fully working application. Not just sending and receiving request and response, but also placing the data gathered to a list view or Entryfield.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/15/2023 15:12:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Successful result on the convertion of JSON response to OpenROAD variable to be readily available to use on any operation on the OpenROAD side. Experimentation and testing have been done to check for the most efficient way of converting JSON response to OpenROAD variable, especially when dealing with arrays or set of data in a table.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/05/2024 12:01:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sending request to server with specific information thrown to accomodate specific search on a query has been done. This took a while since the simple application is evolving into something more complex and various errors have been discovered and fixed. After this, the team has to integrate everything to the sample DCOM application and present the findings.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/02/2024 16:49:55

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The sample application provided was successfully converted to a JSON-RPC Server-Client Application. Dsource was able to test the responce from the Application Server Image to be correct but still need to trace and fix some irregularity with the results. The sample application was stripped down to 3 application (App Server, Connection, UI) to build a necessary application that can interact with the database, the same way how the DCOM Application works. No changes was done to the Business Object Userclass to minimize the changes.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/15/2024 11:29:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Result of the converted application was presented to Sir Sherwin Astorga. Concerns are raised regarding the following: - Complexity of the change needed to be done - Security from outside access - JSON handling complex multiple query and nested array Additional test was requested to further study the JSON conversion method. - verify the length of StringObject Value attribute - Use the JsonObject to Object function to eliminate looping to get values from the reply string - Populate the database to test response time from the server - Create additional table to test nested array behaviour on JSON Some research must also be done including other variable types and security features for JSON type connection.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/07/2023 16:16:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    There was a problem with the dump file 500451 associated with the checkpoint 2088 that stops the rollforward. Currently on the Actian Engineering Team to further investigate the cause.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jan/05/2024 11:54:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    E_DM935A_BAD_DMP_LENGTH would occur when there is a mismatch in what we have read and the length we were expecting to read in the dump file. This error would generally occur when the rollforwarddb is performed across different patches, which is case here as the source and target patches are different. But the rollforwarddb with checkpoint 2089 was successful with the same patches. The problem might be during the generation of the checkpoint itself. To check further on this, we need you to perform rollforwarddb with checkpoint 2088 on to a different test machine and see how it goes. NOTE: Before proceeding with performing rollforward, kindly perform cksum file for dump 500451 on both source and target servers and check if the value is same.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/30/2023 16:36:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After upgrading to 11.2, stored procedure from hfdcs database got "No MST is currently in progress, cannot declare another cursor" error while running the application. The application was created with Visual Studio and uses Ingres.Client.dll in .NET to call on the web services. The "No MST" error shows on the application only from time to time.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/13/2023 15:22:04

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon client's testing, it appears that the cause of error was one of the other stored procedure (named sp_tm_evaluation_set) that triggers an error “DUPLICATE KEY ON INSERT detected.”, and upon proceeding to the concerned stored procedure sp_tm_evaluation_update, the error “No MST is currently in progress, cannot declare another cursor” occurs. The client added the rollback statement in the negative case part of the stored procedure sp_tm_evaluation_set and the “No MST… ” error has been resolved.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/22/2024 18:12:45

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    INGDB1A was down earlier due to some hardware failure. After thr server was up, Sir Stephen performed a rollforward. After rollforward, the database became inconsistent, they ran 'sql -A10' against pfmdb and the datababase became consistent again. Currently, Sir Sherwin is performing some testing for the database. DSI will further investigate the logfiles.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/23/2024 19:59:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    February 22, 2024 19:00 Run pfmdb ckpdb -v #x #m12 pfmdb on ingdb1a February 22, 2024 01:00 Running ckpdb -v #x #m12 pfmdb completed 07:00 The server ingdb1a was down because of hardware failure (memory) 09:30 Rerouted to ingdb2a The database was down because DBLOC1 has no data. CKPT2 was mounted instead of DBLOC1 Attempted to run rollforward but failed because of I/O error due to file system incompatibility (DBLOC1 and CKPT2 has different file system type) Attempted to run the rollforward for the 2nd time but failed 14:30 Rerouted again to ingdb1a 14:45 Run rollforwarddb pfmdb +c +j #x #c2158 #m12 on ingdb1a 17:00 Finished running rollforwarddb pfmdb +c +j #x #c2158 #m12 with some inconsistency. ‘sql -A10’ was run against pfmdb to patch inconsistency 18:45 Usermod on affected tables: -pf_ledger_21_25 -pf_ledger_79_00 -pf_ledger_01_05 -pf_ledger_06_10 -pf_ledger_11_15 - pf_ledger_16_20 February 23, 2024 05:45 HDMF reported to DSI that there’s discrepancy on the data between ingdb1a and data_warehouse. 12:38 Run rollforwarddb pfmdb -j -e #x #c2158 #m12 on ingdb1a As of writing, there is on-going replaying and/or testing of data.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/29/2024 19:50:19

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    February 23, 2024 Continuation: 16:00 Initial testing of rollforwarddb went well. HDMF restored the journals using home grown utility tool. Unfortunately, some data are still missing. Februay 24, 2024 10:00 Upon checking, the data loaded on ingdrdb duplicates of what is loaded data on data_warehgouse. As next step, HDMF will perform checkpoint on ingdrdb and then copy the checkpoint files on ingdb1a to perform rollforward. 18:45 Checkpoint on ingdrdb started.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/29/2024 19:59:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As of February 25, 2024 05:00 Checkpoint on ingdrdb finished. Copying of checkpoint files from ingdrdb to ingdb1a started. 12:40 Copying of checkpoint files from ingdrdb to ingdb1a finished. 12:47 Running rollforwarddb pfmdb +c -j #x #c2160 #m12 on ingdb1a started. 13:12 Running rollforwarddb pfmdb +c -j #x #c2160 #m12 on ingdb1a completed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/12/2024 13:42:28

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    On February 23, 2024 Due to service disruption on ingdb1a, the test server ingdrdbclone was downgraded to Actian X 11.1 as one of the back up servers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/12/2024 13:46:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    As per investigation. The journal files were corrupted due to failed failover and rollforward to ingdb2a. Kindly see attached Incident Report for more details

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 16:48:10

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After an unsucessfull rollforward on VW locations, there's a checkpoint error on VW/X100 server

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 16:59:39

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    These are the steps taken to resolve the error. 1. Check errlog.log, vectorwise.log 2. Check ownership of all pfmdb directory and change ownership to ingres for directories with root 3. Checked /II_DATABASE/ingres/data/vectorwise/pfmdb/wal/location_map and found out that it contains only default,data,/II_DATABASE/ingres/data/vectorwise/pfmdb/CBM/default 4. Restore / recreate location_map from backup to contain all the necessary locations. 5. Checked existing db_key from /II_DATABASE/ingres/data/vectorwise/pfmdb/CBM and compared to all db locations 6. Copied master db_key to all db locations 7. Tried running checkpoint again but with same error. 8. Copied master db_key to work locations 9. Successfully ran checkpoint.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 17:05:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Creating this case to investigate on the journal files creation and integrity for checkpoint sequence 2158 for journals 1605757 to 1606259 21-Feb-24 Wed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 17:21:48

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    To check if such inconsistency in the creation of journal files will re-occur again, we strongly recommend to refresh the archiver on the pfmdb database by disabling it and enabling again by offline checkpoint. ingstop -dmfacp alterdb -disable_journaling pfmdb ingstart -dmfacp ckpdb +j pfmdb Initial schedule for this is on Saturday 2-Mar-24.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/04/2024 13:34:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Stephen Molina performed the archiver (dmfacp) restart on a database level using the recommended actions. Checkpoint procedure was successful on 3-Mar-24 Sunday 00:02:40. Rollforward procedure on Cebu DR site was successful on 4-Mar-24 Monday 05:52:36. We recommend to continue with the rollforward procedure everyday on a DR site and send us the following: 1. inglogs of ingdb1a every after checkpoint 2. checkpoint debug file 3. rollforward debug file

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/04/2024 13:34:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Stephen Molina performed the archiver (dmfacp) restart on a database level using the recommended actions. Checkpoint procedure was successful on 3-Mar-24 Sunday 00:02:40. Rollforward procedure on Cebu DR site was successful on 4-Mar-24 Monday 05:52:36. We recommend to continue with the rollforward procedure everyday on a DR site and send us the following: 1. inglogs of ingdb1a every after checkpoint 2. checkpoint debug file 3. rollforward debug file

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/04/2024 13:34:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Stephen Molina performed the archiver (dmfacp) restart on a database level using the recommended actions. Checkpoint procedure was successful on 3-Mar-24 Sunday 00:02:40. Rollforward procedure on Cebu DR site was successful on 4-Mar-24 Monday 05:52:36. We recommend to continue with the rollforward procedure everyday on a DR site and send us the following: 1. inglogs of ingdb1a every after checkpoint 2. checkpoint debug file 3. rollforward debug file

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/22/2024 17:56:42

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    An error was encountered when using Web Browser Control, the client have identified that the DLL iWebBrowser depends on the End-of-Life Internet Explorer instead of MS Edge/Chrome/Safari, and it is understand Microsoft replaced it with a non-ActiveX control called WebView2. The concern was is there a new version of the Web Browser Control or an alternative solution to this.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/26/2024 18:04:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    addEventListener() is a JavaScript method, and the old Microsoft WebBrowser Control does not support modern HTML pages (with current JavaScript stuff). We would recommend you to upgrade OR6.2 to OpenROAD 11.2 that comes with WebView2 support - see according documentation: https://testdocs.actian.com/openroad/11.2/index.html#page/RelSum/WebView2_Updates.htm https://testdocs.actian.com/openroad/11.2/index.html#page/LangRef/Url_Method. Alternatively, you can use the "CALL SYSTEM" statement to open the web site externally (in a separate web browser window like Edge, Firefox or Chrome).

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Feb/29/2024 04:32:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Started preconfiguration of Facial Recognition demo unit.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/29/2024 12:06:57

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    All devices are setup on the agreed configuration. Complete names are added to the database and QR codes are generated from HikCentral. Next step is the official announcement to use the device by the participating employees from both Petron Megaplaza 18th floor and JELPS 15th Floor.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/10/2024 16:14:20

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Still no Go-Signal from the HR to proceed with using the installed terminals for both JELP 15th Floor and Petron Megaplaza 18th floor. This delay was due to busy schedule of HR Dept for their Sportsfest. Dsource raised concerns about the availability of the devices installed since it was just loaned from HikVision and might be pull-out soon. Sir Neil Balderas mentioned that there might be a feedback by the Third Week of June with regards to this. Dsource is just in stand-by for Support.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/25/2024 15:15:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    HR gave the go-signal to use the Facial Recognition Devices

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/04/2024 19:23:27

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Meeting with SIr Neil Balderas to set the Demonstration date for Facial Recognition for Time-keeping System. Demo was set on April 30, 2024 (Tuesday) at 2:00PM. Attendees will be: Dsource: Chris Delgado, Rowell Magno, Kylle Azul HikVision: Miguel Sarmiento, Morning Xu HDMF: Anthony Cristobal, Neil Balderas, Isaganie Babiano, Jonathan Haber

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/30/2024 19:24:09

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Successful demonstration of Hikvision device. Next step is to install everything to their system for actual testing with actual employees.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/08/2024 19:24:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource managed to register some of the employees from Petron Megaplaza, specifically from the HRDD, HRMD, and HRSG departments, via face capture and fingerprint on the Facial Recognition device

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/15/2024 19:25:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Sir Anthony of HDMF received the POC document for the Facial Recognition Project. Dsource also checked the area where the FR device will be installed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/15/2024 19:25:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource managed to install the facial recognition device on JELP office. Waiting for Sir Anthony to connect it to their network and provide its power.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/21/2024 19:26:31

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The facial recognition device on Petron Megaplaza was mounted and working

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/22/2024 19:29:58

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Configured the FR device on Petron Megaplaza through HikCentral and all the test transactions from 05/21/24 to 05/22/24 were pushed to their database

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/23/2024 19:31:13

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Discussed the changes on the POC parameters. Due to initial testing, HDMF decided to use 2 factor authentication to eliminate multiple accidental log-ins. They also opted to use QR + Face authentication to avoid touching the device.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/11/2024 17:20:02

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    We would like to request a copy of lichostinfo and version.rel of all your Database servers and Application servers for the annual self-audit and license issuance for June 2024.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 17:21:15

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Lichost and version.rel sent

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/11/2024 17:35:53

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Please ignore this if you receive this email. This is just a Test.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/11/2024 17:43:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Please ignore this comment.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 16:00:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    this is a comment

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/12/2024 10:44:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource discussed with Sir Sherwin the POC that they are going to setup for JSON code conversion. Sir Sherwin identified the application that is going to be convert and its processes. First step is to secure a NDA for the source codes Dsource were going to handle. Dsource then discussed with Ms Marinella Alindog the process of the NDA, apparently, it can be set-up directly with Sir Sherwin. Dsource will be drafting an NDA and start processing the POC.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/11/2024 13:49:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    POC document sent for signature and requirements to start the POC was requested.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2024 13:51:15

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    POC document signed and received back by DSOURCE. Source code was provided and passed through Sir Alvin Tabarrejo. Original code was configured to fetch information from a test database and is running. Application for conversion is the "Pag-IBIG Fund Business Intelligence Reports Management System" COnversion to a JSON setup started.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/08/2024 19:45:28

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Conversion Status: Still converting frames mainly for extraction, export, and report catalog . All frames are partially modified just to show the data. Created a 4gl procedures and modified frames for local testing. Needs further modification to pass all data especially the report details frame. Will upload the application[rms_appserver] in the app server with another application [rms_procedures] since they're interconnected. Issue: Encountered an issue wherein upon converting the login frame for local testing there is a discrepancy with the details while using the same credentials

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/13/2024 19:46:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upon further modification, was able to identify the issue and managed to solve it. The issue occurs when a procedure is called and populates the object(user class) that essentially overwrites the objects that are connected in the entry fields ( i.e. username and password). Resolved the issue by redeclaring the user class in the UI frame and populating the existing one based on the data fetched. Details Discrepancy Issue - Solved

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: May/21/2024 19:49:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    On-going conversion of DCOM to JSON. Uploaded the application img to app server. Experiencing 'method not found' to some procedures when called, further troubleshooting is required.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/10/2024 15:50:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Encountered an issue where a whole UserClass was needed to pass as a parameter to another UserClass. Since the remote request parameter only accepts a string/varchar datatype, still trying to figure out a way to pass the whole UserClass as a parameter. Code Example: ReportExport.UserInfo = UserInfo.duplicate(); Tried converting the UserClass to a JsonObject and pass as a string to JSON-RPC request but was unsuccessful. Had a discussion with Sir Sherwin Astorga about this and he mention that he did it to lessen the code and make sure everything is copied from client to server. Dsource offered an alternative to create a ready duplicate of the UserClass to the Server side and just copy all the attribute values instead of the whole UserClass. He agreed and gave the Go-Signal to proceed.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/10/2024 17:07:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Was able to convert frm_login and frm_main successfully via the byref_param approach. frm_login • Fixed where the method doesn't return anything. frm_main • Tried the approach to pass the whole user class via JSON request using byref_params. • Was able to get the expected value. frm_report_export • partially converted to show data. • some procedures have duplicate functions. frm_report_extract_to_excel • partially converted to show data. some procedures have duplicate functions.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/21/2024 12:33:23

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource have finished the conversion of BIRMS from DCOM to JSON-RPC server-client configuration. A POC - Result Document was created to specify all outputs and challenges encountered during the POC.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/17/2024 03:34:01

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After upgrading the operating system (RHEL 9) of ingdb2a (HLMS) the iimgmgtsvr went missing.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/17/2024 03:45:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. cd /II_SYSTEM/ingres/utility 2. iisumgmtsvr 3. ingprenv -- II_MTS_JAVA_HOME=/II_SYSTEM/ingres/jre should be on ingprenv already 4. If II_MTS_JAVA_HOME=/II_SYSTEM/ingres/jre already on ingprenv, edit config.dat and add the following line: iisetres ii.ingdb2b.ingstart.*.mgmtsvr 1 5. ingstop 6. ingtstart 7. ingstatus -- to make sure iimgmtsvr started 8. ingstop 9. ingstatus 10. Check if iimgmtsvr is still running. If yes: Run iimgmtsvr -stop 11. Run ingtstatus -- all services should be stopped. 13. Run ingstart -- mgmtsvr should automatically start

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2024 11:27:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    In compliance with HDMF's request for stand by support during the upgrade of ingdb1b's upgrade of operating system to RHEL 9.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/23/2024 11:27:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    In compliance with HDMF's request for stand by support during the upgrade of ingdb1b's upgrade of operating system to RHEL 9.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/04/2024 12:41:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After upgrading to RHEL 9.x, EMA shows publickey error on database server

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/04/2024 12:41:22

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    After upgrading to RHEL 9.x, EMA shows publickey error on database server. RHEL 9 has tightened security and deprecated a number of algorithms and ciphers. It's most likely that the ssh key that we are trying to use does not meet the new requirements.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/04/2024 12:49:55

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    To check if there's error in Nagios docker exec ema /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg Run to reset the ssh key to the target database server docker exec -it ema ssh-copy-id -i /usr/local/nagios/etc/ssh/id_rsa ingres@172.16.226.231 restart the docker docker exec ema /etc/init.d/nagios restart

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2024 11:38:54

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. Login to the EMA Server 172.17.248.106 2. Remove the entry of the target server from the /home/ingres/ema/ema/nagios/etc/ssh/known_hosts 3. Login to the target server 172.16.226.231 4. Remove the entry of the EMA Server on the /home/ingres/.ssh/authorized_keys 5. Login to the EMA Server again 6. Ran docker exec -it ema ssh-copy-id -i /usr/local/nagios/etc/ssh/id_rsa ingres@172.16.226.231. 7. Ran docker exec ema /etc/init.d/nagios restart 8. Go to nagios browser but still having errors Note: Suspected that ssh id (id_rsa) on EMA Server needs updating to support RHEL 9.x OS. For further investigation and testing

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Apr/17/2024 17:09:52

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    1. Login EMA Server 2. Go to /home/ingres/ema/ema/nagios/etc/ssh 3. Backup id_rsa and id_rsa.pub 4. Generate new ssh-key using command ssh-keygen -t ed25519 5. Save as /home/ingres/ema/ema/nagios/etc/ssh/id_rsa 6. Login to target server -- legacypdcsvr 7. Go to /home/ingres/.ssh 8. Remove entry from file authorized_keys 9. Login EMA Server 10. Go to /home/ingres/ema/ema/nagios/etc/ssh and run docker exec -it ema ssh-copy-id -i /usr/local/nagios/etc/ssh/id_rsa ingres@172.16.226.231 ssh ingres@172.16.226.231 docker exec ema /etc/init.d/nagios restart 11. Check on Nagios browser NOTE: ssh-keygen -t ed25519 applicable only for RHEL7,8,9

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/11/2024 11:05:47

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Ms Dyojie Lapuz send a request for assistance on consuming Web Service Data using OpenROAD. The request originated from the requirement of integrating Registration System of Pag-ibig Fund with PhilSys System.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/13/2024 11:18:07

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    The document from PhilSys was shared to Dsource stating the instruction on integrating the System.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/18/2024 11:48:49

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Dsource Sent a sample code on sending JSON-RPC request from an OpenROAD application. DECLARE request = stringobject; reply = stringobject; ENDDECLARE BEGIN CurRemoteServer.Initiate(image = '', type = RP_SHARED, location= 'http://100.100.111.15:8080/openroad/app', routing='http-jsonrpc'); request.Value =' {"jsonrpc": "2.0", "id": 1, "method": "go", "params": {"p_this": {"fname":"Cruz","lname":"Juan","mname":"De la"}, "$byref_params":"p_this"}}'; reply = CurRemoteServer.JsonRpcRequest(request=request); END

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jun/18/2024 15:11:35

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Jan Edmond De Vera send out specific code for calling REST API via OpenRoad client. This code uses Microsoft XML 6.0 external library to call HTTP requests. DECLARE http = winhttp!XmlHttp60; rstr = stringobject; hr = INTEGER NOT NULL; url = varchar(2000); ENDDECLARE BEGIN http.Open('GET', 'https://url/xample', FALSE); http.setRequestHeader('accept','application/json'); http.setRequestHeader('authorization','api token'); http.Send(); rstr = http.responsetext; MESSAGE 'RESPONSE:' + HC_NEWLINE + '-' + rstr.Value + '-'; END

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/02/2024 15:13:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Batch 7 for the Introductory training of Actian X and OpenROAD for newly hired developers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Jul/02/2024 15:13:33

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Batch 7 for the Introductory training of Actian X and OpenROAD for newly hired developers.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Oct/06/2024 14:15:34

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Using visual DBA 10.2, there are no stored procedures showing in the DBA

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/10/2024 14:16:26

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Upgrading the current visual DBA of client from 10.2 to the latest (11.2)

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/29/2024 14:20:25

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Using standalone installer of Actian OpenROAD 11.2, error occurs when using 'tables' to a database instance via vnode

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/10/2024 14:22:50

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Actian identified this as a bug in Actian 11.2, this error is currently on patch with Actian.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Sep/30/2024 14:30:18

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    AN ERROR OCCURS WHEN INSTALLING AND OPENING VOSA

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/10/2024 14:47:37

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Error has been resolved by using the latest installer (patch 20026). Link given by the actian support also helps us to resolve this issue

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Nov/11/2000 14:50:41

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    There is an issue where changes within user classes are not taking effects unless we closes the whole workbench. This issue is within the actian engineering team, and is awaiting for resolution.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Dec/11/2024 15:18:47

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Client encountered session limit errors. Upon checking the inglogs, E_CL1613_PC_SP_PROC and E_CL2539_THREAD_CREATE_FAIL have seen on the error log. Also "Resource temporarily unavailable" whenever they tried to switch to user ingres.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/05/2025 16:08:40

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Slowdown on parallel checkpoint for multiple data locations. Apparently, it is not seems to be doing a parallel checkpoint even though it has a #m12 flag.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 16:24:00

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Spencer, If you happen to do the checkpoint this weekend. Can you send me the following files: 1. Inglogs before and after checkpoint 2. debug/output file of the checkpoint 3. exact command of the checkpoint with #m12 flag If you can do the same comparison for #m12 and #m13, just send me the exact ckpdb command that you used for the checkpoint. Thank you! Regards, Chris

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/05/2025 16:06:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Eservices (onlinesvr) which accommodate different online applications of HDMF. Error log show locking on several tables of virtual_branch database such as: vb_claims_app_public_master reg_usernames vb_request_master reg_loyaltycard_link_requests IPM shows sessions hanging while processing database procedures like vb_user_code_hist and vb_insert_mem_user_code_hist

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/05/2025 16:11:44

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    It seems that the details from the iifile_info of a table is not accurate upon checking on the locations. No file found.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 17:19:59

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Hi Sir Spencer, Can you run and send me the output file help table pf_ledger_21_25 Thank you! Regards, Chris

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 16:09:11

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    dsf

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 16:12:51

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    new comment

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    COMMENTS:

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge: Mar/06/2025 17:27:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    test

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    SOLUTION :

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Date Acknowledge : Mar/06/2025 17:27:17

                                                                                                                                                                                                                                                                                                                                                                                                                                                                    Error has been resolved by using the latest installer (patch 20026). Link given by the actian support also helps us to resolve this issue