Transport Runs Unexpectedly in Single User Mode in Identity Manager (4381798)

During transport operations in One Identity Manager, customers may experience transports unexpectedly running in Single User Mode, even when this was not explicitly intended.

This behavior can lead to significant operational issues, including:

• Deadlocks at database level

• Transport jobs aborting unexpectedly
• DBQueue processing stopping or becoming inconsistent
• The system remaining in a trigger-free state for an extended period
• Increased operational effort due to having to carefully choose different transport methods (favorites, selected objects, change labels, etc.)

This behavior was reported by multiple customers and did not occur in earlier Identity Manager versions.

The determination of Single User Mode during transports is complex and cannot be derived reliably in all scenarios (for example, when transporting configuration objects or objects with preprocessor conditions).

Historically, the transport framework attempted to automatically determine whether Single User Mode was required, based on object types and internal logic.

This led to inconsistent or unexpected behavior in certain customer environments, especially those with complex configurations and schema extensions.

As a result, the Product Team identified this as a functional gap rather than a configuration error.

This issue has been acknowledged as an enhancement by the Product Team.

Customers experiencing this issue should contact One Identity Support and request Hotfix #430398 for their environment

This enhancement improves transport stability and reduces the risk of DBQueue inconsistencies and unintended Single User Mode usage.