How to connect Non-sysdba Account via RMAN, When Threaded_execution=TRUE
(Doc ID 2125305.1)
Last updated on OCTOBER 22, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Non-Sysdba username: RMAN
Target Database: ora12102
When threaded_execution=FALSE, non-sysdba account (ie rman) can perform RMAN duties, since it has sysbackup granted.
When threaded_execution=TRUE, it is failing with error ORA-01031
Listener setting, specific to threaded_execution has been set (DEDICATED_THROUGH_BROKER_LISTENER=ON)
$ rman target rman/<password>@ora12102
Recovery Manager: Release 184.108.40.206.0 - Production on Fri Apr 8 18:24:43 2016
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
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