Upgraded production to 11.2.0.4 a few nights ago. The primary is 3-node RAC and the standby is 2-node RAC. Notice that one of the threads was not transmitting redo to the standby. Saw this repeatedly in the alert log:
Error 1033 received logging on to the standby
Turns out this was a problem of my own making. In $ORACLE_HOME/dbs, I had the following:
-rw-rw—- 1 oracle oinstall 1544 Sep 18 01:44 hc_ncpp5.dat
Let’s know all versions of kamagra brand for a healthy and effective ED treatment: Kamagra Tablets – It was the first genuine drug, produced by Ajanta Pharmacy to make buy levitra viagra ED treatment more comfortable. There is no substantial evidence that Serogen is really effective. viagra no prescription pamelaannschoolofdance.com The endocrinology cheap generic viagra treatment in France is considered as a successful remedy of men’s erection issue. Soft Tabs are the most reliable and effective form of treating erectile dysfunction viagra cialis india and other sexual problems in males. -rw-r–r– 1 oracle oinstall 55 Sep 18 01:38 initncpp5.ora
lrwxrwxrwx 1 oracle oinstall 40 Sep 18 01:38 orapwnp5 -> /u01/app/oracle/admin/ncpp/dbs/orapwncpp
lrwxrwxrwx 1 oracle oinstall 45 Sep 18 01:38 spfilencpp5.ora -> /u01/app/oracle/admin/ncpp/dbs/spfilencpp.ora
Since the primary is RAC, I put the password file and spfile on shared storage. I then create softlinks in $ORACLE_HOME/dbs. The softlink was a typo. That’s what I get for staying up until 3am while sick when trying to upgrade a production database. The fix was as simple as:
mv orapwnp5 orapwncpp5
That fixed everything for me!
