Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / July 2006

Tip: Looking for answers? Try searching our database.

db2diag.log

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Asphalt Blazer - 10 Jul 2006 19:50 GMT
Hi,
        here is a message I have been recieving in my db2diag.log file

240 E457831A419        LEVEL: Warning (OS)

PID     : 369436               TID  : 5707        PROC : java

INSTANCE: db2inst1             NODE : 000

FUNCTION: DB2 UDB, oper system services, sqloqualifydir, probe:30

CALLED  : OS, -, unspecified_system_function

OSERR   : ENOENT (2) "A file or directory in the path name does not
exist."

DATA #1 : File name, 27 bytes

/u01/home/db2inst1/db2inst1

This is repeating through out the day. I cannot find anything in the
dbm or db parameters that point to this location. This being a new
machine no other users are connected to it. I am just prepping up the
machine.
rhino_redux@yahoo.ca - 10 Jul 2006 20:49 GMT
> Hi,
>          here is a message I have been recieving in my db2diag.log file
[quoted text clipped - 20 lines]
> machine no other users are connected to it. I am just prepping up the
> machine.

It _appears_ that DB2 is trying to write to a specfic path,
/u01/home/db2inst1/db2inst1, and not finding it.

I think you need to figure out _why_ it is trying to write to that
path. Then, if that is the correct path, you'll need to create the
necessary directories or, if it isn't the correct path, you'll want to
change the parameters to make it point to the desired path.

Based on the "FUNCTION:" line, I'm _guessing_ that DB2 is trying to
write a log file to that path. I would have expected to see the
troublesome path in your dbm or db configurations but you say that you
have already checked them and that path is not used. All I can suggest
is that you double-check them just to see if you missed one. Perhaps it
is the data warehouse database, not one of the ones you created for
yourself??

--
Rhino
Asphalt Blazer - 11 Jul 2006 16:52 GMT
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
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.