1) logretain=recovery --- set it in the db cfg
2) userexit=on --- set it in the db cfg
3) The userexit you have to build. It needs to be an executable in the path that db2 can reach (likeliest place is in /sqllib/bin). There are samples in /sqllib/c/samples
It does not have to be in C, it can be any command file, script, executable, as long as its name is: db2uext2
In the exit samples, you'll see that it requires you to ideb=ntify a path accessible to DB2 to archive the files. That's where they go when you use the "archive log" command.
Note that you will need the exit to retrieve your logs if you ever have to do a restore/rollforward of the db.
Once those exist, your "archive log" command forces the current active log to be closed and, as it is full, to be archived to the path you specified in the userexit.
There's a lot of info in the DB2 Admin. Guide.
HTH, Pierre.
Carla Cristina Alonzo Ducl�s wrote:
Hello,
I�m planning a backup strategy e I�d like to know more about archive db2 logs.
I�ve read some documents and I didn�t understand where db2 put archived logs after the command:
# db2 archive log for database <database name>
So, I have some doubts. I�ll be so gratefull with any help. :)
How do I have to proceed after this command has been executed? Can I execute this command with online database? Do I have finish all connection to the database before execute this command?
I have db2 7.2.7 and AIX 4.3.3.
Thanks a lot,
Carla
-- Pierre Saint-Jacques, IBM Certified Solutions Expert - Administration SES Consultants Inc. 514-737-4515
- ::: 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
