Database Tuning (MOSC)

MOSC Banner

Strange behavior after AWR data captured for Active Data Guard standby DB

edited May 5, 2020 5:07AM in Database Tuning (MOSC) 3 commentsAnswered

We have implemented in our organization AWR data captured for Active Data Guard standby databases (according to Doc ID 2409808.1: How to Generate AWRs in Active Data Guard Standby Databases), and we are experiencing this strange behavior:

  1. DBA_HIST_ACTIVE_SESS_HISTORY is empty for the active DG. same goes with DBA_HIST_SYSMETRIC_HISTORY. also empty.
  2. Every LOB column are being cut after 4000 bytes. For example: in DBA_HIST_SQLTEXT, SQL_TEXT column is cut after 4000. Also in DBA_HIST_SQL_PLAN , OTHER_XML column is cut after 4000.

I wonder if anyone have implemented it, and whether they are experiencing the same phenomenon. If it happened to anyone else too, and you have managed to overcome this two situations, please share.

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