Phil, It is a registry variable. I think you need to set it to ON. The path will then be the same as your current log path with a '2' on the end.
So if you have /database_logs as your log path, your second log path will be /database_logs2 Cheers, Jeremy "Philip Nelson (DBA)" wrote: > Guys, > > I'm looking at the new dual logging capabilities of DB2 V7.2. > > It tells me I need to set a new "registry variable", NEWLOGPATH2 (changed in Fixpack >5 to DB2_NEWLOGPATH2). > > That sounds like "WinDoze-speak" to me. > > Should I set this as a Unix environment variable, or by using the "db2set" command. >I tried the latter and got an error message. > > Doing a "db2set -all" doesn't list this variable as being a valid one. > > TIA > > Phil Nelson > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** You are subscribed to [EMAIL PROTECTED] > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** You are subscribed to [EMAIL PROTECTED] *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
