Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Administration (MOSC)

DG configuration failed after cleared old one with

Apr 23, 2017 11:48PM edited Apr 24, 2017 2:03PM in Database Administration (MOSC) 4 commentsAnswered

DGMGRL> create configuration XXXP1 as primary database is XXX1W connect identifier is 'xxcw1101-dgscan:6101/XXX1W';

Configuration "xxx1" created with primary database "xxx1w"

DGMGRL> add database yyy1R as connect identifier is 'yycr1101-dgscan:6101/yyy1R' maintained as physical;

Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month