From: Serge Rielau on
Ian wrote:
> 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.
>
Correct on all accounts.


--
Serge Rielau
SQL Architect DB2 for LUW
IBM Toronto Lab
From: Frederik Engelen on
On Nov 26, 3:00 pm, Serge Rielau <srie...(a)ca.ibm.com> wrote:
> Ian wrote:
> > 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.
>
> Correct on all accounts.
>
> --
> Serge Rielau
> SQL Architect DB2 for LUW
> IBM Toronto Lab

Ian,

It's clear now, I misread

"HADR does not replicate stored procedure and UDF object and library
files."

as two seperate things ("stored procedures" and "UDF object and
library files").

Thanks for your explanation.

Kind regards,

Frederik
From: Frederik Engelen on
On Nov 26, 11:45 am, Ian <ianb...(a)mobileaudio.com> wrote:
> 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.

Ok, I understand now. Thanks for the explanation.