Automic Workload Automation

Expand all | Collapse all

Transport case compatibility between v11 and v12

  • 1.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 05:27 AM
    Is the transport case compatible between version 11 and 12?


    Target v11
    Target v12
    Source v11
    Source v12

    Update: It is possible to load a v11 transport case into a v12 system, but not vice versa.


  • 2.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 06:07 AM
    Did a Client Transport (All Objects) from V11.2.3 to V12GA *Just for Fun* - so far I did not encounter any incompatibilities.

    Usually a transport case can always be loaded to a higher AE Version.


  • 3.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 07:41 AM
    It appears to be impossible to load a v12 transport case file into a v11.2.3 system.
    20161207/134006.557 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: aa34b0  DB-HDBC: aeaa50
    20161207/134006.557 - U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR'
    20161207/134006.557 - U00003592 UCUDB - Status: '' Native error: '904' Msg: 'ORA-00904: "VERSI_PATCH": invalid identifier'
    20161207/134006.557 - U00003594 UCUDB Ret: '3590' opcode: 'SLUC' SQL Stmnt: 'select VERSI_DBVersion from UC_VERSI order by VERSI_Major desc, VERSI_Minor desc, VERSI_Patch desc'
    20161207/134006.557 - U00003590 UCUDB - DB error: 'OCIStmtExecute', 'ERROR   ', '', 'ORA-00904: "VERSI_PATCH": invalid identifier'
    20161207/134006.559 - U00038081 Version of database objects: '11.2.3+build.401'
    20161207/134006.559 - U00038123 Unable to load transport case with version '12.0' into database with version '11.2'.
    Version of database not compatible to transport case.
    20161207/134006.559 - U00021432 Invalid version of Transport Case
    Application return code = 1


  • 4.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 07:52 AM
    Yes its definitely impossible to load a Transport case from AE12 to AE 11.2

    Transport Cases in general are NOT downward compatible (from higher to lower AE Version).

    Its the same with V10 > V9, or V11.2 > V11.1 etc...



  • 5.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 07:55 AM
    Docu says:
    The Transport Case is downward, but not upward compatible. Therefore it is not possible to load a Transport Case from a newer into an older Automation Engine system.

    https://docs.automic.com/documentation/WEBHELP/English/AWA/11.2/AE/11.2/All%20Guides/help.htm#ucaade.htm?Highlight=transport%20case




  • 6.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 07:58 AM
    Yeah, this is what we expected.

    It means that we cannot upgrade our systems in a staged way, because once the DEV system has been upgraded, it will no longer be possible to load transport case files from DEV into TEST or PROD.

    We ran into the same obstacle when upgrading from v9 to v11.2.


  • 7.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 08:17 AM
    We are in the same Situation.

    We will clone our DEV System (V9) - update this to 11.2 and will test on this system.


  • 8.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 08:28 AM
    Hi Michael_Lowry

    As a workaround you should be able to export objects as xml from version 12, and adapt them by adapting the <uc-export> tag to the target version.

    I did a test at my end exported an object from AWI v12 and changed
    <uc-export clientvers="12.0.0-dev+main.build.3446"> to <uc-export clientvers="10.0.7+hf.4.build.459">

    Then successfully imported it to v10.

    It may not be ideal in your case as there are restrictions (number of simultaneous exports, issues when trying to import VARA.SEC.SQL objects), but can definitely be used when dealing with a few objects.

    P.S. : it's not supported either...




  • 9.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 08:31 AM
    AND you should exactly know if there were any bigger DB structure changes between source and target version.

    In my case (V9 - V11.2)  I avoid proceeding to prevent data inconsistences of my System.


  • 10.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 08:31 AM
    Thanks, Antoine_Sauteron. XML is definitely more flexible for the reason you mentioned.

    You mentioned a specific example of a type of object that cannot be moved via XML from v12 to v11. Are there others?

    Is there a list of XML schema changes between v11 and v12? This would help us identify objects that might pose problems during import.


  • 11.  Transport case compatibility between v11 and v12

    Posted 12-07-2016 08:46 AM
    Michael Lowry wrote:
    Is there a list of XML schema changes between v11 and v12? This would help us identify objects that might pose problems during import.
    By the way, the section of the v12 documentation describing the XML schema for object exports is still mostly broken.


  • 12.  Transport case compatibility between v11 and v12

    Posted 12-09-2016 03:01 AM
    Hi Michael,

    I unfortunately do not have such a list. My first attempt was to import in v10 a modified export of a v12 VARA.SEC.SQL object. I then got this error:

    hl9n6igu1mg3.pnghttps://us.v-cdn.net/5019921/uploads/editor/09/hl9n6igu1mg3.png" width="448">

    However, I just tried in v11.2 and the import was successful... So it would not seem there would be changes between v11.2 and v12, but rather between v10 and these 2 versions.

    I did a bit of further testing - created the same objects in 3 versions : v10.0.8, v11.2.2 and v12.0, exported them and compared the 3 xml files with Notepad++.

    V10 vs v11.2


    1 - Of course the <uc-export clientvers=> contained different values

    2 - <VARA OVD_VRName=> contained 2 additional parameters in v10 : 'client=' and 'system='
    V10
    <VARA OVD_VRName="FREI" client="0022" data_type="SQLI_SEC" name="VARA.SEC_SQLI.SAA.EXPORTED" replacementmode="2" system="WS10">
    V11.2
    <VARA OVD_VRName="FREI" data_type="SQLI_SEC" name="VARA.SEC_SQLI.SAA.EXPORTED" replacementmode="2">

    3 -  There were also these additional tags in v10 :
    <Created>Antoine Sauteron on: 2016-12-09 08:20:11</Created>
    <Modified>Antoine Sauteron on: 2016-12-09 08:22:23      4 x</Modified>
    <LastUsed/>

    V11.2 vs v12

    Exports looked almost the same.

    1 - Once again values of 'clientvers=' differed as expected.
    2 - There was this error message in the <infobar> tag in V12 export:
    <infobar>U04002751 Attention: There is a variable-replacement restriction in case of security limits (SQLVAR_SECURITY_LEVEL)!</infobar>

    The import in v11.2 worked fine after changing the client version, but failed in v10 with the error above (screenshot).

    After changing this to "<infobar/>" (I discovered the '/' means that the tag's content should not be filled) and adjusting the clientvers= field the import in v10 was finally successful.


    Conclusion

    1- There are a few additional tags and values in v10 : 
    • 'client=' and 'system=' in the tag corresponding to the object type - VARA in our example.
    • <Created>, <Modified> and <LastUsed>.
    They can be safely discarded as an xml file that does not contain them could be imported.

    2 - No noticeable discrepancies between v11.2 and v12 exports in this case.

    3 -The infobar message seemingly caused the import issue in V10 (maybe because of the different length of U codes ?).



  • 13.  Transport case compatibility between v11 and v12

    Posted 12-12-2016 05:54 AM
    Antoine Sauteron wrote:
    Conclusion
    1. There are a few additional tags and values in v10:
      • 'client=' and 'system=' in the tag corresponding to the object type - VARA in our example.
      • <Created>, <Modified> and <LastUsed>.
      They can be safely discarded as an xml file that does not contain them could be imported.
    2. No noticeable discrepancies between v11.2 and v12 exports in this case.
    3. The infobar message seemingly caused the import issue in V10 (maybe because of the different length of U codes ?).
    Thanks for the tests and the information. Allow me to summarize:
    • When moving XML files from one AE version to another, the Theclientversattribute of theuc-exportelement must be updated to match the version of the target system.
    • Theclientandsystemattributes of theuc-exportelement, as well as theCreated,Modified, andLastUsedelements, were omitted from XML export files starting with v11. They are optional.
    • infobarelements present in the XML file have no impact on object definitions, but may prevent successful import into some AE versions. If present, these elements may be removed.


  • 14.  Transport case compatibility between v11 and v12

    Posted 12-13-2016 02:56 AM