High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Error:Backing up a Physical Standby database requires a recovery catalog

edited Feb 5, 2019 6:35AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 8 commentsAnswered ✓

we have 4 node RAC and we have build the 4 node Standby database (SP32) through OEM and planning to take the RMAN backup's from OEM console.

1) OEM USER: MXK25 build the Standby setup (SP32) and he can able to schedule the backup's from OEM Console

2) OEM USER: Sysman can't able to trigger the "Schedule backup" from OEM Console through sysman user and other users in OEM Console for the same standby database (SP32)

3) for finding the root cause we are build the Standby database through OEM SYSMAN user, but sysman user also can't able to trigger the "Schedule backup" from OEM Console and other users also for the standby database (SP30)

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center