Re: Help with backup control file to trace

You're not gonna like this.... but it is impossible for the command simply not to work.

So: how do you *know* that it doesn't work? Do you open the trace files in the directory and just read the first X lines? See nothing that looks like a 'create controlfile' file, and give up?

The reason I ask is that all such trace files include the Session Identifier (or PID, or something like that anyway) as part of their filename -the point being that you only get one such number per session, and hence ALL trace files in a session are appended to the same file. So, if you do a SQL_TRACE=TRUE for a session, and *then* do a backup to trace, your file won't "appear" -the 'create controlfile' commands will be stuck on the end of your SQL trace file. You'll have to do a mammoth page down before you find the relevant commands.

Have a GOOD look before you declare the thing simply doesn't work. I guarantee it will be there somewhere.

Regards
HJR "Andrew Au" <andrewa1_at_home.com> wrote in message news:UP2K6.97323$HF.22179797_at_news4.rdc1.on.home.com...
> Has anyone seen this problem before?
> I am running Oracle 8.1.6 on Solaris. When I issue
> Alter database backup controlfile to trace
>
> it is supposed to generate a trace file in the udump directory. But
> sometimes it does not create anything in the udump. It just executes the
> command but no trace file is generated. I checked the udump directory as
> specified in:
>
> show parameters dump
>
> so I am sure I am looking at the right directory. Sometimes it works and
> sometimes it does not. This is driving me crazy.
>
> Does anyone have any ideas?
>
> Please Email me as well as posting to this group.
>
>
Received on Wed May 09 2001 - 07:33:59 CDT