Details
-
Type:
CR
-
Status:
Cancelled
(View Workflow)
-
Priority:
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
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 3 hours
-
Work with L3 to check the issue and analyze the log then L3 shared query for run to fix.
-
- Time Spent:
- 1 hour
-
follow up on DB refresh action schedule with concerned team
-
- Time Spent:
- 2 hours
-
Troubleshoot for run the API and schedule db refresh script and confirmed to L3.
-
- 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.
