Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: Financial
-
Labels:None Labels
-
Customer:Zain Kuwait
Description
Customer has raised issue for the attached nodes SN present in the Unmapped and FR as well.
After did analysis , it has been observed that the asset first Financialised under Active Inventory later it got decommissioned and again inserted via Generic Connector with same SN but sync didn't work and result in two different records present in both Unmapped and Financial Report with same SN.
Kindly check and do rectify the same.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 4 hours
-
Run the script and restart the nep after working hours.
-
- Time Spent:
- 3 hours
-
Validate the duplicate sn and have call with L3 to discuss the duplication in the network
-
- Time Spent:
- 4 hours
-
Validate the Passive Data and update the Serial number manually for the assets, also delete few assets manually as told by Dev team, then engage cybermak to run the script and nep restart, after reatrt check nep ok or not
-
- Time Spent:
- 1 day
-
Checked the application status and analyze the log for all zain OPCOS and share the reports.
-
- Time Spent:
- 1 day
-
Patch has been applied and monitor the server next day, also run the script over the weekend.
-
- Time Spent:
- 4 hours
-
Worked with dev team to monitor the query output, due to this partition was full which free the disk space.
-
- Time Spent:
- 7 hours
-
Testing different scenerios also nep went down and reported to L2 and restart the nep and again start doing testing and make document
-
- Time Spent:
- 1 hour
-
Testing document finalize and shared with Dev team
-
- Time Spent:
- 1 hour
-
Coordinate with L3 and L2 for the errors related to testing and new script provided by L3 and asked L2 to deploy the same
-
- Time Spent:
- 1 day
-
Run the query and take output of all Zain OPCOS and shared to dev team.
-
- Time Spent:
- 1 day
-
Worked with L3 to run query and troubleshooting for issue which caused db issue.
-
- Time Spent:
- 3 hours, 10 minutes
-
Testing
-
- Time Spent:
- 4 hours
-
Data Validation of Active, Passive and IT Import. Also confirm customer to proceed with patch deployment
-
- Time Spent:
- 2 hours, 30 minutes
-
Validate the same and raised issue with L3
-
- Time Spent:
- 2 hours
-
Discussion with Medhat and WIfred differnet time over email regarding the way forward on this ticket
-
- Time Spent:
- 1 hour
-
Customer raised issue for the past ticket discuss with and asked him to provide the details with snippet or close the ticket
-
- Time Spent:
- 4 hours
-
Duplicate sn check
