[LS-706] ORA error related to null ENODBID during NON IP xml import - staging Created: 09/Oct/25  Updated: 14/Jan/26  Due: 17/Oct/25  Resolved: 14/Jan/26

Status: Closed
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Abir Messaikeh Assignee: Abir Messaikeh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days, 7 hours
Original Estimate: Not Specified

Customer:
OMAN-Tel
Planned Start:
Planned End:
Product: NEP
Actual Start:
Date of Baselining:

 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")

 Comments   
Comment by Abir Messaikeh [ 09/Oct/25 ]

https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/EfWcD8Qfcn5Lt_eoU6X9SKQBxINrdYAr0iN1-vWRha49Qg?e=xVfd3P

Comment by Marwan Kanaan [ 09/Oct/25 ]

Dear @Mohan Singh Rathor,

Kindly note that the issue has been addressed and was reproducible on my local environment with the same fatal error.

Furthermore, the issue has been fixed, and a patch is required.

Patch Number: 3.7.0.1360

Comment by Abir Messaikeh [ 13/Oct/25 ]

Dear @Marwan Kanaan,

The issue persists with the non-IP XML import even after the deployment of the latest patch." "The XML import has been stuck in the 'saving to instance' phase for over 20 hours.

We used the same xml as we used last import. Please find the logs during the import.
server.log.2025-10-11.gz

Caused by: Error : 1400, Position : 147, Sql = insert into NEP_181.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, C
ELLID) values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 ), OriginalSql = insert into NEP_181.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID,
TacID, UPLINKEARFCN, CELLID) values (?, ?, ?, ?, ?, ?, ?, ?), Error Msg = ORA-01400: cannot insert NULL into ("NEP_181"."LTECELL"."ENODEBID")
2025-10-11 19:42:39,073 INFO [stdout] (AsyncAppender-Dispatcher-Thread-125) 19:42:39-[FATAL][SaveRunner] Error while calling saving instances to Database: [User: importer][Action: com.mobinets.nep.npt.service.AutoImportService.importNetwork(String, String, NEPBundles, ImporterParams) 037a00d4-6130-4f6d-a7ec-e9e3e0b43130]

Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("NEP_181"."LTECELL"."ENODEBID")

logs below
https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/EXw4WDE3WUhGpem1hZZN39wBE2EQlW1ZlmGWkSBlLDJNXw?e=my5deK

Comment by Abir Messaikeh [ 15/Oct/25 ]

new fix in NEP_OMANTEL - Build 3.7.0.1364

Generated at Wed Apr 15 16:21:34 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.