Hello,

After restoring my database I have some problems with diag.log who
becomes very large. The "logretain" and "userexit" are set to
"recovery" and "on" respectively.

Any suggestions are welcome...

Greetz


2005-04-25-13.50.33.699000+120 E86152469H468 LEVEL: Error
PID : 3344 TID : 1604 PROC : db2syscs.exe
INSTANCE: DB2INST1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgInvokeUserexit, probe:1550
MESSAGE : ADM1833E The user exit program returned an error when
archiving log
file "S0000658.LOG" from
"C:\DB2INST1\NODE0000\SQL00001\SQLOGDIR\"
for database "WORKLOAD". The error code was "1".

2005-04-25-13.50.33.699000+120 I86152939H380 LEVEL: Error
PID : 3344 TID : 1604 PROC : db2syscs.exe
INSTANCE: DB2INST1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000658.LOG to USEREXIT from
C:\DB2INST1\NODE0000\SQL00001\SQLOGDIR\ with rc = 1.

2005-04-25-13.50.33.699000+120 I86153321H370 LEVEL: Warning
PID : 3344 TID : 1604 PROC : db2syscs.exe
INSTANCE: DB2INST1 NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgRetryFailedArchive,
probe:4780
MESSAGE : Still unable to archive log file 658 due to rc 1 for
LOGARCHMETH1
using method 4 and target .

Hi Peter,

- did you compile the db2uext2.c with the right paths?
- did you copy the resulting db2uext2 to the sqllib/adm/ - directory?

What does USEREXIT.ERR (in ARCHIVE_PATH) say?

regards,

Norbert

Hi Norbert,

Where can I find the USEREXIT.ERR file? I do not have one in neither
C:/IBM/SQLLIB and C:\DB2INST1

Regards, Peter


Norbert Munkel <nm@acoreus.de> wrote in message news:<JH9be.4$YY6.244@se2-cb104-9.zrh1.ch.colt.net>...
> Hi Peter,
>
> - did you compile the db2uext2.c with the right paths?
> - did you copy the resulting db2uext2 to the sqllib/adm/ - directory?
>
> What does USEREXIT.ERR (in ARCHIVE_PATH) say?
>
> regards,
>
> Norbert

Hi Peter,

Peter wrote:
> Hi Norbert,
>
> Where can I find the USEREXIT.ERR file? I do not have one in neither
> C:/IBM/SQLLIB and C:\DB2INST1

You should find it, wherever you have configured it in db2uext2.
As you are saying you are experiencing this problem since restoring the
database, I guess you have not compiled the userexit program (db2uext2)
at all. Please do so and copy it to the appropriate directory. Would be
sqllib/adm on a unix system. Please see reference documentation about
placement of userexit-routines in a windows environment.

regards,

Norbert

Peter,

it looks like, you have to set the new log managemt on.
Look for LOGARCHMETH1 in your db cfg.
For the new log managemt you don't need an userexit.

regards,
Joachim Müller

"Peter" <nomorems@yahoo.com> schrieb im Newsbeitrag
news:d95604f.0504250436.2e2508f8@posting.google.co m...
> Hello,
>
> After restoring my database I have some problems with diag.log who
> becomes very large. The "logretain" and "userexit" are set to
> "recovery" and "on" respectively.
>
> Any suggestions are welcome...
>
> Greetz
>
>
> 2005-04-25-13.50.33.699000+120 E86152469H468 LEVEL: Error
> PID : 3344 TID : 1604 PROC : db2syscs.exe
> INSTANCE: DB2INST1 NODE : 000
> FUNCTION: DB2 UDB, data protection, sqlpgInvokeUserexit, probe:1550
> MESSAGE : ADM1833E The user exit program returned an error when
> archiving log
> file "S0000658.LOG" from
> "C:\DB2INST1\NODE0000\SQL00001\SQLOGDIR\"
> for database "WORKLOAD". The error code was "1".
>
> 2005-04-25-13.50.33.699000+120 I86152939H380 LEVEL: Error
> PID : 3344 TID : 1604 PROC : db2syscs.exe
> INSTANCE: DB2INST1 NODE : 000
> FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
> MESSAGE : Failed to archive log file S0000658.LOG to USEREXIT from
> C:\DB2INST1\NODE0000\SQL00001\SQLOGDIR\ with rc = 1.
>
> 2005-04-25-13.50.33.699000+120 I86153321H370 LEVEL: Warning
> PID : 3344 TID : 1604 PROC : db2syscs.exe
> INSTANCE: DB2INST1 NODE : 000
> FUNCTION: DB2 UDB, data protection, sqlpgRetryFailedArchive,
> probe:4780
> MESSAGE : Still unable to archive log file 658 due to rc 1 for
> LOGARCHMETH1
> using method 4 and target .

Hi,

Joachim Müller wrote:
> Peter,
>
> it looks like, you have to set the new log managemt on.
> Look for LOGARCHMETH1 in your db cfg.
> For the new log managemt you don't need an userexit.

you are absolutely right for 8.2 UDB. But as I understand, he is(was)
already using userexit. Never change a running system... ;-)

Oh... it is not running at all... sorry.

regards,

Norbert Munkel

Norbert,

changed all direct archiving with userexit to the new log management,
worked as designed...

regards,
Joachim Müller

"Norbert Munkel" <nm@acoreus.de> schrieb im Newsbeitrag
news:vqrbe.6$YY6.256@se2-cb104-9.zrh1.ch.colt.net...
> Hi,
>
> Joachim Müller wrote:
>> Peter,
>>
>> it looks like, you have to set the new log managemt on.
>> Look for LOGARCHMETH1 in your db cfg.
>> For the new log managemt you don't need an userexit.
>
> you are absolutely right for 8.2 UDB. But as I understand, he is(was)
> already using userexit. Never change a running system... ;-)
>
> Oh... it is not running at all... sorry.
>
> regards,
>
> Norbert Munkel
>
>