From: Bassem Sabbagh <bassem.sabbagh@mobinets.com>
Sent: 29 May 2025 10:44
To: Indrasan Yadav <Indrasan.Yadav@nuiva.com>; ABHINAV PARASHAR <ABHINAV.PARASHAR@mobinets.com>
Cc: Abir Messaikeh <Abir.Messaikeh@nuiva.com>; Sanju Yadav <Sanju.Yadav@mobinets.com>; Azmat Ali <Azmat.Ali@nuiva.com>
Subject: RE: Facing an issue when opening NEP on production

Dear Abhinav,

Please check urgently ?

Thanks

From: ABHINAV PARASHAR <ABHINAV.PARASHAR@mobinets.com>
Sent: Thursday, May 29, 2025 8:43 AM
To: Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Indrasan Yadav <Indrasan.Yadav@nuiva.com>
Cc: Abir Messaikeh <Abir.Messaikeh@nuiva.com>; Sanju Yadav <Sanju.Yadav@mobinets.com>; Azmat Ali <Azmat.Ali@nuiva.com>; Manjit Kumar <manjit.kumar@mobinets.com>
Subject: RE: Facing an issue when opening NEP on production

Dear Bassem,

An error was observed after completing the first end global interception of the importNetwork process during today’s XML import. Upon reviewing the previous logs, it appears that the errors encountered are the primary cause of the issue.

Please find below a snippet of the key error messages for your reference:
ORA-00957: duplicate column name
Exception executing batch [could not execute batch]
Failed SaveOrUpdate com.mobinets.nps.model.network.gsm.Bsc.
RMI service 'Oppack3GProcessService' is not bound to registry at port '10246'

These errors indicate a schema inconsistency, likely due to duplicate column definitions, which is preventing proper data persistence. As a temporary measure, the NEP server was restarted and is currently operating normally.
I’ve attached the full server log from today for further analysis. Kindly review and align the necessary resources to address this issue.
Let me know if any further details are needed from my end.

@Indrasan Yadav please create a jira and assign it to Dr. Khaled
@Khaled Khalil it seems the below error is appearing after we applied the last patch on production.
Kindly check it as priority since it is blocking the import ..

Thanks

Dears,
The issue has been resolved. Patch is needed: 3.7.1.682
Regards,
Mustapha

After patch deployed on production now we can access the NEP.

Thank you