How to rename a redo logfile.

By -

While Opening the database with resetlogs option post incomplete media recovery (Migrated database to another server), receiving the following error:


SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00349: failure obtaining block size for
'/oracle/app/oracle/oradata/ORCL/redo01.log'
ORA-27041: unable to open file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9

 SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [ksvworkmsgalloc: bad reaper],
[0x080010003], [], [], [], [], [], [], [], [], [], []
SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 2;
ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 2
*
ERROR at line 1:
ORA-00349: failure obtaining block size for '/oracle/app/oracle/oradata/ORCL/redo02.log'
ORA-27041: unable to open file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9

Reason:

Since this database was migrated to another server, the redo log file which it is trying to read or flush is not physically available there. Also controlfile is having the information of redo log file as per your previous server structure. Hence you are receiving this error.

Solution:


SQL> select * from v$log;
SQL> set pages 333 line 222
    GROUP#    THREAD#  SEQUENCE#      BYTES  BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME     CON_ID
---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------ --------- ----------
         1          1          0  209715200        512          1 NO  CLEARING_CURRENT    1.0844E+13 16-APR-20   1.8447E+19                    0
         3          1          0  209715200        512          1 NO  CLEARING            1.0844E+13 16-APR-20   1.0844E+13 16-APR-20          0
         2          1          0  209715200        512          1 NO  CLEARING            1.0844E+13 16-APR-20   1.0844E+13 16-APR-20          0



SQL> col member for a70
SQL> select * from v$logfile;

    GROUP# STATUS  TYPE    MEMBER                                                                 IS_     CON_ID
---------- ------- ------- ---------------------------------------------------------------------- --- ----------
         3         ONLINE  /oracle/app/oracle/oradata/ORCL/redo03.log                           NO           0
         2         ONLINE  /oracle/app/oracle/oradata/ORCL/redo02.log                           NO           0
         1         ONLINE  /oracle/app/oracle/oradata/ORCL/redo01.log                           NO           0



SQL> alter database rename file '/oracle/app/oracle/oradata/ORCL/redo03.log' to '/orcl_data/oradata/ORCL/redo/redo03.log';

Database altered.

SQL> alter database rename file '/oracle/app/oracle/oradata/ORCL/redo02.log' to '/orcl_data/oradata/ORCL/redo/redo02.log';

SQL>
Database altered.

SQL>
alter database rename file '/oracle/app/oracle/oradata/ORCL/redo01.log' to '/orcl_data/oradata/ORCL/redo/redo01.log';


SQL>
Database altered.

SQL>ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 2;

Database altered.

SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1;

Database altered.

SQL>  ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3;

Database altered.

SQL> alter database open resetlogs;

Database altered.

SQL>


Congrats, It's all done.

Thanks & Regards
Nikhil Kumar.

Comments

Post a Comment

Popular posts from this blog

How to set the root password after creating instance on oracle cloud

By -
How to set the root password after creating instance on oracle cloud? since you have created instance on oracle cloud, it requires you private .ppk key file to login from putty you can login on your instance by directly providing that private key. and on Linux/Unix defult user is "opc". since during creation of instance it  will not ask you for  root password. You dont need any password to connect to root. to connect to root type below command as opc user. [opc@sts ~]$ sudo su [root@sts opc]# by this you will login as root. Now change your password [root@sts opc]# passwd Changing password for user root. New password: Retype new password: passwd: all authentication tokens updated successfully. [root@sts opc]# All done. Thanks & Regards Nikhil Kumar.
Read more

TNS-12541 TNS-12560 TNS-00511 TNS:protocol adapter error No listener

By -
Oracle Listener does not start with errors:  TNS-12541: TNS:no listener TNS-12560, TNS-00511, Linux Error: 2: No such file or directory, The listener supports no services euls25002.sgp.st.com:oraSID 51> ps -ef | grep -i tns root       330     2  0 Jul19 ?        00:00:00 [netns] oraSID   17512     1  0 Jul20 ?        00:01:25 /oracleSID/SID/121/bin/tnslsnr LISTENER_SID -inherit oraSID   56223 56131  0 08:02 pts/1    00:00:00 grep --color=auto -i tns euls25002.sgp.st.com:oraSID 52> lsnrctl status LISTENER_SID LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 25-SEP-2017 08:02:19 Copyright (c) 1991, 2014, Oracle.  All rights reserved. Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SID.WORLD)) TNS-12541: TNS:no listener  TNS-12560: TNS:protocol adapter error   TNS-00511: No listener    Linux Error: 2: No such file or directory ...
Read more

Queryable inventory could not determine the current opatch status.

By -
[oracle@Testing02 OPatch]$ ./datapatch -verbose SQL Patching tool version 12.2.0.1.0 Production on Fri May 15 15:54:19 2020 Copyright (c) 2012, 2019, Oracle.  All rights reserved. Log file for this invocation: /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log Connecting to database...OK Bootstrapping registry and package to current versions...done Queryable inventory could not determine the current opatch status. Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual' and/or check the invocation log /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log for the complete error. Prereq check failed, exiting without installing any patches. Please refer to MOS Note 1609718.1 and/or the invocation log /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log for information on how to resolve the above errors. SQL...
Read more