Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
On Aug 20, 8:32 am, Veeru71 <m_ad...@hotmail.com> wrote:
> Given a logical log file, wow can we find out its location
> (dbspace) ?
> onstat -l doesn't show this info.> Thanks
It actually is in the onstat -l output. The "begin" column is the
physical address of the begining of that log file. The physical
address is a chunk number and page offset into that chunk. Prior to
10, "begin" would be in the format of CCCPPPPP where C = chunk number
in hex and P is the page offset in hex. All, 5 P locations would be
in use, but not all C positions would be used if not required. In 10
with big chunks I believe we format the output to be C:P with a ':'
seperator, so the number to the left of the ':' would be the chunk
that, that log was in. Then once you have your chunk number you can
map that to the dbspace with onstat -d.
Veeru71 wrote:
> Given a logical log file, wow can we find out its location
> (dbspace) ?
> onstat -l doesn't show this info.> Thanks
>
Using the sysmaster database:
SELECT l.number logfile, d.name dbspace
FROM syslogfil l, syschunks c, sysdbspaces d
WHERE l.chunk = c.chknum AND c.dbsnum = d.dbsnum
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.