{"id":529,"date":"2022-02-02T10:01:20","date_gmt":"2022-02-02T09:01:20","guid":{"rendered":"https:\/\/anjo.pt\/keyword-oracle\/?p=529"},"modified":"2022-02-02T10:18:39","modified_gmt":"2022-02-02T09:18:39","slug":"solution-for-oda-19-13-list-availablepatches-error","status":"publish","type":"post","link":"https:\/\/anjo.pt\/keyword-oracle\/2022\/02\/02\/solution-for-oda-19-13-list-availablepatches-error\/","title":{"rendered":"Solution for ODA 19.13 list-availablepatches error"},"content":{"rendered":"\n

After patching an ODA to 19.13, often we have the error<\/p>\n\n\n\n

[root@oda-01 DB1]# odacli list-availablepatches\nDCS-10001:Internal error encountered: For input string: \"\".\n<\/code><\/pre>\n\n\n\n
The workaround provided by Oracle on the 19.13 “Known Issues”<\/a> is incomplete and might not solve the problem in many cases.<\/p>\n\n\n\n
The complete solution is to change all patchmetadata.xml files where this “targetVersion” is missing. Here is the sed command that creates a backup (extension .bck) and adds the missing bit:<\/p>\n\n\n\n
sed -i.bck -E 's\/name=\"DB\" repotag=\"(1[0-9]\\.[0-9]{1,2}\\.[0-9]\\.[0-9]\\.[0-9]{6})\"><\\\/component>\/name=\"DB\" repotag=\"\\1\" targetVersion=\"\\1\"><\\\/component>\/g' \/opt\/oracle\/oak\/pkgrepos\/System\/*\/patchmetadata.xml<\/code><\/pre>\n\n\n\n
Now, odacli list-availablepatches<\/code> is back to normal:<\/p>\n\n\n\n
[root@oda-01 DB1]# odacli list-availablepatches\n-------------------- ------------------------- -------------------------\nODA Release Version  Supported DB Versions     Available DB Versions\n-------------------- ------------------------- -------------------------\n\n19.6.0.0.0           19.6.0.0.200114           Clone not available\n                     18.9.0.0.200114           Clone not available\n                     12.2.0.1.200114           Clone not available\n                     12.1.0.2.200114           Clone not available\n                     11.2.0.4.200114           Clone not available\n\n19.13.0.0.0          21.4.0.0.211019           Clone not available\n                     19.13.0.0.211019          19.13.0.0.211019\n                     12.2.0.1.211019           Clone not available\n                     12.1.0.2.211019           Clone not available\n\n19.10.0.0.0          19.10.0.0.210119          Clone not available\n                     18.13.0.0.210119          Clone not available\n                     12.2.0.1.210119           Clone not available\n                     12.1.0.2.210119           Clone not available\n                     11.2.0.4.210119           Clone not available\n\n18.8.0.0.0           18.8.0.0.191015           Clone not available\n                     18.8.0.0.191015           Clone not available\n                     12.2.0.1.191015           Clone not available\n                     12.1.0.2.191015           Clone not available\n                     11.2.0.4.191015           Clone not available\n\n18.5.0.0.0           11.2.0.4.190115           Clone not available\n                     12.1.0.2.190115           Clone not available\n                     12.2.0.1.190115           12.2.0.1.190115\n                     18.5.0.0.190115           Clone not available\n\n18.4.0.0.0           11.2.0.4.181016           Clone not available\n                     12.1.0.2.181016           Clone not available\n                     12.2.0.1.181016           Clone not available\n                     18.4.0.0.181016           Clone not available\n\n18.2.1.0.0           11.2.0.4.180417           Clone not available\n                     12.1.0.2.180417           Clone not available\n                     12.2.0.1.180417           Clone not available\n\n12.2.1.4.0           11.2.0.4.180417           Clone not available\n                     12.1.0.2.180417           Clone not available\n                     12.2.0.1.180417           Clone not available\n<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
After patching an ODA to 19.13, often we have the error The workaround provided by Oracle on the 19.13 “Known Issues” is incomplete and might not solve the problem in many cases. The complete solution is to change all patchmetadata.xml files where this “targetVersion” is missing. Here is the sed command that creates a backup […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[67,68],"tags":[],"class_list":{"0":"post-529","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-engineer-systems","7":"category-oda","8":"czr-hentry"},"_links":{"self":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/529","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/comments?post=529"}],"version-history":[{"count":2,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/529\/revisions"}],"predecessor-version":[{"id":531,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/529\/revisions\/531"}],"wp:attachment":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/media?parent=529"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/categories?post=529"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/tags?post=529"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}