Welcome! » Log In » Create A New Profile

log not flushing

Posted by Remco Post 
Remco Post
log not flushing
November 09, 2017 04:00AM
Hi All,

for my current customer we’ve build a number of SP 8.1.1 servers. One thing that is new is that sometimes the server doesn’t empty the DB2 active log after a full database backup. The only way it seems that the log gets flushed is by restarting the TSM server. I’ve seen this now 2 or 3 times in the few months that we’re actively using these servers and it makes me feel uneasy. And no, it’s not like the server is very busy, the server was completely idle as far as I can see.

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Marc Lanteigne
Re: log not flushing
November 09, 2017 04:59AM
Hi Remco,

That's normal, that's how active logs work. Only the archive log will be
purged after a database backup.

The active log includes transactions that are in-flight, that is that they
are currently running. The only reason that they go away when you restart
the server is that when the server shuts down, it ends all the
transactions. No transactions=no active logs.

Your server is working normally. Just make sure you have sufficient active
log space and that the filesystem/LUN used for the active log is not shared
with anything.

-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclanteigne@ca.ibm.com
Office Hours: Monday to Friday, 7:00 to 16:00 Eastern

Follow me on: Twitter, developerWorks, LinkedIn


-----Original Message-----
From: Remco Post [mailto:r.post@PLCS.NL]
Sent: Thursday, November 9, 2017 7:59 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] log not flushing

Hi All,

for my current customer we’ve build a number of SP 8.1.1 servers. One thing
that is new is that sometimes the server doesn’t empty the DB2 active log
after a full database backup. The only way it seems that the log gets
flushed is by restarting the TSM server. I’ve seen this now 2 or 3 times in
the few months that we’re actively using these servers and it makes me feel
uneasy. And no, it’s not like the server is very busy, the server was
completely idle as far as I can see.

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Remco Post
Re: log not flushing
November 09, 2017 05:00AM
> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Hi Remco,
>
> That's normal, that's how active logs work. Only the archive log will be
> purged after a database backup.
>
> The active log includes transactions that are in-flight, that is that they
> are currently running. The only reason that they go away when you restart
> the server is that when the server shuts down, it ends all the
> transactions. No transactions=no active logs.
>
> Your server is working normally. Just make sure you have sufficient active
> log space and that the filesystem/LUN used for the active log is not shared
> with anything.

Hi Marc,

you are right, my bad.

But, 96 ff-ing GB of active log on an idle TSM server? no processes, no sessions, nothing… We have configured 128 GB of active log space for these servers, so I guess all I can do is wait until the server crashes?

>
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com
> Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 7:59 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] log not flushing
>
> Hi All,
>
> for my current customer we’ve build a number of SP 8.1.1 servers. One thing
> that is new is that sometimes the server doesn’t empty the DB2 active log
> after a full database backup. The only way it seems that the log gets
> flushed is by restarting the TSM server. I’ve seen this now 2 or 3 times in
> the few months that we’re actively using these servers and it makes me feel
> uneasy. And no, it’s not like the server is very busy, the server was
> completely idle as far as I can see.
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Remco Post
Re: log not flushing
November 09, 2017 05:59AM
> On 9 Nov 2017, at 13:57, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Hi Remco,
>
> When looking at Q LOG F=D, is it 96 GB in " Used Space on File System (MB)"
> or " Used Space(MB)"?
> If the former, that's normal. New log files are created as soon as old
> ones are archived.

I know, so we have 128 GB in use on the filesystem, and about 30 GB free on disk because apparently now a db backup can copy archived log files back to the active log directory.

> If the latter, you may want to revisit the capacity planning to assess if
> 128 GB is sufficient for that environment.

that would make a valid recommendation if the active log was filling up during the backup window, or for that matter any other activity on the server. As stated, this server appears to be idle. No sessions, no processes, no activity whatsoever. So there should be (I guess) also 0 transactions in progress on the database.

( I thought the max was 128 GB, turns out that with 8.1 this has een raised to 512 GB)

>
> For a medium size environment, 128 GB is normally sufficient. For large
> implementations, 256 GB is recommended (in some cases larger).
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com
> Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 8:47 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] log not flushing
>
>> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>>
>>
>> Hi Remco,
>>
>> That's normal, that's how active logs work. Only the archive log will
>> be purged after a database backup.
>>
>> The active log includes transactions that are in-flight, that is that
>> they are currently running. The only reason that they go away when
>> you restart the server is that when the server shuts down, it ends all
>> the transactions. No transactions=no active logs.
>>
>> Your server is working normally. Just make sure you have sufficient
>> active log space and that the filesystem/LUN used for the active log
>> is not shared with anything.
>
> Hi Marc,
>
> you are right, my bad.
>
> But, 96 ff-ing GB of active log on an idle TSM server? no processes, no
> sessions, nothing… We have configured 128 GB of active log space for these
> servers, so I guess all I can do is wait until the server crashes?
>
>>
>> -
>> Thanks,
>> Marc...
>> ________________________________________________________
>> Marc Lanteigne
>> Accelerated Value Specialist for Spectrum Protect
>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>> Friday, 7:00 to 16:00 Eastern
>>
>> Follow me on: Twitter, developerWorks, LinkedIn
>>
>>
>> -----Original Message-----
>> From: Remco Post [mailto:r.post@PLCS.NL]
>> Sent: Thursday, November 9, 2017 7:59 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: [ADSM-L] log not flushing
>>
>> Hi All,
>>
>> for my current customer we’ve build a number of SP 8.1.1 servers. One
>> thing that is new is that sometimes the server doesn’t empty the DB2
>> active log after a full database backup. The only way it seems that
>> the log gets flushed is by restarting the TSM server. I’ve seen this
>> now 2 or 3 times in the few months that we’re actively using these
>> servers and it makes me feel uneasy. And no, it’s not like the server
>> is very busy, the server was completely idle as far as I can see.
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post@plcs.nl
>> +31 6 248 21 622
>>
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Marc Lanteigne
Re: log not flushing
November 09, 2017 05:59AM
Ok, but how much is actually used when looking at Q LOG?

There could also be background tasks running that do not show up in Q PROC
like reorgs for example. No Spectrum Protect activity is not always
synonym to no database activity.l

-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclanteigne@ca.ibm.com
Office Hours: Monday to Friday, 7:00 to 16:00 Eastern

Follow me on: Twitter, developerWorks, LinkedIn


-----Original Message-----
From: Remco Post [mailto:r.post@PLCS.NL]
Sent: Thursday, November 9, 2017 9:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] log not flushing

> On 9 Nov 2017, at 13:57, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Hi Remco,
>
> When looking at Q LOG F=D, is it 96 GB in " Used Space on File System
(MB)"
> or " Used Space(MB)"?
> If the former, that's normal. New log files are created as soon as
> old ones are archived.

I know, so we have 128 GB in use on the filesystem, and about 30 GB free on
disk because apparently now a db backup can copy archived log files back to
the active log directory.

> If the latter, you may want to revisit the capacity planning to assess
> if
> 128 GB is sufficient for that environment.

that would make a valid recommendation if the active log was filling up
during the backup window, or for that matter any other activity on the
server. As stated, this server appears to be idle. No sessions, no
processes, no activity whatsoever. So there should be (I guess) also 0
transactions in progress on the database.

( I thought the max was 128 GB, turns out that with 8.1 this has een raised
to 512 GB)

>
> For a medium size environment, 128 GB is normally sufficient. For
> large implementations, 256 GB is recommended (in some cases larger).
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
> Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 8:47 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] log not flushing
>
>> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM>
wrote:
>>
>>
>> Hi Remco,
>>
>> That's normal, that's how active logs work. Only the archive log
>> will be purged after a database backup.
>>
>> The active log includes transactions that are in-flight, that is that
>> they are currently running. The only reason that they go away when
>> you restart the server is that when the server shuts down, it ends
>> all the transactions. No transactions=no active logs.
>>
>> Your server is working normally. Just make sure you have sufficient
>> active log space and that the filesystem/LUN used for the active log
>> is not shared with anything.
>
> Hi Marc,
>
> you are right, my bad.
>
> But, 96 ff-ing GB of active log on an idle TSM server? no processes,
> no sessions, nothing… We have configured 128 GB of active log space
> for these servers, so I guess all I can do is wait until the server
crashes?
>
>>
>> -
>> Thanks,
>> Marc...
>> ________________________________________________________
>> Marc Lanteigne
>> Accelerated Value Specialist for Spectrum Protect
>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>> Friday, 7:00 to 16:00 Eastern
>>
>> Follow me on: Twitter, developerWorks, LinkedIn
>>
>>
>> -----Original Message-----
>> From: Remco Post [mailto:r.post@PLCS.NL]
>> Sent: Thursday, November 9, 2017 7:59 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: [ADSM-L] log not flushing
>>
>> Hi All,
>>
>> for my current customer we’ve build a number of SP 8.1.1 servers. One
>> thing that is new is that sometimes the server doesn’t empty the DB2
>> active log after a full database backup. The only way it seems that
>> the log gets flushed is by restarting the TSM server. I’ve seen this
>> now 2 or 3 times in the few months that we’re actively using these
>> servers and it makes me feel uneasy. And no, it’s not like the server
>> is very busy, the server was completely idle as far as I can see.
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post@plcs.nl
>> +31 6 248 21 622
>>
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Remco Post
Re: log not flushing
November 09, 2017 05:59AM
> On 9 Nov 2017, at 14:22, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Ok, but how much is actually used when looking at Q LOG?
>

at this moment over 102,000 MB in use, 28, 000 MB free, of in total 131,072 MB, and yes, still raising.

> There could also be background tasks running that do not show up in Q PROC
> like reorgs for example. No Spectrum Protect activity is not always
> synonym to no database activity.l

apparently there is something running, there must be, the log is getting even more full. Unfortunately I have no indication of what it could be. I did search the actlog for reorg processes, and there were some, those have ended. So…. in the end I’ll wind up restarting the instance I guess, to make sure things don’t go wrong during the backup window.

>
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com
> Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 9:16 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] log not flushing
>
>> On 9 Nov 2017, at 13:57, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>>
>>
>> Hi Remco,
>>
>> When looking at Q LOG F=D, is it 96 GB in " Used Space on File System
> (MB)"
>> or " Used Space(MB)"?
>> If the former, that's normal. New log files are created as soon as
>> old ones are archived.
>
> I know, so we have 128 GB in use on the filesystem, and about 30 GB free on
> disk because apparently now a db backup can copy archived log files back to
> the active log directory.
>
>> If the latter, you may want to revisit the capacity planning to assess
>> if
>> 128 GB is sufficient for that environment.
>
> that would make a valid recommendation if the active log was filling up
> during the backup window, or for that matter any other activity on the
> server. As stated, this server appears to be idle. No sessions, no
> processes, no activity whatsoever. So there should be (I guess) also 0
> transactions in progress on the database.
>
> ( I thought the max was 128 GB, turns out that with 8.1 this has een raised
> to 512 GB)
>
>>
>> For a medium size environment, 128 GB is normally sufficient. For
>> large implementations, 256 GB is recommended (in some cases larger).
>> -
>> Thanks,
>> Marc...
>> ________________________________________________________
>> Marc Lanteigne
>> Accelerated Value Specialist for Spectrum Protect
>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>> Friday, 7:00 to 16:00 Eastern
>>
>> Follow me on: Twitter, developerWorks, LinkedIn
>>
>>
>> -----Original Message-----
>> From: Remco Post [mailto:r.post@PLCS.NL]
>> Sent: Thursday, November 9, 2017 8:47 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: [ADSM-L] log not flushing
>>
>>> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM>
> wrote:
>>>
>>>
>>> Hi Remco,
>>>
>>> That's normal, that's how active logs work. Only the archive log
>>> will be purged after a database backup.
>>>
>>> The active log includes transactions that are in-flight, that is that
>>> they are currently running. The only reason that they go away when
>>> you restart the server is that when the server shuts down, it ends
>>> all the transactions. No transactions=no active logs.
>>>
>>> Your server is working normally. Just make sure you have sufficient
>>> active log space and that the filesystem/LUN used for the active log
>>> is not shared with anything.
>>
>> Hi Marc,
>>
>> you are right, my bad.
>>
>> But, 96 ff-ing GB of active log on an idle TSM server? no processes,
>> no sessions, nothing… We have configured 128 GB of active log space
>> for these servers, so I guess all I can do is wait until the server
> crashes?
>>
>>>
>>> -
>>> Thanks,
>>> Marc...
>>> ________________________________________________________
>>> Marc Lanteigne
>>> Accelerated Value Specialist for Spectrum Protect
>>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>>> Friday, 7:00 to 16:00 Eastern
>>>
>>> Follow me on: Twitter, developerWorks, LinkedIn
>>>
>>>
>>> -----Original Message-----
>>> From: Remco Post [mailto:r.post@PLCS.NL]
>>> Sent: Thursday, November 9, 2017 7:59 AM
>>> To: ADSM-L@VM.MARIST.EDU
>>> Subject: [ADSM-L] log not flushing
>>>
>>> Hi All,
>>>
>>> for my current customer we’ve build a number of SP 8.1.1 servers. One
>>> thing that is new is that sometimes the server doesn’t empty the DB2
>>> active log after a full database backup. The only way it seems that
>>> the log gets flushed is by restarting the TSM server. I’ve seen this
>>> now 2 or 3 times in the few months that we’re actively using these
>>> servers and it makes me feel uneasy. And no, it’s not like the server
>>> is very busy, the server was completely idle as far as I can see.
>>>
>>> --
>>>
>>> Met vriendelijke groeten/Kind Regards,
>>>
>>> Remco Post
>>> r.post@plcs.nl
>>> +31 6 248 21 622
>>>
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post@plcs.nl
>> +31 6 248 21 622
>>
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Marc Lanteigne
Re: log not flushing
November 09, 2017 06:59AM
Are you using cloud containers? If so, check:
http://www-01.ibm.com/support/docview.wss?uid=swg1IT18137

Short term, I'd increase the activelog filesystem, and then increase the
activelogsize. It's good that you keep a buffer, filesystem larger than
activelogsize.

Once the server is stable that way, further investigation may be required,
you might need a PMR to look into that.



-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclanteigne@ca.ibm.com
Office Hours: Monday to Friday, 7:00 to 16:00 Eastern

Follow me on: Twitter, developerWorks, LinkedIn


-----Original Message-----
From: Remco Post [mailto:r.post@PLCS.NL]
Sent: Thursday, November 9, 2017 9:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] log not flushing

> On 9 Nov 2017, at 14:22, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Ok, but how much is actually used when looking at Q LOG?
>

at this moment over 102,000 MB in use, 28, 000 MB free, of in total 131,072
MB, and yes, still raising.

> There could also be background tasks running that do not show up in Q
> PROC like reorgs for example. No Spectrum Protect activity is not
> always synonym to no database activity.l

apparently there is something running, there must be, the log is getting
even more full. Unfortunately I have no indication of what it could be. I
did search the actlog for reorg processes, and there were some, those have
ended. So…. in the end I’ll wind up restarting the instance I guess, to
make sure things don’t go wrong during the backup window.

>
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
> Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 9:16 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] log not flushing
>
>> On 9 Nov 2017, at 13:57, Marc Lanteigne <marclanteigne@CA.IBM.COM>
wrote:
>>
>>
>> Hi Remco,
>>
>> When looking at Q LOG F=D, is it 96 GB in " Used Space on File System
> (MB)"
>> or " Used Space(MB)"?
>> If the former, that's normal. New log files are created as soon as
>> old ones are archived.
>
> I know, so we have 128 GB in use on the filesystem, and about 30 GB
> free on disk because apparently now a db backup can copy archived log
> files back to the active log directory.
>
>> If the latter, you may want to revisit the capacity planning to
>> assess if
>> 128 GB is sufficient for that environment.
>
> that would make a valid recommendation if the active log was filling
> up during the backup window, or for that matter any other activity on
> the server. As stated, this server appears to be idle. No sessions, no
> processes, no activity whatsoever. So there should be (I guess) also 0
> transactions in progress on the database.
>
> ( I thought the max was 128 GB, turns out that with 8.1 this has een
> raised to 512 GB)
>
>>
>> For a medium size environment, 128 GB is normally sufficient. For
>> large implementations, 256 GB is recommended (in some cases larger).
>> -
>> Thanks,
>> Marc...
>> ________________________________________________________
>> Marc Lanteigne
>> Accelerated Value Specialist for Spectrum Protect
>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>> Friday, 7:00 to 16:00 Eastern
>>
>> Follow me on: Twitter, developerWorks, LinkedIn
>>
>>
>> -----Original Message-----
>> From: Remco Post [mailto:r.post@PLCS.NL]
>> Sent: Thursday, November 9, 2017 8:47 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: [ADSM-L] log not flushing
>>
>>> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM>
> wrote:
>>>
>>>
>>> Hi Remco,
>>>
>>> That's normal, that's how active logs work. Only the archive log
>>> will be purged after a database backup.
>>>
>>> The active log includes transactions that are in-flight, that is
>>> that they are currently running. The only reason that they go away
>>> when you restart the server is that when the server shuts down, it
>>> ends all the transactions. No transactions=no active logs.
>>>
>>> Your server is working normally. Just make sure you have sufficient
>>> active log space and that the filesystem/LUN used for the active log
>>> is not shared with anything.
>>
>> Hi Marc,
>>
>> you are right, my bad.
>>
>> But, 96 ff-ing GB of active log on an idle TSM server? no processes,
>> no sessions, nothing… We have configured 128 GB of active log space
>> for these servers, so I guess all I can do is wait until the server
> crashes?
>>
>>>
>>> -
>>> Thanks,
>>> Marc...
>>> ________________________________________________________
>>> Marc Lanteigne
>>> Accelerated Value Specialist for Spectrum Protect
>>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>>> Friday, 7:00 to 16:00 Eastern
>>>
>>> Follow me on: Twitter, developerWorks, LinkedIn
>>>
>>>
>>> -----Original Message-----
>>> From: Remco Post [mailto:r.post@PLCS.NL]
>>> Sent: Thursday, November 9, 2017 7:59 AM
>>> To: ADSM-L@VM.MARIST.EDU
>>> Subject: [ADSM-L] log not flushing
>>>
>>> Hi All,
>>>
>>> for my current customer we’ve build a number of SP 8.1.1 servers.
>>> One thing that is new is that sometimes the server doesn’t empty the
>>> DB2 active log after a full database backup. The only way it seems
>>> that the log gets flushed is by restarting the TSM server. I’ve seen
>>> this now 2 or 3 times in the few months that we’re actively using
>>> these servers and it makes me feel uneasy. And no, it’s not like the
>>> server is very busy, the server was completely idle as far as I can
see.
>>>
>>> --
>>>
>>> Met vriendelijke groeten/Kind Regards,
>>>
>>> Remco Post
>>> r.post@plcs.nl
>>> +31 6 248 21 622
>>>
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post@plcs.nl
>> +31 6 248 21 622
>>
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Marc Lanteigne
Re: log not flushing
November 09, 2017 06:59AM
Hi Remco,

When looking at Q LOG F=D, is it 96 GB in " Used Space on File System (MB)"
or " Used Space(MB)"?
If the former, that's normal. New log files are created as soon as old
ones are archived.
If the latter, you may want to revisit the capacity planning to assess if
128 GB is sufficient for that environment.

For a medium size environment, 128 GB is normally sufficient. For large
implementations, 256 GB is recommended (in some cases larger).
-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Accelerated Value Specialist for Spectrum Protect
416.478.0233 | marclanteigne@ca.ibm.com
Office Hours: Monday to Friday, 7:00 to 16:00 Eastern

Follow me on: Twitter, developerWorks, LinkedIn


-----Original Message-----
From: Remco Post [mailto:r.post@PLCS.NL]
Sent: Thursday, November 9, 2017 8:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] log not flushing

> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Hi Remco,
>
> That's normal, that's how active logs work. Only the archive log will
> be purged after a database backup.
>
> The active log includes transactions that are in-flight, that is that
> they are currently running. The only reason that they go away when
> you restart the server is that when the server shuts down, it ends all
> the transactions. No transactions=no active logs.
>
> Your server is working normally. Just make sure you have sufficient
> active log space and that the filesystem/LUN used for the active log
> is not shared with anything.

Hi Marc,

you are right, my bad.

But, 96 ff-ing GB of active log on an idle TSM server? no processes, no
sessions, nothing… We have configured 128 GB of active log space for these
servers, so I guess all I can do is wait until the server crashes?

>
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
> Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 7:59 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] log not flushing
>
> Hi All,
>
> for my current customer we’ve build a number of SP 8.1.1 servers. One
> thing that is new is that sometimes the server doesn’t empty the DB2
> active log after a full database backup. The only way it seems that
> the log gets flushed is by restarting the TSM server. I’ve seen this
> now 2 or 3 times in the few months that we’re actively using these
> servers and it makes me feel uneasy. And no, it’s not like the server
> is very busy, the server was completely idle as far as I can see.
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Skylar Thompson
Re: log not flushing
November 09, 2017 07:00AM
Content preview: Hi Remco, This sounds like database reorganization to me.
You can verify by looking for ANR0293I ("reorganization for table ... started")
and ANR0294I ("reorganization for table ... ended") messages in the activity
log. There are some server option tunings you can do to control it (ALLOWREORGTABLE,
ALLOWREORGINDEX, REORGBEGINTIME, REORGDURATION) but in general it's a good
thing for long-term performance and disk utilization. When the server is
otherwise idle is actually the best time to do the reorgs, since it won't
interfere with your production loads. [...]

Content analysis details: (0.7 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
0.7 SPF_NEUTRAL SPF: sender does not match SPF record (neutral)
-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
X-Barracuda-Connect: mx.gs.washington.edu[128.208.8.134]
X-Barracuda-Start-Time: 1510238307
X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384
X-Barracuda-URL: https://148.100.49.27:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 1450
X-Virus-Scanned: by bsmtpd at marist.edu
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.44663
Rule breakdown below
pts rule name description
---- ---------------------- --------------------------------------------------

Hi Remco,

This sounds like database reorganization to me. You can verify by looking
for ANR0293I ("reorganization for table ... started") and ANR0294I
("reorganization for table ... ended") messages in the activity log. There
are some server option tunings you can do to control it (ALLOWREORGTABLE,
ALLOWREORGINDEX, REORGBEGINTIME, REORGDURATION) but in general it's a good
thing for long-term performance and disk utilization. When the server is
otherwise idle is actually the best time to do the reorgs, since it won't interfere
with your production loads.

On Thu, Nov 09, 2017 at 12:57:05PM +0100, Remco Post wrote:
> Hi All,
>
> for my current customer we???ve build a number of SP 8.1.1 servers. One thing that is new is that sometimes the server doesn???t empty the DB2 active log after a full database backup. The only way it seems that the log gets flushed is by restarting the TSM server. I???ve seen this now 2 or 3 times in the few months that we???re actively using these servers and it makes me feel uneasy. And no, it???s not like the server is very busy, the server was completely idle as far as I can see.
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622

--
-- Skylar Thompson (skylar2@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine
This message was imported via the External PhorumMail Module
Remco Post
Re: log not flushing
November 09, 2017 08:59AM
> On 9 Nov 2017, at 15:38, Skylar Thompson <skylar2@U.WASHINGTON.EDU> wrote:
>
>
> Hi Remco,
>
> This sounds like database reorganization to me. You can verify by looking
> for ANR0293I ("reorganization for table ... started") and ANR0294I
> ("reorganization for table ... ended") messages in the activity log. There
> are some server option tunings you can do to control it (ALLOWREORGTABLE,
> ALLOWREORGINDEX, REORGBEGINTIME, REORGDURATION) but in general it's a good
> thing for long-term performance and disk utilization. When the server is
> otherwise idle is actually the best time to do the reorgs, since it won't interfere
> with your production loads.
>

Skylar,

we do (and maybe should reconsider) have allowreorgtable set to no. Index reorg were running yesterday, right in the window between reorgbegintime and reorgduration. So, again, a potential candidate but no, not it.

> On Thu, Nov 09, 2017 at 12:57:05PM +0100, Remco Post wrote:
>> Hi All,
>>
>> for my current customer we???ve build a number of SP 8.1.1 servers. One thing that is new is that sometimes the server doesn???t empty the DB2 active log after a full database backup. The only way it seems that the log gets flushed is by restarting the TSM server. I???ve seen this now 2 or 3 times in the few months that we???re actively using these servers and it makes me feel uneasy. And no, it???s not like the server is very busy, the server was completely idle as far as I can see.
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post@plcs.nl
>> +31 6 248 21 622
>
> --
> -- Skylar Thompson (skylar2@u.washington.edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Remco Post
Re: log not flushing
November 16, 2017 04:59AM
> On 9 Nov 2017, at 15:13, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>
>
> Are you using cloud containers? If so, check:
> http://www-01.ibm.com/support/docview.wss?uid=swg1IT18137 http://www-01.ibm.com/support/docview.wss?uid=swg1IT18137

fortunately no ;-)

>
> Short term, I'd increase the activelog filesystem, and then increase the
> activelogsize. It's good that you keep a buffer, filesystem larger than
> activelogsize.

20% over the active log size seems to be a good idea.

>
> Once the server is stable that way, further investigation may be required,
> you might need a PMR to look into that.
>

What I found today is a correlation with our nas backup script. This is a fairly long but simple script that runs four ’backup node’ commands in parallel, and that say 20 times over to backup all 80 NAS volumes. On nights where the log starts filling it turns out that this script only starts 3 out of 4 backup node commands. The 4th never really starts, but I guess that there are some things that do get done, like starting a db transaction at some level to start that command. The admin schedule for the NAS backup remains in ’started’ state, but no apparent processes going on….

>
>
> -
> Thanks,
> Marc...
> ________________________________________________________
> Marc Lanteigne
> Accelerated Value Specialist for Spectrum Protect
> 416.478.0233 | marclanteigne@ca.ibm.com
> Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
>
> Follow me on: Twitter, developerWorks, LinkedIn
>
>
> -----Original Message-----
> From: Remco Post [mailto:r.post@PLCS.NL]
> Sent: Thursday, November 9, 2017 9:47 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] log not flushing
>
>> On 9 Nov 2017, at 14:22, Marc Lanteigne <marclanteigne@CA.IBM.COM> wrote:
>>
>>
>> Ok, but how much is actually used when looking at Q LOG?
>>
>
> at this moment over 102,000 MB in use, 28, 000 MB free, of in total 131,072
> MB, and yes, still raising.
>
>> There could also be background tasks running that do not show up in Q
>> PROC like reorgs for example. No Spectrum Protect activity is not
>> always synonym to no database activity.l
>
> apparently there is something running, there must be, the log is getting
> even more full. Unfortunately I have no indication of what it could be. I
> did search the actlog for reorg processes, and there were some, those have
> ended. So…. in the end I’ll wind up restarting the instance I guess, to
> make sure things don’t go wrong during the backup window.
>
>>
>> -
>> Thanks,
>> Marc...
>> ________________________________________________________
>> Marc Lanteigne
>> Accelerated Value Specialist for Spectrum Protect
>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>> Friday, 7:00 to 16:00 Eastern
>>
>> Follow me on: Twitter, developerWorks, LinkedIn
>>
>>
>> -----Original Message-----
>> From: Remco Post [mailto:r.post@PLCS.NL]
>> Sent: Thursday, November 9, 2017 9:16 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: [ADSM-L] log not flushing
>>
>>> On 9 Nov 2017, at 13:57, Marc Lanteigne <marclanteigne@CA.IBM.COM>
> wrote:
>>>
>>>
>>> Hi Remco,
>>>
>>> When looking at Q LOG F=D, is it 96 GB in " Used Space on File System
>> (MB)"
>>> or " Used Space(MB)"?
>>> If the former, that's normal. New log files are created as soon as
>>> old ones are archived.
>>
>> I know, so we have 128 GB in use on the filesystem, and about 30 GB
>> free on disk because apparently now a db backup can copy archived log
>> files back to the active log directory.
>>
>>> If the latter, you may want to revisit the capacity planning to
>>> assess if
>>> 128 GB is sufficient for that environment.
>>
>> that would make a valid recommendation if the active log was filling
>> up during the backup window, or for that matter any other activity on
>> the server. As stated, this server appears to be idle. No sessions, no
>> processes, no activity whatsoever. So there should be (I guess) also 0
>> transactions in progress on the database.
>>
>> ( I thought the max was 128 GB, turns out that with 8.1 this has een
>> raised to 512 GB)
>>
>>>
>>> For a medium size environment, 128 GB is normally sufficient. For
>>> large implementations, 256 GB is recommended (in some cases larger).
>>> -
>>> Thanks,
>>> Marc...
>>> ________________________________________________________
>>> Marc Lanteigne
>>> Accelerated Value Specialist for Spectrum Protect
>>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>>> Friday, 7:00 to 16:00 Eastern
>>>
>>> Follow me on: Twitter, developerWorks, LinkedIn
>>>
>>>
>>> -----Original Message-----
>>> From: Remco Post [mailto:r.post@PLCS.NL]
>>> Sent: Thursday, November 9, 2017 8:47 AM
>>> To: ADSM-L@VM.MARIST.EDU
>>> Subject: Re: [ADSM-L] log not flushing
>>>
>>>> On 9 Nov 2017, at 13:09, Marc Lanteigne <marclanteigne@CA.IBM.COM>
>> wrote:
>>>>
>>>>
>>>> Hi Remco,
>>>>
>>>> That's normal, that's how active logs work. Only the archive log
>>>> will be purged after a database backup.
>>>>
>>>> The active log includes transactions that are in-flight, that is
>>>> that they are currently running. The only reason that they go away
>>>> when you restart the server is that when the server shuts down, it
>>>> ends all the transactions. No transactions=no active logs.
>>>>
>>>> Your server is working normally. Just make sure you have sufficient
>>>> active log space and that the filesystem/LUN used for the active log
>>>> is not shared with anything.
>>>
>>> Hi Marc,
>>>
>>> you are right, my bad.
>>>
>>> But, 96 ff-ing GB of active log on an idle TSM server? no processes,
>>> no sessions, nothing… We have configured 128 GB of active log space
>>> for these servers, so I guess all I can do is wait until the server
>> crashes?
>>>
>>>>
>>>> -
>>>> Thanks,
>>>> Marc...
>>>> ________________________________________________________
>>>> Marc Lanteigne
>>>> Accelerated Value Specialist for Spectrum Protect
>>>> 416.478.0233 | marclanteigne@ca.ibm.com Office Hours: Monday to
>>>> Friday, 7:00 to 16:00 Eastern
>>>>
>>>> Follow me on: Twitter, developerWorks, LinkedIn
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Remco Post [mailto:r.post@PLCS.NL]
>>>> Sent: Thursday, November 9, 2017 7:59 AM
>>>> To: ADSM-L@VM.MARIST.EDU
>>>> Subject: [ADSM-L] log not flushing
>>>>
>>>> Hi All,
>>>>
>>>> for my current customer we’ve build a number of SP 8.1.1 servers.
>>>> One thing that is new is that sometimes the server doesn’t empty the
>>>> DB2 active log after a full database backup. The only way it seems
>>>> that the log gets flushed is by restarting the TSM server. I’ve seen
>>>> this now 2 or 3 times in the few months that we’re actively using
>>>> these servers and it makes me feel uneasy. And no, it’s not like the
>>>> server is very busy, the server was completely idle as far as I can
> see.
>>>>
>>>> --
>>>>
>>>> Met vriendelijke groeten/Kind Regards,
>>>>
>>>> Remco Post
>>>> r.post@plcs.nl
>>>> +31 6 248 21 622
>>>>
>>>
>>> --
>>>
>>> Met vriendelijke groeten/Kind Regards,
>>>
>>> Remco Post
>>> r.post@plcs.nl
>>> +31 6 248 21 622
>>>
>>
>> --
>>
>> Met vriendelijke groeten/Kind Regards,
>>
>> Remco Post
>> r.post@plcs.nl
>> +31 6 248 21 622
>>
>
> --
>
> Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.post@plcs.nl
> +31 6 248 21 622
>

--

Met vriendelijke groeten/Kind Regards,

Remco Post
r.post@plcs.nl
+31 6 248 21 622
This message was imported via the External PhorumMail Module
Sorry, only registered users may post in this forum.

Click here to login