Re: RMAN - Failed due ti could not find file.

From: <timkarnold_at_comcast.net>
Date: Sun, 01 Sep 2002 03:08:17 GMT
Message-ID: <Bwfc9.332669$2p2.14079232@bin4.nnrp.aus1.giganews.com>

<SUSOTT_at_amnutrition.com> wrote in message news:fgRb9.2127$K%2.408374_at_newsfeed.slurp.net...
> I have Oracle 8i instance running on Win2k(pc name oraprod).
> I have the OEM installed in another instance (8i) on a seperate Win2k
> (pc name anioracle01). I am running the console from a laptop.
>
> I can create and schedule a backup for the instance on oraprod.
> As soon as it starts executing, I am receiving in the job output
> Failed with the job output detail window showing "Could not find
> C:\winnt\temp\2072150336.9"
> No other messages are present that I have been able to locate.
> When I check on the pc (oraprod), I find the file in the specified
> directory.
> The user I am using for backups is Admin equilivant with log on as a batch
> rights on both pcs (And can read/write to the directory).
>
> Could someone tell me what I am missing or where to look for probable
> causes?
>
>

Is C shared?

If not, try the following steps:

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

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.
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'.
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'.
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.)
Go to the Control Panel and then open up the Services panel.
Double click on the appropriate service (TNSListener or OracleService<SID>).
Change the "Log on as" user from the "Local System Account" to "This Account".
Specify the service to log on as the Administrator user.
Click on "OK".
Shutdown the TARGET database and stop and start the services on the Target machine. Restart the TARGET database.
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<SID> and the OracleTNSListener services use.

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 1(<path and file name of Datafile 1>) 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

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>"

Received on Sat Aug 31 2002 - 22:08:17 CDT