Duplicate database failed

Similar Questions

• RMAN-04014: failed to start: ORA-00600 during the duplicate database

  Hello
  
  Oracle version: 11.2.0.2
  
  OS: linux rhel 5
  
  I do duplicate database of active database
  

  rman target sys/*******@pindb AUXILIARY sys/*****@test
  
  Recovery Manager: Release 11.2.0.2.0 - Production on Mon Nov 26 19:56:41 2012
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  
  connected to target database: pindb (DBID=4116200880)
  connected to auxiliary database: TEST (not mounted)
  
  RMAN> run {
  allocate channel C1 type disk;
  allocate auxiliary channel DUP type disk;
  DUPLICATE TARGET DATABASE  TO 'TEST' FROM ACTIVE DATABASE  DB_FILE_NAME_CONVERT '/oradata/pindb','/oradata/test';
  }2> 3> 4> 5>
  
  using target database control file instead of recovery catalog
  allocated channel: C1
  channel C1: SID=699 device type=DISK
  
  allocated channel: DUP
  channel DUP: SID=5 device type=DISK
  
  Starting Duplicate Db at 26-NOV-12
  
  contents of Memory Script:
  {
     sql clone "create spfile from memory";
  }
  executing Memory Script
  
  sql statement: create spfile from memory
  
  contents of Memory Script:
  {
     shutdown clone immediate;
     startup clone nomount;
  }
  executing Memory Script
  
  Oracle instance shut down
  
  connected to auxiliary database (not started)
  released channel: C1
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Duplicate Db command at 11/26/2012 19:57:07
  RMAN-06403: could not obtain a fully authorized session
  RMAN-04006: error from auxiliary database: ORA-01034: ORACLE not available
  ORA-27101: shared memory realm does not exist
  Linux-x86_64 Error: 2: No such file or directory
  RMAN-03015: error occurred in stored script Memory Script
  RMAN-04014: startup failed: ORA-00600: internal error code, arguments: [kck_rls_check must use (11,0,0,0,0) or lower], [kdt.c], [9576], [11.2.0.2.0], [], [], [], [], [], [], [], []
  RMAN-04017: startup error description: ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

  Please can someone offer
  
  Thank you

  Hello;

  In my view, that it is a bug that has to do with the compatibility of the compression.

  I think that work around is:

  alter system  set "_compression_compatibility"="11.2.0";
  

  Let me confirm with a document number of MOS

  Subsequently Cannot find the doc of MOS - this has some details:

  http://www.acehints.com/2011/11/fix-RMAN-duplicate-database-failed-ora.html

  http://bryangrenn.blogspot.com/2011/12/ora-600-kckrlscheck-must-use-110000-or.html

  Best regards

  mseberg

  Published by: mseberg on November 26, 2012 16:07

• RMAN duplicate database RAC w/ASM to stand alone without ASM fails

  Trying to duplicate database in order to upgrade to 11.2 and migrate from Windows to Solaris with minimal downtime, using GoldenGate. The source database is 11.1.0.7 on Windows 2003 x 64 a 2 RAC node. The auxiliary database is 11.1.0.7 on a single Windows 2003 x 64 server. The steps to reach where the error has occurred are:
  
  1 created auxiliary instance on remote node. creating oradim and the listener.
  
  2 copied password for the remote node target file and put it in the directory %ORACLE_HOME%\database and % ORACLE_HOME%\dbs.
  
  3 created PFILE in %ORACLE_HOME%\database and copied to %ORACLE_HOME%\dbs just in case.
  
  db_name = "UTILAX".
  instance_name = UTILAX
  diagnostic_dest = a: \oracle\admin\utilax'
  db_file_name_convert =('+Data/util','D:\oracle\oradata\utilax')
  log_file_name_convert =('+Data/util','D:\oracle\log\utilax')
  SGA_TARGET = 5g
  control_files=D:\oracle\oradata\utilax\control01.dbf
  compatible = '11.1.0'
  
  4 Startup nomount performed.
  
  5. backup Ran full on the head node to the D drive and outside the DSO.
  
  rman target % = / catalog=rman/password@RMAN
  
  RMAN > run {}
  allocate channel d1 type disk;
  database backup in format "D:\backups\df_t%t_s%s_p%p".
  SQL 'alter system archive log current';
  backup format 'D:\backups\al_t%t_s%s_p%p' archivelog all;
  output channel d1;
  }
  
  6 copied only the manual backup (22 GB) to the remote host files in the same directory on the D drive. D:\backups same folder on both servers.
  
  7. connected with rman, target, catalog and auxiliary databases. A run the rman command to duplicate the database on the target instance.
  
  DUPLICATE THE TARGET DATABASE TO 'UTILAX' IN THE CURRENT DATABASE.
  
  Errors received
  RMAN-03009: failure of the backup on the channel ORA_DISK_1 command
  ORA-17628: error Oracle 19505 returned by remote Oracle Server
  
  8. looked in the auxiliary database alerts log. Errors found:
  ORA-19505: impossible to identify the file 'D:\ORACLE\ORADATA\UTILAX\DATAFILE\SYSTEM.327.716381457 '.
  ORA-27040: create file error, cannot create the file
  04002 - OSD: could not open the file
  S/O-error: (OS 3) the system cannot find the path specified
  
  9 creates all directories to the path and try again. Same mistakes.
  
  
  Must miss one or two steps but document metalink 382269.1 followed as closely as possible. Sorry for the lack of screenshots but databases are private networks. Someone who did that regularly offer any help?
  
  Thank you

  Since you have already made the backup and copied to the auxiliary server, why use again 'data base active'

  DUPLICATE THE TARGET DATABASE TO 'UTILAX' IN THE CURRENT DATABASE.

  Just try to DUPLICATE the DATABASE to 'UTILAX' TARGET nofilenamecheck;

  This would work out.

  or if you want to continue to make use of the active database functionality, then

  DUPLICATE TARGETS DATABASE to the 'UTILAX' of the active database nofilenamecheck.

  Published by: srp on December 28, 2011 12:24 AM

• Create the database fails with error ORA-01505: Error adding log files

  Hi all
  
  hope someone can help out me, I'm creating a database by using a SQL script, the content of the script is:
  create the testora database
  the user sys identified by oracle
  the user identified by oracle's system
  LogFile Group 1 ('/ u01/app/oracle/oradata/testora/redo01a.log ',' / u02/app/oracle/oradata/testora/redo01b.log') blocksize 512 re-use, 100 m in size.
  Group 2 ('/ u01/app/oracle/oradata/testora/redo02a.log ',' / u02/app/oracle/oradata/testora/redo02b.log') blocksize 512 re-use, 100 m in size.
  Group 3 ('/ u01/app/oracle/oradata/testora/redo03a.log ',' / u02/app/oracle/oradata/testora/redo03b.log') blocksize 512 re-use, 100 m in size.
  maxLogFiles 5
  maxlogmembers 5
  MAXDATAFILES 100
  US7ASCII character set
  AL16UTF16 national character set
  Local extended management
  DataFile ' / u01/app/oracle/oradata/testora/system01.dbf' re-use of 400 m size
  SYSAUX datafile ' / u01/app/oracle/oradata/testora/sysaux01.dbf' re-use of 400 m size
  default tablespace users
  DataFile ' / u02/app/oracle/oradata/testora/users01.dbf' size 500 m reuse autoextend on maxsize unlimited
  default temporary tablespace tempts1
  tempfile ' / u01/app/oracle/oradata/testora/temp01.dbf' size 20 m reuse autoextend on maxsize 4g
  Undo tablespace undotbs1
  DataFile ' / u01/app/oracle/oradata/testora/undotbs01.dbf' size 200 m reuse autoextend on maxsize unlimited
  ;
  
  It fails in the creation of the database with the following result:
  
  SQL > @/home/oracle/Oracle_Scripts/testora_db_script.sql
  create the testora database
  *
  ERROR on line 1:
  ORA-01092: ORACLE instance is complete. Disconnection forced
  ORA-01501: CREATE DATABASE failed
  ORA-01505: Error adding log files
  ORA-01184: logfile group 1 already exists
  Process ID: 3486
  ID of the session: 1 serial number: 3

  This is the documentation: http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_5004.htm#i2142335
  >
  If only the DB_RECOVERY_FILE_DEST initialization parameter is specified, Oracle database then creates a log file member to this place.

• RMAN DUPLICATE DATABASE RESULT IN A RE - ORG

  Database Version 10.2.0.4
  
  When I perform a duplicate database RMAN is the new database completely reorganized? The new database can be any fragmentation or water marks high if the source database has done?
  
  Thank you

  The answer to your question is no duplicate RMAN does not cause a re - org, RMAN is a block of files of database level backup, RMAN duplicate is a double level of a data block. Therefore, duplicate RMAN is fundamentally a restoration of the source database, because it is in another location and an instance of the database and the database name change.

• Duplicate target database failed with the newspaper missing in the CCR

  Hi all

  I'm duplicating a database of node 2 CARS to the test environment.

  I took archivelog and pending full database backup in the database. dB Dimensions 950 g.

  I restored it to test the environment but get error during recovery

  operating system: aix 7.1

  version of DB: oracle 10g

  I ran the following command to launch two copies

  RMAN > run

  2 > {}

  3 > allocate auxiliary channel ch1 type disk;

  4 > allocate auxiliary channel ch2 type disk;

  5 > allocate auxiliary channel ch3 type disk;

  6 > allocate auxiliary channel ch4 type disk;

  7 > target database duplicate testing up to THAT TIME "2013-12 - 25:10:47:00';"

  {8 >}

  and get below error

  content of Script memory:

  {

  until ' 2013-12 - 25:10:47:00 ";

  recover

  clone database

  delete archivelog

  ;

  }

  execution of Script memory

  executing command: SET until clause

  From pick up to 2013-12 - 27:18:12:49

  starting media recovery

  Oracle error:

  ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

  ORA-01194: file 1 needs a recovery more match

  ORA-01110: data file 1: '+ DATA/test/datafile/system.390.835293413 '.

  output channel: ch1

  output channel: ch2

  output channel: ch3

  output channel: ch4

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of Db in dual at 27/12/2013 18:14:10

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06053: unable to perform the recovery of the media because of the missing journal

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291696 lowscn 74780879027

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153927 lowscn 74780427224

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291691 lowscn 74763859437

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291690 lowscn 74763843501

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291689 lowscn 74762972560

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153920 lowscn 74761443419

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291688 lowscn 74758111689

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153919 lowscn 74758103358

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291687 lowscn 74758088445

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153918 lowscn 74758078214

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291686 lowscn 74758067675

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153917 lowscn 74758049415

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291685 lowscn 74758046873

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291684 lowscn 74758026214

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153916 lowscn 74757674479

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291683 lowscn 74757658342

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153915 lowscn 74757643881

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291682 lowscn 74757641006

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291681 lowscn 74757621180

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153914 lowscn 74757618464

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291680 lowscn 74757599470

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153913 lowscn 74757584128

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291679 lowscn 74757584121

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291678 lowscn 74757567231

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291677 lowscn 74757550865

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153912 lowscn 74757547289

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291676 lowscn 74757533624

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153911 lowscn 74757513739

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291675 lowscn 74757513659

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291674 lowscn 74757498265

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291673 lowscn 74757483667

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153910 lowscn 74757469005

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291672 lowscn 74757468526

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291671 lowscn 74757453293

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291670 lowscn 74757440237

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153909 lowscn 74757426220

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291669 lowscn 74757422172

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291668 lowscn 74757407202

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153908 lowscn 74757389651

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291667 lowscn 74757386560

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291666 lowscn 74757369955

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153907 lowscn 74757352175

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291665 lowscn 74757351898

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291664 lowscn 74757335274

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291663 lowscn 74757319172

  RMAN-06102: no channel to restore a backup or a copy of the diary of don't thread 1 seq 153906 lowscn 74757314019

  RMAN-06102: no channel to restore a backup or a copy of the journal don't screw 2 seq 291662 lowscn 74756304245

  MAN-06102: no restaurant chain

  RMAN >

  RMAN >

  well let me know what command should I use to do the archivelog backup if it is not present in our existing backup, restore and recover up to what sequence and thread

  Can you restore your backup to tape archivelogs and apply them manually to the restoration of the database?

  list backup of archivelog from the logseq in the error message to check if they are available. And what type of device. You may find that they are available on the device of type TAPE (SBT) but you specified the device DISC type in the command duplicate.

  As long as you have the archivelogs need supported somewhere, you can restore it and apply then having the OPEN RESETLOGS command completed successfully

• RMAN duplicate for standby database failed

  Hello
  I have try several times and for one reason, the auxialiary database finished just as it goes up the auxiliary instance.
  Target database in double check to stanby with the following error. Primary and auxiliary bodies
  Run 11.2.0.2 and are on the same platform of Solaris/patches. Everyone ran in that issue and solve it?
  
  RMAN target / catalog user@catalog
  startup nomount
  Run {}
  allocate auxiliary channel tp1 type sbt_tape;
  allocate auxiliary channel tp2 type sbt_tape;
  target database double standby nofilenamecheck;
  }
  :
  :
  :
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00601: fatal error in the Recovery Manager
  RMAN-03004: fatal error when executing command
  RMAN-04006: auxiliary database error: ORA-01092: ORACLE terminated instance. Disconnection forced
  RMAN-03002: failure of the command duplicate Db at the 15:28:52 01/02/2012
  RMAN-05501: abandonment of duplicate target database
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-03009: failure of switch control on channel clone_default at the 15:28:52 01/02/2012
  ORA-03113: end of file on communication channel

  You have error ORA-7445. I would ask allows you to check the MOS document that said Mseberg.

  Also, do not have the DATA01 on the standby database if your wait is a database not ASM. But you must give the path in the db_file_name_convert and log_file_name_convert on the eve pfile/spfile database

  1 question: is your watch set up database to be on ASM or not?

  See document MOS * no not guide to create physical standby on Normal file system for ASM primary with RMAN [838828.1 ID] * If your principal is on ASM and intelligence on the file system

  See document MOS * Step By Step Guide on creating physical standby with RMAN duplicate in ASM Filesystem for primary ASM [837102.1 ID] * If your primary and the day before are on ASM

  Published by: srp on February 3, 2012 03:49

• Failed to start after the duplicate database dbconsole

  Hello
  
  The last time I tried to replicate a database on oracle database 11 g 2. Data source a sid is vvcoredb and database target a sid is orcl. I duplicated from VVCOREDB to well ORCL. I can access and query the database on ORCL. But I can't access dbconsole. I don't know why. I missed a few things?
  
  P/s: I database starting with the default command is: sql > startup.
  
  Anyone have any suggestions for me?
  
  Thanks in advance!

  See the emca command-line reference
  http://docs.Oracle.com/CD/E11882_01/server.112/e25494/dbcontrol002.htm#ADMIN13410

  EMCA - deconfig dbcontrol db | all - rest drop
  EMCA - config dbcontrol db | rest all - create

  Hemant K Collette

• duplicate database

  Hi all
  
  _ While I was trying to test the database duplicate, I found this error
  
  [oracle@amila ~] $ export ORACLE_SID = dup
  [oracle@amila ~] $ rman target sys/oracle@orcl auxiliary.
  
  Recovery Manager: release 11.2.0.1.0 - Production Thu Jun 2 16:30:55 2011
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
  
  connected to target database: ORCL (DBID = 1279684735)
  connected to the auxiliary database: DUP (unassembled)
  
  RMAN > duplicate target database to the dup
  2 > active database
  3 > spfile;
  
  From duplicate Db 2 June 11
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Db in dual at 02/06/2011 16:33:31
  RMAN-06217: not connected to an auxiliary database with a network service name
  
  RMAN > exit
  
  
  Complete recovery manager.
  [oracle@amila ~] $
  [oracle@amila ~] $ rman target sys/oracle@orcl auxiliary /@dup
  
  11.2.0.1.0 - production on Thu Jun 2 of Recovery Manager: release 16:34:16 2011
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
  
  connected to target database: ORCL (DBID = 1279684735)
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00554: initialization of the package manager internal collection failed
  RMAN-04006: auxiliary database error: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
  [oracle@amila ~] $
  
  _ And I have the following, as well
  
  [oracle@amila ~] $ lsnrctl status
  
  LSNRCTL for Linux: Version 11.2.0.1.0 - Production on June 2, 2011 16:48:25
  
  Copyright (c) 1991, 2009, Oracle. All rights reserved.
  
  Connection to (ADDRESS = (PROTOCOL = tcp)(HOST=) (PORT = 1521))
  STATUS of the LISTENER
  ------------------------
  Alias LISTENER
  Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
  Start date June 2, 2011 07:06:26
  Uptime 0 days 9 h 41 min 59 s
  Draw level off
  Security ON: OS Local Authentication
  SNMP OFF
  Parameter Listener of the /u01/app/grid/product/11.2.0/grid/network/admin/listener.ora file
  The listener log file /U01/app/grid/diag/tnslsnr/AMILA/listener/alert/log.XML
  Summary of endpoints listening...
  (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=amila.swt.lk) (PORT = 1521)))
  Summary of services...
  Service '+ ASM' a 1 instance (s).
  Instance '+ ASM' READY State, has 1 operation for this service...
  Service 'catdb.amila.swt.lk' has 1 instance (s).
  Instance "catdb' READY State, has 1 operation for this service...
  'Dup' service has 1 instance (s).
  Instance "dup", LOCKEDstatus, has 1 operation for this service...
  Service 'orcl.amila.swt.lk' has 1 instance (s).
  Instance "orcl", State LOAN, has 1 operation for this service...
  Service 'orclXDB.amila.swt.lk' has 1 instance (s).
  Instance "orcl", State LOAN, has 1 operation for this service...
  Service 'test.amila.swt.lk' has 1 instance (s).
  Instance of 'test', State LOAN, has 1 operation for this service...
  The command completed successfully
  [oracle@amila ~] $
  [oracle@amila ~] $ tnsping dup
  
  AMT Ping utility for Linux: Version 11.2.0.1.0 - Production on June 2, 2011 17:03:44
  
  Copyright (c) 1997, 2009, Oracle. All rights reserved.
  
  Use settings files:
  
  
  TNSNAMES adapter used to resolve the alias
  Try to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = amila.swt.lk) (PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dup)))
  OK (0 msec)
  
  _ And the tnsnames.ora has these lines as well
  
  tnsnames.ora # Network Configuration file: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
  # Generated by Oracle configuration tools.
  
  DUP =
  (DESCRIPTION =
  (ADDRESS_LIST =
  (ADDRESS = (PROTOCOL = TCP)(HOST = amila.swt.lk) (PORT = 1521))
  )
  (CONNECT_DATA =
  (SERVER = DEDICATED)
  (SERVICE_NAME = dup)
  )
  )
  
  Could someone advise me on this subject please_

  First cannot connect to the only auxiliary database, let us know you are able to connect or not

  sqlplus sys/***@dup as sysdba

  &

  RMAN target sys/***@dup

  post any errors

• Duplicate database RMAN 11 GR 2 ORA-17627 ORA-01017 RMAN-03009 ORA-17628

  Hello
  
  I'm getting ORA-17627: ORA-01017: name of user and password invalid. connection refused when using the RMAN duplicate on the same host using the account Oracle DBA. The system is Linux Oracle and Oracle 11.2.0.1 5.5
  
  I tested the connectivity and passwords and everything works fine. What could be the reason of this problem please?
  
  Details below:
  
  Thank you.
  
  
  H3. Summary of the solution:
  
  A big thank you to all who responded! The problem is solved finally :-)
  
  The ORA-17627: ORA-01017 has been corrected using the connection string to connect to the target database, instead of target rman / in the command prompt
  

  $ rman
  RMAN> connect target sys/password@orcl
  RMAN> connect auxiliary sys/password@clonedb
  RMAN> duplicate target database to clonedb from active database;

  However, there was still another question:
  

  channel ORA_DISK_1: starting datafile copy
  input datafile file number=00001 name=+DATA/orcl/datafile/system.256.737564331
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/29/2010 14:40:21
  ORA-17628: Oracle error 19505 returned by remote Oracle server
  continuing other job steps, job failed will not be re-run

  The alert.log to the auxiliary database (clonedb) shows:
  
  Errors in the /u01/app/oracle/diag/rdbms/clonedb/clonedb/trace/clonedb_ora_6129.trc file:
  ORA-19505: impossible to identify the file ' / scratch/oradata/clonedb/datafile/orcl/datafile/system.256.737564331 '.
  ORA-27040: create file error, cannot create the file
  Linux-x86_64 error: 2: no such file or directory
  
  I fixed the problem by changing the following text in the settings of the clonedb instance file:
  
  * .db_file_name_convert =('+Data/ORCL/','/Scratch/oradata/clonedb/')
  * .log_file_name_convert =('+Data/ORCL/onlinelog/','/Scratch/oradata/clonedb/logfile/')
  
  Thank you!
  
  
  
  
  
  H3. Problem:

  [orcl@ol55]$ rman target /
  
  Recovery Manager: Release 11.2.0.1.0 - Production on Tue Dec 28 21:40:25 2010
  
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  
  connected to target database: ORCL (DBID=1265345286)
  
  RMAN> connect auxiliary sys/test@clonedb
  
  connected to auxiliary database: CLONEDB (not mounted)
  
  RMAN> duplicate target database to clonedb from active database;
  
  Starting Duplicate Db at 28-DEC-10
  using target database control file instead of recovery catalog
  allocated channel: ORA_AUX_DISK_1
  channel ORA_AUX_DISK_1: SID=19 device type=DISK
  
  contents of Memory Script:
  {
     sql clone "create spfile from memory";
  }
  executing Memory Script
  
  sql statement: create spfile from memory
  
  contents of Memory Script:
  {
     shutdown clone immediate;
     startup clone nomount;
  }
  executing Memory Script
  
  Oracle instance shut down
  
  connected to auxiliary database (not started)
  Oracle instance started
  
  Total System Global Area     839282688 bytes
  
  Fixed Size                     2217992 bytes
  Variable Size                645924856 bytes
  Database Buffers             188743680 bytes
  Redo Buffers                   2396160 bytes
  
  contents of Memory Script:
  {
     sql clone "alter system set  db_name = 
   ''ORCL'' comment=
   ''Modified by RMAN duplicate'' scope=spfile";
     sql clone "alter system set  db_unique_name = 
   ''CLONEDB'' comment=
   ''Modified by RMAN duplicate'' scope=spfile";
     shutdown clone immediate;
     startup clone force nomount
     backup as copy current controlfile auxiliary format  '/scratch/oradata/clonedb/controlfile/control01.ctl';
     restore clone controlfile to  '/scratch/oradata/clonedb/controlfile/control02.ctl' from 
   '/scratch/oradata/clonedb/controlfile/control01.ctl';
     alter clone database mount;
  }
  executing Memory Script
  
  sql statement: alter system set  db_name =  ''ORCL'' comment= ''Modified by RMAN duplicate'' scope=spfile
  
  sql statement: alter system set  db_unique_name =  ''CLONEDB'' comment= ''Modified by RMAN duplicate'' scope=spfile
  
  Oracle instance shut down
  
  Oracle instance started
  
  Total System Global Area     839282688 bytes
  
  Fixed Size                     2217992 bytes
  Variable Size                645924856 bytes
  Database Buffers             188743680 bytes
  Redo Buffers                   2396160 bytes
  
  Starting backup at 28-DEC-10
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=35 device type=DISK
  channel ORA_DISK_1: starting datafile copy
  copying current control file
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of Duplicate Db command at 12/28/2010 21:42:08
  RMAN-03015: error occurred in stored script Memory Script
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/28/2010 21:42:08
  ORA-17629: Cannot connect to the remote database server
  ORA-17627: ORA-01017: invalid username/password; logon denied
  ORA-17629: Cannot connect to the remote database server

  H3. Configuration
  
  H4. Listener and Tnsnames
  
  H3. Note: (UR = A) clause in tnsnames.ora is intended to operate with a dynamically
  Manager recorded for the SERVICE_NAME against SID is preferable. (ID 362656.1)
  
  

  $ cat /u01/app/oracle/product/11.2.0/grid/network/admin/listener.ora
  
  LISTENER =
    (DESCRIPTION_LIST =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = ol55.example.com)(PORT = 1521))
      )
    )
  
  SID_LIST_LISTENER =
     (SID_LIST =
         (SID_DESC =
            (ORACLE_HOME= /u01/app/oracle/product/11.2.0/db)
            (SID_NAME = clonedb)
            (GLOBAL_DBNAME= clonedb.example.com)
         )
      )
  
  
  
  
  ADR_BASE_LISTENER = /u01/app/oracle
  
  ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER = ON
  
  
  $ cat tnsnames.ora
  # tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db/network/admin/tnsnames.ora
  # Generated by Oracle configuration tools.
  
  CLONEDB =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ol55.example.com)(PORT = 1521))
      (CONNECT_DATA =
        (SERVER = DEDICATED)
        (SERVICE_NAME = clonedb.example.com)
        (UR = A)
      )
    )
  
  
  $ lsnrctl status
  
  LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 28-DEC-2010 21:35:54
  
  Copyright (c) 1991, 2009, Oracle.  All rights reserved.
  
  Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
  STATUS of the LISTENER
  ------------------------
  Alias                     LISTENER
  Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
  Start Date                26-DEC-2010 02:59:35
  Uptime                    2 days 18 hr. 36 min. 18 sec
  Trace Level               off
  Security                  ON: Local OS Authentication
  SNMP                      OFF
  Listener Parameter File   /u01/app/oracle/product/11.2.0/grid/network/admin/listener.ora
  Listener Log File         /u01/app/oracle/diag/tnslsnr/ol55/listener/alert/log.xml
  Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ol55.example.com)(PORT=1521)))
  Services Summary...
  Service "+ASM" has 1 instance(s).
    Instance "+ASM", status READY, has 1 handler(s) for this service...
  Service "clonedb.example.com" has 2 instance(s).
    Instance "clonedb", status UNKNOWN, has 1 handler(s) for this service...
    Instance "clonedb", status BLOCKED, has 1 handler(s) for this service...
  Service "orcl.example.com" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
  Service "orclXDB.example.com" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
  Service "test.example.com" has 1 instance(s).
    Instance "test", status READY, has 1 handler(s) for this service...
  Service "testXDB.example.com" has 1 instance(s).
    Instance "test", status READY, has 1 handler(s) for this service...
  The command completed successfully

  H4. pFile and spfile
  

  $ cat initclonedb.ora
  clonedb.__db_cache_size=192937984
  clonedb.__java_pool_size=4194304
  clonedb.__large_pool_size=4194304
  clonedb.__oracle_base='/u01/app/oracle'
  clonedb.__pga_aggregate_target=339738624
  clonedb.__sga_target=503316480
  clonedb.__shared_io_pool_size=0
  clonedb.__shared_pool_size=293601280
  clonedb.__streams_pool_size=0
  *.audit_file_dest='/u01/app/oracle/admin/clonedb/adump'
  *.audit_trail='db'
  *.backup_tape_io_slaves=TRUE
  *.compatible='11.2.0.0.0'
  *.control_files='/scratch/oradata/clonedb/controlfile/control01.ctl','/scratch/oradata/clonedb/controlfile/control02.ctl'
  *.db_block_checking='full'
  *.db_block_checksum='full'
  *.db_block_size=8192
  *.db_create_file_dest='/scratch/oradata/clonedb'
  *.db_domain='example.com'
  *.db_name='clonedb'
  *.db_recovery_file_dest='+FRA'
  *.db_recovery_file_dest_size=12884901888
  *.log_archive_dest='/scratch/oradata/clonedb/archivelog'
  *.diagnostic_dest='/u01/app/oracle'
  *.dispatchers='(PROTOCOL=TCP) (SERVICE=clonedbXDB)'
  *.memory_target=843055104
  *.open_cursors=300
  *.processes=150
  *.remote_login_passwordfile='EXCLUSIVE'
  *.undo_tablespace='UNDOTBS1'
  *.db_file_name_convert=('+DATA','/scratch/oradata/clonedb/datafile')
  *.log_file_name_convert=('+DATA','/scratch/oradata/clonedb/logifle')
  
  $ sqlplus / as sysdba
  
  SQL*Plus: Release 11.2.0.1.0 Production on Tue Dec 28 21:26:41 2010
  
  Copyright (c) 1982, 2009, Oracle.  All rights reserved.
  
  Connected to an idle instance.
  
  SQL> startup nomount pfile='$ORACLE_HOME/dbs/initclonedb.ora'
  ORACLE instance started.
  
  Total System Global Area  839282688 bytes
  Fixed Size              2217992 bytes
  Variable Size            641730552 bytes
  Database Buffers       192937984 bytes
  Redo Buffers              2396160 bytes
  SQL> 

  H4. Password file and the connection test
  

  $ orapwd file=$ORACLE_HOME/dbs/orapwclonedb password='test'
  
  $ sqlplus 'sys/test@clonedb as sysdba'
  
  SQL*Plus: Release 11.2.0.1.0 Production on Tue Dec 28 19:58:14 2010
  
  Copyright (c) 1982, 2009, Oracle.  All rights reserved.
  
  Connected to an idle instance.

  Published by: Dude on December 29, 2010 06:37

  Hi guy,
  Please configure the tnsnames and auditor of the target and auxiliary.
  That set the script to use OIC to connect in both instances like this:

  connect target sys/test@orcl
  connect auxiliary sys/test@clonedb

  Please after the release.
  Kind regards
  Tycho

• Test the connection to the database failed: connection to the server could not

  I have one of my servers HPOV NNMi 9.23 restarted this morning and NNMi is loading is no longer.  I see the following errors in the newspapers said:

  /var/opt/OV/log/NNM/public/nmsdbmgr.log

  06/04/2015-09:28:05 connection to the database test failed: connection to the server could not: connection refused
  The server running on host "127.0.0.1" and accept
  TCP/IP connections on port 5432?

  /var/opt/OV/log/NNM/public/postgres.log

  2015-04-06 09:25:55.312 EDT: 8580:0LOG: could not translate the hostname "localhost", "5432" service at the address: name or service not known not

  2015-04-06 09:25:55.312 EDT: 8580:0WARNING: could not create listen to "localhost".

  2015-04-06 09:25:55.312 EDT: 8580:0FATAL: could not create TCP/IP sockets

  I have checked/etc/hosts and found the following entry:

  #; Local
  #;
  127.0.0.1 localhost

  The command line, I can ping localhost without problem.  Not sure why NNMi begins not at this point.

  Turns out be the permissions on the file/etc/hosts.

• Connect to the Oracle database fails when you use Microsoft ODBC or OLE DB Driver

  There was a problem when you apply the KB3126587 hotfix where connections to an Oracle database using the Microsoft ODBC driver fails if run from automated processes. Running the same process manually would succeed. The update issued KB3147071 solved the problem successfully.

  Yesterday, several patched have been applied and the problem came back. The patches are: KB2862152, KB2868626, KB3163244, KB3168965, KB3170455, KB3163251.

  I saw yet no acknowledgement or difficulty of Microsoft. I prefer not to uninstall security patches, but it is a problem of production.

  Any ideas what specific patch maybe breaking it again?

  Thank you

  Josh

  Server: Windows 2008 R2

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• addition of relief in dataguard broker database fails

  When adding of Eve in dataguard broker database, I get the following error

  DGMGRL > add database as uat login is uat maintained as physical;

  Error: ORA-16698: parameter LOG_ARCHIVE_DEST_n defined for the object to add

  Failed.

  DGMGRL > output

  I deleted the log_archive_dest_2 parameter in the primary database and null value

  SQL > sho parameter log_archive_dest_1;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  Log_archive_dest_1 string LOCATION = USE_DB_RECOVERY_FILE_

  DEST = VALID_FOR (ALL_LOGFILES, A).

  LL_ROLES) DB_UNIQUE_NAME = prod

  SQL > sho parameter log_archive_dest_2;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  LOG_ARCHIVE_DEST_2 string

  log_archive_dest_20 string

  Can someone help me please

  vmkumar wrote:

  When adding of Eve in dataguard broker database, I get the following error

  DGMGRL > add database as uat login is uat maintained as physical;

  Error: ORA-16698: parameter LOG_ARCHIVE_DEST_n defined for the object to add

  Failed.

  DGMGRL > output

  I deleted the log_archive_dest_2 parameter in the primary database and null value

  SQL > sho parameter log_archive_dest_1;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  Log_archive_dest_1 string LOCATION = USE_DB_RECOVERY_FILE_

  DEST = VALID_FOR (ALL_LOGFILES, A).

  LL_ROLES) DB_UNIQUE_NAME = prod

  SQL > sho parameter log_archive_dest_2;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  LOG_ARCHIVE_DEST_2 string

  log_archive_dest_20 string

  Can someone help me please

  What you have shown here is the log_archive_dest_2 of the primary database. You must clear the log_archive_dest_2 of the standby database too.

  The error is speaking on the parameter log_archive_dest_2 of the database pending. 12 c, then the broker configuration, you must clear the log_archive_dest_2 (destinations archive remote) on the primary and standby databases. DG broker would take care of her.

  On autonomy in standby:

  SQL > alter system set log_archive_dest_2 = ";

  And then try to add the standby database to the broker configuration.

  HTH

  -Jonathan Rolland

• Recover the database failed after restoration

  Dear people,

  We are trying to restore the RMAN backup on another Linux machine. We did this activity several times. The backup has been taken from a RAC instance and we are trying to restore to RAC. After the success of the restoration of the data files, while we publish "recover the database'; It ends with the following error messages:

  RMAN-00571, RMAN-00569
  RMAN-03002 recover command failed

  RMAN-11003 failure during parsing / execution of the sql statement: alter database recover if necessary until cancel using backup control file

  ORA-19801: DB_RECOVERY_FILE_DEST initialization parameter is not defined

  ORA-00280: change 123123213123213123 thread 1 is in sequence #10787

  Kind regards

  Ali

  ProDBA wrote:

  Dear people,

  We are trying to restore the RMAN backup on another Linux machine. We did this activity several times. The backup has been taken from a RAC instance and we are trying to restore to RAC. After the success of the restoration of the data files, while we publish "recover the database'; It ends with the following error messages:

  RMAN-00571, RMAN-00569
  RMAN-03002 recover command failed

  RMAN-11003 failure during parsing / execution of the sql statement: alter database recover if necessary until cancel using backup control file

  ORA-19801: DB_RECOVERY_FILE_DEST initialization parameter is not defined

  ORA-00280: change 123123213123213123 thread 1 is in sequence #10787

  Kind regards

  Ali

  1. as you have said several times, you performed the restore, then you have not yet checked the parameter above so defined or not?

  2. I hope that its very easy to understand ENGLISH characters

  3 try to correctly set the parameter and size, try again to display the error (since some changes for thread 1 is necessary (hopefully, you gave 123 repeatedly instead of posting of the number of real change in your message))

  -Pavan Kumar N

• RMAN duplicate database

  Hi experts. I duplicate my database to another server. My question is what should I copy file full backup on my server to another or not?

  Hello

  Follow the same pattern

  http://docs.Oracle.com/CD/B19306_01/server.102/b14237/initparams112.htm#REFRN10098

  LOG_FILE_NAME_CONVERT = 'string1' , 'string2' , 'string3' , 'string4' , ...

  Where:

  • string1is the model of the primary database file name
  • string2is the model of the database backup file name
  • string3is the model of the primary database file name
  • string4is the model of the database backup file name

  -Thank you

  Pavan Kumar N