2.0 May 9, 2022 - New Bug Fixes for Patch 15753\n\nBug 135096 II-4342 (GENERIC)\n\nCross table update query between table and view fails with error: E_US125D Ambiguous replace: you have specified several replacements for the same row.\n\nBug 136054 II-5554 (GENERIC)\n\ninfodb shows X100 supported : Yes in user databases on platforms with no x100 support (Solaris, AIX, HP-UX, VMS)\n\nBug 136714 II-6190 (GENERIC)\n\nThe resulting datatype of date('string') within the procedure changes after clearing the cache using tracepoint qs506. the procedure recompile and uses current date_alias. It is not using the date_alias when the procedure created for the first time\n\nBug 139324 II-8671 (VMS, CLUSTER)\n\nFollowing a node failure, lock requests on remaining nodes are stalled and never granted.\n\nBug 139353 II-8850 (VMS)\n\nE_SC033D_TZNAME_INVALID is not displaying the timezone name.\n\nBug 139406 II-8926 (VMS)\n\nThe DBMS server may hang. PSTACK trace show that the ast_thread is stalled waiting for IO AST to complete.\n\nBug 139509 II-9053 (ENHANCEMENT)\n\nAdd support for the ipv4, ipv6 and uuid datatype to QBF utilities. A default display format for ipv4, ipv6, and uuid is c15, c39, and c36 respectively. A maximum of 15, 39, 36 character is required to apply inserts and/or updates as valid values in ipv4, ipv6, and uuid.\n\nBug 139625 II-9170 (GENERIC)\n\nA query that does a cross table update with a view runs slow due to the view is being materialized.