Unable to read LOGS.DIR entry from D_UV_LOGS

[chenghowe]

We face a problem that we can open the job, compile and design but it
can't run and validate the job. This happen since we migrate (copy) the storage disk to another.

During DataStage shutdown, error message show :

root@host:[/sbin/init.d]#cd /sbin/init.d
root@host:[/sbin/init.d]#./uv.rc stop
DeadLock Daemon shutdown
Unable to read LOGS.DIR entry from D_UV_LOGS.
Unable to open uvdrlogd Daemon info file.
Unable to locate UVDR log directory.
Daemon stopped.

Storage Migration is copy whole thing from old harddisk to a new harddisk. Was it have to re-install DataStage again?

[ray.wurlod]

This is a very annoying message to get for DataStage; it's actually from the UniVerse transaction logging daemon (uvlogd), which wakes during startup to determine whether logging is enabled. It never is for DataStage, but it checks a few things anyway. UV_LOGS is the file where information about UniVerse transaction logging files exists, and the LOGS.DIR entry in its dictionary (D_UV_LOGS) contains the pathname of the directory in which the transaction logs reside.

A quick fix would be to create an entry pointing to any existing directory. For example, in the uvsh environment on your server:

Code: Select all

LOGTO UV
INSERT INTO DICT UV_LOGS (@ID, F1, F2) VALUES ('LOGS.DIR', 'X', '/tmp');

Or it may simply be that uvlogd does not have read permission to D_UV_LOGS or read and execute permission to the UV home directory.

[chulett]

While not having a clue about this particular message, I was curious about something.

In this 'migration' from one storage disk to another, did anything about the end result change? Meaning, does your current configuration match your old configuration - mount points, pathnames where everything lives, permissions, things of that nature? Ray has already asked about the permissions but I was wondering what else might have changed.

[ray.wurlod]

I don't think anything's moved, otherwise /.uvhome would be wrong, and a different message would have been generated. However, if the permissions are wrong or the installation is incomplete the indicated error message could have occurred.

[chenghowe]

Thank You for your reply, i verify again between old storage and the new storage, the configuration, pathname and permission is the same.

1) How do i know that uvlogd deamon have read permission to D_UV_LOGS or read and execute permission to the UV home directory?

Was it the command as show below

Code: Select all

/ardent/users=> ls -l
drwxr-xr-x   7 dsadmin    adm           1024 Apr 15 09:25 dsadmin
drwxr-xr-x   5 dsuser01   datastage     1024 Apr 17  2003 dsuser01

/ardent=> ls -l
drwxr-xr-x  19 root       sys           1024 Apr 17  2003 users
drwxrwxrwx  42 root       sys           4096 Sep 15  2004 uv

/ardent/uv=> ls -l
total 47804
-rwxrwxrwx   1 root       sys           8192 Jun 14  2001 &DEVICE&
-rwxrwxrwx   1 root       other        16384 Sep 13  2000 &MAP&
-rwxrwxrwx   1 root       sys          16384 Jun 14  2001 &PARTFILES&
drwxrwxrwx  18 root       other         1024 Apr 17  2003 &SAVEDLISTS&
drwxrwxrwx   3 root       other         7168 Apr 17  2003 APP.PROGS
drwxrwxrwx   3 root       other         7168 Apr 17  2003 APP.PROGS.O
-rwxrwxrwx   1 root       other        10240 Sep 13  2000 BLTRS
drwxrwxrwx   2 root       other         3072 Apr 17  2003 BP
drwxrwxrwx   2 root       other         2048 Apr 17  2003 BP.O
-rwxrwxrwx   1 root       other         9728 Jun 14  2001 DATA.TYPES
-rwxrwxrwx   1 root       other        14336 Sep 13  2000 DICT.DICT
-rwxrwxrwx   1 root       other         2048 Sep 13  2000 DICT.PICK
-rwxrwxrwx   1 root       sys           3377 Jun 14  2001 DSRAdmin.u
-rwxrwxrwx   1 root       other         4096 Sep 13  2000 D_&DEVICE&
-rwxrwxrwx   1 root       other         4096 Sep 13  2000 D_&MAP&
-rwxrwxrwx   1 root       other         4096 Sep 13  2000 D_&PARTFILES&

/ardent/uv=> ls -ltr *uvlogd*
-rwxrwxrwx   1 root       sys            486 Jun 14  2001 uvlogd.script

2) The script show below, what is the column description for "F1" and "F2". Can i simply give any name for "F1" and any directory which exist in my harddisk for "F2"?

Code: Select all

LOGTO UV 
INSERT INTO DICT UV_LOGS (@ID, F1, F2) VALUES ('LOGS.DIR', 'X', '/tmp');

Error Message Show :

root@host:[/datastage]#cd /sbin/init.d
root@host:[/sbin/init.d]#./uv.rc stop
usp: no spool daemon
An error has occurred during uniVerse initialization
Please contact the system administrator
Error code: 2 2
An error has occurred during uniVerse initialization
Please contact the system administrator
Error code: 2 2
An error has occurred during uniVerse initialization
Please contact the system administrator
Error code: 2 2
uniVerse has been brought down.
root@host:[/sbin/init.d]#./uv.rc start
uniVerse has been brought up.
uniVerse Log Daemon started
Deadlock Daemon has been started
root@host:[/sbin/init.d]#
root@host:[/sbin/init.d]#./uv.rc stop
DeadLock Daemon shutdown
Unable to read LOGS.DIR entry from D_UV_LOGS.
Unable to open uvdrlogd Daemon info file.
Unable to locate UVDR log directory.
Daemon stopped.
uniVerse has been brought down.

Thank You.

[krigg5]

Hi,

Just to add chenghowe question,

1) how are we going to log into uvsh environment? through unix using root or through datastage administrator?

2) how can we check either the LOGS.DIR entry is exist in its dictionary (D_UV_LOGS) ?

3) what is the value for F1 and F2 in your code given earlier? it seem like F2 is the pathname for the LOGS.DIR to be create? correct me if i'm wrong.. and the 'X' value is stand for what?

4) how are we going to issue this command :
LOGTO UV INSERT INTO UV_LOGS (@ID, F1, F2) VALUES ('LOGS.DIR', 'X', '/tmp');
Is it through Datastage Administrator?

Kindly advise..thanks..

[ray.wurlod]

You seem to have three threads going on this problem. My bet is that your "migration" was performed with UNIX utilities, and therefore that there is a lot of repair needed. See other thread for details that are as complete as I can manage out of my head.