{"id":1178,"date":"2026-07-20T10:00:00","date_gmt":"2026-07-20T08:00:00","guid":{"rendered":"https:\/\/anjo.pt\/keyword-oracle\/?p=1178"},"modified":"2026-07-30T13:26:24","modified_gmt":"2026-07-30T11:26:24","slug":"1178","status":"publish","type":"post","link":"https:\/\/anjo.pt\/keyword-oracle\/2026\/07\/20\/1178\/","title":{"rendered":"OEM 13.5 &#8211; Failed to allocate OCIEnv from Perl corrective actions"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">At a client, since Enterprise Manager 13.5 Release 1 Update 30 (RU 30) &#8211; the <s>April<\/s> June 2026 update -, that Corrective Action to extend tablespaces stopped to work. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">They got two production application completely frozen due to this! <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The symptoms were that the Perl script triggered by OEM Agent could not anymore connect to the database. The error was found for instance at $AGENT_HOME\/agent_inst\/sysman\/log\/emagent_perl.trc:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nWARN:  instanceDiskPerformanceMetric.pl: Could not connect to sys\/(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=srv0nnnn.xxx.ch)(Port=1521))(CONNECT_DATA=(SID=+ASM))): Failed to allocate OCIEnv\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">The problem was clear with the Agent version, because by rolling it back, the problem disappeared.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We opened a Service Request, that went its typical way and it is still open. At the end I found the solution myself.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The problem needed to be either with Perl or Client drivers. The Perl was the latest version, seems correctly working. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then I found the Oracle Support note <a href=\"https:\/\/support.oracle.com\/ic\/builder\/rt\/customer_portal\/live\/webApps\/customer-portal\/?anchorId=&amp;kmContentId=2909209&amp;page=sptemplate&amp;sptemplate=km-article\">KB398956 &#8220;On OEM 13c : How To Upgrade Perl DB Client Version For 13.5 &amp; 13.4 OEM Agent Home From 12c To 19c&#8221;<\/a>. There, the link for the patch <a href=\"https:\/\/support.oracle.com\/support\/?patchId=37099808\" target=\"_blank\" rel=\"noreferrer noopener\">37099808<\/a> to be applied on OEM 13.5 was not working (on 16.07.2026). So I decided to follow the instructions for OEM 13.4.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I <a href=\"https:\/\/www.oracle.com\/database\/technologies\/instant-client\/linux-x86-64-downloads.html#tab-id-5a1f77f3-ab1e-41b0-a6b4-3e645d82834f\">downloaded the latest instant client 19.31<\/a> and unzipped in a staging area ($STAGING_AREA below). <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then I did what the note above said for OEM 13.4:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nemctl stop agent\ncd \/u00\/app\/oracle\/product\/agent\/agent_13.5.0.0.0\nmv instantclient \/tmp\/agent_instantclient\ncp -ar $STAGING_AREA\/instantclient_19_31 .\nmv instantclient_19_31 instantclient\ncd instantclient\nln -s libclntshcore.so.19.1 libclntshcore.so.12.1\ncp -a adrci uidrvci ..\/bin\/\nemctl start agent\n<\/pre><\/div>\n\n\n<p class=\"wp-block-paragraph\">When testing again, the Corrective Action was back working. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The client is now creating a Gold Image and deploy this agent version everywhere.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Update 30.07.2026: the client tried also the solution by installing the patch 37099808. It did not work. Then, the client did install the instantclient manually as decribed above, and it works. Manual install seems the right solution.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At a client, since Enterprise Manager 13.5 Release 1 Update 30 (RU 30) &#8211; the April June 2026 update -, that Corrective Action to extend tablespaces stopped to work. They got two production application completely frozen due to this! The symptoms were that the Perl script triggered by OEM Agent could not anymore connect to [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,89,6],"tags":[],"class_list":["post-1178","post","type-post","status-publish","format-standard","category-bug","category-enterprise-manager","category-oracle","czr-hentry"],"_links":{"self":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/1178","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=1178"}],"version-history":[{"count":3,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/1178\/revisions"}],"predecessor-version":[{"id":1182,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/1178\/revisions\/1182"}],"wp:attachment":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/media?parent=1178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/categories?post=1178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/tags?post=1178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}