Monday, March 7, 2016

kfod corrupt after patching

Short post that hopefully will save you time After patching to QFSDP 2016 jan it looked like dbca wasn't seeing ASM disks any more. Quickly @vanpupi found that it was related to kfod. apparently on a linux system it uses % instead of $ in $ORACLE_HOME/bin/kfod both in GI as in the DB home change the kfod file to following




did the trick good find pieter

Thursday, March 3, 2016

using oplan

While preparing for the QFSDP of january 2016 we ran into an issue with oplan. We wanted to use oplan to generate the steps for patching since opatchauto couldn't be used in this case. but ran into this on a exadata OVM machine with plenty of rac databases

oracle.oplan.sdk.OPlanException: There is no RAC DB Instance running onexa01adm01vm01
 at oracle.oplan.db.cmdtranslator.commands.SqlPatchCommand.getOracleSIDForActiveInstance(
 at oracle.oplan.db.cmdtranslator.commands.SqlPatchCommand.getExecutionStep(
 at oracle.oplan.db.cmdtranslator.commands.SqlPatchCommand.generateExecutionSteps(
 at oracle.oplan.sdk.cmdtranslator.Command.getExecutionSteps(
 at oracle.oplan.core.engine.SequencingEngine.expandRollingPhase(
 at oracle.oplan.core.engine.SequencingEngine.expandPhases(
 at oracle.oplan.core.engine.SequencingEngine.getExecutionPlan(
 at oracle.oplan.sdk.oplan.OPlan.process(
 at oracle.oplan.sdk.oplan.OPlan.generateApplySteps(
 at oracle.oplan.sdk.oplan.OPlan.main(

after scratching our head we figured out that this was due to a database that was not running. since it wasn't needed anymore we removed it from the cluster and then everything went fine. The problem is that the error message is not clear at all. hope this helps when you encounter this .