https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&...

How to Configure RMAN to Write to Shared Drives on Windows NT/2000/2003 [ID 145843.1] Modified 29-JUN-2011 Type BULLETIN Status PUBLISHED

Applies to:
Oracle Server - Standard Edition Oracle Server - Personal Edition Oracle Server - Enterprise Edition - Version: 9.0.1.0 and later Microsoft Windows (32-bit) Microsoft Windows x64 (64-bit) - OS Version: 7 Microsoft Windows x64 (64-bit) - Version: 2008 R2 Microsoft Windows (32-bit) - OS Version: 7 Microsoft Windows x64 (64-bit) Microsoft Windows Itanium (64-bit) z*OBSOLETE: Microsoft Windows 2000

[Release: 9.0.1 and later]

Purpose
Following are step-by-step instructions for configuring RMAN to write to mapped (shared/networked) drive(s) on Windows platfoms

Scope and Application

RMAN users who are familiar with basic RMAN functionality as well as database configuration on the Windows Platform.

How to Configure RMAN to Write to Shared Drives on Windows NT/2000/2003

Rate FILES TO WRITINGthis documentA MAPPED DRIVE WITH RMAN ---------------------------------------------------------------------------The problem of backing up to a mapped network drive using the SYSTEM account is a security issue. However, there is a workaround that allows Oracle to access a shared drive. The Oracle services are originally configured to log on using the SYSTEM account.

By default, Oracle requires the SYSTEM user to have privi

The SYSTEM account should not be granted access to the shared drive, ther

THE STEPS NEEDED TO RESOLVE THIS ISSUE ---------------------------------------------------------------------------1. On the machine where you wish to write the files to, create a shared drive granting the user 'Administrator' FULL Control. Note: For reference below, this Administrator will use the password 'test', this will be referred to as the "Destination" machine. 2. On the machine with the TARGET DB, verify the Administrator user has the same password of the user that shared the drive on the destination machine. 3. Map a network drive on the TARGET machine to the shared drive on the destination machine. When mapping this drive, use the Administrator

In

user with t

4. On the TARGET machine, BOTH the OracleTNSListener Service and the OracleService<SID> services must be configured to start using the (As discussed above, Oracle uses the Local System account by default.) a. Go to the Control Panel and then open up the Services panel. b. Double click on the appropriate service (TNSListener or OracleService<SID>). c. Change the "Log on as" user from the "Local System Account" to "This Account". d. Specify the service to log on as the Administrator user. c. Click on "OK". 5. Shutdown the TARGET database and stop and start the services on the Target 6. You should now be able to use RMAN from the Catalog machine to copy the Special Windows 2003/2008/XP/7/Vista Update : As Windows has a changed access behavior, the solution is a little restrict : Don't use local drive letters for mapping network shares. Workaround is to use UNC locations directly, e.g. backup to \\B\share Since this is in fact an absolute location this is always the same for any So whether accessed from node A or node B, \\B\share is always the shared machine. Restart the TARGET database.

Administrator/test

datafiles.

In the RMAN script, specify the drive letter that you mapped

in s

node in the network. location on B.

FINAL NOTES ---------------------------------------------------------------------------It is recommended to use the Domain Administrator account to ensure that passwords are the same across the various machines.

If there is no domain, use the

If your backups are to be automated using the AT command, it is best to start up the SCHEDULE service under the same Administrator account that the OracleSe In the event that you HAVE to use a user account for the Oracle Services, rather then using the SYSTEM account, you can create a batch file that reconnects

COMMON MISTAKES ---------------------------------------------------------------------------If the OracleService<SID> and OracleTNSListener services are not configured to use the same account as the shared drive, you can expect the following errors RMAN-10035: exception raised in RPC: ORA-19504: failed to create file <file name> ORA-27040: skgfrcre: create error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 5) Access is denied. ORA-19600: input file is datafile <path and file name of Datafile> ORA-19601: output file is datafile-copy <path and file name of file> to be created RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.COPYDATAFILE If the mapped drive is created on the CATALOG machine and NOT on the TARGETmachine, you can expect the following errors. RMAN-10035: exception raised in RPC: ORA-19504: failed to create file <file name> ORA-27040: skgfrcre: create error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 3) The system cannot find the path specified. ORA-19600: input file is datafile 1 <path and file name of Datafile > ORA-19601: output file is datafile-copy 0 < path and file name of file> to be created RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.COPYDATAFILE

Related

1 di 2

29/03/2012 12:47

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&...

Products

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Standard Edition

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Personal Edition

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition

Keywords

DATABASE RECOVERY Errors

ORA-19600; ORA-27040; ORA-19504; ORA-19601; ORA-19624; RMAN-10035; RMAN-10031

Back to top Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

2 di 2

29/03/2012 12:47