In DB2 sde.setcurrentversion('user.version', ?) fails with a fully qualified name for a version.
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM031330
Submitted
January 15, 2008
Last Modified
April 2, 2025
Applies to
No Product Found
Version found
9.1
Status
Known Limit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
Additional Information
No Public Explanation
Workaround
Dated - June 25th, 2008 - This has been fixed at 9.1 via qfe-sde-91-cq00309839-Neeta---------------------------------------------------------------------------------------------------------------Fixed ownership check for setcurrentversion() sp & updated sp release #. CQ00291178 and described in KB article 32867 This now works correctly. Tested with build (Pre-release) for DB2 Build 1015 Thu Jul 6 Tested as follows -db2 => call sde.setcurrentversion('FUNKYTOWN',?)Value of output parameters--------------------------Parameter Name : MESSAGEParameter Value :Procedure successfully completed. Version set to state 109.Return Status = 0db2 => call sde.setcurrentversion('VTEST.FUNKYTOWN',?)Value of output parameters--------------------------Parameter Name : MESSAGEParameter Value :Procedure successfully completed. Version set to state 109.