11g recover physical incomplete eve

Hello Experts,

My configuration:

-OS: RHEL 6.4

-DB oracle: Oracle Standard Edition, c. 11.2.0.4

I am migrating the current RHEL 5, Oracle Standard Edition 10.2.0.4.0 Configuration for new RHEL 6.4 g 11 configuration.

The environment of 10g successfully runs to physical standby mode (manual, no Data Guard):

-Archived redo logs from the primary are copied to the standby server using rsync every 15 minutes

-All transported archived recovery logs are applied on the standby server using point in time recovery, every 3 hours.

-Watch the CRA alerts log files applied and ends with "Incomplete recovery applied to change 292650109"

-Changes in the primary DB DML/DDL not display correctly in the standby database.

The same installer does not work on the new 11g environment: embedded recovery logs not applied during the point in time recovery.

Creation of the database pending:

The same SID was created on the physical server and the server backup, using DBCA.

On the physical server:

-create pfile from spfile

-stop physical sid

-scp pfile to the standby server

-file password for CPS to the standby server

-scp all the data files to the standby server

-Start physics sid

-create the standby controlfile

-scp controlfile ensures the standby server

On the standby server:

-Copy the controlfile Eve in the data directory

-Copy the log files archived from the physical server to the standby server

-installation of starting using physics pfile

-create spfile from pfile

-stop

-startup nomount (using the spfile)

-ALTER DATABASE MOUNT STANDBY DATABASE;

- alter session set nls_date_format ='yyyy-mm - dd:hh24:mi:ss';

- alter auto sleep back the base until time ' 2014 - 06 - 13:08:15:00';

This time is about 10 minutes before performing the backups on the physical server.

This translates to ORA-01547 levert, ORA-01152 and ORA-01110.

- recover the database pending;

pointing to the file redo01.log on the physical server (and even redo02.log and redo03.log)

Only after this database backup can be started in read-only mode:

- ALTER DATABASE OPEN read ONLY;


Applying the redo logs:

Cronjobs using the archived redo logs are shipped to physical standby without problem.

The point in time recovery on the standby will never beyond June 14, 03:14:41, as reflected in the alerts log:


Fri Jul 04 09:30:53 2014

ALTER database recover basic auto sleep until 2014 "- 07 - 04:07:30:53'"

Start of recovery Media

has started the process of logmerger

Fri Jul 04 09:30:53 2014

Managed Standby recovery not using real time applies

Parallel Media Recovery started with 4 slaves

Recovery Media Log /oracle/arch/blldp/blldp_arch_1_73_849877970.arc

Incomplete recovery applied all redo them ever generated.

Change recovery completed by 780221 14/06/2014 time 03:14:41

Media recovery complete (blldp)

Completed: alter auto sleep back the base until time ' 2014 - 07 - 04:07:30:53'

Fri Jul 04 09:30:55 2014

ALTER DATABASE OPEN READ ONLY

The file to archive mentioned is present, as are the other files of archive after 14/06/2014:

SQL > show parameter LOG_ARCHIVE_DEST_1;

LOCATION = / oracle/db/blldp/arch MANDATORY

$ cd/oracle/db/blldp/arch

$ ls - lrth

-rw - r-. 1 oracle oinstall 13M 14 Jun 03:14 blldp_arch_1_73_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K Jun 03:14 blldp_arch_1_74_849877970.arc 14

-rw - r-. 1 oracle oinstall 23M 14 Jun 22:08 blldp_arch_1_75_849877970.arc

-rw - r-. 1 oracle oinstall 2.8 M June 15 at 04:10 blldp_arch_1_76_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K June 15 to 04:10 blldp_arch_1_77_849877970.arc

-rw - r-. 1 oracle oinstall 19M 15 June at 19:00 blldp_arch_1_78_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 16 June to 03:07 blldp_arch_1_80_849877970.arc

-rw - r-. 1 oracle oinstall 7.0 M June 16 at 03:07 blldp_arch_1_79_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 17 Jun 03:07 blldp_arch_1_82_849877970.arc

-rw - r-. 1 oracle oinstall 16M 17 Jun 03:07 blldp_arch_1_81_849877970.arc

-rw - r-. 1 oracle oinstall 18M 18 June to 03:07 blldp_arch_1_83_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 18 June to 03:07 blldp_arch_1_84_849877970.arc

-rw - r-. 1 oracle oinstall 21M 19 June 00:13 blldp_arch_1_85_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 19 June to 03:07 blldp_arch_1_87_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M June 19 at 03:07 blldp_arch_1_86_849877970.arc

-rw - r-. 1 oracle oinstall 30M 20 June 00:14 blldp_arch_1_88_849877970.arc

-rw - r-. 1 oracle oinstall 1.4 M 20 Jun 03:08 blldp_arch_1_89_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 20 Jun 03:08 blldp_arch_1_90_849877970.arc

-rw - r-. 1 oracle oinstall 29M 21 June 00:15 blldp_arch_1_91_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 21 June to 03:09 blldp_arch_1_93_849877970.arc

-rw - r-. 1 oracle oinstall 1.4 M 21 June to 03:09 blldp_arch_1_92_849877970.arc

-rw - r-. 1 oracle oinstall 20M 21 June at 18:09 blldp_arch_1_94_849877970.arc

-rw - r-. 1 oracle oinstall 22M 22 June 00:17 blldp_arch_1_95_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 22 June to 04:29 blldp_arch_1_97_849877970.arc

-rw - r-. 1 oracle oinstall 1.9 M 22 June 04:29 blldp_arch_1_96_849877970.arc

-rw - r-. 1 oracle oinstall 19M 22 June at 19:00 blldp_arch_1_98_849877970.arc

-rw - r-. 1 oracle oinstall 21M 23 June 00:18 blldp_arch_1_99_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 23 June to 03:09 blldp_arch_1_101_849877970.arc

-rw - r-. 1 oracle oinstall 1.4 M June 23 at 03:09 blldp_arch_1_100_849877970.arc

-rw - r-. 1 oracle oinstall June 30M 24 00:19 blldp_arch_1_102_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 24 June to 03:11 blldp_arch_1_104_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M June 24 at 03:11 blldp_arch_1_103_849877970.arc

-rw - r-. 1 oracle oinstall 30M 25 June 00:21 blldp_arch_1_105_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 25 June to 03:10 blldp_arch_1_107_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M June 25 at 03:10 blldp_arch_1_106_849877970.arc

-rw - r-. 1 oracle oinstall 30M 26 June 00:22 blldp_arch_1_108_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 26 June to 03:12 blldp_arch_1_110_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M 26 June 03:12 blldp_arch_1_109_849877970.arc

-rw - r-. 1 oracle oinstall June 26M 27 00:23 blldp_arch_1_111_849877970.arc

-rw - r-. 1 oracle oinstall 5.0 M June 27 at 03:09 blldp_arch_1_112_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K June 27 to 03:09 blldp_arch_1_113_849877970.arc

-rw - r-. 1 oracle oinstall 30M 28 June 00:24 blldp_arch_1_114_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K June 28 to 03:15 blldp_arch_1_116_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M Jun 28 03:15 blldp_arch_1_115_849877970.arc

-rw - r-. 1 oracle oinstall 21M 28 June at 18:09 blldp_arch_1_117_849877970.arc

-rw - r-. 1 oracle oinstall 21M 29 June 00:25 blldp_arch_1_118_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 29 Jun 04:10 blldp_arch_1_120_849877970.arc

-rw - r-. 1 oracle oinstall 1.9 M Jun 29 04:10 blldp_arch_1_119_849877970.arc

-rw - r-. 1 oracle oinstall 22M 29 June at 22:00 blldp_arch_1_121_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 30 June to 03:06 blldp_arch_1_123_849877970.arc

-rw - r-. 1 oracle oinstall 18M 30 June to 03:06 blldp_arch_1_122_849877970.arc

-rw - r-. 1 oracle oinstall 29 M 1 July 00:27 blldp_arch_1_124_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 1 Jul 03:09 blldp_arch_1_126_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M on July 1, 03:09 blldp_arch_1_125_849877970.arc

-rw - r-. 1 oracle oinstall July 25M 2 00:28 blldp_arch_1_127_849877970.arc

-rw - r-. 1 oracle oinstall 7.2 M 2 Jul 03:09 blldp_arch_1_128_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 2 Jul 03:09 blldp_arch_1_129_849877970.arc

-rw - r-. 1 oracle oinstall 23M 2 Jul 22:00 blldp_arch_1_130_849877970.arc

-rw - r-. 1 oracle oinstall 20M 3 July 00:29 blldp_arch_1_131_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 3 Jul 03:08 blldp_arch_1_133_849877970.arc

-rw - r-. 1 oracle oinstall 3.2 M 3 Jul 03:08 blldp_arch_1_132_849877970.arc

-rw - r-. 1 oracle oinstall 31M 4 July 00:30 blldp_arch_1_134_849877970.arc

-rw - r-. 1 oracle oinstall 1.0 K 4 Jul 03:08 blldp_arch_1_136_849877970.arc

-rw - r-. 1 oracle oinstall 1.5 M 4 Jul 03:08 blldp_arch_1_135_849877970.arc

-rw - r-. 1 oracle oinstall 3.1 M 4 Jul 10:38 blldp_arch_1_137_849877970.arc

Registration of the other log files as below is not supported on a data base on hold:

alter database register logfile ' / oracle/arch/blldp/blldp_arch_1_74_849877970.arc';

I tried to adjust the following parameters:

*.standby_archive_dest='/Oracle/DB/blldp/arch '

* .standby_file_management = "AUTO".

but the first has led to: ORA-32004: outdated or obsolete or the parameters specified for the instance of RDBMS

As stated in other posts: on 11g, simply set LOG_ARCHIVE_DEST_1, I did.

But still the arc after June 14 files are not processed (according to the journal alerts and changes in the primary DB after June 14 do not appear in the database the day before).

Am I missing a setting that prevents the CRA files after June 14 being processed?

I made mistakes to put in place the day before DB, causing this problem?

Please advise me.

Best regards

Peter

The database is not "aware" of the subsequent archivelogs.  They shall be made or catalogued.

OR you need a backup controlfile fresh.

Also, as this is a Standard Edition installation, I'm surprised he isn't complaining about the database 'sleep '. Your controlfile is not likely to be a standby controlfile.

Hemant K Collette

Tags: Database

Similar Questions

  • Is it possible to create physical databases Eve from an another standby database?

    Is it possible to create physical databases idle for another physical standby database? I intend to create the second physical standby database, but I don't want to add more downtime to the production database to create the second database pending.

    You don't have to get the amount of Production downtime. Copy instead, ensure another wait. But, adds the second Eve also in Production for Archive log shipping.

  • Physics ArchivedLogs eve

    Hello guys...

    A physics mode standby, when we execute
    SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
    2 > DISCONNECT FROM the SESSION.

    So what parameter determines where the archived logs will be recovered, STANDBY_ARCHIVE_DEST or *nLOG_ARCHIVE_DEST_ *.

    If the STANDBY_ARCHIVE_DEST andn LOG_ARCHIVE_DEST_ have a non-null value, then what is the use of LOG_ARCHIVE_DEST_n ?

    Thanks in advance...

    LOG_ARCHIVE_DEST_n is used on the primary database to define what is the standby database Oracle Net service name.
    STANDBY_ARCHIVE_DEST is used to define the location on the host computer on standby database where archived redo logs should be stored.

  • OBIEE 11G - layer physical attributes has a yellow triangle next to th

    Hello

    What it means if there is a yellow triangle next to some of the attributes in the physical layer.

    Thanks for your time and your help.

    Hello

    It indicates a serious problem with an object that requires the attention of the user (for example, an object must be edited or deleted)

    Please indicate if this can help

    Thank you...

  • Starting physical db intelligence 11g

    In 11g creating physical DB standby with rman duplicate the day before we start db in nomount pfile mode which has only DB_NAME. How to startup nomount with only db_name without memory setting mode.

    He got Thannx,

    When an Oracle instance starts, it reads the parameters for initialization of a

    setup initialization file. This file must specify at least the

    DB_NAMEparameter. All other parameters have default values.

    Reg,

    Ni3

  • ORA-01274 physical pending - DELETED a FEW WORDS NO RESPONSE REQUIRED.

    Hello

    I configured a physical database Eve with transport services ARCH, which works very well.
    When I create a set of data files and the users on the main site, and then create a control journal, the journal of alerts to the backup site is written with error: * ORA-01274 *.

    I have attributed this to a configuration problem and did the whole excerceise from the creation of the primary database of Eve databe and configure the dataguard.

    But the problem still persists. Is this normal? I was told that new tablespaces/data files will not be replicated on the site of Eve by transport services. Is this true? If so, please tell me how to reproduce them on the backup site.
    If not, please help me solve the problem.

    Also, I post here the alert log for a better understanding of the problem. Kindly go through it...
    +
    Clearing online redo logfile 1 /u02/app/oracle/oradata/saasridb/redologs/r01.log
    Clearing online log 1 of thread 1 sequence number 37
    Sun Mar 22 12:47:42 2009
    Errors in file /u02/app/oracle/admin/asridb/bdump/saasridb_mrp0_20176.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u02/app/oracle/oradata/asridb/redologs/r01.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 39
    Sun Mar 22 12:47:43 2009
    Completed: alter database recover managed standby database disconnect from session
    Using STANDBY_ARCHIVE_DEST parameter default value as /u02/app/oracle/saasridb/archival
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 20213
    RFS[1]: Identified database type as 'physical standby'
    Sun Mar 22 12:49:04 2009
    RFS LogMiner: Client disabled from further notification
    Sun Mar 22 12:49:40 2009
    RFS[1]: No standby redo logfiles created
    RFS[1]: Archived Log: '/u02/app/oracle/saasridb/archival/1_39_682125307.arc'
    Sun Mar 22 12:49:42 2009
    Media Recovery Log /u02/app/oracle/saasridb/archival/1_39_682125307.arc
    Media Recovery Waiting for thread 1 sequence 40
    Sun Mar 22 12:56:33 2009
    RFS[1]: No standby redo logfiles created
    RFS[1]: Archived Log: '/u02/app/oracle/saasridb/archival/1_40_682125307.arc'
    Sun Mar 22 12:56:38 2009
    Media Recovery Log /u02/app/oracle/saasridb/archival/1_40_682125307.arc
    File #5 added to control file as 'UNNAMED00005' because
    the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
    The file should be manually created to continue.
    Errors with log /u02/app/oracle/saasridb/archival/1_40_682125307.arc
    MRP0: Background Media Recovery terminated with error 1274
    Sun Mar 22 12:56:38 2009
    Errors in file /u02/app/oracle/admin/saasridb/bdump/a_mrp0_20176.trc:
    ORA-01274: cannot add datafile '/u02/app/oracle/oradata/saasridb/datafiles/a_master.dbf' - file could not be created
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail
    Sun Mar 22 12:56:39 2009
    Errors in file /u02/app/oracle/admin/saasridb/bdump/a_mrp0_20176.trc:
    ORA-01274: cannot add datafile '/u02/app/oracle/oradata/saasridb/datafiles/a_master.dbf' - file could not be created
    Sun Mar 22 12:56:39 2009
    MRP0: Background Media Recovery process shutdown (adb)
    +
    Thanks in advance,
    Aswin.

    Published by: ice_cold_aswin on March 22, 2010 18:09

    Removed a few words... No need to answer...

    Thank you.

    Published by: ice_cold_aswin on March 22, 2010 18:12

    Hello...

    Yes, because the standby_management parameter is set to Manual , you have this problem. Follow these steps on the standby database: -.

    1 alter database recover managed standby database cancel;

    2. Select * from v$ datafile;

    3 alter database create datafile '' as ' / u02/app/oracle/oradata/asridb/datafiles/asrim_master.dbf' ;---> to check the name of the data file.

    4 alter system set standby_file_management = auto scope = both;

    5 change the recovery of database managed standby database disconnect from the session;

    Oracle recommends running the database physical standby with all of the following parameters:

    1 STANDBY_FILE_MANAGEMENT = AUTO
    2 DB_FILE_NAME_CONVERT = set to a proper string value that will help you automatically added to the database name data files pending at the hearing of datafile create on the primary.

    HTH
    Anand

  • problem in physical recovery standby database (Data Guard) by rman

    Hi all

    I created a physical database Eve, I want to make a backup of it by rman and when I lose datafile is that I can restore, backup and restore is fine, but in recovery I encounter a problem
    scenarios is followed

    1. in rman, I create a backup of database Eve by this command:
    backup database more archivelog delete all entries;

    2. I run this command in rman to recover standby database
    Run {}
    2 > set up what SNA 1392701.
    3 > restore database;
    4 > restore database;
    {5 >}
    (1392701 is extracted from this query "SELECT MAX (NEXT_CHANGE #) + 1 UNTIL_SCN FROM V$ LOG_HISTORY LH ')
    V$ DATABASE DB WHERE LH. RESETLOGS_CHANGE #= DB. RESETLOGS_CHANGE # AND LH. RESETLOGS_TIME =
    DB. RESETLOGS_TIME; (""http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")

    but result RMAN is like this:
    executing command: SET until clause


    From restoration to 13 December 08
    using channel ORA_DISK_1
    channel ORA_DISK_1: from datafile backupset restoration
    channel ORA_DISK_1: specifying datafile (s) to restore from
    backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
    restoring datafile 00004 in /u01/app/oracle/oradata/sari/users01.dbf
    restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
    restoring datafile to /u01/app/oracle/oradata/sari/users02.dbf 00006
    channel ORA_DISK_1: reading of the backup/home/oracle/backup/0ek24dt4_1_1 element
    channel ORA_DISK_1: restored the backup part 1
    piece handle = / home/oracle/backup/0ek24dt4_1_1
    tag = TAG20081213T042506
    channel ORA_DISK_1: restore complete, duration: 00:01:07
    Finished restoration to 13 December 08
    From back to 13 December 08
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 116 sequence is already on the disk that the file /u01/app/oracle/oradata/archive/1_116_666786084.arc
    archive log thread 1 sequence 117 is already on the disk that the file /u01/app/oracle/oradata/archive/1_117_666786084.arc
    Archive newspaper filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread = 1 sequence = 116
    Archive newspaper filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread = 1 sequence = 117
    Cannot find the log archiving
    archive log thread = 1 sequence = 118
    RMAN-03002: failure of the command recover to 2008-12-13 05:14:13
    RMAN-06054: recovery of media asking unknown journal: thread 1
    SEQ 118 lowscn 1392700


    3. then I refuse 1392701 to 1392700 and I run this command

    Run {}
    2 > set up what SNA 1392700.
    3 > restore database;
    4 > restore database;
    {5 >}
    executing command: SET until clause
    From restoration to 13 December 08
    using channel ORA_DISK_1
    channel ORA_DISK_1: from datafile backupset restoration
    channel ORA_DISK_1: specifying datafile (s) to restore from
    backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
    restoring datafile 00004 in /u01/app/oracle/oradata/sari/users01.dbf

    restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
    restoring datafile to /u01/app/oracle/oradata/sari/users02.dbf 00006
    channel ORA_DISK_1: reading of the backup/home/oracle/backup/0ek24dt4_1_1 element
    channel ORA_DISK_1: restored the backup part 1
    total, handle = / home/oracle/backup/0ek24dt4_1_1 tag = TAG20081213T042506
    channel ORA_DISK_1: restore complete, duration: 00:01:08
    Finished restoration to 13 December 08
    From back to 13 December 08
    using channel ORA_DISK_1

    starting media recovery
    archive log thread 1 116 sequence is already on record as
    file /u01/app/oracle/oradata/archive/1_116_666786084.arc

    archive log thread 1 sequence 117 is already on record as
    file /u01/app/oracle/oradata/archive/1_117_666786084.arc

    archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc = 1 thread
    sequence = 116archive log
    filename=/U01/app/Oracle/oradata/archive/1_117_666786084.arc
    thread = 1 sequence = error 117Oracle:

    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS
    would get the below error
    ORA-01152: 1 no file has been restored from a sufficiently old backup
    ORA-01110: data file 1: ' / u01/app/oracle/oradata/sari/system01.dbf'

    media recovery complete, duration: 00:00:10
    Finished recover to 13 December 08


    4. If I run
    Run {}
    restore the database;
    recover the database;
    }

    I receive this error on step 2 (06054 RMAN: recovery of media asking unknown journal: thread 1)
    SEQ 118 lowscn 1392700)

    5. If I just restore the database and I do not perform a recovery by rman and I restart repeat if applies to all things seem well
    but in the opening of database, I get ORA-01152: 1 file was not restored from a sufficiently old backup
    Ora-01110: data file 1: ' / u01/app/oracle/oradata/sari/system01.dbf' error)

    do you know what is the problem

    Thank you

    Published by: ARKH 12 December 2008 23:06

    This is because as soon as you open the standby database, application of roll forward stops. At least that's true up to 10 gr 2, 11 g, you have the option "Active Dataguard" (requires an additional license), which allows to apply, while the database is open.

    Werner

  • Physically unavailable space after shrinking at the object level

    Hello

    When the shrink command on table, its run successfully and is to show the free space on dba_free_space, but I checked on asm diskgroup, space is not recover physically. \

    (1) why need feature "alter table table_name retractable cascade" used, if the space is not recover physically.

    Database version: 11.2.0.3

    Version of the operating system: Solaris sparc

    Kind regards

    Arya

    For free space in database file level

    You can resize the data file until the space used to aid under sql

    SELECT ' ALTER DATABASE DATAFILE "' | FILE_NAME | "' RESIZE '. CEIL ((NVL(HWM,1) * 8192) / 1024/1024). AM; "RELATIVE_ DBADF SHRINK_DATAFILES,.

    (SELECT FILE_ID, MAX(BLOCK_ID+BLOCKS-1) HIGH WATER MARK OF THE DBA_EXTENTS BY FILE_ID GROUP) DBAFS

    WHERE DBADF. FILE_ID = DBAFS. CEIL ((NVL(HWM,1) FILE_ID (+) AND CEIL(BLOCKS* 8192 /1024/1024) - * 8192) / 1024/1024) > 0;

  • Primary database is RAC and physical intelligence is the single instance

    Hi all

    I use Oracle RAC 11.2.0.3 as primary database, we will begin to use the Oracle Data Guard.
    I am designing my infrastructure and planing to use single instance Oracle 11.2.0.3 my stand physical database.

    My question is it possible to have my sleep as single instance database while the primary is RAC?
    is it possible to build my Oracle database single instance ensures from the primary database to the RAC, RMAN backup?
    Are there restrictions (or all of the points to consider) as my primary database is CARS while the physics of Eve is the only Oracle instance?

    in the link below
    [http://docs.oracle.com/cd/B28359_01/server.111/b28294/concepts.htm#i1039416]
    It was mentioned that primary can be CARS or simple and even the day before, but my question is possible to have primary as CARS all on standby as single instance? or it should be like each other?
    The primary database can be either a single-instance Oracle database or an Oracle Real Application Clusters (RAC) database.
    Similar to a primary database, a standby database can be either a single-instance Oracle database or an Oracle RAC database.
    Kind regards

    http://docs.Oracle.com/CD/B28359_01/server.111/b28294/rac_support.htm

  • ORA-17629: when you try to use database active for the construction of Eve

    Hey guys, I did research on it for hours and I tried different things but when even cannot get a handle of what Miss me...

    I'll try the 11 g physical creation Eve to help "...". of the active database"instead of the old way. I keep running into a brick wall. Any help would be appreciated.
    DB version is 11.2.0.2 on AIX

    This is what has been done...
    1 created pfile on primary and standby
    2 created orapwd file and transferred to the standby
    3 standby db is nomounted (startup nomount) and listener is running

    cemabc_p = main forum nom_unique
    cemabc_s = unique name of instance eve

    im commands running in mode ensures:
    RMAN target backup_admin/temabc@cemabc_p catalog rman/qaabc@rmnabc

    AUXILIARY backup_admin/temppw@cemabc_s connection
    RMAN > DUPLICATE TARGET DATABASE BEFORE database NOFILENAMECHECK active;

    From February 22, 13 Db double
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID = 7 type of device = DISK

    content of Script memory:
    {
    backup that copy reuse
    TargetFile ' / oracle/app/oracle/product/11.2.0.2/dbs/orapwcemabc' auxiliary format
    ' / oracle/app/oracle/product/11.2.0.2/dbs/orapwcemabc';
    }
    execution of Script memory

    From backup February 22, 13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 112 type device = DISK
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Db in dual at 22/02/2013 14:53:52
    RMAN-05501: abandonment of duplicate target database
    RMAN-03015: an error has occurred in the script stored memory Script
    RMAN-03009: failure of the backup command on the ORA_DISK_1 channel at 22/02/2013-14:53:52
    ORA-17629: unable to connect to the remote database server
    ORA-17629: unable to connect to the remote database server



    What ive tried so far... I tried to connect from the primary database:
    adcabc1: / home/oracle/dba > rman target backup_admin/temabc catalog rman/qabc@rmnabc

    Recovery Manager: release 11.2.0.2.0 - Production on Fri Feb 22 14:52:51 2013

    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

    connected to target database: CEMABC (DBID = 4229695208)
    connected to the recovery catalog database

    RMAN > catalog resync db_unique_name all;


    from full resynchronization of the recovery catalog
    full complete Resync

    from full resynchronization of the recovery catalog
    full complete Resync

    from full resynchronization of the recovery catalog
    full complete Resync



    Still no luck.
    I have cemabc_p and cemabc_s both primary and standby tnsping succuessfully.

    Im sure I'm missing a step, if it didn't there was more information need... Let me know

    Ok

    I guess that

    connected to target database: CEMABC (DBID=4229695208)
    connected to auxiliary database: CEMABC (not mounted)
    

    On the remote server's right? If so, it shows that RMAN was able to connect to the main server and the local static connection. So the problem is probably that the principal server cannot connect back.

    You need an entry for the CLONE in your TNSNAMES file. ORA on both servers. Can you confirm this?

    Can you post the listener.ora for clone entry?

    I'm double control it

    rman target backup_admin/temabc@cemabc_p catalog rman/qaabc@rmnabc
    

    (Above is odd)

    Mine:

    rman target=sys/@recover2 auxiliary=sys/@reclone
    

    I use SYS/password both for him to work.

    Also, make sure that these are defined

    listener.ora
    INBOUND_CONNECT_TIMEOUT_ = 120
    
    sqlnet.ora
    SQLNET.INBOUND_CONNECT_TIMEOUT = 120
    

    Restart the listeners later

    Best regards

    mseberg

    Published by: mseberg on February 22, 2013 15:10

    Published by: mseberg on February 22, 2013 15:11

  • The upgrade of physical standby database

    Hi guru,.

    We have Oracle 11 GR 2 (11.2.0.1) in a production of single instance database. This prod db has a physical database Eve sitting on another server. We would like to improve our prod & Eve at 11.2.0.3

    I remember reading a document of MOS on the upgrade of the previous day, but unfortunately not able to find.

    Grateful if you could guide me.

    Thank you

    Prem

    PL see this Doc MOS and the Docs of MOS, he made reference to

    How to level one database and secondary physical to Oracle10gR2 (10.2) [ID 407040.1]

    HTH
    Srini

  • How to get the MAC address for the physical NETWORK adapter of the HOST ESX (vmnic0/vmnic1)

    I can recover physical NIC details for the server HOST ESX, but MAC is empty... How can I get?

    Thank you/HKS

    $net = get-VMHostNetwork - VMHost myServer.domain.net

    $net | FC

    class VMHostNetworkInfoImpl

    {

    VMKernelGateway = 166.12.113.1

    ConsoleGateway = 166.12.113.1

    ConsoleGatewayDevice = vswif0

    DnsAddress =

    [

    169.40.0.2

    169.40.0.1

    ]

    DnsFromDhcp = False

    DnsDhcpDevice =

    DomainName = domaine.net

    Host name = hostname1

    SearchDomain =

    [

    EU.hedani.NET

    ]

    PhysicalNic =

    [

    class PhysicalNicImpl

    {

    BitRatePerSec = 1000

    FullDuplex = True

    WakeOnLanSupported =

    ID = key - vim.host.PhysicalNic - vmnic0

    DeviceName = vmnic0

    Mac =

    DhcpEnabled = False

    IP =

    SubnetMask =

    }

    class PhysicalNicImpl

    {

    BitRatePerSec = 0

    FullDuplex = False

    WakeOnLanSupported =

    ID = key - vim.host.PhysicalNic - vmnic1

    DeviceName = vmnic1

    Mac =

    DhcpEnabled = False

    IP =

    SubnetMask =

    }

    ]

    VirtualSwitch =

    [

    class VirtualSwitchImpl

    {

    Key = key - vim.host.VirtualSwitch - vSwitch0

    Name = vSwitch0

    NumPorts = 128

    NumPortsAvailable = 105

    NIC =

    [

    vmnic1

    vmnic0

    ]

    MTU =

    }

    class VirtualSwitchImpl

    {

    Key = key - vim.host.VirtualSwitch - vSwitch1

    Name = vSwitch1

    NumPorts = 64

    NumPortsAvailable = 56

    NIC =

    MTU =

    }

    class VirtualSwitchImpl

    {

    Key = key - vim.host.VirtualSwitch - vSwitch2

    Name = vSwitch2

    NumPorts = 64

    NumPortsAvailable = 64

    NIC =

    MTU =

    }

    ]

    ConsoleNic =

    [

    class HostConsoleVirtualNicImpl

    {

    PortGroupName = Service_Console_VLAN1

    ID = key - vim.host.VirtualNic - vswif0

    DeviceName = vswif0

    Mac = 00:50:56:4 c: 1 d: 3B

    DhcpEnabled = False

    IP = 111.11.111.11

    Subnet mask = 255.255.255.0

    }

    class HostConsoleVirtualNicImpl

    {

    PortGroupName = Service_Console_ISOL

    ID = key - vim.host.VirtualNic - vswif1

    DeviceName = vswif1

    Mac = 00:50:56:4 d: 88:87

    DhcpEnabled = False

    IP = 10.0.0.241

    Subnet mask = 255.255.255.0

    }

    ]

    VirtualNic =

    [

    class HostVMKernelVirtualNicImpl

    {

    VMotionEnabled = True

    PortGroupName = Vmotion_VLAN1

    ID = key - vim.host.VirtualNic - portgroup3

    DeviceName = portgroup3

    Mac = 00:50:56:65:04:56

    DhcpEnabled = False

    IP = 166.12.113.72

    Subnet mask = 255.255.255.0

    }

    ]

    }

    get-vmhost | % {(get-view $_.id).config.network.pnic} | select Device, Mac
    

    http://www.vmwarescripting.com

  • physical creation of the standby database

    Hi master,

    I tried to create physical databases Eve on the same host as my primary database, I followed the steps according to the oracle documentation.

    but it always ben difficult to create one on the same machine with a different directory structure.

    I just want to know what additional steps should I follow? I need to create controlfile everywhere for standby? or the same controlfile will work for me?

    But if I recreate it could be the difference in thread...

    What is delicate procrdure?



    Thanks and greetings
    VD

    My dear friend... even if you create a database of watch on the same host that you don't need to recreate the controlfile. Standby Controlfile will work for you. DB_convert settings will change the path of the data files in the controlfile. If you re-create a controlfile... then it won't be identified as standby controlfile.

    Concerning

  • Accidentally open a standby database: can I return to standby mode?

    Hello world

    I accidentally opened a physical database Eve (I shot to the top of the body of Eve with "START" instead of the usual "STARTUP MOUNT" command)

    Do I have a chance to return to mode standby without duplicating fully all the data files in a full reconstruction of Eve? (Bandwidth network between the main site and will mean hours of copying files between sites).


    something like:

    1 / stop immediately the mistakenally open mode standby; in fact already done ;-)

    2 / create new control on primary eve files and copy them on standby

    3 / copy the logs to check-in to the main site in standby mode

    4 / re open an instance sleep and hopefully recover the gap between the standby and primary

    We are running Oracle 10 g 2 with dataguard.

    Thanks in advance!

    Jose

    JO * 356268 * os wrote:

    Hello world

    I accidentally opened a physical database Eve (I shot to the top of the body of Eve with "START" instead of the usual "STARTUP MOUNT" command)

    Do I have a chance to return to mode standby without duplicating fully all the data files in a full reconstruction of Eve? (Bandwidth network between the main site and will mean hours of copying files between sites).

    something like:

    1 / stop immediately the mistakenally open mode standby; in fact already done ;-)

    2 / create new control on primary eve files and copy them on standby

    3 / copy the logs to check-in to the main site in standby mode

    4 / re open an instance sleep and hopefully recover the gap between the standby and primary

    We are running Oracle 10 g 2 with dataguard.

    Thanks in advance!

    Jose

    Looks like you think more complex

    If you accidentally open eve of Galzain READ ONLY instead of mount status, then you can safely stop and then again start in State.

    But the following description that you mentioned, I did not understand. Your watch was already split and it works well and that you opened before in OPEN mode? Is that your question? If yes no need to worry about follow below steps and nothing to restore controlfile or something Eve elementary school.

    (1) immediate closure

    (2) startup mount

    (3) start MRP

  • RMAN restore until THE SNA in DATA GUARD environment

    Hello

    OS = RHL5

    DB = 11.2.0.3 primary and 1 physical database paused.

    I have a huge request changes tomorrow and its possible that I have an obligation to RESTORE the database 5 hours back because the application.

    I think to be adopted following the method of the official documentation of the Oracle (untilClause):

    MOUNT FORCE OF START

    RUN

    {

    UNTIL THE SNA 1418901.  # The necessary number SNA will be used here.

    RESTORE THE DATABASE;

    RECOVER THE DATABASE;

    }

    ALTER DATABASE OPEN RESETLOGS;

    I will of course take Level0 backup tonight and LEVEL1 backup before the start of the work.

    My humble question is that: If this is the good method I adopt? and if so, then what about physical databases eve? Is that something to restore/recovery too? It is not required or waiting for database necessary to create again (which I'm afraid of)?

    Flash back is not enabled.

    Pack of thank you for the suggestion.

    Best regards

    You can enable FLASHBACK DATABASE on major sites and relief and set a RESTORE POINT before the migration of the applications.

    If you stop to redo expedition to the France, the waking state is the last SNA that was applied (i.e. 1001). If you need to return the primary SNA 1011 and then resume the delivery of roll forward, Eve can continue to 1002 from totally ignorant.  If you flashback primary to a SNA lower, say, 998, you would have to flashback the night before as well (997 or 998) until you can resume redo expedition to the France.

    See the Oracle support Note: how Flashback the primary database in standby Configuration (Doc ID 728374.1)

    Hemant K Collette

Maybe you are looking for