[Link]
_afrLoop=400805162584281&parent=DOCUMENT&sourceId=
2160858.1&id=145843.1&_afrWindowMode=0&_adf.ctrl-state=d71q9r2zj_311
How to Configure RMAN to Write to Shared Drives on Windows NT/2000/2003 (Doc ID
145843.1)
To
Bott
om
APPLIES TO:
Oracle Database - Enterprise Edition - Version [Link] and later
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
***Checked for relevance on 20-July-2015***
PURPOSE
Following are step-by-step instructions for configuring RMAN to write to mapped (shared/networked) drive(s)
on Windows platforms
SCOPE
RMAN users who are familiar with basic RMAN functionality as well as database configuration on the
Windows Platform.
DETAILS
WRITING FILES TO A MAPPED DRIVE WITH RMAN
---------------------------------------------------------------------------The problem of backing up to a mapped network drive using the SYSTEM account is a security issue.
By default, Oracle requires the SYSTEM user to have privileges to write to the drives.
Microsoft considers granting SYSTEM owned service access to a shared drive 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.
The SYSTEM account should not be granted access to the shared drive, therefore the Oracle services
for the TARGET DB need to be reconfigured to logon using an Administrator account
(preferably a Domain Administrator).
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.
In the example here, the password would be 'test'.
3. Map a network drive on the TARGET machine to the shared drive on the destination machine.
When mapping this drive, use the Administrator user with the password 'test'.
4. On the TARGET machine, BOTH the OracleTNSListener Service and the OracleService<SID> services
must be configured to start using the Administrator/test account.
(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 machine.
Restart the TARGET database.
6. You should now be able to use RMAN from the Catalog machine to copy the datafiles.
In the RMAN script, specify the drive letter that you mapped in step 3.
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 (not drive letter) directly, e.g. backup to \\B\share
Since this is in fact an absolute location this is always the same for any node in the network.
So whether accessed from node A or node B, \\B\share is always the shared 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 local Administrator account and ensure that
the passwords are the same for this account across all of the machines.
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 OracleService<SID> and the OracleTNSListener services use.
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 the shared drives at system startup.
The batch file runs automatically as a service when the server starts and would establish the connection
to the shared drives, regardless of which user logs into the system.
This process of creating the batch file is outlined in the Microsoft's Knowledgebase
Article ID: 243486 - "How to Run a Batch File Before Logging on to Your Computer."
The batch file is not supported by Oracle and is only mentioned here as an alternative way to reconnect
the shared drives.
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 TARGET machine, 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
