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

Overflowlogpath

P: n/a
Per the manual:

If 'overflowlogpath' is not specified during a rollforward operation,
DB2 will retrieve the log files into the active log path.

My question is: With userexit enabled, the archive log files are
copied
over from the active log path directory to 'another directory'. So,
when a ROLLFORWARD is issued and OVERFLOWLOGPATH is not specified, how
does DB2 'know' at all where the archived log files are? In other
words, how does DB2 know what directory the userexit program copied
the log files to, so it can copy those log files into the active log
path?

TIA
Raquel.
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
In article <9a**************************@posting.google.com >,
ra****************@yahoo.com says...
Per the manual:

If 'overflowlogpath' is not specified during a rollforward operation,
DB2 will retrieve the log files into the active log path.

My question is: With userexit enabled, the archive log files are
copied
over from the active log path directory to 'another directory'. So,
when a ROLLFORWARD is issued and OVERFLOWLOGPATH is not specified, how
does DB2 'know' at all where the archived log files are? In other
words, how does DB2 know what directory the userexit program copied
the log files to, so it can copy those log files into the active log
path?

TIA
Raquel.


This is also done by the userexit. In the samples/c/db2uext2.cdisk
file you can see which parms could be supplied to the userexit.

Copied from db2uext2.cdisk:

4. DB2 calls "db2uext2" in the following format -

db2uext2 -OS<os> -RL<release> -RQ<request> -DB<dbname>
-NN<nodenumber> -LP<logpath> -LN<logname>
[-AP<adsmpasswd>]

where: os = operating system
release = DB2 release
request = 'ARCHIVE' or 'RETRIEVE'
dbname = database name
nodenumber = node number
logpath = log file path
logname = log file name
logsize = log file size (optional)
startingpage = starting offset in 4K page unit
(optional)
adsmpasswd = ADSM password (optional)

Note: logsize and startingpage are only used when
logpath is a raw device.

5. Log files are archived and retrieved from disk with the
following naming convention:

archive: archive path + database name +
node number + log file name
retrieve: retrieve path + database name +
node number + log file name

For example: If the archive path was "c:\mylogs",
the retrieve path was "c:\mylogs",
the database name was "SAMPLE",
the node number was NODE0000, and the
file name was "S0000001.LOG", the log file
would be:

archived to -
"c:\mylogs\SAMPLE\NODE0000\S0000001.LOG"

retrieved from -
"c:\mylogs\SAMPLE\NODE0000\S0000001.LOG"

Note: The subdirectory c:\mylogs\SAMPLE\NODE0000\
is created by the user exit sample program.
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.