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

Yes.

I managed to fix it by following Ted's suggestions that the changes are not reflected. What you suggest here would work to.

What I did:

Openned up Oracle Enterprise Manager, opened the offending database, and under [database]->Instance->Stored Configurations->default stored config I modified the startup options to reflect the required utl_file_dir value that I needed.

The databased wanted to restart afterwards, so I let it. I tried the backup that broke the procedure before... And voila, this time it worked.

Thanks for the help guys,
mike

>Any changes you make to the init.ora can be forced to be applied to an
>SPFILE by issuing the command 'create spfile from pfile'. You can also do
>it the other way around. For that command to work, though, you must *not*
>have started up with the file you are attempting to create. In other words,
>you startup specifying the pfile you wish to use, *then* you can create an
>spfile that is functionally identical. Another plain 'startup' (without a
>'pfile=' paramter) will then use the new spfile.
>
>The other thing you can do, though, is issue 'alter system' commands,
>specifying at the end the new parameter "scope=spfile". That writes changes
>directly to the spfile. The default is to change both the current Instance
>setting (if that's actually possible and also to change the spfile) -in
>other words, the default is "scope=both".
>
>For example, alter system set log_archive_dest=C:\here scope=spfile;
>Or: alter system set log_archive_start=true scope=spfile;
>and so on.
>
>If you don't want to use an spfile, just delete it. Oracle then has to use
>the old-fashioned init.ora. If you issue the startup command with a pfile
>parameter, then Oracle uses the pfile even if there's an Spfile.
>
>Regards
>HJR
>--
>Resources for Oracle: http://www.hjrdba.com
>===============================
>
>
>"Michael Kers" <m.k_at_mailandnews.com> wrote in message
>news:3bf3fd27.86833610_at_news.easynews.com...
>> 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 - 16:59:04 CST