Posts tagged ‘ORA-39097’

December 12, 2011

Export Bump on Logical standby database failed with error ORA-39068 and ORA-39097

ORA-39006, ORA-39068, ORA-16224, ORA-39097 Errors Raised During Datapump Export With Logical Standby Dataguard Guard_Status Set to ‘ALL’ [ID 1236184.1]

Modified 13-OCT-2010     Type PROBLEM     Status MODERATED

In this Document
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support’s Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server – Enterprise Edition – Version: 10.2.0.4 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.

Symptoms

The following errors are seen during execution of Datapump export:
ORA-39006: internal error
ORA-39068: invalid master table data in row with PROCESS_ORDER=-3
ORA-16224: Database Guard is enabled
ORA-39097: Data Pump job encountered unexpected error -16224

The logical standby Dataguard guard_status has a value of ‘ALL.’
This value can be confirmed by the following query:

     SQL > select guard_status from v$database;

Cause

This is expected behavior when Datapump export is executed on a standby database when Dataguard guard_status has a value of 'ALL.' Datapump execution must be able to create a Master Table to store metadata for the Datapump task. When the standby database guard_status is set to 'ALL,' no updates are allowed including the creation of the Master Table which is required for Datapump to execute.

Solution

Alter the database so that the Dataguard guard_status is set to a value of either 'STANDBY' or 'NONE' then repeat the Datapump export task.

Follow

Get every new post delivered to your Inbox.