We are running datapatch on a Windows environment after a BP patching, but it was failing with: For the fix, we applied solution suggested on: 12.1: datapatch -verbose Fails with Following Error”PLS-00201: identifier ‘UTL_FILE’ must be declared” (Doc ID 2265408.1):
This post will go though the all the steps needed to upgrade a 12.1.0.2 database to a 19c using AUTOUPGRADE. Source DB: 1:- Create 19c directory and copy software: 2:- Create response file for a silent 19c Instalation: 3:- Execute 19c pre-requisites: 4:- Install 19c software in silent mode: 5:- Execute root.sh (as root): 6:-... » read more
This activity is part of a GI upgrade from 12.1.0.2 to 19c, in which we need to apply latest PSU first, so here are the steps: 1:- Patches available here: 2:- (as ROOT) Update OPACH version to latest available. (p6880880_122010_Linux-x86-64.zip) 3:- (as ROOT) Run prepatch script. (RDBMS instances should be stopped first) 4:- GI patching:... » read more
Cloud tools are not known to provide huge amount of details when you have an error.In this case we were running patching prechecks which were failing with: Checking log, se can see error was given while trying to execute “select status from pdb_plug_in_violations where type = ‘ERROR’ and status = ‘PENDING’ order by name, time;”... » read more
Sometimes you are doing a cloud patch precheck and error is a bit cryptic, it even says “ready to apply patch”! Now, if you try from the other node it can give you a hint: Somehow it can not copy file from DBNODE_B to DBNODE_A, and indeed, we tried to ssh both ways and we... » read more