I am trying to upgrade all of our databases from 11.2.0.2 to 11.2.0.3 this year. My first upgrades were on a 2-node RAC primary with 2-node RAC standby database in a testbed. There isn’t much to this database as it is just a starter database. But this let me test out the upgrade on RAC databases with both a primary and standby. I documented the process along the way.
After that, I was ready to upgrade our development and test databases. I used the DBUA to perform the upgrade and it went off without a hitch. Our dev and test databases are clones of production and we were able to test our custom application with the new version.
Finally, I was ready to upgrade production. Again, I used the DBUA to perform the upgrade of the primary database. But this time, I hit an error:
Whether viagra online shop one has erectile problems due to stress and anxiety. online viagra store Spinal cord injury occurs when there is any damage to the ulnar nerve the messages from the brain cannot transmit to the little finger, it is just like cutting a telephone cord. Symptoms Irritable Bowel Syndrome pain http://greyandgrey.com/wp-content/uploads/2018/07/Logan.pdf viagra prices in usa can be extremely uncomfortable but manageable once diagnosed so it’s best to stay alert for symptoms. ED caused by viagra price uk http://greyandgrey.com/wp-content/uploads/2018/07/WTC-Monitoring-Program-Oct-2010.pdf stress, depression, shift change, lifestyle change and aging is treatable with this wonderful medicine. ORA-16205 log_archive_dest2 contains repeated or conflicting values
Uh oh. This was unexpected as I had not seen this error in any of my previous upgrades. The dev and test databases do not have a standby, so LOG_ARCHIVE_DEST2 is not set. My testbed is set up slightly differently, so I did not catch the issue there. Since this was an unforeseen event, I cancelled my upgrade that evening and decided to get to the bottom of the issue and reschedule the upgrade for a later date.
I discovered that Bug 13387526 (fixed in 11.2.0.4) can cause this issue for this parameter when you do STARTUP UPGRADE on the database. In my testbed, I created a RAC 11.2.0.2 database with a RAC standby. In the primary, I set LOG_ARCHIVE_DEST_2 to something very similar to what was in production. I attempted the upgrade on this testbed and ran into the same bug. To get around the problem, I set LOG_ARCHIVE_DEST_2 to ‘service=my_standby db_unique_name=my_standby’. With this minimal parameter setting, the upgrade then proceeded correctly. After the upgrade was done, I set this parameter back to its original setting.
