Datasphere: transport package is locked in Exporting

[albertosimeoni]

Hello Experts,

I have a package that is locked with status "Exporting" from 2024.07.26 till now 2024.08.01

The target packages in "Export Folder" has been created, but in the application "Transport/Packages" the package is in state "Exporting".

This situation locks every object inside the Package from being edited / deleted / overwritten by a manual import.

In SAP HANA Cloud cockpit of Datasphere instance (System Monitor -> Open Cockpit) there are no activities related to this at database level.

How can I unlock the situation?

I try to:

• Manually delete an object inside this package => error no permission (due to the locks set by package export Process

 

• Manually import an object from the other tenant => error can not import.
• Try to delete the target package generated in Transport / Export folder => no effect.

Edit: after the update planned on the last weekend (and possibly some restart during saturday / sunday night), the problem persist.

Best Regards,

Alberto

[Martin_Kuma · Accepted solution]

Hi Alberto, 

could it be, that there is an issue with "uroboros"? 

During the export of the package, the system will lock all dependent spaces of all objects you are exporting.

All objects must also be deployed, do you see any errors in the messages? Something stating, that one of the objects in dependent space is not deployed. 

Check also if you do not use business builder objects. You may have those in not released versions. 

The error messages are not really that straight forward in DSP 😞

Cheers

Martin 

[albertosimeoni · Accepted solution]

Unfortunately every object is deployed (and no objects from Business Builder).

Edit: The only "Particular" objects I have, are 3 tables from OpenSQL Schemas.
But they are active as other objects.

I do not have cross space sharing involved in that packages or dependent objects.

I also check objects in dependent packages but everything is deployed.

[Martin_Kuma · Accepted solution]

No cross-space sharing, no dependent objects or all are deployed. All depended packages included... Only other reason I could think of is authorization for the OpenSQL Schema. 

This may be worth to get SAP involved.

EDIT: just a guess. Did you try to delete the package and re-create it? Just if there is no issue in the cloud storage with the file self (or where-ever you create and store the packages)

[albertosimeoni · Accepted solution]

We open an incident and just before i found this note https://me.sap.com/notes/3503531/E

[albertosimeoni · Accepted solution]

We open an incident and just before i found this note (This issue is currently under investigation by development.) https://me.sap.com/notes/3503531/E