Details

    • Customer:
      Ooreedo Tunisia

      Description

      I initiated a sample XML (2025-06-04-11.48.54_Ooredoo_Tunisia) import on server .102 on dated 04-06-2025, but the connection was unexpectedly refused before the import could complete.

      Following this, I requested a platform restart to Natnael Asfaw. After the restart, I attempted the XML import again, but the same issue is occurring.

      Server log & XML is attached here for reference.

      1. server.log
        7.24 MB
        Indrasan Yadav
      2. OT-17_Updated.rar
        25 kB
        Indrasan Yadav
      1. Error Snippet.jpg
        52 kB

        Activity

        Hide
        Indrasan Yadav added a comment -

        Dear @Natnael Asfaw,

        As discussed over Teams, I initiated an XML import on server .102, but the connection was unexpectedly refused before the import could complete.

        Following this, I requested a platform restart. After the restart, I attempted the XML import again, but the same issue is occurring.

        Please advise on the next steps or if any further investigation is required from my end.

        Thank you
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @Natnael Asfaw, As discussed over Teams, I initiated an XML import on server .102, but the connection was unexpectedly refused before the import could complete. Following this, I requested a platform restart. After the restart, I attempted the XML import again, but the same issue is occurring. Please advise on the next steps or if any further investigation is required from my end. Thank you Indrasan
        Hide
        Indrasan Yadav added a comment -

        Dear @Indrasan Yadav

        Please note that there are errors during import which might cause connection refused. Kindly check with DEV Team

        2025-06-04 14:28:14,964 ERROR [com.mobinets.nps.bo.imtDataInput.impl.NetworkCreateManager] (Thread-137) error while flushing and clearing session saveToDatabase...: org.hibernate.exception.ConstraintViolationException: could not execute batch

        2025-06-04 14:28:14,966 ERROR [com.mobinets.nps.services.imtDataInput.impl.ImtCreateWS] (Thread-137) Unavailable Service 'Save to Database'.: org.hibernate.exception.ConstraintViolationException: could not execute statement

        2025-06-04 14:28:14,979 INFO [stdout] (AsyncAppender-Dispatcher-Thread-124) Caused by: Error : 1400, Position : 147, Sql = insert into ooredoo.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 ), OriginalSql = insert into ooredoo.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (?, ?, ?, ?, ?, ?, ?, ?), Error Msg = ORA-01400: cannot insert NULL into ("OOREDOO"."LTECELL"."ENODEBID")

        Best,

        Show
        Indrasan Yadav added a comment - Dear @Indrasan Yadav Please note that there are errors during import which might cause connection refused. Kindly check with DEV Team 2025-06-04 14:28:14,964 ERROR [com.mobinets.nps.bo.imtDataInput.impl.NetworkCreateManager] (Thread-137) error while flushing and clearing session saveToDatabase...: org.hibernate.exception.ConstraintViolationException: could not execute batch 2025-06-04 14:28:14,966 ERROR [com.mobinets.nps.services.imtDataInput.impl.ImtCreateWS] (Thread-137) Unavailable Service 'Save to Database'.: org.hibernate.exception.ConstraintViolationException: could not execute statement 2025-06-04 14:28:14,979 INFO [stdout] (AsyncAppender-Dispatcher-Thread-124) Caused by: Error : 1400, Position : 147, Sql = insert into ooredoo.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 ), OriginalSql = insert into ooredoo.LTECELL (CELLDUPLEXINGMODE, DOWNLINKEARFCN, EnodebID, MIMOCONFIGURATION, PCID, TacID, UPLINKEARFCN, CELLID) values (?, ?, ?, ?, ?, ?, ?, ?), Error Msg = ORA-01400: cannot insert NULL into ("OOREDOO"."LTECELL"."ENODEBID") Best,
        Hide
        Diana Hamdouche added a comment -

        Dears,

        Same occurred for Omantel and we agreed with @Abir to do the following as a work around:

        Try importing the non IP XML with the import of 4g cell disabled by using the below property:
        cell4gElement=false

        After it is completed try imploring the same xml without disabling the previous property and confirm.

        Show
        Diana Hamdouche added a comment - Dears, Same occurred for Omantel and we agreed with @Abir to do the following as a work around: Try importing the non IP XML with the import of 4g cell disabled by using the below property: cell4gElement=false After it is completed try imploring the same xml without disabling the previous property and confirm.
        Hide
        Indrasan Yadav added a comment -

        Dear All,

        The import has been successfully completed.

        I would like to clarify the process for future imports of the RAN XML. Should we follow the same approach next time—first importing the XML without the LTE cell information, and then importing it again with the LTE cell included?

        Thank you,
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear All, The import has been successfully completed. I would like to clarify the process for future imports of the RAN XML. Should we follow the same approach next time—first importing the XML without the LTE cell information, and then importing it again with the LTE cell included? Thank you, Indrasan
        Hide
        Indrasan Yadav added a comment -

        Hi Indrasan

        Our understanding is just the first time this is required , from now on import full with LTE CELL and let us know if it will be ok

        thx
        Abir

        Show
        Indrasan Yadav added a comment - Hi Indrasan Our understanding is just the first time this is required , from now on import full with LTE CELL and let us know if it will be ok thx Abir

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Time Spent - 1 day, 1 hour, 30 minutes Remaining Estimate - 2 hours, 30 minutes
              2h 30m
              Logged:
              Time Spent - 1 day, 1 hour, 30 minutes Remaining Estimate - 2 hours, 30 minutes
              1d 1h 30m

                Drag and Drop