FLASHBACK Database: rman vs. sql command differences

I am new to Oracle and want to understand the difference and that is the correct way of rear turn signals to the database?


RMAN command vs SQL command on the use of FLASHBACK DATABASE
 SQL> FLASHBACK DATABASE TO RESTORE POINT BEFORE_ONLINE_TEST;  {CODE} Vs 
RMAN > run {}
flashback database to restore the BEFORE_TEST_320130313 point;
SQL ' alter database open resetlogs; }
 
Referring this article on http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmflash.htm#BGBDCAFA it says we can use both RMAN and SQL command for database flashback.

Questions:

1. Difference between using RMAN and SQL command on database flashback?

2. When to use RMAN or SQL on the  database flashback?

3. Which is the Oracle recommended or best way ?

Edited by: Sivaprasad S on Mar 15, 2013 7:26 PM

Edited by: Sivaprasad S on Mar 15, 2013 7:26 PM

Edited by: Sivaprasad S on Mar 15, 2013 7:27 PM

Edited by: Sivaprasad S on Mar 15, 2013 7:27 PM

Edited by: Sivaprasad S on Mar 15, 2013 7:28 PM

Edited by: Sivaprasad S on Mar 15, 2013 7:29 PM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            

So when you run your SQLPlus flashback, you get the following error:

ORA-38761: redo log sequence 1 in thread 1, incarnation 3 could not be found

This means so that the sequence 1 has probably been removed from the disk and is necessary.

When you run the RMAN command look at the log what RMAN:

* journal archived for thread 1 sequence 2 is already on the disc in the file +DG_PERF_FLASH_02/TestDB/archivelog/2013_03_14/thread_1_seq_2.3612.810054205*
* journal archived for thread 1 with sequence 3 is already on the disc in the file +DG_PERF_FLASH_02/TestDB/archivelog/2013_03_14/thread_1_seq_3.1588.810054205*

So sequence 2 and 3 are already on record according to the above message.

Then you get this message:

channel dev_2: restoration of archives Journal
Archives journal thread = 1 sequence = 1

So RMAN knows he needs 1 thus sequence and restores this newspaper archive she needs for recovery.

In a Word while running SQLPlus she communicate with RMAN and restore the log file for you, however with RMAN, it won't.

You can restore the newspaper archive manually, and then run in SQLPlus that will then work.

Published by: Freddie Essex on March 18, 2013 12:46

Tags: Database

Similar Questions

  • creation of database using the SQL command * more

    Hello

    This isn't a matter of urgency.

    I learn the Oracle DBA. I have installed Oracle 9.2 in my windows system. And I'm trying to create a database using the SQL command.

    OracleVersion: 9.2
    Windows XP operating system

    CREATE DATABASE suri
    USER SYS identified by manager
    USER system identified by surendra
    LOGFILE GROUP 1 ('F:\Oracle\oradata\suri\redo01.log') SIZE 100M,
            GROUP 2 ('F:\Oracle\oradata\suri\redo02.log') SIZE 100M,
            GROUP 3 ('F:\Oracle\oradata\suri\redo03.log') SIZE 100M
       MAXLOGFILES 5
       MAXLOGMEMBERS 5
       MAXLOGHISTORY 1
       MAXDATAFILES 100
       MAXINSTANCES 1
       CHARACTER SET US7ASCII
       NATIONAL CHARACTER SET AL16UTF16
    DATAFILE 'F:\Oracle\oradata\suri\system01.dbf' size 200M EXTENT MANAGEMENT LOCAL
    UNDO tablespace undots datafile 'F:\Oracle\oradata\suri\undots01.dbf' size 200M
    DEFAULT TEMPORARY TABLESPACE tempts1 DATAFILE 'F:\Oracle\oradata\suri\temp01.dbf' SIZE 100M EXTENT MANAGEMENT LOCAL
    I get the error like below when executing the CREATE DATABASE command.

    ERROR at line 16:
    ORA-25139: invalid option for CREATE TEMPORARY TABLESPACE
    I have validated the syntax but not able to find where is the error.

    Please let me know if you need more details.

    Thanks in advance for your help.


    Kind regards
    Suri

    OracleVersion: 9.2

    Why a so old version (and desupported)? In any case...

    TEMPORARY TABLESPACE tempts1 DATAFILE 'F:\Oracle\oradata\suri\temp01.dbf' SIZE 100 M EXTENT MANAGEMENT LOCAL default

    .. try change DATAFILE with TEMPFILE.

  • Database of flashback through RMAN (10 g)

    Hi all;

    How can get a rear base using database of flashback (rman) in 10 g.

    SQL > select current_scn, to_char (SYSTIMESTAMP, "YYYY-MM-DD HH24:MI:SS) database v$.

    TO_CHAR (SYSTIMESTAM CURRENT_SCN

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

    1153432 2014-05-25 00:07:35

    SQL > select * from tab;

    TNOM TABTYPE CLUSTERID

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

    TAB6 TABLE

    TABLE TAB1

    TABLE TAB2

    SQL > delete from tab2.

    2048 deleted rows.

    SQL > truncate table tab1;

    Table truncated.

    SQL > drop table tab6.

    Deleted table.

    SQL > commit;

    Validation complete.

    SQL > conn / as sysdba

    Connected.

    SQL > drop user cascade of sam;

    Deleted user.

    SQL > shutdown immediate;

    The database is closed.

    The database is dismounted.

    ORACLE instance stops.

    SQL > bootable media.

    ORACLE instance started.

    Total System Global Area 465567744 bytes

    Bytes of size 1274308 fixed

    96472636 variable size bytes

    364904448 of database buffers bytes

    Redo buffers 2916352 bytes

    Mounted database.

    SQL > exit

    Disconnected from the database to Oracle 10 g Enterprise Edition Release 10.2.0.5.0 - Production

    With partitioning, OLAP, Data Mining and Real Application Testing options

    [oracle@oel5 ~] target rman $ /.

    Recovery Manager: Release 10.2.0.5.0 - Production on Sun may 25 00:10:21 2014

    Copyright (c) 1982, 2007, Oracle.  All rights reserved.

    connected to target database: ORCL (DBID = 1373939619, is not open)


    RMAN > FLASHBACK DATABASE TO TIME timestamp ('2014-05-25 00:07:35 ');

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

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

    RMAN-00558: error occurred during parsing of order entry

    RMAN-01009: syntax error: found 'identifier': expected an a: 'double-quoted-string, equal, single-quoted-string '.

    RMAN-01008: the bad ID was: timestamp

    RMAN-01007: in the file column 28 line 1: entry standard

    Recovery Manager: Release 10.2.0.5.0 - Production on Sun may 25 00:10:21 2014

    Copyright (c) 1982, 2007, Oracle.  All rights reserved.

    connected to target database: ORCL (DBID = 1373939619, is not open)

    FLASHBACK DATABASE IN TIME ' TO_DATE ('2014-05-25 00:07:35 ',' YYYY-MM-DD HH24:MI:SS') ";

  • RMAN and sql

    Hi all

    While using the tool rman that sometimes we will make a few commands like

    RMAN > sql 'alter system switch logfile;

    and some commands like

    RMAN > change the editing of the database;

    is there a difference between these two executions.

    Please let me know.

    Thank you very much.

    While using the tool rman that sometimes we will make a few commands like
    RMAN > sql 'alter system switch logfile;
    and some commands like
    RMAN > change the editing of the database;

    is there a difference between these two executions.

    a few commands that you cannot run RMAN directly, so it has to use SQL to run these commands.

    Because EXECUTE is a SQL * more control, you cannot run a PL/SQL command by specifying EXECUTE within the RMAN SQL command. Instead, you must use the keywords BEGIN and END. For example, to run a procedure from PL/SQL named rman.rman_purge through the RMAN SQL command

    Source:-http://download.oracle.com/docs/cd/B10501_01/server.920/a96565/rcmsynta54.htm

  • Flashback database syntax question

    EE Oracle 10.2.0.4 on OEL 5

    This should be a matter of syntax simple, right?

    Practice some scenarios to return back and looking at the syntax to
    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14194/rcmsynta032.htm#sthref515

    In the examples, they show a
    RMAN> FLASHBACK DATABASE TO TIMESTAMP
       TO_TIMESTAMP('2002-03-11 16:00:00', 'YYYY-MM-DD HH24:MI:SS');
    but the real syntax diagram does not show an option "TIMESTAMP", just "on TIME" and "AHEAD of TIME".

    Based on, let's try a simple test
    RMAN> flashback database to time = '18-MAY-2010 12:50:00';
    
    Starting flashback at 18-MAY-2010 13:10:00
    using channel ORA_DISK_1
    
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of flashback command at 05/18/2010 13:10:00
    ORA-01830: date format picture ends before converting entire input string
    Hmm, okay, then what format does? In fact, he reported in two different formats:
    Starting flashback at 18-MAY-2010 13:10:00
    and
    RMAN-03002: failure of flashback command at 05/18/2010 13:10:00
    If pressing on some others, let's try that should be obvious:
    RMAN> flashback database to time = to_date('05/18/2010 12:50:00','mm/dd/yyyy hh24:mi:ss')
    
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "double-quoted-string, single-quoted-string"
    RMAN-01008: the bad identifier was: to_date
    RMAN-01007: at line 1 column 30 file: standard input
    
    
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "(": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
    RMAN-01007: at line 1 column 37 file: standard input
    
    RMAN>
    Built on the docs and other resources on the web, I find several variations on the theme, but all end up throwing one of the errors above.

    I can't believe, I've been reduced to what should be a matter of doc, but in this case, it's the documentation examples which throw errors. I'm going blind? The brain cell was killed by that I had last week of beer criticism? ;-)

    From:

    RMAN> flashback database to time = to_date('05/18/2010 12:50:00','mm/dd/yyyy hh24:mi:ss')
    
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "double-quoted-string, single-quoted-string"
    RMAN-01008: the bad identifier was: to_date
    RMAN-01007: at line 1 column 30 file: standard input
    

    Could you please try adding double quotes around the expression date?

     flashback database to time = "to_date('05/18/2010 12:50:00','mm/dd/yyyy hh24:mi:ss')";
    
  • Can feature FLASHBACK DATABASE undo the loss of control of file/ORL?

    DB version: 11.2.0.4

    Platform: Oracle Linux 6.4

    I personally have not tested the FLASHBACK DATABASE feature. I came across examples of logical errors such as truncate Table being overturned on FLASHBACK DATABASE.

    I guess that FLASHBACK DATABASE feature may undo the loss of the data files. But will be a loss of control or the Group of newspapers online file again defeated using FLASHBACK DATABASE?

    Hello

    "I guess that feature FLASHBACK DATABASE can cancel the data files loss." Do not assume, check it out

    Flashback database cannot cancel the loss of data files, control files and redo log files.

    Flashback Database limitations

    Because Flashback Database works by undoing changes to data files that exist at the present time when you run the command, it has the following limitations:

    • Flashback Database can only undo changes in an Oracle database data file. It cannot be used to fix the failings of the media, or recover the accidental deletion of data files.
    • You cannot use Flashback Database to cancel a file of data reduction operation. However, you can disconnect the wizened file, flash back, the rest of the database, and then later restore and restore the shriveled data file.
    • You cannot use Flashback Database only to retrieve a data file. If you Flash back, a database at a time when a data file exist in the database, that the entry of data file is added to the control file. You can only recover the database using RMAN to fully restore and recover the data file.
    • If the database control file is restored from backup or re-created, all the accumulated flashback journal information is ignored. You cannot use FLASHBACK DATABASE to get back to a point in time before the restoration or re-creation of a control file.
    • When you use Flashback Database with a time of target during a NOLOGGING operation was underway, corruption block is likely in database objects and files of data that is affected by the NOLOGGING operation. For example, if you perform a direct path INSERT operation in NOLOGGING mode and it runs from 09:00 to 09:15 April 3, 2005, and then use you Flashback Database to return to the target time 09:07 on this date, the objects and data files updated by the direct path INSERT have finished block operation Flashback Database corruption. If possible, avoid using Flashback Database with a time or SCN coinciding with a NOLOGGING operation. Also, perform a full or incremental backup of the immediately affected data files backup after each NOLOGGING operation to ensure recovery of points in time after the operation. If you plan to use Flashback Database to return to a point in time in the course of an operation, for example a direct path INSERT , consider performing the operation in LOGGING mode.

    See: https://docs.oracle.com/cd/E11882_01/backup.112/e10642/flashdb.htm#BRADV286

  • ORA-38760: this database instance could not turn on the flashback database

    Hi guys

    Without knowing it, I deleted all the files in the directory "fra" where "flashback" folder was there because of space issues. Now am facing the error.

    It's my practical database.

    SQL > startup

    ORACLE instance started.

    Total System Global Area 608174080 bytes

    Bytes of size 1268920 fixed

    184550216 variable size bytes

    419430400 of database buffers bytes

    Redo buffers 2924544 bytes

    Mounted database.

    ORA-38760: this database instance could not turn on the flashback database

    SQL > alter flashback database;

    Database altered.

    SQL > SHUTDOWN IMMEDIATE;

    SQL > STARTUP MOUNT

    SQL > select flashback_on from database v$.

    FLASHBACK_ON

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

    RESTORE POINT ONLY

    Am not able to extinguish the flame.

    SQL > select * from v$ restore_point;

    Select * from v$ restore_point

    *

    ERROR on line 1:

    ORA-38701: Flashback database log 1 seq 1 wire 1:

    "/ u01/fra/PROD/flashback/o1_mf_c1l5n3lq_.flb".

    ORA-27037: unable to get file status

    Linux error: 2: no such file or directory

    Additional information: 3

    SQL > select flashback_on from database v$.

    FLASHBACK_ON

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

    RESTORE POINT ONLY

    I also tried to create a restore point and the flashback there.

    SQL > create restore point guaranteed rspt1 flashback database;

    Restore point created.

    SQL > select * from v$ restore_point;

    Select * from v$ restore_point

    *

    ERROR on line 1:

    ORA-00600: internal error code, arguments: [krfg_get_keepseq_2], [1], [0], [0,]

    [0], [0], [0], [0]

    SQL > flashback data base to restore the point rspt1;

    flashback database to restore the rspt1 point

    *

    ERROR on line 1:

    ORA-38729: not enough flashback database data log do FLASHBACK.

    Please help me in this regard.

    Alert log file:

    ...

    ...

    ...

    Mount of redo thread 1, with mount id 305866694

    Sun 25 Oct 10:13:30 2015

    Bytes allocated of 3981204 in the shared pool for the generation of flashback buffer

    From RVWR background process

    RVWR started with pid = 16, OS id = 15486

    Sun 25 Oct 10:13:30 2015

    Errors in the /u01/oracle/product/10.2.0/db_1/admin/prod/bdump/prod_rvwr_15486.trc file:

    ORA-38701: seq 11 Flashback database log 11 1 thread: ' / u01/fra/PROD/flashback/o1_mf_c2oqypb0_.flb '.

    ORA-27037: unable to get file status

    Linux error: 2: no such file or directory

    Additional information: 3

    Sun 25 Oct 10:13:30 2015

    Database mounted in exclusive Mode

    Completed: ALTER DATABASE MOUNT

    Sun 25 Oct 10:13:30 2015

    ALTER DATABASE OPEN

    ORA-38760 marked during: ALTER DATABASE OPEN...

    Trace file:

    ...

    ...

    ...

    :() 2015-10-25 10:13:30.087 SERVICE NAME

    SESSION ID: (156.1) 2015-10-25 10:13:30.087

    ORA-38701: seq 11 Flashback database log 11 1 thread: ' / u01/fra/PROD/flashback/o1_mf_c2oqypb0_.flb '.

    ORA-27037: unable to get file status

    Linux error: 2: no such file or directory

    Additional information: 3

    1. Thank you.

    you experience serious problem... because usually it works very well.

    Try the following:

    SQL > shutdown immediate;

    SQL > bootable media.

    SQL > alter flashback database;

    SQL > alter database backup controlfile to trace noresetlogs;

    SQL > shutdown immediate;

    go to the trace file generated from running (alter database backup controlfile to trace noresetlogs ;)

    location of the trace file is located in the query:

    SQL > select * from v$ diag_info;

    It will contain the script with the SQL commands, you can rename the file with the extension ".sql".

    SQL > startup nomount

    SQL > @trace_file. SQL

    SQL > restore database;

    SQL > alter database open;

    So basically you are going to recreate the files of control again...

  • ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

    Hello

    I am getting below error when executing the activities of flashback. Currently we have backups, so when I tried the command flashback in RMAN my question solved.

    But if I want to do the same thing using SQLPLUS what steps should I take?

    ERROR:

    ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

    ORA-38762: redo logs needed for SNA to SNA 20062842936 20062842926

    ORA-38761: redo log sequence 4 in thread 2, 65 incarnation cannot

    consulted

    DATABASE:11.2.0.3.0 (UAT)

    RMAN will automatically restore logs archived redo required for the operation of blowback when they are not present on the drive, while (as meyssoun said) when using sqlplus required archived redo logs must be available on the disc.

    Concerning

    AJ

  • Unable to do the flashback database!

    Hi all

    I activated the flashback database and created a restore point with database of flashback guaranteed so that I can do a flashback database. When I do a flashback database, its says he needs the archivelogs to perform a recovery. Flashback log usually can all have a change given in flashback logs to use for flashbacking a database. Why apply archivelogs when all the changed data does not appear in flashback log itself? please tell me.

    Kind regards

    Pradeep. V

    Hello

    Database of flashback need newspapers archives files.

    "Flashback Database is similar to traditional point-in-time recovery in its effects. To restore a database to the State at a time in the recent past. Flashback Database is much faster than the point-in-time recovery, because it doesn't require you to restore the backup data files and requires fewer changes of the archived redo logs. »

    "No file in the fast recovery area is eligible for deletion if this is required to meet a guaranteed restore point. However, archived redo logs required to meet a guaranteed restore point can be deleted after that only they are saved on disk or on tape. When you use the RMAN FLASHBACK DATABASE command, if the archived redo must convince guaranteed a restore point are not available in the area of fast recovery, then they are restored from backups of logs. »

    REF. Doc:using Flashback Database, and Restore Points

    HTH

  • 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

  • RMAN vs SQL

    Hello

    Recently, I noticed when I pulled the immediate stop of RMAN , it was much faster then the execution even S * QL invite *, is there is no logic behind that?

    Piyush

    Hello

    There is no difference in the speed of the SQL command RMAN.

    The only thing that matters is the amount of work that needs to be cancelled. When there is a lot of work to reduce the immediate closure takes more time.

    Friend

  • With the help of Flashback Database with Yvert

    Hello!

    I am not able to flashback table that was dropped...? .....


    SQL > select log_mode, flashback_on from v$ database;

    LOG_MODE FLASHBACK_ON
    YES ARCHIVELOG


    SQL > select current_scn from v$ database;

    CURRENT_SCN
    * 545466 *.

    SQL > create user usman identified by usman;
    Created by the user.

    SQL > grant connect, usman resources;
    rant succeeded.

    SQL > conn usman/usman
    Connected.

    SQL > create table testtable (id number (9));
    Table created.

    SQL > insert into testtable values (101);
    1 line of creation.

    SQL > insert into testtable values (102);
    1 line of creation.

    SQL > insert into testtable values (103);
    1 line of creation.

    SQL > commit;
    Validation complete.

    SQL > select * from testtable;
    ID

    101
    102
    103

    SQL > conn sys as sysdba
    Enter the password:
    Connected.

    SQL > select current_scn from v$ database;

    CURRENT_SCN
    * 545536 *.

    SQL > drop table testtable is serving;
    Deleted table.

    SQL > commit;
    Validation complete.

    SQL > testtable desc;
    ERROR:
    ORA-04043: testtable object does not exist

    I stop my database and started in flashback mount my database.with RMAN I checked incarnation...

    RMAN > list incarnation;
    using the control file of the target instead of recovery catalog database

    List of Incarnations of the database
    DB key Inc key STATE ID DB name DB reset reset time SNA

    1 1 1221198182 1 AUGUST 30 PARENT ORCL 05
    2 2 ORCL 1221198182 CURRENT 534907 28 JULY 09

    SQL > flashback to the SNA database 545466;
    Flashback complete.

    By mistake I have flashback my database to bad SNA 545466 as above... But I had to flashback to the SNA 545536 which I noted before a fall table.

    SQL > alter database open resetlogs;
    Database altered.

    After level incarnation resetlog also changes...

    RMAN > list incarnation;
    using the control file of the target instead of recovery catalog database

    List of Incarnations of the database
    DB key Inc key STATE ID DB name DB reset reset time SNA

    1 1 1221198182 1 AUGUST 30 PARENT ORCL 05
    2 2 ORCL 1221198182 PARENT 534907 28 JULY 09
    3 3 ORCL 1221198182 CURRENT 545472 28 JULY 09


    After opening of database with resetlog option when I try to connect it is in error.

    SQL > conn usman/usman
    ERROR:
    ORA-01017: name of user and password invalid. connection refused
    WARNING: You are more connected to ORACLE.

    It means I have the flashback database before the creation of the SNA 545466 user;

    I stop my database and the flashback to the right RCS 545536 which was before the deleted table.


    SQL > flashback to the SNA database 545536;
    Flashback complete.

    SQL > alter database open resetlogs;
    Database altered.

    But still he does not connect the user usman... Please helpppp

    SQL > conn usman/usman
    ERROR:
    ORA-01017: name of user and password invalid. connection refused
    WARNING: You are more connected to ORACLE.

    How can I get my table with flashback only

    Please answer me...

    Hi Usman,

    you're right, I didn't notice the "purge" in your ad:
    >
    ...
    SQL > drop table testtable is serving;
    Deleted table.
    ...
    >

    Kind regards
    Uwe

    http://uhesse.WordPress.com

  • Maximum length of the SQL command

    I created a MySQL database and a LabView 8.6 application that inserts data into the database using the SQL Toolbox.  I have a problem very long character data insertion in a LONGTEXT field.  I determined that the problem occurs when the SQL command is more than 1 048 574 characters or the length of a particular field exceeds 1 048 326 characters (cannot say who).

    The error I get is "error-2147467259 occurred at NI_Database_API.lvlib:Conn Execute.vi.  "Exception occurred in the Microsoft OLE DB provider for ODBC drivers: [MySQL] [ODBC 5.1 Driver] [mysqld - 5.1.35 - community] MySQL version disappeared in NI_Database_API.lvlib:Conn Execute.vi.

    According to the MYSQL documentation, a LONGTEXT can 4294967295 characters, so length shouldn't be a problem.  The documentation also indicates "the effective maximum length of LONGTEXT columns also depends on the maximum packet size that is configured in the client/server protocol and available memory", but I don't know how to configure the packet size in LabView.

    I enclose the code example that reproduces the problem, although it is based on a special run table structure effectively.  The table definition is included on the diagram.

    This setting must be configured outside of LabVIEW (UDL or DSN).

    You must configure the server and the client:

    I found this link while searching on stackoverflow

    http://dev.MySQL.com/doc/refman/5.1/en/packet-too-large.html

    You may need to select/Configure a specific vendor (different) in order to set this variable.

  • Files without a NAME during the Flashback Database

    Hi all

    Why, in flashback, database, retrieve a tablespace has dropped the datafile (s) consisting of within table get renamed to UNNAMEDnnn? I was going through some examples on the internet but did not find any concrete reason as to why this happens during the flashback recovery. If the tablespace can be recreated during the process, why not data files that compose?

    Could someone help me please in my understanding.

    Thank you.

    Prithwish Adhikari wrote:

    Hello

    I was talking about the flashback database to retrieve a tablespace has fallen. Please find below the link

    http://www.DBA-Oracle.com/t_rman_159_restore_dropped_tablespace.htm

    My question is

    "

    flashback

    database to the SNA 460217.

    database of flashback to the SNA 460217

    *

    ERROR on line 1:

    ORA-38795: WARNING: flashback has managed but open resetlogs would get error

    below

    ORA-01245: offline file 5 will be lost if resetlogs is done

    ORA-01111: name for the data file 5 is unknown - rename it to the correct file

    ORA-01110: data file 5: ' / u01/oracle/product/10.2.0/db_1/dbs/UNNAMED00005'

    "

    Why, in flashback, database, the data file associated with the storage space gets renamed to unnamed?

    Thanks for the link and new info.

    The reason is the same as in these quotes from doc that I have provided. As ORA-01111 indicates the name of the actual file is unknown so Oracle creates a unique name, then stops recovery so that you can provide the name and location.

    Why, during the flashback database, retrieve a tablespace has fallen...

    This formulation and the wording of the article, is probably what is mislead you. You cannot recover a tablespace using FLASHBACK DATABASE:

    Here is the doc for FLASHBACK DATABASE

    http://docs.Oracle.com/CD/B28359_01/backup.111/b28273/rcmsynta023.htm

    Notes A Flashback Database use operation applies to the entire base. You cannot flash back, individual storage spaces. A Flashback Database operation is similar to a point-in-time data recovery (DBPITR) with RECOVER , but RMAN uses flashback logs to undo changes to a point before the time runs out or SNA

    See that second sentence? You NEED to recover the entire database and, as this quote from doc says, made it like CAMILLE by RECOVER.

    In this example, the storage space AND data files were dropped. So please check the doc to DROP TABLESPACE

    https://docs.Oracle.com/CD/B28359_01/server.111/b28286/statements_9004.htm

    Oracle database deletes all metadata about the space of storage data files and all the data dictionary tempfiles in the tablespace. The database also automatically removes the operating system all data files managed by Oracle and tempfiles in the tablespace. Other data files and tempfiles are not removed from the operating system unless you specify INCLUDING CONTENTS AND DATAFILES .

    See? No additional data in the dictionary for the tablespace or data files. Real datafiles is more if they were managed by Oracle. But there MAY be data files of the operating system if you do NOT use this last clause.

    If Oracle recreates the files using unique names and then allows you to CONFIRM that the name and location should really be.

    You have a problem with that? Or just try to understand?

  • LOV query fails, but works in SQL commands

    I am trying to create a type with semi-automatic item text field, but the query I fill in the definition of LOV returns an error:

    Impossible to analyze the query SQL LOV!

    ORA-00942: table or view does not exist

    Although when I try the same query in the form of SQL commands, it works without any problem. No idea what I am doing wrong?

    The query is as follows, where v_prt_gem_t is a view and prt_gem is a table.

    SELECT
          PG.POST_CODE||' '||PT.NAAM
    FROM
          V_PRT_GEM_T PT
          INNER JOIN
          PRT_GEM PG
          ON
          PT.NR = PG.NR
    WHERE
          LAN_NR = 4
    
    

    Julijan wrote:

    I am trying to create a type with semi-automatic item text field, but the query I fill in the definition of LOV returns an error:

    Impossible to analyze the query SQL LOV!

    ORA-00942: table or view does not exist

    Although when I try the same query in the form of SQL commands, it works without any problem. No idea what I am doing wrong?

    The query is as follows, where v_prt_gem_t is a view and prt_gem is a table.

    1. SELECT
    2. PG. POST_CODE | » '|| PT. NAAM
    3. Of
    4. PT V_PRT_GEM_T
    5. JOIN IN-HOUSE
    6. PG PRT_GEM
    7. WE
    8. PT. NR = PG. NR
    9. WHERE
    10. LAN_NR = 4

    It is likely that CERTAIN privileges on one or two tables/views used are granted for the scheme of the analysis of the application through a role, not directly to the schema. Role-based privileges will be observed in the workshop of SQL in the latest versions of database, but not for running applications. See (YABAOAE) yet another Blog about Oracle Application Express: Application Express and SQL Analysis for detailed information.

    That's why you always have to give the full APEX and the database version numbers when you ask a question: implementations and features change over time. If we know exactly which versions are used so we can determine what behavior is expected, and what bugs exist or have been corrected...

Maybe you are looking for