Duplicate RMAN DATABASE

Hello

I am creating a new 11.2.0.1 database by duplicating a 11.2.0.1 existing database with Rman "from database" option.

I created a password file and the listening port is configured this way.
The database to the is started in nomount State.

RMAN
connect target sys/pwd123@SRCDB
connect auxiliary sys/pwd123@AUXDB
AUXDB duplicate target database
ACTIVE DATABASE;

It does not, saying that "ORA-12528: TNS:listener: all appropriate instances are blocking new connections" which is normal given that the listener is havig a handful in the State BLOCKED for this AUXDB is it in NOMOUNT State.

Could you please help me on how to proceed?

An option can be manually create the controlfile and edit the instance before doing the double. I hope that Rman can continue from there.
Another option is to go for the basic duplicate backup.

Is there another way to go?

Kind regards
Aravind

It does not, saying that "ORA-12528: TNS:listener: all appropriate instances are blocking new connections" which is normal given that the listener is havig a handful in the State BLOCKED for this AUXDB is it in NOMOUNT State.

Could you please help me on how to proceed?

An option can be manually create the controlfile and edit the instance before doing the double. I hope that Rman can continue from there.
Another option is to go for the basic duplicate backup.

Is there another way to go?

Provide static record side AUXILIARY for your auxiliary instance, then try again. For example, edit listener.ora as

SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = AUXDB)
      (ORACLE_HOME = )
      (SID_NAME = AUXDB)
    )
  )

LISTENER =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521))
  )

And restart the receiver on the auxiliary host and try again

Tags: Database

Similar Questions

  • ORA-01017 when duplicate RMAN database active

    Hello, ORACLE guru!

    I have some difficulties trying to reproduce DB via RMAN duplicate from active database.

    The script is simple:

     run
 {
 allocate channel ch1 device type disk;
 allocate auxiliary channel aux1 device type disk;
 duplicate target database to mydb from active database;
 }

    The problem is in this summary:

    Starting backup at 15-JAN-14
channel ch1: starting datafile copy
copying current control file
Oracle instance started


Total System Global Area   10689474560 bytes


Fixed Size                     2237776 bytes
Variable Size               4227861168 bytes
Database Buffers            6442450944 bytes
Redo Buffers                  16924672 bytes


contents of Memory Script:
{
   sql clone "alter system set  db_name =
''mydb'' comment=
''Reset to original value by RMAN'' scope=spfile";
   sql clone "alter system reset  db_unique_name scope=spfile";
   shutdown clone immediate;
}
executing Memory Script


sql statement: alter system set  db_name =  ''mydb'' comment= ''Reset to original value by RMAN'' scope=spfile


sql statement: alter system reset  db_unique_name scope=spfile


Oracle instance shut down
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/15/2014 12:16:07
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ch1 channel at 01/15/2014 12:15:57
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


RMAN>
RMAN>

    check and see the differences:

    The database with RMAN duplicate

  • RMAN-05501: abandonment of duplicate target database

    Hello

    I have a little problem with my duplication of the previous day.
    The stupif thing is that I created the day before with this script, first time and after that I decided to recreate it in a different folder
    and since then, I get this error at the end of the process.


    starting media recovery

    Journal archived for thread 1 with sequence 13143 is already on the disc in the file /archives/CMOVP/archivelogs/1_13143_810397891.arc
    Journal archived for thread 1 with sequence 13144 is already on the disc in the file /archives/CMOVP/archivelogs/1_13144_810397891.arc
    Journal archived for thread 1 with sequence 13145 is already on the disc in the file /archives/CMOVP/archivelogs/1_13145_810397891.arc
    Journal archived for thread 1 with sequence 13146 is already on the disc in the file /archives/CMOVP/archivelogs/1_13146_810397891.arc
    Archive log file name=/archives/CMOVP/archivelogs/1_13143_810397891.arc thread = 1 sequence = 13143
    output channel: prm1
    output channel: stby1
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command duplicate Db at 01/05/2013 23:39:32
    RMAN-05501: abandonment of duplicate target database
    RMAN-03015: an error has occurred in the script stored memory Script
    ORA-00283: cool cancelled due to errors
    RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' / archives/CMOVP/archivelogs/1_13143_810397891.arc'
    ORA-00283: cool cancelled due to errors
    ORA-00354: corrupted redo log block header
    ORA-00353: journal corruption near block 2048 change 1524092704 time 01/05/2013 22:18:20
    ORA-00334: archived log: ' / archives/CMOVP/archivelogs/1_13143_810397891.arc'


    I followed all the steps to create the instance of relief, as I said, I've created a first time

    What has changed the second time is that I have insert the following parameters in my init.ora

    db_file_name_convert = "/ oradata/oradata/cmovelprodco/cmovelprodco ', ' / oradata/oradata/cmovelproddr/cmovelproddr.
    LOG_FILE_NAME_CONVERT = "/ oradata/oradata/cmovelprodco/cmovelprodco ', ' / oradata/oradata/cmovelproddr/redolog".


    I run the script to duplicate the db:

    run
    {
    allocate channel prm1 type disk;
    allocate auxiliary channel stby1 type disk;
    DUPLICATE TARGET DATABASE
    FOR STANDBY
    ACTIVE DATABASE
    DORECOVER
    NOFILENAMECHECK;
    }

    But every time I had this type of corruption archivelog
    But when I validate the archives (archivelog Validate all) they are [OK]

    Clues?
    Thxs for your help

    okKarol wrote:
    To the main Site

    SQL > select GROUP #, TYPE, substr (MEMBER, 1, 40) from v$ logfile;

    GROUP # TYPE SUBSTR (MEMBER, 1, 40)
    ---------- ------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    3 /data1/oracle/CMOVP/redo01g3.rdo online
    3 /data2/oracle/CMOVP/redo02g3.rdo online
    2 /data2/oracle/CMOVP/redo02g2.rdo online
    2 /data1/oracle/CMOVP/redo01g2.rdo online
    1 /data1/oracle/CMOVP/redo01g1.rdo online
    1 /data2/oracle/CMOVP/redo02g1.rdo online
    4 /data1/oracle/CMOVP/Stbyredo01g4.rdo EVE
    5 /data2/oracle/CMOVP/Stbyredo01g5.rdo EVE
    6 /data1/oracle/CMOVP/Stbyredo01g6.rdo EVE
    7 /data2/oracle/CMOVP/Stbyredo01g7.rdo EVE

    In secondary Site

    1 * select GROUP #, TYPE, substr (MEMBER, 1, 40) in v$ logfile

    GROUP # TYPE SUBSTR (MEMBER, 1, 40)
    ---------- ------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    /Mcelnetapp/Data1/Oracle/CMOVP/redo01g3.RDO in LINE 3 > I have rename manually
    3 /mcelnetapp/data2/oracle/CMOVP/redo02g3.rdo online > renames manually
    2 /data2/oracle/CMOVP/redo02g2.rdo online
    2 /data1/oracle/CMOVP/redo01g2.rdo online
    1 /mcelnetapp/data1/oracle/CMOVP/redo01g1.rdo online > rename manually
    1 /mcelnetapp/data2/oracle/CMOVP/redo02g1.rdo online > renames manually
    4 /data1/oracle/CMOVP/Stbyredo01g4.rdo EVE
    5 /data2/oracle/CMOVP/Stbyredo01g5.rdo EVE
    6 /data1/oracle/CMOVP/Stbyredo01g6.rdo EVE
    7 /data2/oracle/CMOVP/Stbyredo01g7.rdo EVE

    Then

    SQL> SHUTDOWN IMMEDIATE

    Move files:
    MV /data1/oracle/CMOVP/redo01g2.rdo /mcelnetapp/data1/oracle/CMOVP/redo01g2.rdo
    MV /data2/oracle/CMOVP/redo02g2.rdo /mcelnetapp/data2/oracle/CMOVP/redo02g2.rdo

    SQL> STARTUP MOUNT
SQL> ALTER DATABASE RENAME FILE '/data1/oracle/CMOVP/redo01g2.rdo' to '/mcelnetapp/data1/oracle/CMOVP/redo01g2.rdo';
SQL> ALTER DATABASE RENAME FILE '/data2/oracle/CMOVP/redo02g2.rdo' to '/mcelnetapp/data2/oracle/CMOVP/redo02g2.rdo';
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

    Concerning
    Mr. Mahir Quluzade

  • Duplication duplicate a database with RMAN, different host database different withou

    Hello

    I want to duplicate a database with RMAN, different host, a different database without RMAN Duplicate Technic.

    I HOST1 with a database DB1 and
    HOST2 with a DB2 database

    I have a complete backup of the DB1 in host HOST2. How can I use this backup to clone the database?

    Thank you

    see the links: -.
    http://kamranagayev.WordPress.com/2010/03/29/RMAN-video-tutorial-series-performing-disaster-recovery-with-RMAN/ (Video Tutorial)
    http://oracleinstance.blogspot.com/2010/08/disaster-recovery-using-RMAN-demo.html
    http://gavinsoorma.com/recovery-scenarios/

  • Doubts to duplicate a RMAN database on another test server

    Hello

    DB: 10.2.0.4
    Operating system: Aix 5.3 L

    I have the single server database and I want to duplicate other test server (AIX 5.3) database (10.2.0.4).

    My questions are,

    1) I'll have to take backup RMAN in Production , and then a move to the Test Server?.

    2) in the Test Server , I duplicate RMAN connection and database creation reason as follows.

    RMAN TARGET SYS/xxx@test SYS/xxx@PROD ASSISTANT

    RUN
    {
    allocate channel c1 DEVICE TYPE disk;
    DUPLICATE TARGET DATABASE to test nofilenamecheck. # test is my database to the TEST Server
    }

    The steps above from RMAN will work without RMAN backup in the TEST Server? If not, then how can create the database test without backup RMAN duplicate?



    My main problem is that I have enough disk space in my production server is saved and my database size is 3TO. My database is on ASM.


    I really like, if I have no response.

    Thank you
    Therese

    Yes, database of target duplicate of the active database is available 11 g.

    For 10g, you will need to take backup of primary education and take it all to the test and database duplicated just run.

    Hope that helped u :)

    Mark it as answered and close the question if answered :)

  • Another issue duplicate RMAN - RAC database to single instance

    Hello

    I have a problem with RMAN duplicate procedure and hoped that someone can help you.

    I would like to create a duplicate of our data base RAC production on a separate and autonomous, database on another site server. This duplicate will be used to execute queries to another business unit that I don't want to have access to our database of intensive production.

    My procedure goes like this:

    1. create a (not ASM) disk based backup data files and recovery logs archived:

    'run {} '.
    allocate channel d1 type disk;
    backup format ' / u02/stage/df_t%t_s%s_p%p' database more entered archivelog delete;
    output channel d1;
    }"

    2 tar and scp those files to the same location on the standalone database server.

    3. in the meantime, work that's happened on the basis of data production and other archived redo logs have been generated. I don't really care about these papers for the purposes of the duplicate however, I just want to replicate to the point of the last backup. I have to do this, run the following SQL to determine the sequence number should I be duplicating up to:

    "Select max(sequence#) thread # v $ archived_log, whereas the deleted = 'YES' group by thread #;"

    4 duplicate the production to the stand-alone database database (SQL Net work orders).

    'run {} '.
    until the sequence (the value returned by the SQL statement above);
    duplicate target database xxx;
    }"

    However, my problem because I don't know how to handle the fact that he has two sons. I understand that each thread relates to one of the CARS, I don't know which one to specify the copy. We have a service of data that the client application connects through, and that the service runs on any of the bodies. I should just care about newspapers in the instance where the service is running?

    AM I even approach that this is the right way?

    I look forward to any help that people may be able to offer.

    Kind regards

    Phil

    1 9746 569095777 28 OCTOBER 09 569150229 28 OCTOBER 09
    1 9747 569150229 28 OCTOBER 09 569187892 28 OCTOBER 09
    1 9748 569187892 28 OCTOBER 09 569231956 28 OCTOBER 09
    1 9749 569231956 28 OCTOBER 09 569259816 28 OCTOBER 09
    2 7931 569095774 28 OCTOBER 09 569187902 28 OCTOBER 09
    2 7932 569187902 28 OCTOBER 09 569259814 28 OCTOBER 09

    You must use the VALUE until and specify the sequence with the next lowest change, or RMAN will search for the next log in this thread.

    for example, if you specify until the thread in the sequence 9750 1; RMAN will search journal 7933 on thread2 to catch the 1 wire SNA 569259816.
    Specify the set as a thread in 7933 2 sequence; and two copies must go ok!

    Published by: MrShh on October 29, 2009 14:35

  • Duplicate RMAN


    I am trying to perform RMAN duplicate in 11.2.0.2, but faced with the below error.

    mounted database

    output channel: ORA_AUX_DISK_1

    allocated channel: ORA_AUX_DISK_1

    channel ORA_AUX_DISK_1: SID = 19 type of device = DISK

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

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

    RMAN-03002: failure of Db in dual at 12:57:28 05/12/2015

    RMAN-05501: abandonment of duplicate target database

    RMAN-05541: no newspaper archived in the database to target

    controlfile restores successfully but, restore fails. Please help me on this.

    Is this the first time you save the target database or do there are backups of the journal of the archives previously taken?

    Can you try ' overlap archivelog all ' on the basis of target data, if any expired archivelog all found, delete them and then try to make a level 0 backup.

    Include archivelogs all well in backup of L0, may not be the case, but you can do a test and then perform the duplication.

    run

    {

    format of database backup incremental level 0 ' / u02/bkp/%d_inc0_%T_%U.bak';

    ARCHIVELOG backup all the format ' / u02/bkp/%d_arc_%T_%U.bak';

    }

    -Jonathan Rolland

  • Duplicate RMAN with specific backup location

    Hello

    I explain here my architecture:

    -Server Oracle 11.2.0.4 production: prod db with the instance name PROD with RMAN backups on the F: drive

    -Test the Oracle 11.2.0.4 Server: test-db with the instance name TEST with RMAN backups on the F: drive and production available on the G: drive backup drive

    -Customer name: customer

    My goal is to reproduce the production server to the test server instance and I can't achieve this goal. The connection is client-side.

    I do it like this:

    -startup nomount TEST

    -On the client, run the following "rman target sys/pass@PROD auxiliary sys/pass@TEST.

    Then in RMAN, I run the following:

    RUN

    {

    CHANNEL AUXILIARY ALLOCATE ch01 DEVICE TYPE DISK;

    CHANNEL AUXILIARY ALLOCATE ch02 DEVICE TYPE DISK;

    DUPLICATE THE DATABASE TO THE LOCATION OF THE BACKUP TEST "G:\RMAN";

    }

    RMAN does not see my "LOCATION of BACKUP" command because it tries to reproduce the F: drive and can't find the backup files.

    I have the thing like this:

    CH01 channel: reading of the element of backup F:\RMAN\CTRLFILES\CTRL-PROD-C-2267984545-20150826-00

    CH01 channel: ORA-19870: error when restoring full backup, F:\RMAN\CTRLFILES\CTRL-PROD-C-2267984545-20150826-00

    ORA-19505: impossible to identify the file "F:\RMAN\CTRLFILES\CTRL-PROD-C-2267984545-20150826-00 '

    ORA-27041: could not open the file

    04002 - OSD: could not open the file

    S/O-error: (OS 2) the system cannot find the file specified.

    Single quote, double quote, tried almost everything and RMAN always look for the backup in the F: drive. Can you help me to use the G: drive?

    And at the beginning of this thread someone told me not to connect to the target database.

    You use the clauses unwanted duplicating without connecting to the target database. SPFILE clause is not necessary, but you seem to use it in the block of the RACE.

    Create a simple PFILE with all the parameters required for the auxiliary instance, startup nomount and run the duplicate.

    Also worth db_file_name_convert log_file_name_convert parameters in the PFILE to the auxiliary instance file, run the duplicate.

    run

    {

    CHANNEL AUXILIARY ALLOCATE ch01 DEVICE TYPE DISK;

    CHANNEL AUXILIARY ALLOCATE ch02 DEVICE TYPE DISK;

    DUPLICATE THE DATABASE TO THE LOCATION OF THE BACKUP TEST "G:\RMAN";

    output channel ch01.

    output channel ch02;

    }

    HTH

    Duplication of data without a connection to the target database or catalog of database in Oracle 11 g | Shivananda Rao

    -Jonathan Rolland

  • Try to clone RAC database with RMAN database RAC but becomes lower than ORA-01503

    I'm trying to clone a RAC database of RMAN target database is also CARS, so for every thing wen fine but getting "ORA-01503.

    Please find below, please help me solve this problem.

    connect sys/p0ck3t@pcard1 target;

    auxiliary connection;

    Connect the rmancat/rmanamex@rmandb catalog;

    Run {}

    SQL "alter session set optimizer_mode = RULE ';"

    until ' to_date (' may 1, 2015 06:30 ',' Lun ' DD YYYY HH24:MI:SS);

    allocate auxiliary channel t1 type disk;

    allocate auxiliary channel t2 type disk;

    allocate auxiliary channel t3 type disk;

    the value of newname for datafile 4 to "+ DATA/pcardtst/datafile/users.304.723229675";

    the value of newname for datafile 3 to "+ DATA/pcardtst/datafile/sysaux.395.723228961";

    the value of newname for datafile 2 to "+ DATA/pcardtst/datafile/undotbs1_1.dbf";

    the value of newname for datafile 1 to "+ DATA/pcardtst/datafile/system.328.723229027";

    the value of newname for datafile 5 to "+ DATA/pcardtst/datafile/undotbs2.409.723228957";

    the value of newname for datafile 6 to "+ DATA/pcardtst/datafile/pwrcrd_usr01.dbf";

    the value of newname for datafile 7 to "+ DATA/pcardtst/datafile/pwrcrd_undotbs01.dbf";

    the value of newname for datafile 8 to "+ DATA/pcardtst/datafile/pwrcrd_undotbs02.dbf";

    the value of newname for datafile 9 to "+ DATA/pcardtst/datafile/pwrcrd_data_par01.dbf";

    the value of newname for datafile 10 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_par01.dbf";

    the value of newname for datafile 11 in "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_01.dbf";

    the value of newname for datafile 12 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_02.dbf";

    the value of newname for datafile 13 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_03.dbf";

    the value of newname for datafile 14 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_04.dbf";

    the value of newname for datafile 15 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part01_01.dbf";

    the value of newname for datafile 16 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part01_02.dbf";

    the value of newname for datafile 17 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_01.dbf";

    the value of newname for datafile 18 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_02.dbf";

    the value of newname for datafile 19 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_03.dbf";

    the value of newname for datafile 20 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_04.dbf";

    the value of newname for datafile 21 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part02_01.dbf";

    the value of newname for datafile 22 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part02_02.dbf";

    the value of newname for datafile 23 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_01.dbf";

    the value of newname for datafile 24 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_02.dbf";

    the value of newname for datafile 25 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_03.dbf";

    the value of newname for datafile 26 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part03_01.dbf";

    the value of newname for datafile 27 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part03_02.dbf";

    the value of newname for datafile 28 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_01.dbf";

    the value of newname for datafile 29 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_02.dbf";

    the value of newname for datafile 30 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_03.dbf";

    the value of newname for datafile 31 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part04_01.dbf";

    the value of newname for datafile 32 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part04_02.dbf";

    the value of newname for datafile 33 to '+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_01.dbf;

    the value of newname for datafile 34 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_02.dbf";

    the value of newname for datafile 35 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_03.dbf";

    the value of newname for datafile 36 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part01_01.dbf";

    the value of newname for datafile 37 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part01_02.dbf";

    the value of newname for datafile 38 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_01.dbf";

    the value of newname for datafile 39 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_02.dbf";

    the value of newname for datafile 40 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_03.dbf";

    the value of newname for datafile 41 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part02_01.dbf";

    the value of newname for datafile 42 at "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part02_02.dbf";

    the value of newname for datafile 43 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part03_01.dbf";

    the value of newname for datafile 44 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part03_02.dbf";

    the value of newname for datafile 45 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part03_01.dbf";

    the value of newname for datafile 46 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part03_02.dbf";

    the value of newname for datafile 47 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part04_01.dbf";

    the value of newname for datafile 48 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part04_02.dbf";

    the value of newname for datafile 49 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part04_01.dbf";

    the value of newname for datafile 50 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part04_02.dbf";

    the value of newname for datafile 51 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch01.dbf";

    the value of newname for datafile 52 at "+ DATA/pcardtst/datafile/pwrcrd_data_batch02.dbf";

    the value of newname for datafile 53 to '+ DATA/pcardtst/datafile/pwrcrd_data_batch03.dbf;

    the value of newname for datafile 54 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch04.dbf";

    the value of newname for datafile 55 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch05.dbf";

    the value of newname for datafile 56 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch01.dbf";

    the value of newname for datafile 57 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch02.dbf";

    the value of newname for datafile 58 at "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch03.dbf";

    the value of newname for datafile 59 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part01_01.dbf";

    the value of newname for datafile 60 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part01_01.dbf";

    the value of newname for datafile 61 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part02_01.dbf";

    the value of newname for datafile 62 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part02_01.dbf";

    the value of newname for datafile 63 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part03_01.dbf";

    the value of newname for datafile 64 at "+ DATA/pcardtst/datafile/pwrcrd_data_index_part03_01.dbf";

    the value of newname for datafile 65 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part04_01.dbf";

    the value of newname for datafile 66 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part04_01.dbf";

    the value of newname for datafile 67 to '+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_01.dbf;

    the value of newname for datafile 68 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part05_01.dbf";

    the value of newname for datafile 69 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part06_01.dbf";

    the value of newname for datafile 70 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part06_01.dbf";

    the value of newname for datafile 71 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part07_01.dbf";

    the value of newname for datafile 72 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part07_01.dbf";

    the value of newname for datafile 73 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part08_01.dbf";

    the value of newname for datafile 74 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part08_01.dbf";

    the value of newname for datafile 75 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part09_01.dbf";

    the value of newname for datafile 76 to '+ DATA/pcardtst/datafile/pwrcrd_index_hist_part09_01.dbf;

    the value of newname for datafile 77 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part10_01.dbf";

    the value of newname for datafile 78 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part10_01.dbf";

    the value of newname for datafile 79 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part11_01.dbf";

    the value of newname for datafile 80 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part11_01.dbf";

    the value of newname for datafile 81 to '+ DATA/pcardtst/datafile/pwrcrd_data_hist_part12_01.dbf;

    the value of newname for datafile 82 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part12_01.dbf";

    the value of newname for datafile 83 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part13_01.dbf";

    the value of newname for datafile 84 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part13_01.dbf";

    the value of newname for datafile 85 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part14_01.dbf";

    the value of newname for datafile 86 to '+ DATA/pcardtst/datafile/pwrcrd_index_hist_part14_01.dbf;

    the value of newname for datafile 87 to "+ DATA/pcardtst/datafile/powercard_users.375.723228963";

    the value of newname for datafile 88 to "+ DATA/pcardtst/datafile/powercard_users.396.723228959";

    the value of newname for datafile 89 to "+ DATA/pcardtst/datafile/powercard_users.399.723228959";

    the value of newname for datafile 90 to "+ DATA/pcardtst/datafile/powercard_users.393.723228961";

    the value of newname for datafile 91 to '+ DATA/pcardtst/datafile/mig_pc_delivery.309.723228955;

    the value of newname for datafile 92 to "+ DATA/pcardtst/datafile/powercard_index_par.403.723228961";

    the value of newname for datafile 93 to "+ DATA/pcardtst/datafile/powercard_users.381.723228963";

    the value of newname for datafile 94 to "+ DATA/pcardtst/datafile/powercard_index_hist_part01.275.723229411";

    the value of newname for datafile 95 at "+ DATA/pcardtst/datafile/powercard_data_fe_part01.364.723229607";

    the value of newname for datafile 96 to "+ DATA/pcardtst/datafile/powercard_data_hist_part05.380.723228963";

    the value of newname for datafile 97 to '+ DATA/pcardtst/datafile/powercard_data_hist_part10.310.723228959;

    the value of newname for datafile 98 in "+ DATA/pcardtst/datafile/powercard_data_hist_part14.268.723229465";

    the value of newname for datafile 99 to "+ DATA/pcardtst/datafile/powercard_index_hist_part08.367.723229607";

    the value of newname for datafile 100 to "+ DATA/pcardtst/datafile/powercard_index_hist_part09.385.723229087";

    the value of newname for datafile 101 to "+ DATA/pcardtst/datafile/powercard_index_hist_part11.286.723229559";

    the value of newname for datafile 102 to "+ DATA/pcardtst/datafile/powercard_index_hist_part13.355.723229615";

    the value of newname for datafile 103 to "+ DATA/pcardtst/datafile/powercard_data_batch.330.723228961";

    the value of newname for datafile 104 to "+ DATA/pcardtst/datafile/powercard_data_hist_part13.335.723229485";

    the value of newname for datafile 105 to "+ DATA/pcardtst/datafile/powercard_index_bo_part03.285.723229567";

    the value of newname for datafile 106 to "+ DATA/pcardtst/datafile/powercard_index_bo_part01.351.723229617";

    the value of newname for datafile 107 to "+ DATA/pcardtst/datafile/powercard_index_fe_part04.261.723229627";

    the value of newname for datafile 108 to "+ DATA/pcardtst/datafile/powercard_index_hist_part02.264.723229465";

    the value of newname for datafile 109 to "+ DATA/pcardtst/datafile/powercard_data_bo_part01.284.723229573";

    the value of newname for datafile 110 to "+ DATA/pcardtst/datafile/powercard_data_hist_part01.406.723229497";

    the value of newname for datafile 111 to "+ DATA/pcardtst/datafile/powercard_data_hist_part07.291.723229557";

    the value of newname for datafile 112 to "+ DATA/pcardtst/datafile/powercard_data_hist_part08.371.723229615";

    the value of newname for datafile 113 to "+ DATA/pcardtst/datafile/powercard_data_hist_part09.346.723228973";

    the value of newname for datafile 114 to "+ DATA/pcardtst/datafile/powercard_data_hist_part12.401.723229447";

    the value of newname for datafile 115 to "+ DATA/pcardtst/datafile/powercard_index_fe_part02.262.723229625";

    the value of newname for datafile 116 to "+ DATA/pcardtst/datafile/powercard_data_fe_part04.374.723229627";

    the value of newname for datafile 117 to "+ DATA/pcardtst/datafile/powercard_data_bo_part03.276.723229585";

    the value of newname for datafile 118 to "+ DATA/pcardtst/datafile/powercard_data_bo_part04.350.723229633";

    the value of newname for datafile 119 to "+ DATA/pcardtst/datafile/powercard_index_bo_part04.317.723229633";

    the value of newname for datafile 120 to "+ DATA/pcardtst/datafile/powercard_data_hist_part03.400.723229511";

    the value of newname for datafile 121 in '+ DATA/pcardtst/datafile/powercard_index_hist_part12.369.723229605;

    the value of newname for datafile 122 to "+ DATA/pcardtst/datafile/powercard_index_hist_part05.373.723229641";

    the value of newname for datafile 123 to "+ DATA/pcardtst/datafile/powercard_data_par.319.723229635";

    the value of newname for datafile 124 to "+ DATA/pcardtst/datafile/powercard_users.402.723228957";

    the value of newname for datafile 125 to "+ DATA/pcardtst/datafile/powercard_index_batch.356.723229609";

    the value of newname for datafile 126 to "+ DATA/pcardtst/datafile/powercard_index_bo_part02.256.723229647";

    the value of newname for datafile 127 to "+ DATA/pcardtst/datafile/powercard_index_hist_part07.320.723229641";

    the value of newname for datafile 128 to "+ DATA/pcardtst/datafile/powercard_index_hist_part04.258.723229615";

    the value of newname for datafile 129 to "+ DATA/pcardtst/datafile/powercard_data_bo_part02.366.723229651";

    the value of newname for datafile 130 to "+ DATA/pcardtst/datafile/powercard_data_hist_part06.348.723228965";

    the value of newname for datafile 131 to "+ DATA/pcardtst/datafile/powercard_data_hist_part02.307.723229525";

    the value of newname for datafile 132 to "+ DATA/pcardtst/datafile/powercard_index_fe_part01.370.723229647";

    the value of newname for datafile 133 to "+ DATA/pcardtst/datafile/powercard_index_fe_part03.352.723229619";

    the value of newname for datafile 134 to "+ DATA/pcardtst/datafile/powercard_index_hist_part06.266.723229659";

    the value of newname for datafile 135 to "+ DATA/pcardtst/datafile/powercard_index_hist_part10.329.723229027";

    the value of newname for datafile 136 to "+ DATA/pcardtst/datafile/powercard_index_hist_part03.337.723229651";

    the value of newname for datafile 137 to "+ DATA/pcardtst/datafile/powercard_index_hist_part14.263.723229627";

    the value of newname for datafile 138 to "+ DATA/pcardtst/datafile/stpmw_data01.dbf";

    the value of newname for datafile 139 to "+ DATA/pcardtst/datafile/undotbs1_2.dbf";

    the value of newname for datafile 140 to "+ DATA/pcardtst/datafile/undotbs1_3.dbf";

    the value of newname for datafile 141 to "+ DATA/pcardtst/datafile/undotbs1_4.dbf";

    the value of newname for datafile 142 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_03.dbf";

    the value of newname for datafile 143 to "+ DATA/pcardtst/datafile/powercard_data_hist_part05.426.851242407";

    the value of newname for datafile 144 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part11_02.dbf";

    the value of newname for datafile 145 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part12_02.dbf";

    the value of newname for datafile 146 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_04.dbf";

    the value of newname for datafile 147 in "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part05_02.dbf";

    the value of newname for tempfile 1 to "+ DATA/pcardtst/tempfile/temp1.dbf";

    the value of newname for tempfile 2 to "+ DATA/pcardtst/tempfile/temp2.dbf";

    the value of newname for tempfile 3 to "+ DATA/pcardtst/tempfile/temp3.dbf";

    the value of newname for tempfile 4 to "+ DATA/pcardtst/tempfile/pwrcard_temp01.dbf";

    the value of newname for tempfile 5 to "+ DATA/pcardtst/tempfile/pwrcard_temp02.dbf";

    the value of newname for tempfile 6 to "+ DATA/pcardtst/tempfile/pwrcard_temp03.dbf";

    the value of newname for tempfile 7 to "+ DATA/pcardtst/tempfile/pwrcard_temp04.dbf";

    duplicate target database in the pcardtst log file

    GROUP 10 ('+ DATA/pcardtst/onlinelog/group_10_01') size 512 M,

    GROUP 10 ('+ DATA/pcardtst/onlinelog/group_10_02') size 512 M,

    GROUP 11 ('+ DATA/pcardtst/onlinelog/group_11_01') size 512 M,

    GROUP 11 ('+ DATA/pcardtst/onlinelog/group_11_02') size 512 M,

    GROUP 12 ('+ DATA/pcardtst/onlinelog/group_12_01') size 512 M,

    GROUP 12 ('+ DATA/pcardtst/onlinelog/group_12_02') size 512 M,

    GROUP 13 ('+ DATA/pcardtst/onlinelog/group_13_01') size 512 M,

    GROUP 13 ('+ DATA/pcardtst/onlinelog/group_13_02') size 512 M,

    GROUP 14 ('+ DATA/pcardtst/onlinelog/group_14_01') size 512 M,

    GROUP 14 ('+ DATA/pcardtst/onlinelog/group_14_02') size 512 M,

    GROUP 7 ('+ DATA/pcardtst/onlinelog/group_7_01') size 512 M,

    GROUP 7 ('+ DATA/pcardtst/onlinelog/group_7_02') size 512 M,

    GROUP 8 ('+ DATA/pcardtst/onlinelog/group_8_01') size 512 M,

    GROUP 8 ('+ DATA/pcardtst/onlinelog/group_8_02') size 512 M,

    GROUP 9 ('+ DATA/pcardtst/onlinelog/group_9_01') size 512 M,

    GROUP 9 ('+ DATA/pcardtst/onlinelog/group_9_02') size 512 M;

    output channel t1;

    output channel t2;

    output channel t3;

    }

    But gettting error below

    DATA FILE

    "+ DATA/pcardtst/datafile/system.635.878984933".

    CHARACTER SET WE8ISO8859P1

    output channel: t1

    output channel: t2

    output channel: t3

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

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

    RMAN-03002: failure of Db in dual at 06/05/2015 14:26:01

    RMAN-06136: the auxiliary database ORACLE error: ORA-01503: CREATE CONTROLFILE failed

    ORA-01167: two files are the same file/group number or the same file

    ORA-01517: Member of journal: '+ DATA/pcardtst/onlinelog/group_10_02.

    ORA-01517: Member of journal: '+ DATA/pcardtst/onlinelog/group_10_01.

    Complete recovery manager.

    Kind regards.

    Younus

    Hi Eric,.

    Let's not your syntax for log files. Check out the docs:

    http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm#BRADV89956

    You need only name the Group once followed a list separated by commas of the logfile members.

    Concerning

    Thomas

  • duplicate/clone database recovery failed, but backup total available (ORA-19505, ORA-17503)

    Hello

    I'm 11 GR 2. I ran a duplicate of RMAN database ABCD01P with the simple script:

    DUPLICATE THE TARGET DATABASE TO "TESTBKP' OF THE ACTIVE DATABASE.

    It ran fine for about 3 hours and ended in failure, after all my 175 data files

    have been copied to the destination host, when you start to recover. The log shows:

    ...

    content of Script memory:

    {

    until the SNA 607608188039.

    retrieve the archivelog deletion of database clone;

    }

    ...

    destination for the restoration of the data file 00009: +DATAF/testbkp/datafile/ab11_lob.435.847475901

    aux1 channel: reading of the element of backup +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021

    aux2 channel: from additional data file from the restore backup set

    aux2 channel: specifying datafile (s) to restore from backup set

    ...

    and then failed with:

    ORA-19870: error while restoring the backup +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021 piece

    ORA-19505: impossible to identify the file "+ FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021".

    ORA-17503: ksfdopn:2 could not open the file +FRA/abcd01p/backupset/2014_05_13/nnndn1_abcd01p_daily_0.669.847476021

    I do not understand because this file it says it could not identify or open exists and is present in my FRA...

    (this backup from an incremental backup, updated full and the first one I did on the source DB one hour before

    -INCREMENTAL LEVEL BACKUP 1 TO RETRIEVE THE COPY WITH THE TAG... DATABASE PLUS ARCHIVELOG...-)

    Any idea?

    Thank you very much...

    SEB

    Hi Seb,

    I've seen similar error reported when there is simultaneous backup running operation.

    Make sure to run twice at a time when there is no alternative transaction.

    Thank you

    Renu

  • Duplicate target database - until the time?

    Dear Experts,

    RDBMS - 10.2.0.4

    I am trying to update the backup "ORCL2" using a cold of 'ORCL1', the two databases are on different servers. under the safeguard of stamp ORCL1 time is over:
    Finished Control File and SPFILE Autobackup at 12/27/2012 09:28:58
    I was wondering if the clone will run without any problems with command below, please share your ideas...
    run{
---channel allocation commands---
duplicate target database to ORCL2
 until time "to_date('12/27/2012 09:28:58','mm/dd/yyyy hh24:mi:ss')";
---channel release commands---
}
    Published by: DBA112 on December 28, 2012 14:10

    Hello;

    In theory, it should work.

    "DUPLICATE recovers by default until the last archived redo log generated at the time the command was executed, or until one hour set with a SET clause up to THAT."

    Source - database backup and recovery reference 10g Release 2 (10.2) part number B14194-03

    Example of doc

    DUPLICATE TARGET DATABASE TO newdb
    DB_FILE_NAME_CONVERT=('/h1/oracle/dbs/trgt/','/h2/oracle/oradata/newdb/')
    UNTIL TIME 'SYSDATE-1'  # specifies incomplete recovery
...

    Another example

    http://blog.dbauniversity.com/2012/06/RMAN-duplicate-until-time.html

    Best regards

    mseberg

  • Help to order duplicate RMAN

    Hi all

    I need to restore an oracle rac in another server with another dbname.

    I found notes 452868.1 (on the link https://support.oracle.com/CSP/main/article?cmd=show & type = NOT & id = 452868.1 #aref_section31)

    On my system there is the network user and listener is managed by the grid.
    After nomount an istance of simple as test note starting, I can see test service in the status of the listener. but I read blocked service:

    Service 'TEST' has 1 instance (s).
    Instance of 'TEST', LOCKED status, has 1 operation for this service...

    When I try to reproduce the rman test server db:

    RMAN >
    connect the target (the source database)
    connected to target database: DBCORP (DBID = 2331160416)
    auxiliary connection.
    connected to the auxiliary database: TEST (not mounted)
    Connect catalog rmancat/rmanpwd@rmancat
    connected to the recovery catalog database

    RMAN > DATABASE of TARGET 'TEST' FOR ACTIVE DATABASE duplicate;


    From 14 December 12 Db double
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Db in dual at 14/12/2012 12:31:27
    RMAN-05501: abandonment of duplicate target database
    RMAN-06217: not connected to an auxiliary database with a network service name


    Where is my mistake?

    as indicated error, you have to active replication link both sides by using a network service name, so ' target / "or" auxiliary / "will not work in this scenario
    the correct method is written in the note

    dynamic registration in NOMOUNT form will result in a BLOCKED service
    This is why you must modify your listener.ora and use the static record

  • Standy of database backup and restore help to duplicate a database

    OK, here's my situation. I save my 11.1.0.6 database from the backup server (primary backup not suitable, who ruled out a double asset) using a recovery catalog. My goal is to restore this database under another name called (TEST) on another server using the duplicate database command. My questions are:

    (1) I know that I can save my sleep using RMAN database, but what should I back up the control file and the spfile of the primary database as well?

    (2) I use a recovery catalog (who I am already registered in the primary database only with), I have to save the elements of backup of the backup above with the recovery catalog (or are they already registered since I have connected to the catalog when you take the backup of the standby database?)

    (3) if I need backup upward the primary controlfile, can I manually copy the file to the new server or should I create by issuing a 'backup controlfile to trace' command on the primary database server and re-create it.

    I guess my points of friction would be how to publish the duplicate database command, once I have all the parts. If I'm missing something please let me know. This is a database of 1.5 TB and I only have one (1) time to get this right. Lucky me... Thank you all

    (1) I know that I can save my sleep using RMAN database, but what should I back up the control file and the spfile of the primary database as well?

    * ==> spfile must be static most of the time, so that you can make a copy whenever you make changes and save it to your backup location. In regards to your controlfiles, you can back up the database your intelligence and your backups.* database

    (2) I use a recovery catalog (who I am already registered in the primary database only with), I have to save the elements of backup of the backup above with the recovery catalog (or are they already registered since I have connected to the catalog when you take the backup of the standby database?)

    * ==> Oracle documents Oracle® Data Guard Concepts and Administration 11 g Release 2 (11.2) part number E17022-05 not shows you how this.*

    (3) if I need backup upward the primary controlfile, can I manually copy the file to the new server or should I create by issuing a 'backup controlfile to trace' command on the primary database server and re-create it.
    * ==>, You must also back up your controlfiles of RMAN. Read the Oracle Documentation above

    I guess that my points of friction would be how to publish the duplicate database command, once I have all the parts...

    * ==> There is another Oracle documentation on duplication. Oracle® backup and Guide 11 g Release 2 (11.2) part number E10642-04. * user recovery

  • SQL in pl/sql and create the duplicate RMAN script.

    Hello

    I'm new to pl/sql and I am trying to write a script that will generate RMAN commands to make a clone of database.

    I want to be able to run the script, and he invited me to the variables to be used in the script.

    I did some research but I have been unable to find examples of how to proceed.

    Basic script is (it would be obviously a lot more to the final script):

    declare

    dbname varchar2 (9): = & dbname;

    BEGIN
    DBMS_OUTPUT. ENABLE (2000);
    DBMS_OUTPUT. Put_line (' DUPLICATE TARGET DATABASE to ' | dbname |) ';') ;
    end;
    /

    Makes me:

    Enter the value of dbname: ORCL4
    old 3: dbname varchar2 (9): = & dbname;
    new 3: dbname varchar2 (9): = ORCL4;
    dbname varchar2 (9): = ORCL4;
    *
    ERROR at line 3:
    ORA-06550: line 3, column 24:
    PLS-00201: identifier 'ORCL4' must be declared.
    ORA-06550: line 3, column 9:
    PL/SQL: Ignored Element
    ORA-06550: line 7, column 66:
    PLS-00320: the declaration of the type of the expression is incomplete or incorrect
    ORA-06550: line 7, column 9:
    PL/SQL: Statement ignored

    Thank you
    Tom.

    Hi, Tom.

    When SQL * more variable substitution resolves, it puts the string you gave as value (ORCL4 for example) instead of the string representing the name (& dbname, for example). East exaclty what you could do using the Replace function in a text editor: nothing more.
    After SQL * more substituted for these channels, it send s the text changed the database to be compiled. So, where you coded:

    dbname varchar2(9) := &dbname;

    is that it sends to compile

    dbname varchar2(9) := ORCL4;

    in other words, it looks like a variable on the side right of the: = sign.

    You must provide quotes:

    dbname varchar2(9) := '&dbname';

  • Can I save a RMAN database using 2 devices (tape drives 2) at the same time by setting OB_DEVICE?

    Hi all

    Can we backup RMAN database using 2 drives at the same time by setting OB_DEVICE?

    In case of increase the performance of backup on 2 tape drives?

    I know that the possibility to use OB_DEVICE_1 and OB_DEVICE_2 to specify the number of copy of backups in duplex.

    But what I want is to run backup on disk 2 of databases for a single copy!

    Your response is much more appreciate.

    Thank you and best regards,

    Kathya

    Hello

    Just spend two-channel SBT is implicitly:

    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;

    or explicitly block execution:

    RUN
{
  ALLOCATE CHANNEL c1 DEVICE TYPE sbt;
  ALLOCATE CHANNEL c2 DEVICE TYPE sbt;
  BACKUP DATABASE PLUS ARCHIVELOG;
}

    Kind regards

    Mitja

Maybe you are looking for

  • I have a problem with the letter p

    Cuando presiono p be p escribe y followed sola escribe muchas barras diagonal invertida

  • HP Envy 750-114: hp envy 750-114-added to a graphics card

    I am to buy HP Envy 750-114 and upgrade with a graphics card.  The one I found is low power, so it will be fine with the 300 watt power supply that comes with 750-114 envy. The problem is I want to order the video card for a refund until the PC (the

  • Windows XP - key invalid

    Original title: help me please. Hi can sum one help out me? I am currently copy Windows XP Professional SP2 to one of the computers in mi, and I can't use the key I. It will not, except the key that I use. It is my laptop that has the same version of

  • Storage of liquid E2

    Hello I have a problem of sound on the storage, when I tried to install an APP, it will not directly install in my SD card. can someone help me, please. im a beginner with andriod preferred installation location = there only internal, phone, let the

  • 1242 AP WGB can be associated with mesh LAP 1522 5 GHz?

    Hello It is possible to associate AP 1242 configured as WGB to mesh LAP 1522 in the 5 GHz band? Thank you.