Carla, It could be tricky to work out what the source file was. I think there might be a clue in the db2diag.log file. Failing that, as the compiled C program has to be called db2uext2, it could be sourced from db2uext2.cadsm or db2uext2.cdisk. Personally, I'd then do a search to see if I could find the source file on your computer. It's also possible that there is an ARCHIVE.LOG file or a RETRIEVE.LOG file left on your computer somewhere, from when the original developer tested the userexit. If there is, it should be easy to see if you are archiving to tape or disk.
If you want your logs to be archived to ADSM rather than to disk, I'd forget about moving the logfiles to ADSM by using tar or any other tape archive utility. Why not just take db2uext2.cadsm and compile it? If you can set up the ADSM client and server, then compiling a C program is relative childs play :) James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Carla Cristina Alonzo Ducl�s Sent: 24 July 2003 00:04 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [DB2EUG] db2 archive log Hello James, > That command calls the userexit in the same way that the userexit is > called if the transaction log becomes full naturally. > The command is deprecated now, however. Since DB2 v7.2 fixpack 3, an > online backup automatically archives the active log when a DB2 online > backup command completes. It is an interesting information. > This command can only be used when you've set archive logging on i.e. > db2 update db cfg for <db> using logretain true userexit on" Yes, I have userexit set to ON. > The userexit defines the archive destination for the transaction logs. > There's a #define ARCHIVE_PATH which needs updating. And, Can I check this flag with "db2 get db cfg for <db>" ? > The userexit is a compiled C program and has to be called db2uext2 and > has to exist in the sqllib\bin directory. > > Sample db2uext2.c source files are available in the sqllib\samples\c > directory when you install the application development client. > > There's full instructions on what to change and how to compile the C > source file. > > There are example files for ADSM(TSM) which is IBM's tape storage system > and also for transferring the transaction logs to disk. I guess, if you > want to archive logs to another storage system, you have to write your > own code. > > When I used it, I remember having an issue with transaction log files > not being deleted from the active log path when TSM played up. They did > eventually disappear, however, but it was all a bit confusing and IBM > support weren't much help. I asked in another email how can I check what userexit program my database is using. If it is using the disk userexit program (db2uext2.cdisk), and if I want to save the archived logs to a tape device, Can I only copy the files on the directory archive (ARCHIVE PATH) to a tape? Using any tool I want, like tar ou any backup utilitie ? Thanks a lot, I�m so gratefull with all answers in this list. Carla -- Carla Alonzo Ducl�s Systems Administrator Solvo S.A. - Servi�os de Miss�o Cr�tica @ www.solvo.com.br - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
