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

MOSC Banner

The Data Guard status of xxxxxDG is Warning ORA-16856: transport lag could not be determined.

edited Nov 11, 2015 4:09PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 commentsAnswered

Hi All,

I need your suggestion about the below issue.

issue: Receiving multiple incidents with respect to "transport lag could not be determined" error in my production database.

We have raised the SR about the issue and provided all the diag logs to oracle to investigate from their end and they confirmed me to increase the REDO log size. Here I would like to highlight already am having 8GB each redo and nearly am having 8 online redologs and 9 standby redologs. Can you please give me your ideas what will be the issue and what is causes for this error. Archive log generation count is enclosed as below.

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