Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Labels:None Labels
-
Customer:OMAN-Tel
-
Product:NEP
Description
Yesterday, we encountered an error during the NON IP XML import on the .180 server.
Please review the error message below and suggest a solution so we can resolve this issue.
XML name - 2025-10-07-08.16.30_NONIP_OmanTel.xml
Import Start time - 2025-10-07 21:39:08
Please find the logs during the import.
logs_180_07Oct.rar
2025-10-07 23:57:31,549 INFO [stdout] (AsyncAppender-Dispatcher-Thread-119) Caused by: Error : 1400, Position : 147, Sql = insert into NEP_181.LTECELL (CELLDUPLEXINGMO
DE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 ), OriginalSql = insert into NEP_181.L
TECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (?, ?, ?, ?, ?, ?, ?, ?), Error Msg = ORA-01400: canno
t insert NULL into ("NEP_181"."LTECELL"."ENODEBID")
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("NEP_181"."LTECELL"."ENODEBID")
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 4 hours
-
reproduce the issue locally and added for handling for avoiding saving lte without enodebid
-
- Time Spent:
- 4 hours
-
Continuing to investigate the LTE issue, as the problem remains unpredictable and does not follow any logical or consistent scenario so far. Further analysis is ongoing to identify the root cause and determine a stable reproduction pattern.
-
- Time Spent:
- 7 hours
-
Continuing to investigate the LTE issue, as the problem remains unpredictable and does not follow any logical or consistent scenario so far. Further analysis is ongoing to identify the root cause and determine a stable reproduction pattern.
-
- Time Spent:
- 7 hours
-
The root cause was that the LTE ENodeB reference was being incorrectly set or overridden from the XML with invalid data, leading to a fatal error during database saving. The logic was reviewed and corrected to ensure that the LTE ENodeB is properly validated and not overridden by incomplete XML data, aligning the ENodeB reference with the real network object to prevent future inconsistencies.
