Rman restore script windows

When the RMAN backup was taken, if a tag was specified, you can also restore controlfile based a tag name as shown below. Apart from the above straight forward restore database, there are also few variations of this command which are explained in the examples below. Use the one that is appropriate for your situation.

In the last step, recover the database, and then you should open the database with resetlogs options as show below:.

Instead of restoring the full database, you can also restore only specific tablespace as shown below. You can also restore more than one tablespace by separating them with commas as shown below. This will restore both dev1 and dev2 tablespace. You can also restore only a specific datafile from the backup using the restore datafile command as shown below.

You can also restore more than one datafile by separating them with commas as shown below. The following will restore only specific sequence number of the archive logs that are between and You can also restore archivelogs by specifying the starting point of the SCN number as shown below. Please note that when you issue the recover database as mentioned in the step 3 above, it will look for all required archive logs from the archive log destination and applies them to the oracle database datafiles.

Similar to restoring specific tablespace and datafile, depending on the restore operation you did, perform the corresponding recover option. The following are few examples:. For example:. Please note that the preview output will be similar to the rman list summary command output.

This will only provide the report. You can use this before you restore the database. The following are also valid preview option. Then, you need to verify that the client resource and Default group resource are both configured correctly. For information about accessing the client resource, see "Client Resource".

In the client resource, be sure that the Group attribute is set to Default. Finally, check the Default group resource configuration. To open the Groups window, perform the following steps:. Click the Configure tab in the Server window of the main Administrator window to make it active. Click Manage Groups to open the Groups window. The Groups window lists the single group resource named Default.

On Windows, the Groups window does not automatically show the attribute settings of the group resource, so you must perform the following additional steps to see the group's attributes:. In the Edit Group dialog box, the General default tab shows the attributes of the Default group resource.

Click Field Help to learn more about each attribute. The Edit Group dialog box on Windows lists all the attributes of the group resource, as shown in Figure The Start time attribute specifies when the bootstrap backup is configured to begin a. To have the bootstrap information sent to a specific printer, set the Printer attribute to the name of that printer.

Note: Be sure that the Autostart attribute is set to Enabled to enable the automatic bootstrap backup. If Autostart is set to Disabled, the bootstrap backup does not run. If you want to manually run the bootstrap backup on a Windows system, you must be logged in as Administrator.

Then, enter this savegrp command at the system prompt:. Note : Be sure to have a writable media device available before you start a manual bootstrap backup. If you attempt to run the savegrp command for a manual bootstrap backup without an available device, the backup will fail. In that case, you must provide the writable media device and then rerun the savegrp command, to restart the manual bootstrap backup.

At the end of the automatic daily bootstrap backup, LSM prints the bootstrap information to the printer specified in the Printer attribute of the Default group resource; or, if that Printer attribute is blank, to the default printer. At the end of a manual bootstrap backup run with the savegrp command, as described in the previous section, "Manual Bootstrap Backup" , the bootstrap information is sent to the printer specified in that savegrp command.

Be sure to store the bootstrap printout in a safe place. The printed bootstrap information includes dates, locations, and save set ID numbers for the bootstrap save sets backed up during the past month. With this information, you can determine which volumes are needed to recover the LSM Server indexes and resource database files during a disaster recovery. You can view progress messages that appear during the backup or restore and completion messages that advise when the backup or restore is complete.

You can also view the messages in specific online system files. For information about why a backup cannot progress, view the messages in the Pending display. The Pending display shows requests to mount tapes and other conditions that require operator intervention.

See "Volume Operations" for examples of the messages that LSM displays when requesting a volume for Oracle backup or restore. Give a try with less or more number of channels incase if you want to learn what happens :. Before doing anything else, we need to insure that the Archive logging is disabled for the newly restored database.

Rush to the previous SQLPlus session that you started with nomount. This session is already disconnected, hence reconnect and shutdown immediate. Hope this helps few Oracle database beginners out there. As we have restored full database with archive logs, there is no need to restore logs.

Cross verify the database details. This site uses Akismet to reduce spam. Learn how your comment data is processed. Skip to content. Now, we will create another cmd file that will call the above script.

So let us start. Give a try with less or more number of channels incase if you want to learn what happens : Execute the above script from the RMAN prompt. Now start the database in mount state and disable the archive logging. Shutdown the database and restart normally.