Oracle Team

Often switching off resource plan feature of Oracle database is desired. Unfortunately setting parameter RESOURCE_MANAGER_PLAN to empty string does not help, because it does not disable switching to another resource plan, e.g. with dbms_scheduler. Following procedure prevents this switching. 1. Creation of a dummy resource plan, e.g. TEST_PLAN: BEGIN DBMS_RESOURCE_MANAGER.CLEAR_PENDING_AREA(); DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA(); DBMS_RESOURCE_MANAGER.CREATE_PLAN( plan =>’TEST_PLAN’, comment => ‘plan for TEST’, mgmt_mth => ‘EMPHASIS’, active_sess_pool_mth => ‘ACTIVE_SESS_POOL_ABSOLUTE’, parallel_degree_limit_mth => ‘PARALLEL_DEGREE_LIMIT_ABSOLUTE’); DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE( plan =>’TEST_PLAN’, group_or_subplan => ‘OTHER_GROUPS’, comment…

When trying to patch your virtualized ODA with patch 12.1.2.12.0 and immediately after that with 12.2.1.4.0, you might consider to load the patches like this: [[email protected] Oracle_Soft_Repo]# oakcli unpack -package /cloudfs/Oracle_Soft_Repo/p26433712_1212120_Linux-x86-64_1of2.zip Unpacking will take some time, Please wait… Successfully unpacked the files to repository. [[email protected] Oracle_Soft_Repo]# oakcli unpack -package /cloudfs/Oracle_Soft_Repo/p26433712_1212120_Linux-x86-64_2of2.zip Unpacking will take some time, Please wait… Successfully unpacked the files to repository. [[email protected] Oracle_Soft_Repo]# oakcli unpack -package /cloudfs/Oracle_Soft_Repo/p28216780_122140_Linux-x86-64_1of3.zip Unpacking will take some time, Please…

This article describes patching a virtualized Oracle Database Appliance (ODA) containing only an ODA_BASE virtual machine. Do this patching first on test machines because it can not be guaranteed that all causes of failures of single VM ODAs are covered in this article. I got the experience that precheck for ODA patches does not detect some failure conditions which may lead to an unusuable ODA. Overview: Patch first to 12.1.2.12.0 After that patch to 12.2.1.4.0…

When a patch fails on a virtualized Oracle Database Appliance (ODA), this ODA is often unusuable because Linux and OAKD are patched to new release but Grid Infrastructure is still on old version. OAKD cannot be restarted in default mode because in this mode the active Grid Infrastructure version is checked, which will fail due to old version. Also Grid Infrastructure cannot be started due to the fact that OAKD controls access of shared hardware…

When manually upgrading Grid Infrastructure on an ODA according to MOS note 2379389.1 it has to be done as grid user. This can fail with OUI-10022 error which indicates that Oracle inventory is corrupt. But when trying an “opatch lsinventory” as oracle and as grid user these commands succeeded, so inventory seems to be ok. It turned out that the locks subdirectory of the oracle inventory was not writable for the grid user. After making…

Tuesday this week I had the opportunity to get in touch with shareplex, Quest’s replication solution. This product does not rely on Oracle licenses, so can also be used with Standard Edition. It is competitor of Oracle’s GoldenGate an used for asynchronous replication, too. An interesting feature is that not only committed transactions can be replicated, which is an advantage with big transactions. With this feature replication latencies within seconds can be realized. Also migrations…