Prev: knowing if an NLI is active or has occurred recently
Next: DB2 UDB Security Best Practices documentation
From: Bruce on 23 Apr 2010 07:42
On Apr 22, 11:25 am, Naresh Chainani <fornar...(a)gmail.com> wrote:
> On Apr 22, 5:35 am, Bruce <bwmille...(a)gmail.com> wrote:
>
>
>
>
>
> > On Apr 21, 7:47 pm, "Mark A" <no...(a)nowhere.com> wrote:
>
> > > "The Boss" <use...(a)No.Spam.Please.invalid> wrote in message
>
> > >news:4bcf7ed0$0$4570$e4fe514c(a)dreader30.news.xs4all.nl...
>
> > > > It doesn't, and you shouldn't use NLI in a HADR environment.
> > > > Please read my previous reply I posted about 24 hours ago.
>
> > > > --
> > > > Jeroen
>
> > > Bruce understands that one should not use it an HADR environment, but he
> > > needs to check to see if someone else did it.
>
> > Right...HADR has literally saved our B**T many times and we absolutely
> > positively need it...Do I wish that PeopleSoft didn't use NLI?  Sure,
> > but it does and there isn't a way around it.  So, I'm stuck with what
> > I've been given.  Now, back to the question: "How can I know from
> > looking at something in DB2 if HADR has been compromised from an NLI-
> > standpoint?".
>
> Among other places, DB2 stores table information in packed
> descriptors. The NLI-attribute of a table is present there and the
> packed descriptor can be dumped using db2cat. I understand you are
> looking for something that you could query, but I am not aware of any.
>
> db2 "CREATE TABLE PARTTABNLI (ID INT, ALPHA VARCHAR(20)) PARTITION BY
> RANGE (ID) (STARTING FROM (1) ENDING AT (150) EVERY(10) , STARTING
> FROM (200) ENDING AT (250) EVERY (10)) NOT LOGGED INITIALLY"
>
> db2cat -db eee -n PARTTABNLI -s NARESH -t | grep  "Table not logged"
>  Table not logged          : 1
>
> The 'Table not logged' field is set to 0, if NLI attribute is not
> specified during table creation.
>
> Perhaps this could serve as your alternative mechanism to validate
> whether any table is created as NLI. You should be able to automate
> this by querying the database for all tables of interest and invoking
> db2cat.
>
> Naresh

Naresh, thank you very much for this...Your time to help me is very
much appreciated!

-Bruce
From: Bruce on 22 Apr 2010 08:35
On Apr 21, 7:47 pm, "Mark A" <no...(a)nowhere.com> wrote:
> "The Boss" <use...(a)No.Spam.Please.invalid> wrote in message
>
> news:4bcf7ed0$0$4570$e4fe514c(a)dreader30.news.xs4all.nl...
>
> > It doesn't, and you shouldn't use NLI in a HADR environment.
> > Please read my previous reply I posted about 24 hours ago.
>
> > --
> > Jeroen
>
> Bruce understands that one should not use it an HADR environment, but he
> needs to check to see if someone else did it.

Right...HADR has literally saved our B**T many times and we absolutely
positively need it...Do I wish that PeopleSoft didn't use NLI? Sure,
but it does and there isn't a way around it. So, I'm stuck with what
I've been given. Now, back to the question: "How can I know from
looking at something in DB2 if HADR has been compromised from an NLI-
standpoint?".
From: Bruce on 21 Apr 2010 08:04
On Apr 21, 12:38 am, Ian <ianb...(a)mobileaudio.com> wrote:
> On 4/20/10 12:21 PM, Bruce wrote:
>
>
>
>
>
> > On Apr 20, 1:33 pm, "Mark A"<no...(a)nowhere.com>  wrote:
> >> "Bruce"<bwmille...(a)gmail.com>  wrote in message
>
> >>news:ae7155e6-6ce7-49b0-9ccb-f4a5f441748e(a)22g2000vbg.googlegroups.com....
>
> >>> Hi all -
>
> >>> Running AIX 6, UDB 9.1.4.
>
> >>> Other than referring to the db2inst1.nfy log is there anyway to know
> >>> if a table has been created with 'not logged initially'?   I need
> >>> something that I can query to determine the NLI status.
>
> >>> Thanks,
>
> >>> Bruce
>
> >> Did you try db2look? You can pull DDL for one table with -t option
>
> It used to be that unless you specified "NOT LOGGED INITIALLY" when you
> created a table you could not use "ALTER TABLE ... NOT LOGGED
> INITIALLY."  However, this changed a LONG time ago -- perhaps in V7.1,
> maybe earlier -- such that you no longer have allow this for a table
> when you create the table.
>
> > I need something 'queryable'...where does DB2 store the info re: the
> > NLI?  its one thing to create a TABLE with NLI but another thing
> > entirely to know that its done the load and that the NLI option is,
> > essentially, complete.    I need to know that my HADR standby is trust-
> > worthy.
>
> Did you try SYSIBMADM.PDLOGMSGS_LAST24HOURS ?  As in:
>
>     select timestamp, msg
>     from   sysibmadm.pdlogmsgs_last24hours
>     where  msgnum = 5530;
>
> This (of course) only shows you events from the last 24 hours, so if
> you want to see older you would have to look at db2diag.log.  You can
> do this quite easily using db2diag:
>
>     db2diag -H 36h -g msg:=ADM5530W

Thank You. Yes this is more towards what I need...but it appears that
SYSIBMADM.PDLOGMSGS_LAST24HOURS simply goes out to the .nfy log and
simply dumps what's already there...I'm already scanning my db2diag
and .nfy logs for this NLI info but it means I can do a SELECT to get
the data instead of hassling with GREP. Again, I'm looking for a
short list of those tables that may be inconsistent or marked 'bad' on
the HADR standby-side to determine which tables need to be rebuilt due
to an NLI. I'm simply not seeing what I need.

Where does db2 store the info on these NLI tables on the standby-side?
From: The Boss on 21 Apr 2010 18:40
Bruce wrote:
> On Apr 21, 12:38 am, Ian <ianb...(a)mobileaudio.com> wrote:
>> On 4/20/10 12:21 PM, Bruce wrote:
>>
>>
>>
>>
>>
>>> On Apr 20, 1:33 pm, "Mark A"<no...(a)nowhere.com> wrote:
>>>> "Bruce"<bwmille...(a)gmail.com> wrote in message
>>
>>>> news:ae7155e6-6ce7-49b0-9ccb-f4a5f441748e(a)22g2000vbg.googlegroups.com...
>>
>>>>> Hi all -
>>
>>>>> Running AIX 6, UDB 9.1.4.
>>
>>>>> Other than referring to the db2inst1.nfy log is there anyway to
>>>>> know if a table has been created with 'not logged initially'? I
>>>>> need something that I can query to determine the NLI status.
>>
>>>>> Thanks,
>>
>>>>> Bruce
>>
>>>> Did you try db2look? You can pull DDL for one table with -t option
>>
>> It used to be that unless you specified "NOT LOGGED INITIALLY" when
>> you created a table you could not use "ALTER TABLE ... NOT LOGGED
>> INITIALLY." However, this changed a LONG time ago -- perhaps in V7.1,
>> maybe earlier -- such that you no longer have allow this for a table
>> when you create the table.
>>
>>> I need something 'queryable'...where does DB2 store the info re: the
>>> NLI? its one thing to create a TABLE with NLI but another thing
>>> entirely to know that its done the load and that the NLI option is,
>>> essentially, complete. I need to know that my HADR standby is trust-
>>> worthy.
>>
>> Did you try SYSIBMADM.PDLOGMSGS_LAST24HOURS ? As in:
>>
>> select timestamp, msg
>> from sysibmadm.pdlogmsgs_last24hours
>> where msgnum = 5530;
>>
>> This (of course) only shows you events from the last 24 hours, so if
>> you want to see older you would have to look at db2diag.log. You can
>> do this quite easily using db2diag:
>>
>> db2diag -H 36h -g msg:=ADM5530W
>
> Thank You. Yes this is more towards what I need...but it appears that
> SYSIBMADM.PDLOGMSGS_LAST24HOURS simply goes out to the .nfy log and
> simply dumps what's already there...I'm already scanning my db2diag
> and .nfy logs for this NLI info but it means I can do a SELECT to get
> the data instead of hassling with GREP. Again, I'm looking for a
> short list of those tables that may be inconsistent or marked 'bad' on
> the HADR standby-side to determine which tables need to be rebuilt due
> to an NLI. I'm simply not seeing what I need.
>
> Where does db2 store the info on these NLI tables on the standby-side?

It doesn't, and you shouldn't use NLI in a HADR environment.
Please read my previous reply I posted about 24 hours ago.

--
Jeroen


From: Mark A on 21 Apr 2010 19:47
"The Boss" <usenet(a)No.Spam.Please.invalid> wrote in message
news:4bcf7ed0$0$4570$e4fe514c(a)dreader30.news.xs4all.nl...
> It doesn't, and you shouldn't use NLI in a HADR environment.
> Please read my previous reply I posted about 24 hours ago.
>
> --
> Jeroen

Bruce understands that one should not use it an HADR environment, but he
needs to check to see if someone else did it.


First  |  Prev  | 
Pages: 1 2
Prev: knowing if an NLI is active or has occurred recently
Next: DB2 UDB Security Best Practices documentation