By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,610 Members | 1,672 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,610 IT Pros & Developers. It's quick & easy.

DB2 Archive Failure

P: n/a
I am using DB2 8.2 on RH Linux 8.0.

I just compiled db2uext2.c but failed to archive the log files, did
anybody fix this problem before? TIA

db2diag.log
2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
/db/db2log/active/NODE0000/ with rc = 28.

2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
USEREXIT.ERR
************************************************** ******************************
Time of Error: Sun Jun 12 12:39:52 2005

Parameter Count: 8
Parameters Passed:
Database name: SAMPLE
Logfile name: S0000012.LOG
Logfile path: /db/db2log/active/NODE0000/
Node number: NODE0000
Operating system: Linux
Release: SQL08020
Request: ARCHIVE
Audit Log File: /db/db2log/audit/ARCHIVE.LOG
System Call Parms: rm -f
/db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
Media Type: disk
User Exit RC: 28
Error isolation: Error archiving file. Return code 256 received from the system call

************************************************** ******************************

Nov 12 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
If you are using 8.2, you no longer require the userexit. Look at the
DB parameter ARCHMETH1, as the userexit has been incorporated into DB2

The following will archive the logfiles to /db2/logs/

db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs

Cheers,

William wrote:
I am using DB2 8.2 on RH Linux 8.0.

I just compiled db2uext2.c but failed to archive the log files, did
anybody fix this problem before? TIA

db2diag.log
2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
/db/db2log/active/NODE0000/ with rc = 28.

2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
USEREXIT.ERR
************************************************** ******************************
Time of Error: Sun Jun 12 12:39:52 2005

Parameter Count: 8
Parameters Passed:
Database name: SAMPLE
Logfile name: S0000012.LOG
Logfile path: /db/db2log/active/NODE0000/
Node number: NODE0000
Operating system: Linux
Release: SQL08020
Request: ARCHIVE
Audit Log File: /db/db2log/audit/ARCHIVE.LOG
System Call Parms: rm -f
/db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
Media Type: disk
User Exit RC: 28
Error isolation: Error archiving file. Return code 256 received from the system call

************************************************** ******************************


Nov 12 '05 #2

P: n/a

Oops - The parameter is LOGARCHMETH1 not ARCHMETH1
Fred Nurk wrote:
If you are using 8.2, you no longer require the userexit. Look at the
DB parameter ARCHMETH1, as the userexit has been incorporated into DB2

The following will archive the logfiles to /db2/logs/

db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs

Cheers,

William wrote:
I am using DB2 8.2 on RH Linux 8.0.

I just compiled db2uext2.c but failed to archive the log files, did
anybody fix this problem before? TIA

db2diag.log
2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
/db/db2log/active/NODE0000/ with rc = 28.

2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
USEREXIT.ERR
************************************************** ******************************
Time of Error: Sun Jun 12 12:39:52 2005

Parameter Count: 8
Parameters Passed:
Database name: SAMPLE
Logfile name: S0000012.LOG
Logfile path: /db/db2log/active/NODE0000/
Node number: NODE0000
Operating system: Linux
Release: SQL08020
Request: ARCHIVE
Audit Log File: /db/db2log/audit/ARCHIVE.LOG
System Call Parms: rm -f
/db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
Media Type: disk
User Exit RC: 28
Error isolation: Error archiving file. Return code 256 received from the system call

************************************************** ******************************


Nov 12 '05 #3

P: n/a
Thanks Fred.

Can I use that db2uext2 on DB2 8.2?

Fred Nurk wrote:
Oops - The parameter is LOGARCHMETH1 not ARCHMETH1
Fred Nurk wrote:
If you are using 8.2, you no longer require the userexit. Look at the
DB parameter ARCHMETH1, as the userexit has been incorporated into DB2

The following will archive the logfiles to /db2/logs/

db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs

Cheers,

William wrote:
I am using DB2 8.2 on RH Linux 8.0.

I just compiled db2uext2.c but failed to archive the log files, did
anybody fix this problem before? TIA

db2diag.log
2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
/db/db2log/active/NODE0000/ with rc = 28.

2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
PID : 3300 TID : 8192 PROC : db2logmgr
(SAMPLE)
INSTANCE: db2prd NODE : 000
FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
USEREXIT.ERR
************************************************** ******************************
Time of Error: Sun Jun 12 12:39:52 2005

Parameter Count: 8
Parameters Passed:
Database name: SAMPLE
Logfile name: S0000012.LOG
Logfile path: /db/db2log/active/NODE0000/
Node number: NODE0000
Operating system: Linux
Release: SQL08020
Request: ARCHIVE
Audit Log File: /db/db2log/audit/ARCHIVE.LOG
System Call Parms: rm -f
/db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
Media Type: disk
User Exit RC: 28

> Error isolation: Error archiving file. Return code 256 received from the system call
************************************************** ******************************


Nov 12 '05 #4

P: n/a
Ye. You specify LOGARCHMETH1=USEREXIT
It will then look for your DB2 UEXT2 executable
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"William" <We*********@gmail.com> a écrit dans le message de news:
11**********************@f14g2000cwb.googlegroups. com...
Thanks Fred.

Can I use that db2uext2 on DB2 8.2?

Fred Nurk wrote:
Oops - The parameter is LOGARCHMETH1 not ARCHMETH1
Fred Nurk wrote:
> If you are using 8.2, you no longer require the userexit. Look at the
> DB parameter ARCHMETH1, as the userexit has been incorporated into DB2
>
> The following will archive the logfiles to /db2/logs/
>
> db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs
>
> Cheers,
>
> William wrote:
> > I am using DB2 8.2 on RH Linux 8.0.
> >
> > I just compiled db2uext2.c but failed to archive the log files, did
> > anybody fix this problem before? TIA
> >
> > db2diag.log
> > 2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
> > MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
> > /db/db2log/active/NODE0000/ with rc = 28.
> >
> > 2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs,
> > probe:1500
> > MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
> >
> >
> > USEREXIT.ERR
> > ************************************************** ******************************
> > Time of Error: Sun Jun 12 12:39:52 2005
> >
> > Parameter Count: 8
> > Parameters Passed:
> > Database name: SAMPLE
> > Logfile name: S0000012.LOG
> > Logfile path: /db/db2log/active/NODE0000/
> > Node number: NODE0000
> > Operating system: Linux
> > Release: SQL08020
> > Request: ARCHIVE
> > Audit Log File: /db/db2log/audit/ARCHIVE.LOG
> > System Call Parms: rm -f
> > /db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
> > Media Type: disk
> > User Exit RC: 28
> >
> > > Error isolation: Error archiving file. Return code 256 received
> > > from the system call
> >
> >
> > ************************************************** ******************************


Nov 12 '05 #5

P: n/a
A bit more on this.
This is what your db cfg will look like after using the cc to set
logarchmeth1=userexit

D:\SQLLIB\BIN>db2 get db cfg for sample | find "EXIT"
User exit for logging enabled (USEREXIT) = ON
First log archive method (LOGARCHMETH1) = USEREXIT
HTH, Pierre
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"William" <We*********@gmail.com> a écrit dans le message de news:
11**********************@f14g2000cwb.googlegroups. com...
Thanks Fred.

Can I use that db2uext2 on DB2 8.2?

Fred Nurk wrote:
Oops - The parameter is LOGARCHMETH1 not ARCHMETH1
Fred Nurk wrote:
> If you are using 8.2, you no longer require the userexit. Look at the
> DB parameter ARCHMETH1, as the userexit has been incorporated into DB2
>
> The following will archive the logfiles to /db2/logs/
>
> db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs
>
> Cheers,
>
> William wrote:
> > I am using DB2 8.2 on RH Linux 8.0.
> >
> > I just compiled db2uext2.c but failed to archive the log files, did
> > anybody fix this problem before? TIA
> >
> > db2diag.log
> > 2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
> > MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
> > /db/db2log/active/NODE0000/ with rc = 28.
> >
> > 2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs,
> > probe:1500
> > MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
> >
> >
> > USEREXIT.ERR
> > ************************************************** ******************************
> > Time of Error: Sun Jun 12 12:39:52 2005
> >
> > Parameter Count: 8
> > Parameters Passed:
> > Database name: SAMPLE
> > Logfile name: S0000012.LOG
> > Logfile path: /db/db2log/active/NODE0000/
> > Node number: NODE0000
> > Operating system: Linux
> > Release: SQL08020
> > Request: ARCHIVE
> > Audit Log File: /db/db2log/audit/ARCHIVE.LOG
> > System Call Parms: rm -f
> > /db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
> > Media Type: disk
> > User Exit RC: 28
> >
> > > Error isolation: Error archiving file. Return code 256 received
> > > from the system call
> >
> >
> > ************************************************** ******************************


Nov 12 '05 #6

P: n/a
Hi Pierre,

It's very kind of you!!!

I did the test with:
db2 "update db cfg for PRD using LOGARCHMETH1
DISK:/db/db2log/archive/"
it works fine with log archiving, then I did with:
db2 "update db cfg for PRD using LOGARCHMETH2 TSM"
it works fine with TSM too.

I would say, this is a very good feature in DB2 8.2.

Back to my original question, why did it not work when I use db2uext2?
Please check the error message from the above original message. Thanks

Pierre Saint-Jacques wrote:
A bit more on this.
This is what your db cfg will look like after using the cc to set
logarchmeth1=userexit

D:\SQLLIB\BIN>db2 get db cfg for sample | find "EXIT"
User exit for logging enabled (USEREXIT) = ON
First log archive method (LOGARCHMETH1) = USEREXIT
HTH, Pierre
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"William" <We*********@gmail.com> a écrit dans le message de news:
11**********************@f14g2000cwb.googlegroups. com...
Thanks Fred.

Can I use that db2uext2 on DB2 8.2?

Fred Nurk wrote:
Oops - The parameter is LOGARCHMETH1 not ARCHMETH1
Fred Nurk wrote:
> If you are using 8.2, you no longer require the userexit. Look at the
> DB parameter ARCHMETH1, as the userexit has been incorporated into DB2
>
> The following will archive the logfiles to /db2/logs/
>
> db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs
>
> Cheers,
>
> William wrote:
> > I am using DB2 8.2 on RH Linux 8.0.
> >
> > I just compiled db2uext2.c but failed to archive the log files, did
> > anybody fix this problem before? TIA
> >
> > db2diag.log
> > 2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
> > MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
> > /db/db2log/active/NODE0000/ with rc = 28.
> >
> > 2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs,
> > probe:1500
> > MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
> >
> >
> > USEREXIT.ERR
> > ************************************************** ******************************
> > Time of Error: Sun Jun 12 12:39:52 2005
> >
> > Parameter Count: 8
> > Parameters Passed:
> > Database name: SAMPLE
> > Logfile name: S0000012.LOG
> > Logfile path: /db/db2log/active/NODE0000/
> > Node number: NODE0000
> > Operating system: Linux
> > Release: SQL08020
> > Request: ARCHIVE
> > Audit Log File: /db/db2log/audit/ARCHIVE.LOG
> > System Call Parms: rm -f
> > /db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
> > Media Type: disk
> > User Exit RC: 28
> >
> > > Error isolation: Error archiving file. Return code 256 received
> > > from the system call
> >
> >
> > ************************************************** ******************************


Nov 12 '05 #7

P: n/a
Good to know things worked out.
As to the error, I really don't know. I can't see an SQL error code to tie
the "reason code 28" to it.
Are these the only messages that you db2diag.log put out when you got the
error?

Unless you entered the word "db2uext2" instead of "userexit" when you set
the parm in the db cfg but I don't think so!
Regards, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"William" <We*********@gmail.com> a écrit dans le message de news:
11**********************@g47g2000cwa.googlegroups. com...
Hi Pierre,

It's very kind of you!!!

I did the test with:
db2 "update db cfg for PRD using LOGARCHMETH1
DISK:/db/db2log/archive/"
it works fine with log archiving, then I did with:
db2 "update db cfg for PRD using LOGARCHMETH2 TSM"
it works fine with TSM too.

I would say, this is a very good feature in DB2 8.2.

Back to my original question, why did it not work when I use db2uext2?
Please check the error message from the above original message. Thanks

Pierre Saint-Jacques wrote:
A bit more on this.
This is what your db cfg will look like after using the cc to set
logarchmeth1=userexit

D:\SQLLIB\BIN>db2 get db cfg for sample | find "EXIT"
User exit for logging enabled (USEREXIT) = ON
First log archive method (LOGARCHMETH1) = USEREXIT
HTH, Pierre
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"William" <We*********@gmail.com> a écrit dans le message de news:
11**********************@f14g2000cwb.googlegroups. com...
Thanks Fred.

Can I use that db2uext2 on DB2 8.2?

Fred Nurk wrote:
Oops - The parameter is LOGARCHMETH1 not ARCHMETH1
Fred Nurk wrote:
> If you are using 8.2, you no longer require the userexit. Look at
> the
> DB parameter ARCHMETH1, as the userexit has been incorporated into
> DB2
>
> The following will archive the logfiles to /db2/logs/
>
> db2 update db cfg for <dbname> using archmeth1 disk:/db2/logs
>
> Cheers,
>
> William wrote:
> > I am using DB2 8.2 on RH Linux 8.0.
> >
> > I just compiled db2uext2.c but failed to archive the log files, did
> > anybody fix this problem before? TIA
> >
> > db2diag.log
> > 2005-06-12-12.39.52.305630-240 I3534G369 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
> > MESSAGE : Failed to archive log file S0000012.LOG to USEREXIT from
> > /db/db2log/active/NODE0000/ with rc = 28.
> >
> > 2005-06-12-12.39.52.305988-240 I3904G311 LEVEL: Error
> > PID : 3300 TID : 8192 PROC : db2logmgr
> > (SAMPLE)
> > INSTANCE: db2prd NODE : 000
> > FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs,
> > probe:1500
> > MESSAGE : Log archive failed with rc 28 for LOGARCHMETH1.
> >
> >
> > USEREXIT.ERR
> > ************************************************** ******************************
> > Time of Error: Sun Jun 12 12:39:52 2005
> >
> > Parameter Count: 8
> > Parameters Passed:
> > Database name: SAMPLE
> > Logfile name: S0000012.LOG
> > Logfile path: /db/db2log/active/NODE0000/
> > Node number: NODE0000
> > Operating system: Linux
> > Release: SQL08020
> > Request: ARCHIVE
> > Audit Log File: /db/db2log/audit/ARCHIVE.LOG
> > System Call Parms: rm -f
> > /db/db2log/archive/SAMPLE/NODE0000/S0000012.LOG
> > Media Type: disk
> > User Exit RC: 28
> >
> > > Error isolation: Error archiving file. Return code 256 received
> > > from the system call
> >
> >
> > ************************************************** ******************************


Nov 12 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.