We had our userexit working (it is a userexit supplied by OnDemand for use with DB2). We have the exact same one working on a number of other servers so we cannot see what the difference is between the them.

This is the error we receive:

************************************************** ******************************
Time of Error: Thu May 29 12:53:05 2003

Parameter Count: 8
Parameters Passed:
Database name: ARSLKG
Logfile name: S0000012.LOG
Logfile path: /archive/lkg/arsdb_primarylog/NODE0000/
Node number: NODE0000
Operating system: AIX
Release: SQL07024
Request: ARCHIVE
Audit Log File:
System Call Parms:
Media Type: disk
User Exit RC: 4

> Error isolation: Unable to Get Log Configuration Information


this is the first error in the db2uext.err file

************************************************** ******************************
Time of Error: Wed Mar 19 15:20:47 2003

Parameter Count: 8
Parameters Passed:
Database name: ARSLKG
Logfile name: S0000003.LOG
Logfile path: /archive/lkg/arsdb_primarylog/NODE0000/
Node number: NODE0000
Operating system: AIX
Release: SQL07024
Request: ARCHIVE
Audit Log File:
System Call Parms:
Media Type: disk
User Exit RC: 4

> Error isolation: Unable to Get Log Configuration Information



The last time anything was written to our archive log directory was May 12th
/archive/lkg/arsdb_archiveloglog/ARSLKG/NODE000
-rw------- 1 arslkg sysadm1 1060864 May 12 15:40 S0000003.LOG

But this file exists in the primary log location as well with the same file size
/archive/lkg/arsdb_primarylog/ARSLKG/NODE000
-rw------- 1 arslkg sysadm1 1060864 May 12 15:40 S0000003.LOG

I don't know why this problem is here because from my own investigation nothing has changed on the server.

Anyone have any ideas on what I should do?

thanks

mark