Skip to main content
Delphix

KBA1737 ASE Snapsync Fails Due to Hung LOAD TRANSACTION

 

Applicable Delphix Versions

 

Major Release

All Sub Releases

5.2 5.2.2.0, 5.2.2.1, 5.2.3.0

5.1

5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0

5.0

5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1 ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

4.3

4.3.1.0, 4.3.2.0, 4.3.2.1, 4.3.3.0, 4.3.4.0, 4.3.4.1, 4.3.5.0

4.2

4.2.0.0, 4.2.0.3, 4.2.1.0, 4.2.1.1, 4.2.2.0, 4.2.2.1, 4.2.3.0, 4.2.4.0 , 4.2.5.0, 4.2.5.1

4.1

4.1.0.0, 4.1.2.0, 4.1.3.0, 4.1.3.1, 4.1.3.2, 4.1.4.0, 4.1.5.0, 4.1.6.0

4.0

4.0.0.0, 4.0.0.1, 4.0.1.0, 4.0.2.0, 4.0.3.0, 4.0.4.0, 4.0.5.0, 4.0.6.0, 4.0.6.1

Issue

During ASE SnapSync failure occurs throwing a message on the action:

Unmount SQLException: 938: Database 'dxvd7PnmeMQ9trf3dno_sdafdrpo' is unavailable.  It is undergoing LOAD TRANSACTION.
Drop SQLException: 938: Database 'dxvd7PnmeMQ9trf3dno_sdafdrpo' is unavailable.  It is undergoing LOAD TRANSACTION.
Retry Exception: 938: Database 'dxvd7PnmeMQ9trf3dno_sdafdrpo' is unavailable.  It is undergoing LOAD TRANSACTION.

The consequence is subsequent SnapSync attempts will keep failing on this situation.

Troubleshooting

The failure occurs because the staging database used by the ASE dSource is undergoing this LOAD TRANSACTION activity, implying there is an ingestion still happening. Check to make sure there isn't some SnapSync already happening, and if not, then suspect that there is a hung LOAD TRANSACTION on the ASE staging instance.

You can confirm this by running the sp_who command and check the output on the staging database name.

Example output from the sp_who command:

  0             28         sleeping               delphix_user       delphix_user       x0008mn0v                0                dx8nb417vz6MsaryfHx_staging             tempdb                LOAD TRANSACTION      

If this is sleeping, it appears to be a hung LOAD TRANSACTION.

Resolution

The sa user can try to kill the spid with the LOAD TRANSACTION

Alternatively, a restart of the ASE staging instance should free this spid.

Additional Information

 

External Links