Is on the remote server right? If yes it shows that RMAN was able to connect to the Primary server and the local static connection. So the issue is probably that the Primary server cannot connect back.
connected to target database: CEMABC (DBID=4229695208) connected to auxiliary database: CEMABC (not mounted)
This ( above is odd )
rman target backup_admin/temabc@cemabc_p catalog rman/qaabc@rmnabc
I use SYS/PASSWORD on both for it to work.
rman target=sys/@recover2 auxiliary=sys/@reclone
And restart the listeners afterwards
listener.ora INBOUND_CONNECT_TIMEOUT_<listener_name> = 120 sqlnet.ora SQLNET.INBOUND_CONNECT_TIMEOUT = 120
I encountered same problem too, create a user with "SYSDBA" privilege doing RMAN duplicate.
Then ORA-17629 occurs...Do you know any document specify that duplicate must use with SYS user?
Thanks for your reply,
I've copied password file to standby side. And Last time I done successfully with SYS user.
Due to our DB privilege control policy, now I have to create an new DB user with specific system privileges(as below) for data guard maintain/establish purpose .
Are these privileges not enough ?
Need DBA privilege for dba user.
When you changed or create a SYSDBA or SYSOPER user you must copy password file to standby side.
Because password file must be same for data guard configuration databases.
Yes, you can use management database, dba tasks with dba privileged user. But my recomendation use only SYS user for duplication of database.
Unlike sqlplus, RMAN does not support the "AS SYSDBA" syntax. Therefore, it implicitly assumes only a SYS connection.
"The only difference is that RMAN connections to a target or auxiliary database require the
SYSDBA privilege. The
AS SYSDBA keywords are implied and cannot be explicitly specified"
sqlplus allows you to use other usernames because it supports the "AS SYSDBA" syntax.
Hemant K Chitale
Hi Hemant K Chitale,
Thanks for reply,
After logon RNAM with "AS SYSDBA ". The user I created for logon RMAN can perform other backup, restore, recovery tasks, only duplicate command with such problem.
I've raised a SR on MOS now...
Below the script is that I create with.
CREATE USER DGADMIN
IDENTIFIED BY <password>
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
-- 5 System Privileges for DGADMIN
GRANT ALTER DATABASE TO DGADMIN;
GRANT ALTER PROFILE TO DGADMIN;
GRANT ALTER SYSTEM TO DGADMIN;
GRANT ALTER TABLESPACE TO DGADMIN;
GRANT CREATE SESSION TO DGADMIN;
-- 2 ROLE for DGADMIN
GRANT CONNECT TO DGADMIN;
GRANT SYSDBA TO DGADMIN;