Auxiliary database has been started by startup Nomount, but the display status is not started after Rman is connected
$ export oracle_sid=dupdb$ sqlplus '/as sysdba ' sql> startup Nomount $ rmanrecovery manager:release 11.2.0.1.0-produc tion on Fri June 14:16:14 2015Copyright (c) 1982, for Oracle and/or its affiliates. All rights reserved. Rman> Connect target sys/[email protected]connected to target database:ora11 (dbid=785451981) rman> Connect auxiliary sys/[email protected]connected to auxiliary database:dupdb (not started)
#not started, which means that we are connected to an idle routine, which is usually caused by an incorrect oracle_home configuration in the static service name or incorrect SID configuration.
Check the listening file, found that the oracle_home path last one more '/'
SID_LIST_ORA11 = (sid_list = ( Sid_desc = (global_dbname = ora11) (oracle_home =/u11/app/oracle/ Product/11.2.0/dbhome_1) ( sid_name =ora11) ) (Sid_desc = (global_dbname = dupdb) (Oracle_home = /u11/app/oracle/product/11.2.0/dbhome_1/) (sid_name =dupdb) ) )
Remove the '/' from the above code.
In addition, we can also test if we are connected to an instance of the boot instance, or to an idle instance, by Sqlplus Xxx/[email protected] as SYSDBA.
Duplicate database, Rman connection auxiliary database after the state is not correct