Details
-
Type:
Task
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Labels:
-
Customer:Ooreedo Tunisia
Description
Dear @Driss Chibane,
Could you please confirm the following points that I observed during data validation in the staging-DB for Nokia RAN:
1. On checking randomly across some tables for nodes like BSC/RNC/SRAN/BTS/NodeB/eNodeB, I found:
o Only the RNC table exists, but its data is blank (While data is available in CSV-Output).
o BTS is available under the table “Element_Node”.
My question is: since we validated all the CSVs earlier, under which table names and locations in the staging-DB should each dataset be available?
It would be very helpful if you could share a mapping/list that clearly describes which CSV data corresponds to which tables in S-DB.
(Element_Node snippet)
(RNC snippet)
Thank you
Indrasan
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 2 hours, 30 minutes
-
Log in the staging-DB and check the node level data there.
-
- Time Spent:
- 2 hours
-
Make a list of available & missing tables between CSV-CSV Output-Staging DB tables and shared to @Sandya.
-
- Time Spent:
- 2 hours
-
Validated the data in CSV-Output shared by Sandya for given points on 30-09-2025 which is updated on same JIRA.
-
- Time Spent:
- 2 hours
-
After released AI patch & deployed, Checked data first for missing tables are showing on S-DB or not? Now the require tables like BSC/BS/SRAN/NodeB/eNodeB are showing. and data are reflecting. I will continue the validation for whole data.
-
- Time Spent:
- 7 hours
-
Nokia RAN data validation on staging-DB.
-
- Time Spent:
- 6 hours
-
XML Data validation on staging-DB.
-
- Time Spent:
- 7 hours
-
Nokia RAN XML data validation on staging-DB.
-
- Time Spent:
- 2 hours
-
Validated the data in staging-DB & shared my feedback to Sandya on JIRA and email. And discussed with her to clarify the raised points.
Updated the excel sheet about doubts clarification regarding tables in staging DB and attached the updated one on JIRA.
-
- Time Spent:
- 30 minutes
-
Discussed with @Sandya over teams call as she need to understand the highlighted issues.
-
- Time Spent:
- 30 minutes
-
Taken the followed up of CSV Output is uploaded or not on staging-DB which was shared by @Sandya on late evening on 17-10.
-
- Time Spent:
- 1 hour
-
I have I have uploaded the csv_output provided by Sandya into SD. I have also verified that the counts in the CSV are correctly reflected in SD.
-
- Time Spent:
- 2 hours
-
Started data validation on staging-DB for Nokia RAN, which is uploaded by @Basant & CSV Output was shared by @Sandya on 17-10-2025.
-
- Time Spent:
- 4 hours, 30 minutes
-
Data validation completed on staging-DB & shared feedback over an email to Sandya. and discussed over teams call to explain the same.
-
- Time Spent:
- 1 hour
-
shared huweai ran logs to sandya from Ooredeoo
-
- Time Spent:
- 2 hours
-
Prepare the quarry to show the count on staging-DB.
-
- Time Spent:
- 1 hour
-
Update the quarry & add the quarry to show the count. and update the sheet of attribute count and share to @Bassem.
-
- Time Spent:
- 1 hour
-
I have uploaded the CSV output provided by you and executed the csv2db script. After verifying in SD,
-
- Time Spent:
- 4 hours, 30 minutes
-
CSV Output uploaded data validation on staging DB for Nokia RAN, Shared feedback to @Sandya and also explain the same thing to her over teams call.
-
- Time Spent:
- 30 minutes
-
Discuss with Sandya regarding pending issue of Nokia RAN for staging-DB.
-
- Time Spent:
- 1 hour
-
I have uploaded the CSV file provided by sandya and verified the record counts before and after uploading it in SD.
-
- Time Spent:
- 4 hours
-
Data validation on staging-DB for Nokia RAN and shared feedback to Sandya over an email & JIRA.
-
- Time Spent:
- 1 hour
-
I have regenerated the CSV output and compared the record counts before and after uploading it in SD.
-
- Time Spent:
- 30 minutes
-
I have shared csv and SD count sheet from Ooredeoo
-
- Time Spent:
- 1 hour
-
I prepared and shared the CSV file count vs. DB table count comparison report and guided Basant on how to perform it next time
-
- Time Spent:
- 5 hours
-
Checked for highlighted previous issue for Nokia RAN & reverted to Sandya (Validation is based on latest Importer ID-Shared by Basant)
-
- Time Spent:
- 2 hours, 30 minutes
-
Check & validate the data in staging-DB for same connector.
-
- Time Spent:
- 1 hour
-
Taken the followed up with Dr. Khaled to release latest AI patch after compile code committed by @Jharna and requested to deploy the latest AI patch on server and generate the XML and upload csv output on staging-DB.
-
- Time Spent:
- 1 hour
-
I have deployed the latest nep_ai_batch_56 on .102 platform . after that I generated xml and uploaded csv in SD .
-
- Time Spent:
- 4 hours
-
Validate the data in staging-DB and found too many issue which was fixed earlier in all tables, highlighted to Jharna.
-
- Time Spent:
- 4 hours
-
Validated the data on staging-DB and shared feedback to Sandya.
-
- Time Spent:
- 1 hour
-
shared static dumps folder for Nokia RAN XML Data Validation In S-DB
-
- Time Spent:
- 1 hour
-
i have generated nsn ran xml and csv-output and shared on mail .
-
- Time Spent:
- 2 hours
-
Sandya requested an example for raised issues, then asked her to share csv output then i find the gap count & shared example (previously csv output was not shared by integration or Sandya) and explain the all issues to her.
-
- Time Spent:
- 1 hour
-
i have updated the file 21082025.log in ran nokia then i generated the xml and uploaded csv in SD after that i shared on mail .
-
- Time Spent:
- 4 hours
-
Validated the data on staging for of Nokia RAN as updated CSV output uploaded by Integration which was shared by Sandya, now issue is fixed except 2 point which is mention on JIRA.
-
- Time Spent:
- 2 hours
-
I have applied latest nep_ai_batch_60 patch on Ooredeo . after that I generated nsn ran xml and csv-output .
-
- Time Spent:
- 2 hours
-
Latest nep_ai_batch_61 has been successfully deployed on Ooredoo . after that I generated nsn ran xml and csv-output
-
- Time Spent:
- 1 hour, 30 minutes
-
Latest nep_ai_batch_62 has been successfully deployed on 102 platform . after that I generated nsn ran xml and csv
-
- Time Spent:
- 1 hour
-
i have shared dumps from 102 to AI dev .
-
- Time Spent:
- 3 hours
-
Latest nep_ai_batch_64 and nep_ai_batch_65 both pathces have been successfully deployed on 102 . after that I generated twice time nsn ran xml and csv
-
- Time Spent:
- 7 hours, 30 minutes
-
Check & validate for same in XML & Import the XML in NEP then validate it but still uplink & downlink EARFCN & uplink/downlink channel bandwidth is not importing with below error:
The parent EnodeB LNBTS-515143 of LTE Cell : (515143_22) has no supported TDD bands!
However now all this related issue will be tracked under JIRA
OT-138.
