How to Increase my retention period using RMAN

I believe 7 days of backup is enough for me in case of emergency.
Can I do this?
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
For now, it is:
RMAN> show all
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
.

Similar Messages

How to change the retention period of os watcher log,

How to change the retention period of os watcher log, by default it is 7 days. but in our exadata env. automatically oswatcher logs are deleted , so i want to check the retention period.
Regards,
Ani

Hi Ani,
Go to :- /opt/oracle.cellos/validations/init.d/oswatcher
Open the file "oswatcher" file.check for the line "/startOSW.sh X Y Z". Where X is the snapshot interval
make the change and you are done
Regards,
Sunil Bhola

How Can I Change Posting Periods using DI

Hello All,
How Can I Change Posting Periopds using DI.
When Connecting to B1 Company DB , I would like to change default Posting Periods.
My SBO is 2005B.PL41.
Best Regards,
TAK

Hi,
Please take a look at the CompanyService Object in the DI help file. and check for the UpdateFinancePeriod method.
Hope it helps,
Vasu Natari.

How to increase the time period in Debugger

Hi,
If we put Debugging screen Idle for some time,we will get timed out Status bar message.Can we increase that time period.

hi,
A work process which is processing your task is set into a DEBUG mode.
Debugging in general does requesting a huge memory consumption and system resources as well.
This means that system is moving data to its extended memory in PRIV mode.
In this mode normal request being processed by other work processes are located in local memory instead of extended. Extended memory is occupied by data for debugging user exclusively. However this cannot persist in system for a long time. So since you are not active in debugging session for some time system is canceling whole debugging with following messages:
1) Transaction from "PRIV" session reset after timeout (Message no. 14048)
2) Transaction from "DEBUG" mode (after timeout) reset (Message no. 14056)
From basis point of view for production system there should not be a necessity to adjust profile parameters in order to allow debugging for a long time and for a so much users. If you wish to avoid this message anyway or you want to make debugging more comfortable on development or test system you need to consider following profile parameters:
1)rdisp/max_priv_time # Standard value: 600
2)rdisp/wppriv_max_no # Standard value: MAX(1, Anzahl Dialog-WPs)
3)rdisp/max_debug_lazy_time # Standard value: 600
thanks and regards
chinnaiya

How to increase limit of users using portal/SSO

Hello,
I am expending number of users using a portal forms application and recently started to get this error
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
The error appears only for the pages that require SSO, no problem for the public pages. Can something be done to increase the limits for SSO connections?
Thanks.

Hi, can you review this link:
http://www.oracle.com/technology/products/forms/pdf/10g/forms904capacityplanning.pdf
Good Luck...

Backup Database using MSSQL Studio with Retention Period

Hi Experts,
I Want to run backup every first Monday of the month and only keep 2 copies, which means after third month successful backup first month should be deleted.
I know how to schedule the backup for first monday of every month.
My only query is how do we set retention period and how do we define fine name.
Thanks & Regards,
Ak

Hi AKCH,
Based on my understanding, you already know how to schedule the backup job for first Monday of every month. Now you want to set retention period of copies and make sure there are always two copies exist. And you also want to know how to define backup filename
better.
About how to set retention period of copies, you can follow these steps:
1. Open SQL Server Management Studio and expand Maintenance Plans under Management.
2. Right click the plan you have scheduled and choose Maintenance Plans Wizard.
3. Set step by step according to tips.
4. On Select Maintenance Tasks page, you should check Maintenance Cleanup Task.
5. On Define Maintenance Cleanup Task page, you should check Backup files under Delete files of the following type. And check Search folder and delete files based on an extension box under File location, then select the backup folder. Under File age, please
check Delete files based on an extension and set 2 Month(s) under Delete files than the following.
Based on my test, when I use maintenance plan to perform backup for DB, the backup filename is DB_backup_2014_08_27_142154_5382644.bak.
Best regards,
Qiuyun Yu

Increase retention period of Audit logs.

Friends,
We have the requirement from the Auditors to increase the retention period of logs from
3 months to 6 months.
Can someone please guide me on this one? Thanks and let me know.
Do I need to change any parameter in SAP to increase the size of Audit file @ OS level?
Any help or suggestions is helpful.
Regards,
Pranav

Lets return to the original question...
>
Pranav Thaker wrote:
> We have the requirement from the Auditors to increase the retention period of logs from
> 3 months to 6 months.
>
> Can someone please guide me on this one? Thanks and let me know.
> Do I need to change any parameter in SAP to increase the size of Audit file @ OS level?
>
> Any help or suggestions is helpful.
>
The management of daily files seems not to be the problem here, although it is relevant for the number of files created and their size... for storing them on external media for safekeeping (incase some auditor wants to read the file as well, or you do to reconstruct an event).
The possibility exists to delete the audit log files after 3 days. At the application layer, this is blocked for the 1st three days (as a security measure).
Most likely you only need to speak to your basis folks to ensure that there is enough space on the file system for the logs, and reschedule the job which is deleting the files to do so for files older than 6 months (instead of 3).
Now-a-days, 100 MB is not a lot of space and does not cost much. 600 MB will fit on a "vanialla" CD which costs less than 1 Euro. You can also copy then to an external medium before deleting them.
FYI: Reading the logs are a major pain, and I doubt that the auditors actually do this... but there are some usefull techniques you can use to send alerts when certain audit log messages appear (to solve the needle in a haystack problem) or read them all remotely and then use the same to drill down and analyze patterns. But you first need to know what the "alerts" are and which "patterns" to look for in the data you will be collecting. If you are only logging "unsuccesfull transaction start" and stuff like that, then you might as well turn it off again (even if it does keep the auditors happy).
Hope that helps a bit more,
Julius

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.

Using RMAN, how do you restore from an old backup file?

HI,
I use Oracle 9i on Solaris.
I'm currently doing incremental level 0 hot backups every night using RMAN in NOCATALOG mode. The controlfile is backed up with the database. I back it up to a file (e.g. "level0_20041225.dmp"). After I back it up, it's backed up to tape using Veritas. Before doing a backup, I delete the old one first.
I need to restore a copy of the database backup that was taken a month ago. This file is on tape. How do I go about it using RMAN? The documentation is not too clear as it talks more about Restoring the control file and the latest copy of the database.
How do you restore an old copy of the database from a database file?
Pls advise
Thanks

You can recover to the last committed transaction,
provided you have the current controlfile, archived
logs since the backup and the current online logs.
Here's the procedure in a nutshell:
a) Restore datafiles from tape.
b) Recover database using restored files + current
controlfiles and archived/online logs. RMAN will prompt
you for the logs it needs for recovery.
You can also perform this type of recovery using a
backup controlfile. In this case you would still need
all logs as above. After recovery, you would have to
open the database with RESETLOGS because you are using
a backup controlfile.
If you don't want/need to recover up to the last
committed transaction, you use a backup controlfile and
perform incomplete recovery (time or change based). This
simply means that you stop the application of redo at
the time or SCN of your choice.
Most of the scenarios of interest are documented in
the following book:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/toc.htm
Hope this helps.
Kailash.

Cloning a database using rman where source's dbid changed..

Any idea on how to .. cloning a database using rman where source's dbid changed..

if you need to change dbid of target then use DUPLICATE command, see the below links.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1008888
http://www.oracle-base.com/articles/9i/DuplicateDatabaseUsingRMAN9i.php

Database Recover Using RMAN

Dear All(s)
Recently i am managing oracle 10.2.0 database, and doing database coloning and data dumping. Also doing full backup trrough RMAN. Now i want to know what happend if i take only RMAN backup, full and incremental, and how recover it.
1. How i can recover database if i loose entire server machine (in case i have only RMAN backup)
2. How i can build full database using RMAN backup on another server.
Thanks
Waiting for response
Edited by: Naeem Sheeraz on Dec 5, 2008 11:47 AM

+1. How i can recover database if i loose entire server machine (in case i have only RMAN backup)+
If you loose entire server machine its just like the same you make disaster recovery or restore database to another machine.
+2. How i can build full database using RMAN backup on another server.+
10g rman
Khurram

Recover Block level corruption without using Rman

Dear All,
OS - OEL
DB - Oracle 10G
ORA-01578: ORACLE data block corrupted (file # 11, block # 16325)
ORA-01110: data file 11: '/oracle/PROD/fin_dev/data/fin08.dbf'
How we will recover it without using Rman?

If you are not using RMAN, you are using scripted backups. You take the datafile (or tablespace) offline, restore the backup of the datafile and recover the datafile using the SQLPlus commands.
Hemant K Chitale

How to backup Oracle Database Single Instance using RMAN

Folks,
Hello. I am using Oracle Database Server 11gR1 with Operating System Oracle Linux 5.10.
I understand how to backup database instance in SQL Server with Windows. But don't really understand how to backup database instance in Oracle with Linux.
I have done Cold backup and Hot backup for the database instance HRCS90 but both get the same error message.
Cold backup is below:
SQL> startup
ORACLE instance started.
Total System Global Area 538677248 bytes
Fixed Size                  2146024 bytes
Variable Size             528482584 bytes
Database Buffers            4194304 bytes
Redo Buffers                3854336 bytes
Database mounted.
Database opened.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
RMAN> backup database;
Starting backup at 25-NOV-13
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/25/2013 14:26:52
RMAN-06171: not connected to target database
RMAN> backup HRCS90
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, as, backup, backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, database, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, force, file, incremental, keep, (, maxsetsize, nochecksum, noexclude, nokeep, not, proxy, pool, reuse, recovery, section, skip, spfile, skip readonly, setsize, tablespace, tag, to, validate"
RMAN-01008: the bad identifier was: HRCS90
RMAN-01007: at line 1 column 8 file: standard input
RMAN> backup database HRCS90
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, backup, backupset, channel, copy, controlfilecopy, current, database, datafile, datafilecopy, delete, diskratio, db_recovery_file_dest, filesperset, format, from, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, plus, reuse, recovery, section, ;, skip, spfile, skip readonly, setsize, tablespace, tag, to"
RMAN-01008: the bad identifier was: HRCS90
RMAN-01007: at line 1 column 17 file: standard input
While the database instance HRCS90 is startup, I do hot backup using the same commands and get the same error message with above cold backup.
My question is:
Can any folk tell me the specific steps (command by command) to backup a single database instance in Oracle using RMAN ?
Thanks.

Folks,
Hello. Thanks a lot for replying. My database instance named HRCS90 is going to be backed up. My backup directory is /backup_Database_Instance_HRCS90.
If database in open state, we must back up in archive log. If database in mount state but not open, we can back up in noarchive log.
I have tried to back up HRCS90 in archive and noarchive log when database in mount state but not open as below:
SQL>startup mount;
SQL>exit
[user@linux bin]$./rman
RMAN>connect target;
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup as backupset database plus archivelog;
Starting backup at 01-DEC-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=44 device type=DISK
specification does not match any archived log in the recovery catalog
backup cancelled because all files were skipped
Finished backup at 01-DEC-13
Starting backup at 01-DEC-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
channel ORA_DISK_1: starting piece 1 at 01-DEC-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/01/2013 17:52:45
ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 13: Permission denied
RMAN>
RMAN>
RMAN>
RMAN>
RMAN> backup as backupset database;
Starting backup at 01-DEC-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
channel ORA_DISK_1: starting piece 1 at 01-DEC-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/01/2013 17:56:51
ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 13: Permission denied
As we see the above last 2 commands, either archive or noarchive, I get the same error:
Archive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
Noarchive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
My question is:
What is the file "full_0boqei2c_11_1" or "full_0coqeia5_12_1" ? How to solve the above error ?
Thanks.

How can I assign a period (instead of B) in Keynote for blank screen so I can use a Logitech R800 presenter? An option in next version?

I have recently bought a Logitech R800 presenter which works very well with Keynote on a MacBook Pro. The start/stop presentation key does not work but that can be easily fixed by assigning F5 to "Start presentation" for Keynote in the keyboard system preferences. The remaining issue is that the blank screen button sends a period (".") which works as a prompt for a blank screen in PowerPoint, but in Keynote it causes the slideshow to end. Keynote uses the letter "B" for blank screen.
How can I assign a period (instead of B) in Keynote for blank screen? Some sort of work around would be very useful as I often use blank screen in my presentations and much prefer Keynote to PowerPoint.
Perhaps it will be an option in next version of Keynote?
Thanks

As far as I know you can not change these keystrokes without changing the Program files. I am sure it is possible there, but I have no idea where to even start to tell you where to find it.
Your best bet it to go to the Keynote Menu>Provide Keynote Feedback and let Apple know you would like the option to change them.

How to restore a table using RMAN with previous backup ?

Hi everyone,
we have to restore a table from 1 week previous backup using RMAN.
Could you show me how to restore a table using RMAN with previous full backup.
please Help me out.
Thanks
Info > oracle 10g, OS: AIX5L

Hi,
first of all you must have all the archivelogs since you want to recover your table from the previous backups.
anyways if you want to recover your table then you need to perform incomplete recovery to the point where you loss the table for that you need to restore and recover your database.you likely to loose all the transcation which occurs to the point where you you loose your table.
thanks..

How to Increase my retention period using RMAN

Similar Messages

Maybe you are looking for