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

MOSC Banner

Unsupported datatypes

edited May 10, 2010 3:24AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
Hi:

We've a physical standby for DR and we're planning to setup a logical standby for reporting.  I've checked dba_logstdby_unsupported and there are some tables listed with following datatypes.  What would be the best workaround for these data types.

BFILE
TIMESTAMP(6)
ANYDATA
CMN_AQFLSJ2_MESSAGE_TYPE

Doc. 559353.1 discussess EDS for some datatypes but I'm not sure if I can apply same to BFILE, TIMESTAMP and ANYDATA too.

Any help would be much appreciated.

Regards.

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