It is a dw database, i had redirected restored the database from
another machine. But even in that machine there is no path like this. I
double and triple checked the paths in db and dbm cfg's there is no
path like this
the salient paths:
db cfg
Path to log files =
/u02/db2alogs/cdxxxx/NODE0000/
dbm cfg
Default database path (DFTDBPATH) =
/u01/db2catalogs
I dont know why it is still looking for this path
> > Hi,
> > here is a message I have been recieving in my db2diag.log file
[quoted text clipped - 39 lines]
> --
> Rhino
Asphalt Blazer - 11 Jul 2006 17:15 GMT
actually I found one more thing, this error happens when I start the
control center. Well that does not solve the problem.
> It is a dw database, i had redirected restored the database from
> another machine. But even in that machine there is no path like this. I
[quoted text clipped - 56 lines]
> > --
> > Rhino
rhino_redux@yahoo.ca - 11 Jul 2006 19:57 GMT
If you're going to start top-posting, this is going to get
confusing....
> It is a dw database, i had redirected restored the database from
> another machine. But even in that machine there is no path like this. I
[quoted text clipped - 12 lines]
>
> I dont know why it is still looking for this path
It looks like you're working with a flavour of Unix or Linux. Could
there be a symbolic link pointing from one of your paths to the one
mentioned in the message?
Other than that, I'm not sure what else to suggest.
You could try googling on sqloqualifydir or other keywords in the log
entry (in both Google Groups and Google Web) to see if you can find
other problem reports that might be related. That might give you a clue
about what you should do.
You could create the path it wants - just leave it empty or put a
harmless file in there - and see if the problem goes away. This _might_
increase the scope of the problem if the file it wants is critical but
that might be helpful if you get more and/or clearer messages that tell
you what exactly is wrong.
You could ignore the message since there is apparently nothing
misbehaving within your system beyond the generation of this message.
You could call IBM Support and ask for their help. That will cost you
something if you don't already have a support contract but maybe it
will be worth if for your peace of mind.
I suppose it depends on how much this bothers you and how much time and
money you're willing to spend to resolve the problem.
--
Rhino
> > > Hi,
> > > here is a message I have been recieving in my db2diag.log file
[quoted text clipped - 39 lines]
> > --
> > Rhino