New answers tagged

0

I confirm that a full or incremental backup during business hours can make your database inaccessible to end users and web services. Factors that can make things worse: allocating too many channels to RMAN using an out of support version like Oracle 10 having a database that is CPU or memory or network IO bound running Dataguard at the same time ...


3

That depends on your disk subsystem. A full backup is going to involve a metric crud-load of I/O (that is a technical term). That is going to put a huge load on your I/O subsystem. Depending on how I/O bound your system is, how much spare bandwidth your I/O subsystem has, how fast your I/O subsystem is, etc. the impact will range from "yeah, maybe it's a ...


2

That is the typical error message you get on Windows without properly setting up the environment. While the steps in the manual may work flawlessly on Linux/UNIX, on Windows you need extra steps. On Windows, you need to create a service with oradim, start it (if it was not started), and after that you can use sqlplus / as sysdba. The bare minimum is: set ...


1

In order to do a clone, you need to connect to the target database which is the database that you are cloning from. In this case you are doing a restore. So there is no auxiliary database. Just do a startup nomount, provided that you have a pfile with the proper settings. Then restore a specific control file as in "restore control file from ...


0

Could you please tell us how you connected to rman? For example: rman target sys/asdf@prod auxiliary sys/asdf@dev The reason for you problem is that the two databases have trouble communicating with each other. If you use auxiliary / because your rman session is located on the dev server this is not going to work. The reason is pretty simple as follows. ...


3

I write a bash script to perform the backups (RMAN, datapump and also xtrabackup and dump for MySQL in a similar way) and then call that from cron. That way you can handle the email as you want. So a simple crontab line is like this 00 18 * * 0-6 /dba/bin/rman.sh > /tmp/dba_rman_SID.log 2>&1 Then everything is done in the script. So define ...


2

Kris Johnston said in a comment: nomount/mount/open are the states of the database... something can't connect to the db one way and connect as nomount, and connect to the same db a different way and connect as mount or open. It doesn't work like that. It sounds like you are connecting to a different database altogether. To check, verify the dbid's are ...


0

To connect to RMAN from the operating system command line and hide authentication information, you must first start RMAN and then perform either of the following actions: Run the CONNECT commands at the RMAN prompt. ... Run a command file at the RMAN prompt that contains the connection information.


0

It sounds like you need to set up a recovery catalog in a central database, which you can read up on how to set up a Recovery Catalog and maintain it from the Oracle Database 12c Docs. Once you have the recovery catalog, then dropped database backup records are still maintained with their respective retention policies: Connect to the recovery catalog: ...



Top 50 recent answers are included