Forum Stats

  • 3,825,996 Users
  • 2,260,586 Discussions
  • 7,896,760 Comments

Discussions

18c: After recovery tablespace is not coming online.

4122985
4122985 Member Posts: 1
edited Apr 21, 2020 2:55AM in Recovery Manager (RMAN)

The TB1 tablespace is not coming online after recovery. I am using Veritas Backup Exec to backup the DB and recover. Please find RMAN output below. The datafile for TB1 tablesapce (F:\ORACLE\DBFILES\PHUKET\DATAFILE\TB1.DBF) is restored correctly but it is not coming online. The tablespace is not listed in the list of tablesapces.

The tablesapce in question (TB1) is created in CDB. My Oracle version is 18.3

RMAN output:

*************************************************************************************

SQL*Plus: Release 18.0.0.0.0 - Production on Mon Apr 6 01:08:15 2020

Version 18.3.0.0.0

Copyright (c) 1982, 2018, Oracle. All rights reserved.

Connected.

Database closed.

Database dismounted.

ORACLE instance shut down.

ORACLE instance started.

Total System Global Area 2583690704 bytes

Fixed Size 9031120 bytes

Variable Size 687865856 bytes

Database Buffers 1879048192 bytes

Redo Buffers 7745536 bytes

Disconnected from Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production

Version 18.3.0.0.0

Recovery Manager: Release 18.0.0.0.0 - Production on Mon Apr 6 01:10:03 2020

Version 18.3.0.0.0

Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.

connected to target database: PHUKET (not mounted)

# -----------------------------------------------------------------

# RMAN command section

# -----------------------------------------------------------------

RUN {

ALLOCATE CHANNEL ch0

TYPE 'SBT_TAPE';

SEND 'BSA_SERVICE_HOST=WIN-MOGH9HBJT4S,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={D2ED17C2-6001-4ECA-A712-0169269117FB},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\WIN-P98MNHP9CP9\PHUKET';

RESTORE CONTROLFILE FROM 'BE_c-507144180-20200406-01';

ALTER DATABASE MOUNT;

RESTORE

DATABASE;

RECOVER

DATABASE;

RELEASE CHANNEL ch0;

alter database open resetlogs;

}

using target database control file instead of recovery catalog

allocated channel: ch0

channel ch0: SID=387 device type=SBT_TAPE

channel ch0: Veritas/BackupExec/1.1.0

sent command to channel: ch0

Starting restore at 06-APR-20

channel ch0: restoring control file

channel ch0: restore complete, elapsed time: 00:00:25

output file name=F:\ORACLE\DBFILES\PHUKET\CONTROLFILE\O1_MF_H7K574RW_.CTL

output file name=F:\ORACLE\FRA\PHUKET\CONTROLFILE\O1_MF_H7K574TT_.CTL

Finished restore at 06-APR-20

Statement processed

Starting restore at 06-APR-20

skipping datafile 5; already restored to file F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_SYSTEM_H7K5MT8F_.DBF

skipping datafile 6; already restored to file F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_SYSAUX_H7K5MT50_.DBF

skipping datafile 8; already restored to file F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_UNDOTBS1_H7K5MT8X_.DBF

skipping datafile 9; already restored to file F:\ORACLE\DBFILES\PHUKET\9558A20D257A42D1A0EF8FA6736E22CD\DATAFILE\O1_MF_SYSTEM_H7K6GPFX_.DBF

skipping datafile 10; already restored to file F:\ORACLE\DBFILES\PHUKET\9558A20D257A42D1A0EF8FA6736E22CD\DATAFILE\O1_MF_SYSAUX_H7K6GPGD_.DBF

skipping datafile 11; already restored to file F:\ORACLE\DBFILES\PHUKET\9558A20D257A42D1A0EF8FA6736E22CD\DATAFILE\O1_MF_UNDOTBS1_H7K6GPGW_.DBF

skipping datafile 12; already restored to file F:\ORACLE\DBFILES\PHUKET\9558A20D257A42D1A0EF8FA6736E22CD\DATAFILE\O1_MF_USERS_H7K6HF35_.DBF

channel ch0: starting datafile backup set restore

channel ch0: specifying datafile(s) to restore from backup set

channel ch0: restoring datafile 00001 to F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_SYSTEM_H7K4Y2Y8_.DBF

channel ch0: restoring datafile 00003 to F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_SYSAUX_H7K50RJL_.DBF

channel ch0: restoring datafile 00004 to F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_UNDOTBS1_H7K52HY8_.DBF

channel ch0: restoring datafile 00007 to F:\ORACLE\DBFILES\PHUKET\DATAFILE\O1_MF_USERS_H7K52K6T_.DBF

channel ch0: restoring datafile 00014 to F:\ORACLE\DBFILES\PHUKET\DATAFILE\TB1.DBF

channel ch0: reading from backup piece BE_0nusu093_1_1

channel ch0: piece handle=BE_0nusu093_1_1 tag=TAG20200406T010019

channel ch0: restored backup piece 1

channel ch0: restore complete, elapsed time: 00:00:35

Finished restore at 06-APR-20

Starting recover at 06-APR-20

starting media recovery

archived log for thread 1 with sequence 2 is already on disk as file F:\ORACLE\DBFILES\PHUKET\ONLINELOG\O1_MF_2_H7K57BZ7_.LOG

archived log for thread 1 with sequence 3 is already on disk as file F:\ORACLE\DBFILES\PHUKET\ONLINELOG\O1_MF_3_H7K57BZ7_.LOG

archived log file name=F:\ORACLE\DBFILES\PHUKET\ONLINELOG\O1_MF_2_H7K57BZ7_.LOG thread=1 sequence=2

archived log file name=F:\ORACLE\DBFILES\PHUKET\ONLINELOG\O1_MF_3_H7K57BZ7_.LOG thread=1 sequence=3

media recovery complete, elapsed time: 00:00:03

Finished recover at 06-APR-20

released channel: ch0

Statement processed

EXIT

Recovery Manager complete.

*************************************************************************************

Answers

  • Sunny kichloo
    Sunny kichloo Member Posts: 2,459 Gold Trophy
    edited Apr 21, 2020 1:47AM

    Can you please status of tablespace?

    Also is there some error which you have encountered in alert.log

  • Dude!
    Dude! Member Posts: 22,829 Black Diamond
    edited Apr 21, 2020 2:55AM

    I cannot read anyone's mind. What are you trying to accomplish?

    If you are restoring the database to revert a drop tablespace you need to:

    a) restore the controlfile and backup prior to dropping the tablespace

    b) stop recovery prior to dropping the tablespace

    Why are you restoring the database?