Re: Problem with backup using RMAN breaking Procedure utilitizing fopen() - 9i HELP!

Hi Ted,

Thanks for the response. But...

How to rebuild this SPFILE so that changes in the init<sid>.ora file ARE reflected in it?

Is there a way to tell Oracle not to use the SPFILE, but rather to re-read the configuration files on startup?

Thanks,
Mike

On Wed, 14 Nov 2001 00:58:34 GMT, "Ted McCabe" <theom_at_gte.net> wrote:
>Michael:
> The NT registry points to the init<sid>.ora file used during startup of
>NT. Your installation may have created an SPFILE in the database directory.
>If your restart just does 'startup' you use the SPFILE. Changes to the
>init<sid>.ora file are not automagically reflected in the SPFILE.
>
>HTH
>tED
>"Michael Kers" <m.k_at_mailandnews.com> wrote in message
>news:3bf165da.325295990_at_news.easynews.com...
>> Hello,
>>
>> I have a server running 9.0.1.1.1 (9i) on Windows 2000 Server. I have
>> a Predefined backup (default) running on my database every 24 hours.
>> The backup itself succeeds, and the database appears to restart
>> normally. Read and writing to the database is fine before and after.
>>
>> There is a procedure that runs occasionally on the same server that
>> accesses the database that is backed up. This procedure uses
>> utl_file.fopen() to create a new file and writes some data to it.
>>
>> Before the backup being run (after say a machine restart) the
>> procedure will run fine repeatedly. After a backup the procedure will
>> fail on the fopen().
>>
>> init.ora is set correctly, path statement is fine (remember everything
>> runs great before backup).
>>
>> Why would this thing just quit working after a backup? Is something
>> not restarting (NT Oracle service?) or is oracle loading the wrong
>> init.ora file?
>>
>> Thanks in advance for any help / insights
>> Mike
>
>
Received on Thu Nov 15 2001 - 11:38:08 CST