WebSQL> alter database drop logfile group 3; alter database drop logfile group 3 * ERROR at line 1: ORA-01623: log 3 is current log for instance SBIP18DB (thread 1) - cannot drop ORA … WebJul 21, 2011 · ORA-01623: log %s is current log for thread %s - cannot drop. In the process of refreshing a 9i Dev database I had to change the file locations of a few datafiles and …
ORA-01623 & ORA-00312 while dropping redo log file/group
WebDec 31, 2024 · ORA-01623: log 2 is current log for instance O12C (thread 1) - cannot drop. If you’re attempting to drop a member from the current online redo log group, then force a … WebMay 13, 2015 · To change the status of a log group from CURRENT to INACTIVE, simply switch a logfile with this command- sql> alter system switch logfile; Run the command 2 or 3 times if the group status does not change. To check status of group remember the command is sql > select GROUP#,THREAD#,STATUS from v$log; phipps photography
ASM的備份集在檔案系統上恢複測試常見問題1.備份資料庫和控制 …
WebOct 20, 2024 · So, what we need to do to be able to drop the redo log files of instance 2, is to disable thread 2 as follows (database must be open): SQL> alter database disable thread 2; Database altered. Niow, we can proceed with the redo log group dropping without issue: SQL> Alter database drop logfile group 3; Database altered. WebJun 19, 2012 · This was previously a 3 node RAC and when it was moved to a different machine, it got build with a 2-node RAC. Hence thread 3 is no more required. Thats why I am planning to drop these Redo Log Groups. WebJan 21, 2024 · ORA-01623: log 31 is current log for instance RACTEST3 (thread 3) – cannot drop Disable thread before dropping the online redo logfiles. Three nodes RAC database was migrated to two nodes RAC database, while trying to drop online redo logs of thread 3, the errors are as below: phipps pharmacy tn