OraFAQ Forum: Backup & Recovery » TABLE POINT IN TIME RECOVERY

Home » RDBMS Server » Backup & Recovery » TABLE POINT IN TIME RECOVERY (oracle 12c Windows 2012)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

TABLE POINT IN TIME RECOVERY [message #685692]

Mon, 07 March 2022 07:36

muthukrish104
Messages: 82
Registered: November 2017

Member

Hi All,

I am facing the below error messages while trying to recover a table in Point In Time.

The oracle version is 12.1.0.1.0

Recover Command we use:

run {
recover table table_name.
until time "to_date('2022-03-03 12:27:00', 'YYYY-MM-DD HH24:MI:SS')"
auxiliary destination 'Z:\Table_restore';
}

RMAN-03002: failure of recover command at 03/03/2022 22:32:14
RMAN-06962: Error received during export of metadata
RMAN-06960: EXPDP> ORA-31626: job does not exist
ORA-31633: unable to create master table "SYS.TSPITR_EXP_wwtx_sArc"
ORA-01552: cannot use system rollback segment for non-system tablespace '......'

Kindly guide us,

Thanks and regards
Muthu Krish

Report message to a moderator

Re: TABLE POINT IN TIME RECOVERY [message #685693 is a reply to message #685692]

Mon, 07 March 2022 07:55

Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

ORA-01552: cannot use system rollback segment for non-system tablespace '%s'
 *Cause: Tried to use the system rollback segment for operations involving
          non-system tablespace. If this is a clone database then this will
        happen when attempting any data modification outside of the system
        tablespace. Only the system rollback segment can be online in a
        clone database.
 *Action: Create one or more private/public segment(s), shutdown and then
           startup again. May need to modify the INIT.ORA parameter
           rollback_segments to acquire private rollback segment. If this is
         a clone database being used for tablspace point in time recovery
         then this operation is not allowed.  If the non-system tablespace
         has AUTO segment space management, then create an undo tablespace.

Report message to a moderator

Re: TABLE POINT IN TIME RECOVERY [message #685694 is a reply to message #685692]

Mon, 07 March 2022 13:45

John Watson
Messages: 8960
Registered: January 2010
Location: Global Village

Senior Member

Would Z: be a network attached device? A windows "share"? If so, it may be that your database instance has no privileges on it. A common problem if the database instance service is running under the local system account.

Report message to a moderator

Re: TABLE POINT IN TIME RECOVERY [message #685695 is a reply to message #685694]

Tue, 08 March 2022 00:22

muthukrish104
Messages: 82
Registered: November 2017

Member

Hi Michel,

Kindly clarify:

1) Create one or more private/public segment(s), shutdown and then
startup again. May need to modify the INIT.ORA parameter
rollback_segments to acquire private rollback segment.

Ans: By default all the ROLLBACK SEGMENTS are PRIVATE only, am I right?

2) If this is a clone database being used for tablspace point in time recovery
then this operation is not allowed.

Ans: While using TPIT Recovery, it creates a AUXILARY INSTANCE, am I right?

3) If the non-system tablespace has AUTO segment space management, then create an undo tablespace.

Ans: Yes, it is AUTO only. all the DB's are running with an UNDO tablespace, am I right?

Hi John,

Yes, the Z: Drive is from SAN device only. But the DB instance is not running in the local system account, it is a CLUSTER server and has a DR also.

Thanks and regards
Muthu Krish

Report message to a moderator

Previous Topic:	RMAN resotre/clone to new server
Next Topic:	restoring RMAN backup to point in time on another server, different SID & directory structure

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Nov 21 06:29:34 CST 2024