Thomas Mohr
@dbathomas.bsky.social
Oracle DBA since 2002, Microsoft SQL Server Admin since 2012
After dropping Tablespace rman Backup on Standby fails with ORA-20079 and PLS-00302 'INITDIFLAGS' must be declared..... Trying recover from primary service ends with same result. After connecting only to Standby instance (no conn to catalog) this works. Then resync of catalog also works.
October 30, 2025 at 10:42 AM
After dropping Tablespace rman Backup on Standby fails with ORA-20079 and PLS-00302 'INITDIFLAGS' must be declared..... Trying recover from primary service ends with same result. After connecting only to Standby instance (no conn to catalog) this works. Then resync of catalog also works.
Set Incarnation of Standby-DB to same AS on Primary and then
Recover Standby Database from Service Primary DB made it.
Recover Standby Database from Service Primary DB made it.
August 25, 2025 at 8:18 AM
Set Incarnation of Standby-DB to same AS on Primary and then
Recover Standby Database from Service Primary DB made it.
Recover Standby Database from Service Primary DB made it.
Recovery of Standby-DB after PITR on Primary
Dgmgrl config showed Error after PITR, so i tried flashback DB to PrimSCN - 2. OK, dgmgrl showed Success but switchover hangs ……. Hmmm, no Error - message. Alert-log “ends” with ….Media Recovery waiting for …. .
V$managed_standby: No Changes….
Dgmgrl config showed Error after PITR, so i tried flashback DB to PrimSCN - 2. OK, dgmgrl showed Success but switchover hangs ……. Hmmm, no Error - message. Alert-log “ends” with ….Media Recovery waiting for …. .
V$managed_standby: No Changes….
August 25, 2025 at 8:17 AM
Recovery of Standby-DB after PITR on Primary
Dgmgrl config showed Error after PITR, so i tried flashback DB to PrimSCN - 2. OK, dgmgrl showed Success but switchover hangs ……. Hmmm, no Error - message. Alert-log “ends” with ….Media Recovery waiting for …. .
V$managed_standby: No Changes….
Dgmgrl config showed Error after PITR, so i tried flashback DB to PrimSCN - 2. OK, dgmgrl showed Success but switchover hangs ……. Hmmm, no Error - message. Alert-log “ends” with ….Media Recovery waiting for …. .
V$managed_standby: No Changes….
Another story about me and the ‘/’ ;-)
While duplicating DB for Standby i ran into
several errors reg the standby-files.
But why? Checked db_create_file_dest several times. OK, it was ‘/u01/oradata/newdb’ changed to ‘/u01/oradata/newdb/’. It works.
While duplicating DB for Standby i ran into
several errors reg the standby-files.
But why? Checked db_create_file_dest several times. OK, it was ‘/u01/oradata/newdb’ changed to ‘/u01/oradata/newdb/’. It works.
August 1, 2025 at 11:01 AM
Another story about me and the ‘/’ ;-)
While duplicating DB for Standby i ran into
several errors reg the standby-files.
But why? Checked db_create_file_dest several times. OK, it was ‘/u01/oradata/newdb’ changed to ‘/u01/oradata/newdb/’. It works.
While duplicating DB for Standby i ran into
several errors reg the standby-files.
But why? Checked db_create_file_dest several times. OK, it was ‘/u01/oradata/newdb’ changed to ‘/u01/oradata/newdb/’. It works.
Add '/' in config file didn't work.So reinstall Oracle Database Home and make sure that Oracle_Home ends with 'db_home'. Autoupgrade works fine then.
July 4, 2025 at 6:28 AM
Add '/' in config file didn't work.So reinstall Oracle Database Home and make sure that Oracle_Home ends with 'db_home'. Autoupgrade works fine then.
While working with Oracle autoupgrade i ran into "cannot connect to database / maybe wrong sid / database not started or not same oracle_home as written in config file". I noticed that, if connect as sysdba, oracle_home ends with 'db_home/', but in config file without '/'.
July 4, 2025 at 6:27 AM
While working with Oracle autoupgrade i ran into "cannot connect to database / maybe wrong sid / database not started or not same oracle_home as written in config file". I noticed that, if connect as sysdba, oracle_home ends with 'db_home/', but in config file without '/'.
Despite what critics wrote: IMHO it was a great show. I enjoyed :-)
June 21, 2025 at 2:07 PM
Despite what critics wrote: IMHO it was a great show. I enjoyed :-)
Upgrade to 19.27 has been done. Will now start my trip to Munich for the GnR - show.
June 19, 2025 at 7:51 AM
Upgrade to 19.27 has been done. Will now start my trip to Munich for the GnR - show.
Unhappy about not to attend #DOAGDB25 this year due to absence. When i'm back on my chair 19.27 will be installed. Don't forget, 1st deinstall DataPump-Bundle Patch this time :-)
May 2, 2025 at 7:27 PM
Unhappy about not to attend #DOAGDB25 this year due to absence. When i'm back on my chair 19.27 will be installed. Don't forget, 1st deinstall DataPump-Bundle Patch this time :-)
Just wondering about service_names after Database duplication.... Procedure dbms_service.delete_service works, but after auxiliary-db-reboot the service is there again.... Source-db is HA with Data Guard, so the trigger which checks If DB is primary is also copied and starts the service. Disable it.
April 10, 2025 at 12:47 PM
Just wondering about service_names after Database duplication.... Procedure dbms_service.delete_service works, but after auxiliary-db-reboot the service is there again.... Source-db is HA with Data Guard, so the trigger which checks If DB is primary is also copied and starts the service. Disable it.
Still working on removing failed SQL 2022 - Upgrade from 2019-node. But for now: vacation :-) Greetings from Las Vegas
March 9, 2025 at 5:01 AM
Still working on removing failed SQL 2022 - Upgrade from 2019-node. But for now: vacation :-) Greetings from Las Vegas