Details

    • Type: CR CR
    • Status: Cancelled Cancelled (View Workflow)
    • Priority: Normal Normal
    • Resolution: Unresolved
    • Component/s: NEP
    • Labels:
      None Labels
    • Customer:
      Zain KSA 3.X

      Description

      From: Suleiman Kiplangat <Suleiman.K@cybermak.net>
      Sent: Friday, November 7, 2025 3:10 PM
      To: Daljeet Singh Virdi <Daljeet.Virdi@mobinets.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>
      Cc: ALM Support <ALM.Support@cybermak.net>; support <support@mobinets.com>; Kosi Ali <Kosi.A@cybermak.net>; Marwan Yousef <Marwan@cybermak.net>
      Subject: RE: KSA - NEP Inventory sync issue vs NEP DB View

      +++ updating subject.

      From: Suleiman Kiplangat <Suleiman.K@cybermak.net>
      Sent: Friday, November 7, 2025 3:43 PM
      To: Daljeet Singh Virdi <Daljeet.Virdi@mobinets.com>; Abir Messaikeh <Abir.Messaikeh@nuiva.com>
      Cc: ALM Support <ALM.Support@cybermak.net>; support <support@mobinets.com>; Kosi Ali <Kosi.A@cybermak.net>; Marwan Yousef <Marwan@cybermak.net>
      Subject: NEP Inventory sync issue vs NEP DB View vs
      Importance: High

      Dear Daljeet/Abir,

      Kindly note that we have identified an issue where the NEP Inventory report is not syncing to the NEP DB view as expected.
      Site matching was done earlier, resolved on Inventory, but still reporting Auto_Site in DB View.

      Sample nodes with an issue in the DB view but okay in Inventory..

      AQQ2170_01
      AQQ2331_01
      AQQ2424_01
      AQQ2425_01
      AQQ2426_01_NNN
      BAH2152_01
      BHAB2124
      BHMF2137
      BHMF2336_02
      BHS2361_NNN
      BRQ2219_02
      BSA2313_01
      BSA2313_02
      BSA2316
      BSA2318
      HJR2254
      HLA2419_01
      JDJZ2071_01
      JDJZ2418
      MTB2377
      MUMA2070
      MUMA2337
      QLW2370_NNN
      QLW2374_01
      QLW2376_01
      SRA2353_01
      SRA2353_02
      SRA2355
      SRA2359_01
      SRA2359_02
      SRA2362_01
      SRA2362_02
      SRA2362_03
      TBL2297_01
      TBL2319
      TBL2328_01_NNN
      TNM2082_01
      TNM2088_01
      TNM2093

      We request your urgent support to resolve this ASAP.

      Best regards,

      Suleiman Kiplangat
      ALM Support Team
      CyberMAK Information Systems

        Activity

        Manjit Kumar logged work - 07/Nov/25 12:00 AM
        • Time Spent:
          3 hours
           

          Work with L3 to check the issue and analyze the log then L3 shared query for run to fix.

        Abir Messaikeh logged work - 10/Nov/25 12:00 AM
        • Time Spent:
          1 hour
           

          follow up on DB refresh action schedule with concerned team

        Manjit Kumar logged work - 10/Nov/25 12:00 AM
        • Time Spent:
          2 hours
           

          Troubleshoot for run the API and schedule db refresh script and confirmed to L3.

        Manjit Kumar made changes -
        Field Original Value New Value
        Gantt Options Milestone (set to milestone: having a due date but zero effort)
        Planned Start 2025-11-07 24:00 (milestone: set planned start date to due date)
        Planned End 2025-11-07 24:00 (milestone: set planned end date to due date)
        Hide
        added a comment -

        The following script was executed on the KSA database to refresh the database view:

        EXEC DBMS_MVIEW.REFRESH('NE_VIEW');

        Show
        added a comment - The following script was executed on the KSA database to refresh the database view: EXEC DBMS_MVIEW.REFRESH('NE_VIEW');
        Khaled Khalil made changes -
        Assignee Khaled Khalil [ kkhalil ] Bessem Manita [ bmanita ]
        Marwan Kanaan made changes -
        Component/s NEP [ 16200 ]
        Khaled Khalil made changes -
        Assignee Bessem Manita [ bmanita ] Mustapha Al-Hage [ malhage ]
        Hide
        Bessem Manita added a comment -

        Dear Manjit,
        As mentioned earlier by Abir, the API was disabled, so it’s better to keep it as is and handle the DB refresh separately.
        Kindly proceed with creating a new cron job specifically for the DB refresh as done below.

        call REFRESH_ASSET_VIEWS();

        BR,

        Show
        Bessem Manita added a comment - Dear Manjit, As mentioned earlier by Abir, the API was disabled, so it’s better to keep it as is and handle the DB refresh separately. Kindly proceed with creating a new cron job specifically for the DB refresh as done below. call REFRESH_ASSET_VIEWS(); BR,
        Abir Messaikeh made changes -
        Status Open Bug [ 10108 ] Dev Scheduled [ 10014 ]
        Abir Messaikeh made changes -
        Issue Type Bug [ 1 ] CR [ 10900 ]
        Workflow Mobinets_Dev_BugWF_J4.4 [ 198000 ] Mobinets_Dev_WF_J4.4 [ 198013 ]
        Abir Messaikeh made changes -
        Status Dev Scheduled [ 10014 ] Cancelled [ 10013 ]
        Abir Messaikeh made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 hour [ 3600 ]
        Worklog Id 282968 [ 282968 ]
        Abir Messaikeh made changes -
        Baseline Start 2025-11-07 24:00 (set baseline based of initial work logging)
        Baseline End 2025-11-07 24:00 (set baseline based of initial work logging)
        Manjit Kumar made changes -
        Time Spent 1 hour [ 3600 ] 4 hours [ 14400 ]
        Worklog Id 283003 [ 283003 ]
        Manjit Kumar made changes -
        Time Spent 4 hours [ 14400 ] 6 hours [ 21600 ]
        Worklog Id 283009 [ 283009 ]
        Manjit Kumar logged work - 12/Nov/25 12:00 AM
        • Time Spent:
          2 hours, 9 minutes
           

          Checked import status along with analyze the log and after finish import & db view refresh checked data status from db and shared output to cybermak tame late night.

        Manjit Kumar made changes -
        Time Spent 6 hours [ 21600 ] 1 day, 9 minutes [ 29340 ]
        Worklog Id 283220 [ 283220 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Bug Open Bug Dev Scheduled Dev Scheduled
        8h 48m 1 Abir Messaikeh 10/Nov/25 2:46 PM
        Dev Scheduled Dev Scheduled Cancelled Cancelled
        1m 32s 1 Abir Messaikeh 10/Nov/25 2:47 PM
        Subversion JIRA

        Links Hierarchy

         Documentation

        Invalid license: EXPIRED

          People

          • Assignee:
            Mustapha Al-Hage
            Reporter:
            Manjit Kumar
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 9 minutes
              1d 9m

                Drag and Drop