-
I don't know how to sort out this problem.
The best way to use tape for keeping backup.
Other way you may copy your backup file using O/S command to another host. But don't forget that RMAN saves the ways to backup file in the Rec.Cat. and it will not be able to find them automaticaly. You have to catalog them.
Best wishes!
Originally posted by Diggers12
Do you know anywhere i can check this out, do you know if other versions of Oracle work? If this is the case how do I backup to a different machine?
-
OK.
Thanks,
p.s. do you never sleep
-
Here is the Answer KGB
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 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).
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.
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 and the OracleTNSListener services use.
COMMON MISTAKES
----------------------------------------------------------------------------
If the OracleService 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
""
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 1(
1>)
ORA-19601: output file is datafile-copy 0(
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
""
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 (
1>)
ORA-19601: output file is datafile-copy 0 (
file to
be created>)
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.COPYDATAFILE
-
Thanks,
I do sleep by Greenwich time. ;-)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|