Remove archives using RMAN
Hello everyone,
We've two situations (11GR2 (11202) RAC) ...
- first, is even when using "backup as copy archivelog all not backed up 1 times" for backing up logs to normal FS from ASM I get below errors in log file:
Starting backup at 10-OCT-11
current log archived
channel ch1: starting archived log copy
input archived log thread=2 sequence=14123 RECID=44194 STAMP=764124901
channel ch2: starting archived log copy
input archived log thread=1 sequence=18793 RECID=44195 STAMP=764124901
RMAN-03009: failure of backup command on ch1 channel at 10/10/2011 02:00:23
ORA-19635: input and output file names are identical: /oracle/admin/archive_backup/RAC_2_14123.arc
continuing other job steps, job failed will not be re-run
channel ch1: starting archived log copy
input archived log thread=2 sequence=14124 RECID=44196 STAMP=764124930
RMAN-03009: failure of backup command on ch2 channel at 10/10/2011 02:00:24
ORA-19635: input and output file names are identical: /oracle/admin/archive_backup/RAC_1_18793.arc
continuing other job steps, job failed will not be re-run
Is RMAN not supposed to backup only those archives which were not already backed up ?
Or is it that copy is not counted as a backup ???
- Second, when I remove the logs using "delete archivelog all completed before "trunc(sysdate)"" it removes the logs from ASM as well as the copy made using above command.
can anybody help me with this.
thanks
From documentation:
Note: You can only specify NOT BACKED UP integer TIMES when backing up archived redo log files into backup sets.
RMAN does not throw an error, but it ignores the clause.
Werner
Similar Messages
-
Deleting all backed up archives using RMAN
Hi,
I used 'delete input' to delete all the archives backed up.
I am storing archives in dest1 and dest2...i.e, in two locatiions in production.
Although archive in dest1 is getting deleted I am unable to delete those in dest2.Please help to delete archives in dest2 too.Ed,
Probably there is missing one "all" in your command :
C:\>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jul 5 17:37:57 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1308204436)
RMAN> backup archivelog delete ALL input;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "delete": expecting one of: "all, from, high, like, low, scn, sequence, time, until"
RMAN-01007: at line 1 column 19 file: standard input
RMAN> BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
Starting backup at 05-JUL-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=70 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=325 RECID=300 STAMP=786108184
input archived log thread=1 sequence=326 RECID=301 STAMP=786108634
Finished backup at 05-JUL-12
RMAN>Regards
Girish Sharma -
How to remove archive log files using Enterprise Manger
Hi,
I took backup of the archive log files and i deleted those files at OS level but it is not reflecting in the Enterprise Manager it is showing the same. Can any one help in how to delete the archive log files by using Enterprise Manger.
version 10.2.0.1.0
any help is appreciated.
Regards,
AshrafI have the same problem. I have 10gr1 and 10gr2 on different servers. On 10gr1, under administration/manage current backup/image, I can see archivelog files, and can mange them. But on 10gr2, the image doesn't show archivelog files. I can only remove them using rman. I wonder if it's because the different design on 10gr2 or I missed something when setup the backup?
-
Deletion of archive log using RMAN Target in Oracle 10g
Hi All,
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@dbMy Query is can I use
RMAN> delete noprompt expired archivelog all;as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Hello;
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@db
Are you trying to connect it through Grid control ? If connecting through a script, then please post its contents.
Make sure you are not connecting to the target database using "nocatalog".
rman target sys/<pwd_of_target>@<target_db> catalog <catalog_schema>/<catalog_schema_pwd>@<catalog_db>
My Query is can I use
RMAN> delete noprompt expired archivelog all;
as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Are these archives backed up ? The above command only updates the RMAN repository if in case the archives were delete manually at OS level.
I would recommend you to backup these archives and then delete them.
RMAN>backup archivelog all not backedup 1 times delete input;If these archives are already backed up and have not been deleted from the disk, then you can use the below command
RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';where "n" is the number of days behind the current date. Make sure to verify if these archives have been backed up before deleting.
Regards,
Shivananda -
Backup archive logs problem using RMAN
Hi guys
I got failure when using RMAN to backup archive log files:
Starting backup at 20-APR-06
current log archived
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/20/2006 21:53:57
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/o1_mf_1_1_21p5c251_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RMAN> **end-of-file**
My archive log files location:
SQL> show parameter log_archive_dest
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=/opt/oracle/oradata/DB10G/arch/
Current archive log files:
$ ls /opt/oracle/oradata/DB10G/arch
1_17_586191737.dbf 1_21_586191737.dbf 1_25_586191737.dbf 1_29_586191737.dbf 1_33_586191737.dbf
1_18_586191737.dbf 1_22_586191737.dbf 1_26_586191737.dbf 1_30_586191737.dbf 1_34_586191737.dbf
1_19_586191737.dbf 1_23_586191737.dbf 1_27_586191737.dbf 1_31_586191737.dbf 1_35_586191737.dbf
1_20_586191737.dbf 1_24_586191737.dbf 1_28_586191737.dbf 1_32_586191737.dbf afiedt.buf
$
But when I check v$archived_log:
SQL> select name,status,deleted from v$archived_log;
NAME S DEL
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/ A NO
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_18/ A NO
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_19/ A NO
/opt/oracle/oradata/DB10G/redo01.log A NO
/opt/oracle/oradata/DB10G/redo02.log A NO
/opt/oracle/oradata/DB10G/redo03.log A NO
/opt/oracle/oradata/DB10G/arch/1_5_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_6_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_7_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_1_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_2_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_3_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_4_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_5_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_6_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_7_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_8_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_9_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_10_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_11_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_12_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_13_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_14_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_15_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_16_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_17_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_18_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_19_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_20_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_21_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_22_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_23_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_24_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_25_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_26_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_27_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_28_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_29_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_30_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_31_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_32_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_33_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_34_586191737.dbf A NO
More records than actual archived logs. How could it happen? How to solve?
THanks in advance.
SharonHi,
Use
RMAN>crosscheck archivelog all; cmd -
When to delete archive logs- using rman 10.1.0.5
Hello,
I am using rman to backup my database(10.1.0.5) along with backing up the archivelogs delete input. The retention of the backup is set to 1. I am backing the datafiles and archivelogs to disk /backupdata. I noticed that the /backupdata is filling up with a lot of backup archivelogs. Since the retention of the database is set to 1, does that mean that rman will also clean the archivelogs in /backupdata too? What I am asking is, since the retention is set to 1, does rman automatically determine witch archivelogs in the /backupdata to delete if rman determines that the archivelogs is not needed to satisfied the retention 1 condition??? Thank you in advance.rman won't automatically purge your backups. Retention policy can be defined to be 1 (what?) redundancy copies or recovery window?
You may have defined, let's say 1 redundant copy, which means you must have at least one backup to consider the other obsolete, and you will keep one redundant copy. The other backups are not automatically deleted, they are just marked obsolete, and you can delete them.
I suggest you to manually purge your backups, as they will fill up your storage. issue, from a recovery manager session:
rman> report obsolete;
rman > delete noprompt obsolete;
rman> report obsolete;
The delete noprompt obsolete will physically purge all backups reported as obsolete by the first command. You can confirm actions from the last command.
I suggest you to perform a periodic task to purge obsolete backups, schedule last command, it can be done once your regular backup ends.
If you have Enterprise manager DB Control console enabled, it can be scheduled using the internal scheduler, and it can be monitored from within EM.
~ Madrid. -
Hello all,
Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
1-L0 backup
2-L1 Backup ( Incremental cummulative)
Facts:
-Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
* The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
* From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
-The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
-Tracking file is enabled
Target:
Knowing that our backup retention windows is 22hours.
Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
Would this affect L1 backup? and how?
Thank in advance for your response
Alexuser8979607 wrote:
Hello all,
Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
1-L0 backup
2-L1 Backup ( Incremental cummulative)
Facts:
-Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
* The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
* From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
-The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
-Tracking file is enabled
Target:
Knowing that our backup retention windows is 22hours.
Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
Would this affect L1 backup? and how?
Thank in advance for your response
AlexI'm not sure what you are talking about with Backup files Windows retention period ... 22 hours".
I don't know what you mean by "Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup."
If you are not taking your database backups with rman you are on shaky ground. The principles are simple. To recover your database from a failure, you will need to start with an L0 backup. The rman RESTORE command will then restore individual blocks from any applicable and available L1 backups. You would follow that with a RECOVER command, that would attempt to apply all necessary redo from available archivelogs. If the necessary archivelogs have been deleted, rman will attempt to restore them from a backup. You can use rman to backup AND DELETE archivelog files to keep the archivelog destination cleaned out.
I take an L0 backup once a week, an L1 the other 6 days, and archivelogs twice a day. The only time I've had a problem with the archivelog dest filling up is when some buggy code that has a loop goes into production and starts flooding redo.
Exactly how are you taking your database backups? If you are not using rman, then you are already on shaky ground. -
Unable to restore TABLESPACE using RMAN backups
Hi,
I am not able to restore tablespace using RMAN (TSPITR).
I have full backup of database,
While try to restore it's failed.
RMAN> recover tablespace TEST1 until logseq 706 auxiliary destination '/tmp';
Starting recover at 16-OCT-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS2
Creating automatic instance, with SID='CsFz'
initialization parameters used for automatic instance:
db_name=TRAINEE
db_unique_name=CsFz_tspitr_TRAINEE
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp
log_archive_dest_1='location=/tmp'
#No auxiliary parameter file used
starting up automatic instance TRAINEE
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
List of tablespaces that have been dropped from the target database:
Tablespace TEST1
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 16-OCT-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=81 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09
channel ORA_AUX_DISK_1: piece handle=/oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09 tag=TAG20131016T144951
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl
Finished restore at 16-OCT-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 7 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 6 to
"/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 7, 2, 6;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/TRAINEE/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 16-OCT-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /tmp/TRAINEE/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00007 to /tmp/TRAINEE/datafile/o1_mf_undotbs2_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /tmp/TRAINEE/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /tmp/1iomi9rv_1_1
channel ORA_AUX_DISK_1: piece handle=/tmp/1iomi9rv_1_1 tag=TAG20131016T144935
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 16-OCT-13
datafile 1 switched to datafile copy
input datafile copy RECID=11 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf
datafile 7 switched to datafile copy
input datafile copy RECID=12 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=13 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 7 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 6 online";
# recover and open resetlogs
recover clone database tablespace "TEST1", "SYSTEM", "UNDOTBS2", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 7 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 6 online
Starting recover at 16-OCT-13
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 702 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf
archived log for thread 1 with sequence 703 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf
archived log for thread 1 with sequence 704 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf
archived log for thread 1 with sequence 705 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf thread=1 sequence=702
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf thread=1 sequence=703
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf thread=1 sequence=704
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf thread=1 sequence=705
media recovery complete, elapsed time: 00:00:01
Finished recover at 16-OCT-13
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST1 read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
executing Memory Script
sql statement: alter tablespace TEST1 read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_CsFz":
EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
EXPDP> Master table "SYS"."TSPITR_EXP_CsFz" successfully loaded/unloaded
EXPDP> ******************************************************************************
EXPDP> Dump file set for SYS.TSPITR_EXP_CsFz is:
EXPDP> /tmp/tspitr_CsFz_17454.dmp
EXPDP> ******************************************************************************
EXPDP> Datafiles required for transportable tablespace TEST1:
EXPDP> /tmp/TRAINEE/datafile/o1_mf_test1_95wbkyck_.dbf
EXPDP> Job "SYS"."TSPITR_EXP_CsFz" successfully completed at 14:56:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
executing Memory Script
database closed
database dismounted
Oracle instance shut down
Performing import of metadata...
IMPDP> Master table "SYS"."TSPITR_IMP_CsFz" successfully loaded/unloaded
IMPDP> Starting "SYS"."TSPITR_IMP_CsFz":
IMPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_temp_95wblk08_.tmp deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_3_95wblj14_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_2_95wblhn8_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_1_95wblh8q_.log deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf deleted
auxiliary instance file /tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/16/2013 14:56:16
RMAN-06963: Error received during import of metadata
RMAN-06961: IMPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-01565: error in identifying file '/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3Hi,
Cloud you please cheek below link:
ORACLE Cookies: TSPITR to recover a dropped tablespace
Thank you -
Deleting archives with RMAN when physical database is in place
hi all,
i want to backup and remove archvie logs using RMAN on one of my system which is having a physical standby database.how can i ensure RMAN backup and delete only archive logs which are shipped to DR site(physical standby database).when ever i fire my rman script it should delte only the archvies which are alredy shipped.i appreciate your valueble inpus in this regard.
regards
SAngeethHi,
@sangeeth +" what if my database has no flash recovery area confgured. "+
This is introduced in Oracle Database 11g R1. Please check http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/wnbradv.htm#sthref6
Archived log deletion policy enhancements
When you CONFIGURE an archived log deletion policy, the configuration applies to all archiving destinations, including the flash recovery area. Both BACKUP ... DELETE INPUT and DELETE ... ARCHIVELOG obey this configuration, as does the flash recovery area. You can also CONFIGURE an archived redo log deletion policy so that logs are eligible for deletion only after being applied to or transferred to standby database destinations. You can set the policy for mandatory standby destinations only, or for any standby destinations.
Regards,
Vaibhav -
Synchronous multimaster replication Backup strategy using RMAN
Hi all,
I am using synchronous multimaster replication. my question is backup strategy has to perofirm in all the master site or only in any of 1 mastersite? what all problems will encounter in RMAn backup in my scenario please help me out with your suggestion
nagaraj.K
[email protected]You ask: "I want to configure backup strategy using RMAN. any one can help me that"
And the answer is clearly no we can not.
An RMAN backup strategy depends on your SLA (Service Level Agreement) with your customers that you didn't post. What is your down-time window? What is your skill set?
You ask: "How to configure for RMAN Incremental backup?"
Read the docs at http://tahiti.oracle.com for your version (which you didn't mention).
You ask: "What will be backup space and there size ?"
We have no idea. Are you going to create an image copy or a backup set? Read the docs and learn the difference. Are you going to turn on compression? Are you going to back up only changed blocks? We don't know.
You ask: "how to manage growing online archiving files?"
Again we can't help you without knowing your SLA. How many MG/GB are they? What period of time do you need to retain them to meet your SLA? When you figure this out back up to tape those you don't need to keep on the server.
You ask: "how to manage growing data and there disk space?"
This is one we can answer: BUY MORE DISK! That was easy.
You ask: "How we can give good performance our CPU and memory?"
Do you really expect that we can with zero knowledge of your environment, your version, your application, etc. distill into a few short paragraphs the collective wisdom of Cary Millsap, Jonathan Lewis, and the rest of the Oak Table Network membership?
Of course we can not. So what you need to do is buy Cary's book, Jonathan's book, and take their classes.
You ask: "we need keep all archive log in backup files or we need to remove old archive files?"
Remove the old ones after being absolutely sure you have a good backup.
You ask: "where we can take backup tape drive,SAN,disk removable hard disk? which one is better?"
No one solution is better than the other. They are all adequate. -
Using RMAN to delete unwanted archivelog files..??
Hi All,
How can i remove the unwanted archivelog files from the disk, to manage the disk space usage, using RMAN?
My 10g database is in ARCHIVELOG mode and the OS is RHEL ES Release 3
when i tried with 'delete expired archivelog all;', i got the result as follows:
RMAN> delete expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=363 devtype=DISK
specification does not match any archive log in the recovery catalog
Please update...
Many Thanks in advance.....!!!with the delete all input, can i assume that the archivelog files has been got deleted...Don't you trust Oracle ? :-)
You should see two series of messages, like below
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=73 recid=1 stamp=599697994
input archive log thread=1 sequence=74 recid=2 stamp=599698064
input archive log thread=1 sequence=75 recid=3 stamp=599698103
input archive log thread=1 sequence=76 recid=4 stamp=599698138
input archive log thread=1 sequence=116 recid=44 stamp=600271740
input archive log thread=1 sequence=117 recid=45 stamp=600271859
input archive log thread=1 sequence=118 recid=46 stamp=600277637
channel ORA_DISK_1: starting piece 1 at 04-SEP-06
channel ORA_DISK_1: finished piece 1 at 04-SEP-06
piece handle=/home/ora102/flash_recovery_area/DB102/backupset/2006_09_04/o1_mf_annnn_TAG20060904T154722_2hrcmh13_.bkp tag=TAG20060904T154722 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:37
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_73_2h6ok83j_.arc recid=1 stamp=599697994
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_74_2h6omjb9_.arc recid=2 stamp=599698064
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_75_2h6onq39_.arc recid=3 stamp=599698103
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_76_2h6oosvn_.arc recid=4 stamp=599698138
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_116_2hr5tw8c_.arc recid=44 stamp=600271740
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_117_2hr5ym80_.arc recid=45 stamp=600271859
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_118_2hrcm58z_.arc recid=46 stamp=600277637
Finished backup at 04-SEP-06 -
Automatically removing archive logs
I'm currentyl running level 0 and level 1 backups and then removing archive logs using the following command:
backup incremental level 0 database diskratio=0 plus archivelog delete input;
I want to retain a weeks worth of archive logs on disk, I'd like to still use RMAN to manage the archive logs. Any suggestion how I would do so?
TIADon't use the DELETE INPUT and have another delete command that deletes the archivelogs once you know the backup was successful.
RMAN> delete noprompt archivelog all completed before 'sysdate - 7'; -
How do I move databases using RMAN with minimal downtime ?
How can I do the following using RMAN ?
DB version 10.2.0.4
Redhat 5.2
I am not using an rman catalogIn the past I have moved large databases from 1 server to another with 5 minutes downtime using backups done the old way by putting tablespaces in backup mode and making copies of the datafiles.
I used the following method :
========> Part 1
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE set DATABASE "VPMY" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 3
....etc
LOGFILE
......... log file names
DATAFILE
... list of datafiles
CHARACTER SET US7ASCII;
========> Part 2
Up until the scheduled downtime, I would copy the archive logs from the production server to the new and run the following to apply the latest archive logs:
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
->AUTO<-
========> Part 3
After applying the last archive log while in restrict mode -
ALTER DATABASE OPEN resetlogs;
My question is, how do I do Part 2 in RMAN. I have managed to duplicate databases and restore databases using rman to a different server, but this obviously only covers the data upto the backup point. How can I do the above parts 1 -3 with downtime of about 5 minutes like I have done using old methods ?
Any help is much appreciated/you should be able to recover as you go with rman as well..
copy the archived logs from A to B and apply them as they come in.
run
set until sequence x thread 1;
recover database;
if you're not opening the database after recovery you can just increment the set until sequence as the logs come in and do a new recovery. -
I got the above error while i restore the standby database using RMAN backu
Dear All,
RMAN> crosscheck archivelog all;
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
specification does not match any archive log in the recovery catalogi got the above error while i restore the standby database using RMAN backup from production.
Help need.i take the backup without catalog database.
regards,
DBrman> list backup;
it shows lengthier but i showed only the corresponding
BS Key Type LV Size Device Type Elapsed Time Completion Time
3479 Full 17G DISK 01:29:42 09-FEB-13
BP Key: 3479 Status: AVAILABLE Tag: 09FEB13_FULL_ESMSRV1_DB
Piece Name: /oradatabkp/rman/esmsrv1_full_db_09feb13
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3479
File LV Type Ckp SCN Ckp Time Name
1 Full 1759250260 09-FEB-13 /esmsrv1/dbs/system01.dbf
2 Full 1759250260 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3 Full 1759250260 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4 Full 1759250260 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5 Full 1759250260 09-FEB-13 /esmsrv1/dbs/example01.dbf
6 Full 1759250260 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7 Full 1759250260 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8 Full 1759250260 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9 Full 1759250260 09-FEB-13 /esmsrv1/dbs/users01.dbf
10 Full 1759250260 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23 Full 1759250260 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39 Full 1759250260 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
3480 Full 17G DISK 01:21:30 09-FEB-13
BP Key: 3480 Status: EXPIRED Tag: TAG20130209T200021
Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_full_Feb09
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3480
File LV Type Ckp SCN Ckp Time Name
1 Full 1759422265 09-FEB-13 /esmsrv1/dbs/system01.dbf
2 Full 1759422265 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3 Full 1759422265 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4 Full 1759422265 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5 Full 1759422265 09-FEB-13 /esmsrv1/dbs/example01.dbf
6 Full 1759422265 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7 Full 1759422265 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8 Full 1759422265 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9 Full 1759422265 09-FEB-13 /esmsrv1/dbs/users01.dbf
10 Full 1759422265 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23 Full 1759422265 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39 Full 1759422265 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
3481 Full 4M DISK 00:00:03 09-FEB-13
BP Key: 3481 Status: AVAILABLE Tag: TAG20130209T212205
Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_controlfile_copy_Feb09
Controlfile Included: Ckp SCN: 1759462488 Ckp time: 09-FEB-13
BS Key Type LV Size Device Type Elapsed Time Completion Time
3482 Full 0 DISK 00:00:01 09-FEB-13
BP Key: 3482 Status: AVAILABLE Tag: TAG20130209T212212
Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_spfile_copy_Feb09
SPFILE Included: Modification time: 08-FEB-13
ls -l /oradatabkp
root@drsrv1#ls -l /oradatabkp
total 1108672
drwxr-xr-x 2 ovsd dba 96 Sep 27 2009 alert_bkp
-rw-r--r-- 1 oracle dba 195 Mar 15 2007 create.sql
drwxr-xr-x 2 oracle dba 8192 Aug 7 2009 ctrl_bkp
-rw-r--r-- 1 root sys 565114880 Apr 24 2007 drsrv1.tar
drwxrwxrwx 2 root sys 96 Jun 17 2011 drsrv2-ignitebkp
drwxr-xr-x 4 root sys 96 Apr 24 2007 esmsrv1
-rw-r----- 1 root sys 1613824 Feb 22 2007 esmsrv1stby.ctl
-rw-r--r-- 1 esmsrv1 dba 5120 Dec 31 2009 esmtables.dmp
-rw-r--r-- 1 esmsrv1 dba 538 Dec 31 2009 esmtables.log
drwxrwxrwx 4 root sys 8192 Mar 10 2009 export
drwxr-xr-x 8 root sys 8192 Apr 24 2007 finalbackup
-rw-r--r-- 1 oracle dba 3820 Sep 5 2008 invalid.sql
-rw-r--r-- 1 esmsrv1 dba 303104 Dec 31 2009 kirdevports.dmp
-rw-r--r-- 1 esmsrv1 dba 591 Dec 31 2009 kirdevports.log
drwxr-xr-x 2 root root 96 Feb 12 2007 lost+found
-rw-r--r-- 1 oracle dba 24954 Aug 9 2009 ovcontrol-090909.ctl
drwxr-xr-x 22 root sys 8192 Apr 24 2007 ovpi
drwxr-xr-x 2 oracle dba 8192 Aug 7 2009 pfile_bkp
drwxrw-rw- 4 oracle dba 8192 Feb 10 15:25 rman
drwxr-xr-x 28 root sys 8192 Feb 1 17:15 schedbkp
drwxr-xr-x 2 oracle dba 8192 Jul 11 2011 sdnnm
-rw-r--r-- 1 esmsrv1 dba 2196 Dec 31 2009 srirdevports.log
drwxr-xr-x 2 oracle dba 96 Mar 13 2009 statsreport
-rw-r--r-- 1 oracle dba 966 Mar 15 2007 tbs.sql
drwxr-xr-x 5 oracle dba 96 Mar 16 2007 testov
drwxr-xr-x 2 root sys 442368 Mar 11 2009 trendadm_files
root@drsrv1#ls -l /oradatabkp/rman
total 37244448
drwxr-xr-x 2 oracle dba 8192 Feb 10 15:25 esmsrv1
-rw-r----- 1 oracle dba 19068198912 Feb 9 14:21 esmsrv1_full_db_09feb13
drwxrw-rw- 2 oracle dba 8192 Feb 9 21:36 openview
-rw-r--r-- 1 oracle dba 920442 Feb 9 21:37 rmanbkp-all.log -
Problem in performing multiple Point-In-Time Database Recovery using RMAN
Hello Experts,
I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
Environment:
Oracle 11g, ASM,
Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
Snapshot DiskGroups :
Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
Steps performed for point in time recovery:
1. Restore control file from snapshot 2.
RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
3. Catalog data files from snapshot 1.
4. Catalog archive logs from snapshot 2.
5. Perform point in time recovery till given time.
STARTUP MOUNT;
RUN {
SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
SET UNTIL TIME "06-mar-2013 09:30:00";
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
Results:
Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
Starting recover at 28-FEB-13
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/06/2013 11:10:57
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until time 'MAR 06 2013 09:45:00'
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
Doubts:
1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
However for this to work, I always need to keep the AutoBackup feature enabled.
How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
Please help me out in this issue.
Thanks.992748 wrote:
Hello experts,
I'm little newbie to RMAN recovery. Please help me in these doubts:
1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.
Maybe you are looking for
-
I need to consolidate two iTunes libraries from different countries.
I have been struggling for approximately 5 years now to resolve an issue which it seems is normal for those Apple users who move countries from time to time. Specifically, I have ended up (inadvertantly in the first instance) with two distinct iTune
-
My bill cycle date is 2-28-15. Will my new cycle reset on the morning of that day or do I need to continue to stretch my data through the close of that day?
-
?!?! See who can figure this one out first...
ok, so this has been happening on and off for the past 3 months, just curious if anyone else has had this happen as well. so im working in Logic (this happened in 7 and now 8 as well) and i get done with my session and im going to close logic for a b
-
Creating context-sensitive HTML Help without using Map #s
I am uisng RH 8 and am producing a compiled HTML Help file. I am wondering if there is another way to call a topic from our application without using the MAP numbers in RH. The developer would like to use the MAP ID (string) instead. Is there a way t
-
At present hearing them using my headphone are too loud for my ear.