Tag Info

New answers tagged

0

It COULD be simple, but then it's down to luck, more than to anything else. The way of working is very simple : get all processes listed of the main database, ignore the ones from the standby. Then, do the same with the standby database : collect all process info. What is important here, is that you capture this while all is normal. Then you compare both ...


1

Ok, so I had some time to waste, and this is just for the "fun" or "interesting" factor. It's nowhere near that I would use in a real scenario, I have played with it in my lab environment on x86-64 Linux platform, with a few 10g, 11g and 12c databases. At least you can do this even if the database is shut down. When you do a controlfile dump with: alter ...


2

You can try using: ps -ef | grep -v grep | grep ora_pr Or if data guard is in use: ps -ef | grep -v grep | grep ora_rsm


1

The message indicates that no archivelog exists with this sequence in the current incarnation. Failover starts a new incarnation, and log sequences start from 1 again. Let's say your database is at sequence 10 now, and the log sequence was 159 before the failover. V$ARCHIVED_LOG at this point still contains entries about previous incarnation, so the above ...


1

The unique names of the databases in a Data Guard configuration are listed in the log_archive_config parameter in the following form: log_archive_config='DG_CONFIG=(PDB10,PDB10_STBY)' You can remove the old one and add the new one as: alter system set log_archive_config='DG_CONFIG=(PDB10,PDB10SBY)'; After this, you can set log_archive_dest_N to the new ...



Top 50 recent answers are included