My Oracle Support Banner

Data Guard Standby Database log shipping failing reporting ORA-01031 and Error 1017 when using Redo Transport User (Doc ID 1542132.1)

Last updated on MAY 03, 2022

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

***Reviewed for Relevance 16-Jul-2015 ***<br* **

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner. 

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Database username:  REDOSHIP
Standby Database:  STBY

********

Redo shipping and FAL requests are failing between the Primary and Standby sites. 

Enabling a trace of the event 16191 and reproducing the error using a defer and re-enable of the log archive shipping destination in the Primary site shows the following errors appear when a login attempt is made by the Primary to the standby site.

  Redo shipping client performing standby login

 

Archiver Trace Extract

 
The ARCH background process is attempting to connect to the standby site and failing reporting the errors in the trace file, 1031 insufficent privileges, 1017 and 16191.

Changes

 In this case the password file has been recreated and redistributed to the Primary and Standby sites and the RDBMS parameter redo_transport_user is set and SYSOPER has not been granted to the user specified in redo_transport_user.  Another scenario would be where the environment is a brand new environment where the parameter redo_transport_user has been implemented and SYSOPER has not been granted to the user specified in redo_transport_user.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.