I faced this error a few times so I though to write a quick note for an easy fix. While you try to start DB, it gets this error. I know… this is 10g, but sometimes Clients do not want to upgrade and you have to deal with it… If you check alert log, you... » read more
This post will go though the steps needed to upgrade an Oracle Grid High Availability Services (HAS) from version 12c (12.1.0.2) to 19c (19.13.0) on a Linux environment. 1:- As per document Doc ID 2539751.1, Patch 28553832 is a prerequisite for both GI and DB Upgrade. Here the steps to apply Oct 2021 PSU which... » 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
Setting up Network Encryption in our Oracle environment is very easy, we just need to add these lines to the sqlnet.ora on server side: Ideally, on the client side we should add these too: But since ENCRYPTION_CLIENT by default is ACCEPTED, if we see this chart, connection would be encrypted (ACCEPTED – REQUESTED case) Lets... » read more
We had this error while trying to open a DB: Digging a bit on the enviroment, we noticed server had a power cut and DB did not stop gracefully. This is how we fixed: 1:- Start DB in mount and list log files: 2:- Recover Database: (we need to input the failed log file): 3:-... » read more
This is a weird case we had for a Customer where DB/PDB’s were running fine and after a restart, one of the PDB’s went to restricted YES.We don’t know why it went to restricted mode because there hasn’t been a patching activity for a while and DB had few restarts in the past with no... » read more