Running db2updv95 in HADR environment
in [DB2]
|
From: Mark A on 26 Oct 2009 16:31 After a fixpack upgrade on Db2 LUW 9.5, can one run db2updv95 on the Primary database and have everything replicate over to the Standby? Obviously, db2updv95 cannot be run on a standby. Same question for bind of packages Primary (does bind get run on Standby?).
From: Frederik Engelen on 27 Oct 2009 06:49 This command is creating stored procedures, which are somewhat picky in getting replicated. Unless someone knowledgeable enough confirms that it's possible, rebuilding the cluster sounds like a safer idea to me. On Oct 26, 9:31 pm, "Mark A" <no...(a)nowhere.com> wrote: > After a fixpack upgrade on Db2 LUW 9.5, can one run db2updv95 on the Primary > database and have everything replicate over to the Standby? Obviously, > db2updv95 cannot be run on a standby. > > Same question for bind of packages Primary (does bind get run on Standby?).
From: Serge Rielau on 25 Nov 2009 09:10 Frederik Engelen wrote: > This command is creating stored procedures, which are somewhat picky > in getting replicated. > > Unless someone knowledgeable enough confirms that it's possible, > rebuilding the cluster sounds like a safer idea to me. > > On Oct 26, 9:31 pm, "Mark A" <no...(a)nowhere.com> wrote: >> After a fixpack upgrade on Db2 LUW 9.5, can one run db2updv95 on the Primary >> database and have everything replicate over to the Standby? Obviously, >> db2updv95 cannot be run on a standby. >> >> Same question for bind of packages Primary (does bind get run on Standby?). > db2updv95 performs operations on the catalogs. These are logged and hence HADR friendly. Same for binds and rebinds. Cheers Serge -- Serge Rielau SQL Architect DB2 for LUW IBM Toronto Lab
From: Frederik Engelen on 26 Nov 2009 05:16 On Nov 25, 3:10 pm, Serge Rielau <srie...(a)ca.ibm.com> wrote: > Frederik Engelen wrote: > > This command is creating stored procedures, which are somewhat picky > > in getting replicated. > > > Unless someone knowledgeable enough confirms that it's possible, > > rebuilding the cluster sounds like a safer idea to me. > > > On Oct 26, 9:31 pm, "Mark A" <no...(a)nowhere.com> wrote: > >> After a fixpack upgrade on Db2 LUW 9.5, can one run db2updv95 on the Primary > >> database and have everything replicate over to the Standby? Obviously, > >> db2updv95 cannot be run on a standby. > > >> Same question for bind of packages Primary (does bind get run on Standby?). > > db2updv95 performs operations on the catalogs. These are logged and > hence HADR friendly. > Same for binds and rebinds. > > Cheers > Serge > > -- > Serge Rielau > SQL Architect DB2 for LUW > IBM Toronto Lab The documentation for the db2updv95 mentions: - Creation of any new procedures available in the fix pack level that you are installing. Stored procedures are not replicated through HADR. Do you know what kind of procedures are they talking about here? Kind regards, Frederik Engelen
From: Ian on 26 Nov 2009 05:45
Frederik Engelen wrote: > The documentation for the db2updv95 mentions: > - Creation of any new procedures available in the fix pack level that > you are installing. > > Stored procedures are not replicated through HADR. Do you know what > kind of procedures are they talking about here? The implementations (i.e. binaries) of *external* stored procedures and UDFs (i.e. code written in C, Java) are not replicated, although the definition (in the database catalog) of these stored procedures *is*. Many of the stored procedures (and UDFs) that IBM provides are implemented as external routines. The binaries (located in ..../sqllib/function) are updated when you run `db2iupdt`. Running `db2updv95` registers new external routines in the catalogs. What this is saying is that you have to make sure that you have properly updated your instance on the standby server (`db2iupdt`). Note: SQL stored procedures are replicated. |