Both utilities are rarely used – usually in case you already ran into a problem. But it’s useful to have basic knowledge because otherwise it’s hard to start with them. This blog post should give you an overview what the utilities are made for. Continue reading “kfed/kfod – What you need to know”
Also this year I’ll be on DOAG Conference and Exhibition like the last 3 years. Last year without a presentation, but this year with 2. Both are on Wednesday and in one of the largest rooms Sankt Petersburg . Thanks to DOAG team. Continue reading “DOAG 2017 CONFERENCE + EXHIBITION – My Presentations”
NEW SCRIPT! – It check the options linked into the oracle software as described in MOS note “How to Check and Enable/Disable Oracle Binary Options (Doc ID 948061.1)” Continue reading “Check options linked into ORACLE_HOME”
This is a really short blog post but to long for Twitter anyway.
If you access the repository database of Oracle Enterprise Manager (OEM) Cloud Control 13.2 to use it for reports with a different database user, you may face the problem that it is no longer working after the upgrade from 12c.
The recommendation from Oracle is to switch from Patch Set Update (PSU) to Proactive Bundle Patch (PBP) only by installing a new patchset or release. i.e 22.214.171.124 to 126.96.36.199 or 12.1.0.X to 188.8.131.52. But it’s possible at any time even rolling.
The idea is quite simple:
In the environment of the cluster owner or some scripts, you may want to set a variable for the cluster installation usually called CRS_HOME, GRID_HOME or simly ORACLE_HOME.
I like to do that in an automatic and non-static way. But be careful, this means it could go wrong or is being set to an unexpected value.
The main part of this post is how get the information and how to check for an acceptable value. Continue reading “How to determine CRS_HOME”
The parameter local_listener of the asm instance is maintained by the clusterware and sometimes set to a wrong value. A port which is higher then the defined port of the local listener.
SYS@+ASM2> show parameter local_li NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ local_listener string (ADDRESS=(PROTOCOL=TCP)(HOST=XX.XX.XX.XX)(PORT=1526))
I faced the bug only in the following configuration:
- cluster installed with version 184.108.40.206
- patch level newer 160119
- more then 2 cluster interconnects