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
added the logs as per suggested by driss sir , but still they are not coming on server , mailed about it to driss sir.
now radio anteena data is coming in xml, xml shared on mail already , working on the second issue..
done some changes in the code for enodebbandwidth data , check the data in csv and confirm then will check the data on sd.
now enodbandwidth data is coming fine in the csv , please check and confirm.
A separate JIRA (OT-138) has been created for this activity, as the static sheets have been updated and the rules have been changed to parse frequency band, channel bandwidth, and DL/UL EARFCN.
Validation for all these changes will be performed under JIRA OT-138.
Currently, uplink/downlink channel bandwidth and uplink/downlink EARFCN are still not importing into NEP due to the following error:
“The parent EnodeB LNBTS-515143 of LTE Cell (515143_22) has no supported TDD bands.” under "4G Cell".
Although TDD band information is available in the XML, this issue is not being raised to the DEV team at this stage, as it will be validated based on the latest rules and parsing logic under OT-138.
Therefore, closing JIRA OT-84, as all issues under this ticket have been fixed, except the above, which is now tracked and validated separately under OT-138.
From: Bassem Sabbagh <bassem.sabbagh@mobinets.com>
Sent: 29 September 2025 18:04
To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>; Driss Chibane <driss.chibane@mobinets.com>
Cc: Sandya Sharma <Sandya.Sharma@nuiva.com>
Subject: Re: Clarification On CSV Data Availability In Staging-DB
Dear Indrasan,
It should be the other way around. You need to share with Driss or Sandya the list of all CSVs that you are unable to map them with staging DB tables and they will share the tables name.
Thanks