Seen these on tdp 2.2.1 also. Most of them (maybe all of them) are for
the 'c' type files (e.g. oracle controlfiles).

They were once explained as being checked for existance on the tsm
server before actually creating them...

-Marcel


On Thu, Oct 02, 2003 at 01:47:58PM +0200, Loon, E.J. van - SPLXM wrote:
> Hi *SM-ers!
> Since the upgrade of 3 of our Data Protection for Oracle clients from 2.2.1
> to 5.2 I see a LOT of errors in the activity log like:
>
> ANU2602E The object /mount/appl00001//c-862102661-20031002-0a was not found
> on the TSM Server
>
> I checked these messages in the TSM log and compared them with the TSM
> inventory details.
>
> >From the TSM activity log:
> 02-10-2003 10:09:21 ANE4994S (Session: 673547, Node: KL1004XL-ORC)  TDP
> Oracle AIX ANU0599 ANU2602E The object
> /mount/appl00001//c-862102661-20031002-0a was not found on the TSM Server
>
> With a select * from backups where node_name='NODE" from the client's
> inventory on the TSM server:
> KL1004XL-ORC /mount/appl00001 1 ACTIVE_VERSION FILE //
> c-862102661-20031002-0a 316949736 2003-10-02 10:09:22.000000  oracle DEFAULT
>
> So the object not found error occurred at 10:09:21 and the object itself was
> created at 10:09:22!
> It looks like TSM checks whether the object already exists before creating
> it. If this is the case, then this is a new feature introduced in the 5.2 DP
> client. A nasty side affect is a LOT of errors in both the activity log and
> the tdpoerror.log.
> Has anybody seen this before?
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
>

--
     ======--------         Marcel J.E. Mol                MESA Consulting B.V.
    =======---------        ph. +31-(0)6-54724868          P.O. Box 112
    =======---------        marcel AT mesa DOT nl                 2630 AC  
Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
 They couldn't think of a number,           Linux user 1148  --  counter.li.org
    so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com