Talvez esse procedimento também o ajude: *
Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1] In this Document* *Goal* <https://mail.google.com/l%20GOAL> *Solution* <https://mail.google.com/l%20FIX> * This document is being delivered to you via Oracle Support's **Rapid Visibility* <https://mail.google.com/l>* (RaV) process, and therefore has not been subject to an independent technical review.* * Applies to: * Oracle Server - Enterprise Edition - Version: 9.0.1.0 to 11.1.0.6 Information in this document applies to any platform. * Goal Step by step guide on how to create a physical standby database using RMAN without using duplicate command.* * Solution Below are the steps to accomplish the task : * Step 1: Backup the database that includes backup of datafiles, archivelogs and controlfile for standby Step 2: Move the backups to the standby server Step 3: Make proper changes in the parameter files of both primary and standby database Step 4: Do the restore and recover on standby database Step 5: Put the standby database in recover managed mode *Example : ======= Step 1: Backup the primary database that includes backup of datafiles, archivelogs and controlfile for standby* [ora...@test-br ~]$ rman target / Recovery Manager: Release 10.2.0.2.0 - Production on Sun Dec 9 14:56:49 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: ORA10G (DBID=3959250272) RMAN> run 2> { 3> allocate channel c1 type disk; 4> allocate channel c2 type disk; 5> allocate channel c3 type disk; 6> backup database plus archivelog; 7> } using target database control file instead of recovery catalog allocated channel: c1 channel c1: sid=159 devtype=DISK allocated channel: c2 channel c2: sid=138 devtype=DISK allocated channel: c3 channel c3: sid=137 devtype=DISK Starting backup at 09:DEC:2007:14:57:27 current log archived channel c1: starting archive log backupset channel c1: specifying archive log(s) in backup set input archive log thread=1 sequence=32 recid=44 stamp=640387774 input archive log thread=1 sequence=33 recid=45 stamp=640387945 input archive log thread=1 sequence=34 recid=48 stamp=640668312 channel c1: starting piece 1 at 09:DEC:2007:14:57:32 channel c2: starting archive log backupset channel c2: specifying archive log(s) in backup set input archive log thread=1 sequence=35 recid=50 stamp=640882651 channel c2: starting piece 1 at 09:DEC:2007:14:57:32 channel c3: starting archive log backupset channel c3: specifying archive log(s) in backup set input archive log thread=1 sequence=20 recid=20 stamp=640385760 input archive log thread=1 sequence=21 recid=21 stamp=640385772 input archive log thread=1 sequence=22 recid=22 stamp=640385775 input archive log thread=1 sequence=23 recid=23 stamp=640385778 input archive log thread=1 sequence=24 recid=24 stamp=640386245 input archive log thread=1 sequence=25 recid=25 stamp=640386250 channel c3: starting piece 1 at 09:DEC:2007:14:57:32 channel c2: finished piece 1 at 09:DEC:2007:14:57:35 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84xl_.bkp tag=TAG20071209T145731 comment=NONE channel c2: backup set complete, elapsed time: 00:00:04 channel c3: finished piece 1 at 09:DEC:2007:14:57:36 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84z6_.bkp tag=TAG20071209T145731 comment=NONE channel c3: backup set complete, elapsed time: 00:00:05 channel c2: starting archive log backupset channel c2: specifying archive log(s) in backup set input archive log thread=1 sequence=26 recid=26 stamp=640386253 input archive log thread=1 sequence=27 recid=27 stamp=640386256 input archive log thread=1 sequence=28 recid=36 stamp=640387757 input archive log thread=1 sequence=29 recid=37 stamp=640387764 input archive log thread=1 sequence=30 recid=40 stamp=640387769 input archive log thread=1 sequence=31 recid=41 stamp=640387771 channel c2: starting piece 1 at 09:DEC:2007:14:57:37 channel c2: finished piece 1 at 09:DEC:2007:14:57:40 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf892x_.bkp tag=TAG20071209T145731 comment=NONE channel c2: backup set complete, elapsed time: 00:00:04 channel c1: finished piece 1 at 09:DEC:2007:14:57:41 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84xf_.bkp tag=TAG20071209T145731 comment=NONE channel c1: backup set complete, elapsed time: 00:00:10 Finished backup at 09:DEC:2007:14:57:41 Starting backup at 09:DEC:2007:14:57:41 channel c1: starting full datafile backupset channel c1: specifying datafile(s) in backupset input datafile fno=00002 name=/u01/oracle/product/oradata/ora10g/data/undo01.dbf input datafile fno=00003 name=/u01/oracle/product/oradata/ora10g/data/sysaux01.dbf channel c1: starting piece 1 at 09:DEC:2007:14:57:41 channel c2: starting full datafile backupset channel c2: specifying datafile(s) in backupset input datafile fno=00001 name=/u01/oracle/product/oradata/ora10g/data/sys01.dbf input datafile fno=00004 name=/u01/oracle/product/oradata/ora10g/data/rman.dbf channel c2: starting piece 1 at 09:DEC:2007:14:57:41 channel c3: starting full datafile backupset channel c3: specifying datafile(s) in backupset including current control file in backupset channel c3: starting piece 1 at 09:DEC:2007:14:57:45 channel c3: finished piece 1 at 09:DEC:2007:14:57:52 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_ncnnf_TAG20071209T145741_3oqf8kdz_.bkp tag=TAG20071209T145741 comment=NONE channel c3: backup set complete, elapsed time: 00:00:11 channel c3: starting full datafile backupset channel c3: specifying datafile(s) in backupset including current SPFILE in backupset channel c3: starting piece 1 at 09:DEC:2007:14:57:53 channel c3: finished piece 1 at 09:DEC:2007:14:57:56 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnsnf_TAG20071209T145741_3oqf8sq8_.bkp tag=TAG20071209T145741 comment=NONE channel c3: backup set complete, elapsed time: 00:00:04 channel c1: finished piece 1 at 09:DEC:2007:14:58:31 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnndf_TAG20071209T145741_3oqf8fk4_.bkp tag=TAG20071209T145741 comment=NONE channel c1: backup set complete, elapsed time: 00:00:50 channel c2: finished piece 1 at 09:DEC:2007:14:58:31 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnndf_TAG20071209T145741_3oqf8fod_.bkp tag=TAG20071209T145741 comment=NONE channel c2: backup set complete, elapsed time: 00:00:50 Finished backup at 09:DEC:2007:14:58:31 Starting backup at 09:DEC:2007:14:58:31 current log archived channel c1: starting archive log backupset channel c1: specifying archive log(s) in backup set input archive log thread=1 sequence=36 recid=51 stamp=640882711 channel c1: starting piece 1 at 09:DEC:2007:14:58:32 channel c1: finished piece 1 at 09:DEC:2007:14:58:33 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145831_3oqfb0p6_.bkp tag=TAG20071209T145831 comment=NONE channel c1: backup set complete, elapsed time: 00:00:02 Finished backup at 09:DEC:2007:14:58:33 released channel: c1 released channel: c2 released channel: c3 RMAN> run 2> { 3> allocate channel c1 type disk; 4> backup current controlfile for standby; 5> } allocated channel: c1 channel c1: sid=159 devtype=DISK Starting backup at 09:DEC:2007:15:00:09 channel c1: starting full datafile backupset channel c1: specifying datafile(s) in backupset including standby control file in backupset channel c1: starting piece 1 at 09:DEC:2007:15:00:10 channel c1: finished piece 1 at 09:DEC:2007:15:00:11 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_ncnnf_TAG20071209T150009_3oqff2fb_.bkp tag=TAG20071209T150009 comment=NONE channel c1: backup set complete, elapsed time: 00:00:01 Finished backup at 09:DEC:2007:15:00:11 released channel: c1 *Step 2: Move the backups to the standby server * + FTP or SCP the backup pieces. + If the backups are on NFS mount then mount the NFS on standby server with the same name as you mounted on primary database. + Until 9i, you need to move the backup-pieces in exactly the same location on standby as they were created on primary. + From 10g onwards, use CATALOG BACKUPPIECE command if you are moving backup-pieces to a different location. + If the backups are on tape then make sure that you make proper changes on standby server so that you can restore the backups on standby server. *Step 3: Make proper changes in the parameter files of both primary and standby database * *Add the below parameter in primary database parameter file :* log_archive_dest_2='SERVICE=STANDBY' *Add the below parameters in standby database parameter file : * Copy the primary database parameter file and make necessary changes : db_unique_name='standby' instance_name='standby' db_file_name_convert='/u01/oracle/product/oradata/ora10g/data/','/u01/oracle/product/ora10g/oradata/standby/data/','/tmp/','/u01/oracle/product/ora10g/oradata/standby/data/' log_file_name_convert='/u01/oracle/product/oradata/ora10g/log/','/u01/oracle/product/ora10g/oradata/standby/log' standby_archive_dest='/u01/oracle/product/ora10g/oradata/standby/arch1' * Note : In 8i and 9i in-place of db_unique_name='standby' you have to use lock_name_space='standby'* *Step 4: Do the restore and recover on standby database* Note : After the restore try to identify the last archivelog sequence that is backed up and add 1 to it and do the recovery using it. In the below example the last archivelog that is backed up is sequence 36 and we added 1 to it that becomes 37 and we recovered till sequence 37. [ora...@test-br ~]$ export ORACLE_SID=standby [ora...@test-br ~]$ rman target / Recovery Manager: Release 10.2.0.2.0 - Production on Sun Dec 9 15:18:28 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database (not started) RMAN> startup nomount; Oracle instance started Total System Global Area 603979776 bytes Fixed Size 1262224 bytes Variable Size 163581296 bytes Database Buffers 432013312 bytes Redo Buffers 7122944 bytes RMAN> set dbid=3959250272; executing command: SET DBID * For 9i to restore controlfile you need to use the below command :* RMAN> restore controlfile from '/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_ncnnf_TAG20071209T150009_3oqff2fb_.bkp'; * >From 10g onwards you need to use the below command to restore controlfile : * RMAN> restore standby controlfile from '/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_ncnnf_TAG20071209T150009_3oqff2fb_.bkp'; Starting restore at 09:DEC:2007:15:19:50 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=156 devtype=DISK channel ORA_DISK_1: restoring control file channel ORA_DISK_1: restore complete, elapsed time: 00:00:02 output filename=/u01/oracle/product/ora10g/oradata/standby/control01.ctl output filename=/u01/oracle/product/ora10g/oradata/standby/control02.ctl output filename=/u01/oracle/product/ora10g/oradata/standby/control03.ctl Finished restore at 09:DEC:2007:15:19:53 RMAN> sql 'alter database mount standby database'; sql statement: alter database mount standby database released channel: ORA_DISK_1 RMAN> restore database; Starting restore at 09:DEC:2007:15:20:18 Starting implicit crosscheck backup at 09:DEC:2007:15:20:18 allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=156 devtype=DISK Crosschecked 14 objects Finished implicit crosscheck backup at 09:DEC:2007:15:20:20 Starting implicit crosscheck copy at 09:DEC:2007:15:20:20 using channel ORA_DISK_1 Crosschecked 1 objects Finished implicit crosscheck copy at 09:DEC:2007:15:20:20 searching for all files in the recovery area cataloging files... no files cataloged using channel ORA_DISK_1 channel ORA_DISK_1: starting datafile backupset restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00002 to /u01/oracle/product/ora10g/oradata/standby/data/undo01.dbf restoring datafile 00003 to /u01/oracle/product/ora10g/oradata/standby/data/sysaux01.dbf channel ORA_DISK_1: reading from backup piece /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnndf_TAG20071209T145741_3oqf8fk4_.bkp channel ORA_DISK_1: restored backup piece 1 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnndf_TAG20071209T145741_3oqf8fk4_.bkp tag=TAG20071209T145741 channel ORA_DISK_1: restore complete, elapsed time: 00:00:35 channel ORA_DISK_1: starting datafile backupset restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u01/oracle/product/ora10g/oradata/standby/data/sys01.dbf restoring datafile 00004 to /u01/oracle/product/ora10g/oradata/standby/data/rman.dbf channel ORA_DISK_1: reading from backup piece /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnndf_TAG20071209T145741_3oqf8fod_.bkp channel ORA_DISK_1: restored backup piece 1 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_nnndf_TAG20071209T145741_3oqf8fod_.bkp tag=TAG20071209T145741 channel ORA_DISK_1: restore complete, elapsed time: 00:00:25 Finished restore at 09:DEC:2007:15:21:21 The below command will list all the archivelogs which are backed up and from this list we need to identify the maximum sequence for recovery. RMAN> list backup of archivelog all; List of Backup Sets =================== BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 4 65.50K DISK 00:00:01 03:DEC:2007:20:10:18 BP Key: 4 Status: AVAILABLE Compressed: NO Tag: TAG20071203T201017 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_03/o1_mf_annnn_TAG20071203T201017_3o85blm6_.bkp List of Archived Logs in backup set 4 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 9 272579 03:DEC:2007:20:08:38 272631 03:DEC:2007:20:10:16 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 5 688.80M DISK 00:00:48 03:DEC:2007:20:12:22 BP Key: 5 Status: AVAILABLE Compressed: NO Tag: TAG20071203T201133 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_03/o1_mf_annnn_TAG20071203T201133_3o85f0hl_.bkp List of Archived Logs in backup set 5 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 1 1 03:DEC:2007:18:49:10 66282 03:DEC:2007:18:54:55 1 2 66282 03:DEC:2007:18:54:55 100553 03:DEC:2007:18:56:09 1 3 100553 03:DEC:2007:18:56:09 131293 03:DEC:2007:18:57:52 1 4 131293 03:DEC:2007:18:57:52 168479 03:DEC:2007:19:05:44 1 5 168479 03:DEC:2007:19:05:44 210171 03:DEC:2007:19:06:50 1 6 210171 03:DEC:2007:19:06:50 240733 03:DEC:2007:19:08:25 1 7 240733 03:DEC:2007:19:08:25 266780 03:DEC:2007:19:10:40 1 8 266780 03:DEC:2007:19:10:40 272579 03:DEC:2007:20:08:38 1 9 272579 03:DEC:2007:20:08:38 272631 03:DEC:2007:20:10:16 1 10 272631 03:DEC:2007:20:10:16 272683 03:DEC:2007:20:10:42 1 11 272683 03:DEC:2007:20:10:42 272706 03:DEC:2007:20:10:54 1 12 272706 03:DEC:2007:20:10:54 272724 03:DEC:2007:20:10:57 1 13 272724 03:DEC:2007:20:10:57 272744 03:DEC:2007:20:11:00 1 14 272744 03:DEC:2007:20:11:00 272763 03:DEC:2007:20:11:03 1 15 272763 03:DEC:2007:20:11:03 272782 03:DEC:2007:20:11:06 1 16 272782 03:DEC:2007:20:11:06 272802 03:DEC:2007:20:11:09 1 17 272802 03:DEC:2007:20:11:09 272821 03:DEC:2007:20:11:12 1 18 272821 03:DEC:2007:20:11:12 272840 03:DEC:2007:20:11:15 1 19 272840 03:DEC:2007:20:11:15 272861 03:DEC:2007:20:11:33 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 7 61.54M DISK 00:00:04 09:DEC:2007:14:57:35 BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20071209T145731 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84xl_.bkp List of Archived Logs in backup set 7 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 35 400351 07:DEC:2007:03:25:09 489499 09:DEC:2007:14:57:27 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 8 3.08M DISK 00:00:04 09:DEC:2007:14:57:35 BP Key: 8 Status: AVAILABLE Compressed: NO Tag: TAG20071209T145731 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84z6_.bkp List of Archived Logs in backup set 8 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 20 272861 03:DEC:2007:20:11:33 274614 03:DEC:2007:20:56:00 1 21 274614 03:DEC:2007:20:56:00 274621 03:DEC:2007:20:56:12 1 22 274621 03:DEC:2007:20:56:12 274624 03:DEC:2007:20:56:15 1 23 274624 03:DEC:2007:20:56:15 274627 03:DEC:2007:20:56:18 1 24 274627 03:DEC:2007:20:56:18 274796 03:DEC:2007:21:04:05 1 25 274796 03:DEC:2007:21:04:05 274800 03:DEC:2007:21:04:10 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 9 25.00K DISK 00:00:02 09:DEC:2007:14:57:38 BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20071209T145731 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf892x_.bkp List of Archived Logs in backup set 9 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 26 274800 03:DEC:2007:21:04:10 274803 03:DEC:2007:21:04:13 1 27 274803 03:DEC:2007:21:04:13 274806 03:DEC:2007:21:04:16 1 28 274806 03:DEC:2007:21:04:16 275324 03:DEC:2007:21:29:17 1 29 275324 03:DEC:2007:21:29:17 275328 03:DEC:2007:21:29:24 1 30 275328 03:DEC:2007:21:29:24 275332 03:DEC:2007:21:29:29 1 31 275332 03:DEC:2007:21:29:29 275335 03:DEC:2007:21:29:31 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 10 95.73M DISK 00:00:09 09:DEC:2007:14:57:40 BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20071209T145731 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84xf_.bkp List of Archived Logs in backup set 10 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 32 275335 03:DEC:2007:21:29:31 275338 03:DEC:2007:21:29:34 1 33 275338 03:DEC:2007:21:29:34 275545 03:DEC:2007:21:32:25 1 34 275545 03:DEC:2007:21:32:25 400351 07:DEC:2007:03:25:09 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ -------------------- 15 2.00K DISK 00:00:01 09:DEC:2007:14:58:32 BP Key: 15 Status: AVAILABLE Compressed: NO Tag: TAG20071209T145831 Piece Name: /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145831_3oqfb0p6_.bkp List of Archived Logs in backup set 15 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- -------------------- ---------- --------- 1 36 489499 09:DEC:2007:14:57:27 489527 09:DEC:2007:14:58:31 RMAN> recover database until sequence 37; Starting recover at 09:DEC:2007:15:22:38 using channel ORA_DISK_1 starting media recovery channel ORA_DISK_1: starting archive log restore to default destination channel ORA_DISK_1: restoring archive log archive log thread=1 sequence=36 channel ORA_DISK_1: reading from backup piece /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145831_3oqfb0p6_.bkp channel ORA_DISK_1: restored backup piece 1 piece handle=/u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145831_3oqfb0p6_.bkp tag=TAG20071209T145831 channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 archive log filename=/u01/oracle/product/ora10g/flash_recovery_area/ABC/archivelog/2007_12_09/o1_mf_1_36_3oqgq81h_.arc thread=1 sequence=36 channel default: deleting archive log(s) archive log filename=/u01/oracle/product/ora10g/flash_recovery_area/ABC/archivelog/2007_12_09/o1_mf_1_36_3oqgq81h_.arc recid=1 stamp=640884160 Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/u01/oracle/product/ora10g/oradata/standby/data/sys01.dbf' media recovery complete, elapsed time: 00:00:00 Finished recover at 09:DEC:2007:15:22:41 RMAN> exit Recovery Manager complete. Note : No need to worry about the errors, you can safely ignore and move to step 5. Oracle Error: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/u01/oracle/product/ora10g/oradata/standby/data/sys01.dbf' *Step 5: Put the standby database in recover managed mode* After ensuring connectivity from primary to standby using the service specified in LOG_ARCHIVE_DEST_2 parameter of primary and creating a password file on standby with the same sys password as primary, we can start managed recovery on standby. [ora...@test-br ~]$ sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.2.0 - Production on Sun Dec 9 15:49:26 2007 Copyright (c) 1982, 2005, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production With the Partitioning, OLAP and Data Mining options SQL> alter database recover managed standby database disconnect from session; Database altered. 2010/5/18 Raul Francisco Costa F. de Andrade, DBA <raulf...@gmail.com> > Talvez isso ajude: para alterar o nome do database. > > > *Oracle9i Database Utilities** > Release 2 (9.2)* > Part Number A96652-01 > > > Home <http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/index.htm> > > > Book > List<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/nav/docindex.htm> > > > Contents<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/toc.htm> > > > Index<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/index.htm> > > > Master > Index<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/mix.920/a96625/toc.htm> > > > Feedback<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/dcommon/html/feedback.htm> > > ------------------------------ > > > <http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch13.htm><http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch15.htm> > 14 > DBNEWID Utility > > DBNEWID is a database utility that can change the internal database > identifier (DBID) and the database name (DBNAME) for an operational > database. > > This chapter contains the following sections: > > - What Is the DBNEWID > Utility?<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004600> > - Ramifications of Changing the DBID and > DBNAME<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004605> > - Changing the DBID and DBNAME of a > Database<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004665> > - DBNEWID > Syntax<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004966> > > What Is the DBNEWID Utility? > > Prior to the introduction of the DBNEWID utility, you could manually create > a copy of a database and give it a new database name (DBNAME) by re-creating > the control file. However, you could not give the database a new identifier > (DBID). The DBID is an internal, unique identifier for a database. Because > Recovery Manager (RMAN) distinguishes databases by DBID, you could not > register a seed database and a manually copied database together in the same > RMAN repository. The DBNEWID utility solves this problem by allowing you to > change any of the following: > > - Only the DBID of a database > - Only the DBNAME of a database > - Both the DBNAME and DBID of a database > > Ramifications of Changing the DBID and DBNAME > > Changing the DBID of a database is a serious procedure. When the DBID of a > database is changed, all previous backups and archived logs of the database > become unusable. After you change the DBID, you must open the database with > the RESETLOGS option, which re-creates the online redo logs and resets > their sequence to 1 (see the *Oracle9i Database Administrator's > Guide*<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96521/toc.htm>). > Consequently, you should make a backup of the whole database immediately > after changing the DBID. > > Changing the DBNAME without changing the DBID does not require you to open > with the RESETLOGS option, so database backups and archived logs are not > invalidated. However, changing the DBNAME does have consequences. You must > change the DB_NAME initialization parameter after a database name change > to reflect the new name. Also, you may have to re-create the Oracle password > file. If you restore an old backup of the control file (before the name > change), then you should use the initialization parameter file and password > file from before the database name change. > Changing the DBID and DBNAME of a Database > > This section contains these topics: > > - Changing the DBID and Database > Name<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004684> > - Changing Only the Database > Name<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004735> > - Troubleshooting a DBID Change > Operation<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004776> > - Troubleshooting a Database Name Change > Operation<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1004784> > > Changing the DBID and Database Name > > The following steps describe how to change the DBID of a database. > Optionally, you can change the database name as well. > > 1. Ensure that you have a recoverable whole database backup. > > > 1. Ensure that the target database is mounted but not open, and that it > was shut down consistently prior to mounting. For example: > > 3. SHUTDOWN IMMEDIATE > > 4. STARTUP MOUNT > > 5. > > > 1. Invoke the DBNEWID utility on the command line, specifying a valid > user with the SYSDBA privilege. For example: > > 4. % nid TARGET=SYS/ora...@test_db > > 5. > > To change the database name in addition to the DBID, specify the > DBNAMEparameter. This example changes the name to > test_db2: > > % nid TARGET=SYS/ora...@test DBNAME=test_db2 > > > > The DBNEWID utility performs validations in the headers of the datafiles > and control files before attempting I/O to the files. If validation is > successful, then DBNEWID prompts you to confirm the operation (unless you > specify a log file, in which case it does not prompt), changes the DBID for > each datafile (including offline normal and read-only datafiles), and then > exits. The database is left mounted but is not yet usable. For example: > > DBNEWID: Release 9.2.0.1.0 > > > > (c) Copyright 2002 Oracle Corporation. All rights reserved. > > > > Connected to database TEST_DB (DBID=3942195360) > > > > Control Files in database: > > /oracle/dbs/cf1.f > > /oracle/dbs/cf2.f > > > > Change database id of database SOLARIS? (Y/[N]) => y > > > > Proceeding with operation > > Datafile /oracle/dbs/tbs_01.f - changed > > Datafile /oracle/dbs/tbs_02.f - changed > > Datafile /oracle/dbs/tbs_11.f - changed > > Datafile /oracle/dbs/tbs_12.f - changed > > Datafile /oracle/dbs/tbs_21.f - changed > > > > New DBID for database TEST_DB is 3942196782. > > All previous backups and archived redo logs for this database are unusable > > Proceed to shutdown database and open with RESETLOGS option. > > DBNEWID - Database changed. > > > > If validation is not successful, then DBNEWID terminates and leaves the > target database intact. You can open the database, fix the error, and then > either resume the DBNEWID operation or continue using the database without > changing its DBID. > > 1. After DBNEWID successfully changes the DBID, shut down the database: > > > 5. SHUTDOWN IMMEDIATE > > 6. > > > 1. Mount the database. For example: > > 6. STARTUP MOUNT > > 7. > > > 1. Open the database in RESETLOGS mode and resume normal use. For > example: > > 7. ALTER DATABASE OPEN RESETLOGS; > > 8. > > Make a new database backup. Because you reset the online redo logs, the old > backups and archived logs are no longer usable in the current incarnation of > the database. > Changing Only the Database Name > > The following steps describe how to change the database name without > changing the DBID. > > 1. Ensure that you have a recoverable whole database backup. > > > 1. Ensure that the target database is mounted but not open, and that it > was shut down consistently prior to mounting. For example: > > 3. SHUTDOWN IMMEDIATE > > 4. STARTUP MOUNT > > 5. > > > 1. Invoke the utility on the command line, specifying a valid user with > the SYSDBA privilege. You must specify both the DBNAME and > SETNAMEparameters. This example changes the name to > test_db2: > > 4. % nid TARGET=SYS/ora...@test_db DBNAME=test_db2 SETNAME=YES > > 5. > > DBNEWID performs validations in the headers of the control files (*not*the > datafiles) before attempting I/O to the files. If validation is > successful, then DBNEWID prompts for confirmation, changes the database name > in the control files, and exits. After DBNEWID completes successfully, the > database is left mounted but is not yet usable. > > DBNEWID: Release 9.2.0.1.0 > > > > (c) Copyright 2002 Oracle Corporation. All rights reserved. > > > > > > Connected to database TEST_DB (DBID=3942196782) > > > > Control Files in database: > > /oracle/dbs/cf1.f > > /oracle/dbs/cf2.f > > > > Change database name of database TEST_DB to TEST_DB2? (Y/[N]) => Y > > > > Proceeding with operation > > > > Database name changed from TEST_DB to TEST_DB2 - database needs to be > > shutdown. > > Modify parameter file and generate a new password file before restarting. > > > > DBNEWID - Successfully changed database name > > > > If validation is not successful, then DBNEWID terminates and leaves the > target database intact. You can open the database, fix the error, and then > either resume the DBNEWID operation or continue using the database without > changing the database name. > > 1. Shut down the database. For example: > > 5. SHUTDOWN IMMEDIATE > > 6. > > > 1. Set the DB_NAME initialization parameter in the initialization > parameter file to the new database name. > > > 1. Create a new password file. > > > 1. Start up the database and resume normal use. For example: > > 8. STARTUP > > Troubleshooting a DBID Change Operation > > If the DBNEWID utility succeeds in its validation stage but detects an > error while changing the DBID, then the utility stops and leaves the > database in the middle of the change. In this case, you cannot open the > database until the DBNEWID operation is either completed or reverted. > DBNEWID displays messages indicating the status of the operation. > > Before continuing or reverting, fix the underlying cause of the error. > Sometimes the only solution is to restore the whole database from a recent > backup and perform recovery to the point in time before DBNEWID was started. > This underscores the importance of having a recent backup available before > running DBNEWID. > > If you choose to continue the DBID change operation rather than revert it, > reexecute your original command. The DBNEWID utility resumes and attempts to > continue the change until all datafiles and control files have the new DBID. > At this point, the database is left mounted. You should shut it down and > then mount it again prior to opening it with the RESETLOGS option. > > If you choose to revert a DBNEWID operation, and if the reversion succeeds, > then DBNEWID reverts all performed changes and leaves the database in a > mounted state. > > To revert a stalled DBID change operation, run the DBNEWID utility again, > specifying the REVERT keyword. For example: > > % nid TARGET=SYS/oracle REVERT=YES LOGFILE=$HOME/nid.log > > Troubleshooting a Database Name Change Operation > > If you specify that only the database name should be changed (and not the > DBID), then the validation process is the same as for a DBID change except > that DBNEWID checks only the control files. It does not read the datafiles. > If the validation encounters a problem, then the database is left mounted. > > It is possible for validation to succeed, but for the actual database name > change to fail. The possible failure scenarios depend on how many control > files are in the database, as follows: > > - If you have one or more control files and DBNEWID fails on the first > control file, then the database name is not changed in the control file. > You > can either try the operation again or open the database and resume normal > database use. > - If you have more than one control file and DBNEWID fails on the > second control file or on any one thereafter, then some control files will > have the old DBNAME and some will have the new DBNAME. In this case, you > must either manually copy the first changed control file to all > CONTROL_FILES locations, or revert by copying the unchanged control > files to all CONTROL_FILES locations. > > DBNEWID Syntax > > The following diagrams show the syntax for the DBNEWID utility. > > Text description of the illustration > nid.gif<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/img_text/nid.htm> > > Text description of the illustration > nid2.gif<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/img_text/nid2.htm> > > Text description of the illustration > nid3.gif<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/img_text/nid3.htm> > Parameters > > Table > 14-1<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch14.htm#1005723>describes > the parameters in the DBNEWID syntax. > *Table 14-1 Parameters for the DBNEWID Utility* > > *Parameter*** > > *Description*** > > TARGET > > Specifies the username and password used to connect to the database. The > user must have the SYSDBA privilege. If you are using operating system > authentication, then you can connect with the slash (/). If the > $ORACLE_HOME and $ORACLE_SID variables are not set correctly in the > environment, then you can specify a secure (IPC or BEQ) service to connect > to the target database. A target database must be specified in all > invocations of the DBNEWID utility. > > REVERT > > Specify YES to indicate that a failed change of DBID should be reverted > (default is NO). The utility signals an error if no change DBID operation > is in progress on the target database. A successfully completed change of > DBID cannot be reverted. REVERT=YES is only valid when a DBID change > failed. > > DBNAME=new_db_name > > Changes the database name of the database. You can change the DBID and the > DBNAME of a database at the same time. To change only the DBNAME, also > specify the SETNAME parameter. > > SETNAME > > Specify YES to indicate that DBNEWID should change the database name of > the database but should not change the DBID (default is NO). When you > specify SETNAME=YES, the utility only writes to the target database > control files. > > LOGFILE=logfile > > Specifies that DBNEWID should write its messages to the specified file. By > default the utility overwrites the previous log. If you specify a log file, > then DBNEWID does not prompt for confirmation. > > APPEND > > Specify YES to append log output to the existing log file (default is NO). > > HELP > > Specify YES to print a list of the DBNEWID syntax options (default is NO). > Restrictions and Usage Notes > > The DBNEWID utility has the following restrictions: > > - The utility is available only on the UNIX and Windows NT operating > systems. > - The nid executable file should be owned and run by the Oracle owner > because it needs direct access to the datafiles and control files. If > another user runs the utility, then set the user ID to the owner of the > datafiles and control files. > - The DBNEWID utility must access the datafiles of the database > directly through a local connection. Although DBNEWID can accept a net > service name, it cannot change the DBID of a nonlocal database. > - To change the DBID of a database, the database must be mounted and > must have been shut down consistently prior to mounting. In the case of an > Oracle Real Application Clusters database, the database must be mounted in > NOPARALLEL mode. > - You must open the database with the RESETLOGS option after changing > the DBID. Note that you do not have to open with the RESETLOGS option > after changing only the database name. > - No other process should be running against the database when DBNEWID > is executing. If another session shuts down and starts the database, then > DBNEWID aborts. > - All online datafiles should be consistent without needing recovery. > - Normal offline datafiles should be accessible and writable. If this > is not the case, you must drop these files before invoking the DBNEWID > utility. > - All read-only tablespaces must be accessible and made writable at the > operating system level prior to invoking DBNEWID. If these tablespaces > cannot be made writable (for example, they are on a CD-ROM), then you must > unplug the tablespaces using the transportable tablespace feature and then > plug them back in the database before invoking the DBNEWID utility (see the > *Oracle9i Database Administrator's > Guide<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96521/toc.htm> > *). > - You can only specify REVERT when changing only the DBID. > > Examples of Using DBNEWID Changing Only the DBID > > The following example connects with operating system authentication and > changes only the DBID: > > % nid TARGET=/ > > Changing the DBID and Database Name > > The following example connects as user SYS and changes the DBID and also > changes the database name to test2: > > % nid TARGET=SYS/ora...@test1 DBNAME=test2 > > Changing Only the Database Name > > The following example connects as user SYSTEM and changes only the > database name, and also specifies a log file for the output: > > % nid TARGET=SYSTEM/mana...@test2 DBNAME=test3 SETNAME=YES LOGFILE=dbid.out > > ------------------------------ > > > <http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch13.htm> > > > <http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/ch15.htm> > > > Copyright © 1996, 2002 Oracle > Corporation.<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/dcommon/html/cpyr.htm> > All Rights Reserved. > > > Home <http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/index.htm> > > > Book > List<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/nav/docindex.htm> > > > Contents<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/toc.htm> > > > Index<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/server.920/a96652/index.htm> > > > Master > Index<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/mix.920/a96625/toc.htm> > > > Feedback<http://www-css.fnal.gov/dsg/external/oracle_dcm/9iv2/dcommon/html/feedback.htm> > > > > > > Para mudar nome da instancia > > 1- Shutdown no banco; > > 2- Cria o serviço e a instancia > > C:\app\oracle\product\10.2.0\db_1\bin\oradim.exe -new -sid SATP -startmode > manual spfile > > > > > > C:\app\oracle\product\10.2.0\db_1\bin\oradim.exe -edit -sid SATP-startmode > auto -srvcstart system > > > > 3- Seta a instancia: SET ORACLE_SID=SATP > > Verifica-se pela query: > > Select instance_name from v$instance. > > > > 4- Configurar novo serviço com o NETCA > > > > Em 18 de maio de 2010 16:46, Reginaldo de Faveri < > regina...@softplan.com.br> escreveu: > > >> >> Exato. Quando temos comunicação usamos via duplicate... >> >> Diego, estou seguindo o material que você me enviou e ele eh muito bom. >> Soh >> estou com um problema. Estou criando a base com um novo nome então na hora >> do comando "ALTER DATABASE MOUNT;" ocorre o erro abaixo. Você teria alguma >> dica? >> >> RMAN-00571: =========================================================== >> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== >> RMAN-00571: =========================================================== >> RMAN-03002: failure of alter db command at 05/18/2010 16:42:08 >> ORA-01103: database name 'PRODUCAO' in control file is not 'TESTE' >> >> Eu creio que deveriar executar algum comando tipo: "set new__db_name >> TESTE" >> antes do mount; >> >> -----Mensagem original----- >> De: oracle_br@yahoogrupos.com.br <oracle_br%40yahoogrupos.com.br>[mailto: >> oracle_br@yahoogrupos.com.br <oracle_br%40yahoogrupos.com.br>] Em >> nome de Diego Leite >> Enviada em: terça-feira, 18 de maio de 2010 16:24 >> Para: oracle_br@yahoogrupos.com.br <oracle_br%40yahoogrupos.com.br> >> Assunto: Re: [oracle_br] Restore RMAN >> >> >> Ivan, >> >> Acredito que seria otima ideia se o amigo nao tivesse o problema de nao >> comunicacao entre estes servidores, somente por ftp. >> >> (Lembro >> que os servidores (da base origem e da nova base) não tem comunicação. >> Atualmente é feito um backup, baixado via FTP e copiado para o outro >> servidor. >> Certo Reginaldo? tendo comunicacao pode ser feito via duplicate sim... >> >> -- >> Att, >> >> Diego Leite >> DBA ORACLE >> >> Em 18 de maio de 2010 15:43, David Ricardo >> <drb.rica...@gmail.com<drb.ricardo%40gmail.com>> >> escreveu: >> >> > >> > >> > Olá, creio que uma boa opção seria uma DUPLICATE DATABASE com alguns SET >> > NEWNAMES para mudar as localizações dos Datafiles e arquivos do Banco de >> > Dados, e no Duplicate você pode mudar o nome da Instancia também. >> > >> > Ats. >> > >> > Em 18 de maio de 2010 15:18, Ivan Ricardo Schuster >> <ivanr...@gmail.com <ivanrs79%40gmail.com><ivanrs79%40gmail.com >> >>escreveu: >> > >> > >> > >> > > >> > > >> > > No 10g, você pode recuperar seu backup com outro nome usando o >> > > "duplicate target database to ...". Procure no google que você vai >> > > achar vários exemplos. >> > > >> > > No 11g já seria mais fácil, pois você nao precisaria de um backup para >> > > fazer o clone, você poderia fazer usando a new feature "duplicate from >> > > active database". >> > > >> > > 2010/5/18 Diego Leite <diegoleit...@gmail.com<diegoleite2v%40gmail.com> >> <diegoleite2v%40gmail.com><diegoleite2v% >> > 40gmail.com>>: >> > >> > > >> > > > Reginaldo, >> > > > >> > > > ve se te ajuda >> > > > >> > http://www.youngcow.net/doc/oracle10g/backup.102/b14191/rcmrecov002.htm >> > > > >> > > > >> > > > -- >> > > > Att, >> > > > >> > > > >> > > > Diego Leite >> > > > DBA ORACLE >> > > > >> > > > >> > > > >> > > > Em 18 de maio de 2010 14:56, Reginaldo de Faveri >> > > > <regina...@softplan.com.br <reginaldo%40softplan.com.br><reginaldo% >> 40softplan.com.br> <reginaldo% >> > 40softplan.com.br>>escreveu: >> > >> > > > >> > > >> >> > > >> >> > > >> Olá senhores boa tarde? >> > > >> >> > > >> Sempre que precisamos criar uma base a partir de outra (em outro >> > > servidor) >> > > >> fazemos um backup via RMAN, criamos uma instancia com o mesmo nome >> > > original >> > > >> assim como o mesmo caminho. Após o restore, renomeamos a mesma e, >> > quando >> > > >> necessário ajustamos o caminho. >> > > >> >> > > >> Ocorre que gostaria de fazer isto de modo direto tipo um restore >> onde >> > > >> pudesse já informar o nome da nova base bem como o seu novo >> caminho. >> > > >> (Lembro >> > > >> que os servidores (da base origem e da nova base) não tem >> comunicação. >> > > >> Atualmente é feito um backup, baixado via FTP e copiado para o >> outro >> > > >> servidor. >> > > >> >> > > >> Procurei seguir os materiais que tenho assim como o Google mas não >> > > >> consegui. >> > > >> Alguém teria uma receita de bolo? >> > > >> >> > > >> Estou usando Oracle Standard 10.2.0.3 >> > > >> >> > > >> [As partes desta mensagem que não continham texto foram removidas] >> > > >> >> > > >> >> > > >> >> > > > >> > > > >> > > > [As partes desta mensagem que não continham texto foram removidas] >> > > > >> > > > >> > > > >> > > > ------------------------------------ >> > > > >> > > > ---------------------------------------------------------- >> > > >>Atenção! As mensagens do grupo ORACLE_BR são de acesso público e de >> > > inteira responsabilidade de seus remetentes. >> > > > Acesse: http://www.mail-archive.com/oracle_br@yahoogrupos.com.br/ >> > > > ---------------------------------------------------------- >> > > >>Apostilas » Dicas e Exemplos » Função » Mundo Oracle » Package » >> > > Procedure » Scripts » Tutoriais - O GRUPO ORACLE_BR TEM SEU PROPRIO >> > ESPAÇO! >> > > VISITE: http://www.oraclebr.com.br/ >> > > > ---------------------------------------------------------- Links do >> > > Yahoo! Grupos >> > > > >> > > > >> > > > >> > > >> > > >> > >> > -- >> > "O mistério da vida me causa a mais forte emoção. É o sentimento que >> > suscita >> > a beleza e a verdade, cria a arte e a ciência. Se alguém não conhece >> essa >> > sensação ou não pode mais exprimir espanto ou surpresa, já é um >> morto-vivo >> > e >> > seus olhos se cegaram.".(Albert Einstein - 1879 - 1955)" >> > >> > >> > [As partes desta mensagem que não continham texto foram removidas] >> > >> > >> > >> >> [As partes desta mensagem que não continham texto foram removidas] >> >> ------------------------------------ >> >> ---------------------------------------------------------- >> ---------------------------------------------- >> >Atenção! As mensagens do grupo ORACLE_BR são de acesso público e de >> inteira >> responsabilidade de seus remetentes. >> Acesse: http://www.mail-archive.com/oracle_br@yahoogrupos.com.br/ >> ---------------------------------------------------------- >> ---------------------------------------------- >> >Apostilas » Dicas e Exemplos » Função » Mundo Oracle » Package » >> Procedure >> » Scripts » Tutoriais - O GRUPO ORACLE_BR TEM SEU PROPRIO ESPAÇO! VISITE: >> http://www.oraclebr.com.br/ >> ---------------------------------------------------------- >> -------------------------------------------- Links do Yahoo! Grupos >> >> >> > > > > -- > -------------------------------------------------------------- > Raul Francisco da Costa Ferreira de Andrade > DBA - OCA - Oracle Certified Associate > COBIT Foundation 4.1 > Fone: (41)8855-8874 Brt > email: raulf...@gmail.com > Skype: raul.andrade > www.clickdba.com > "Não somos seres humanos passando por uma experiência espiritual > Somos seres espirituais passando por uma experiência humana." > > -- -------------------------------------------------------------- Raul Francisco da Costa Ferreira de Andrade DBA - OCA - Oracle Certified Associate COBIT Foundation 4.1 Fone: (41)8855-8874 Brt email: raulf...@gmail.com Skype: raul.andrade www.clickdba.com "Não somos seres humanos passando por uma experiência espiritual Somos seres espirituais passando por uma experiência humana." [As partes desta mensagem que não continham texto foram removidas] ------------------------------------ -------------------------------------------------------------------------------------------------------------------------- >Atenção! As mensagens do grupo ORACLE_BR são de acesso público e de inteira >responsabilidade de seus remetentes. Acesse: http://www.mail-archive.com/oracle_br@yahoogrupos.com.br/ -------------------------------------------------------------------------------------------------------------------------- >Apostilas » Dicas e Exemplos » Função » Mundo Oracle » Package » Procedure » >Scripts » Tutoriais - O GRUPO ORACLE_BR TEM SEU PROPRIO ESPAÇO! VISITE: >http://www.oraclebr.com.br/ ------------------------------------------------------------------------------------------------------------------------ Links do Yahoo! Grupos <*> Para visitar o site do seu grupo na web, acesse: http://br.groups.yahoo.com/group/oracle_br/ <*> Para sair deste grupo, envie um e-mail para: oracle_br-unsubscr...@yahoogrupos.com.br <*> O uso que você faz do Yahoo! Grupos está sujeito aos: http://br.yahoo.com/info/utos.html
