Hi all -

Running LUW 9.1 under AIX 6 but this applies more generally I believe
to DB2 across all platforms.

I'm restoring DB X from one lpar (LPAR_A) to another (LPAR_B).
Database DB X exists on LPAR_B so this is a 'replace existing'
situation.

Now, having done this many times over the years I see inconsistent
behavior out of DB2 after the restore when it comes to the DB
configuration of DB X on LPAR_B. I expect to see the DB configuration
parms restored to the same as what they are on LPAR_A and it looks
like sometimes those settings DO get restored along with the data yet
other times they do not.

It just seems to me that if I restore a DB that the CFG Parms should
be restored as well...or at least given the option to make 'em the
same or not.

What's the rule? I can't find any documentation from IBM on this
subject.

Thanks in Advance,

-B

On Jul 7, 9:14*am, Bruce <bwmille... (AT) gmail (DOT) com> wrote:
Some more clarification...

The database seeds were different...DB X on LPAR_A was created using
'db2 create DB' and not originally from a DB restore from LPAR_B which
occurred later.

Documentation from the "Data Recovery and High Availability Guide and
Reference V9.7 Page 268" book:


Compares the database seeds. If the seeds are different:
<============== which they are
– Deletes the logs associated with the existing database.
– Copies the database configuration file from the backup image.
<=========== but the cfg parms WERE different after the restore...
– Sets NEWLOGPATH to the value of the logpath database configuration
parameter if NEWLOGPATH was specified on the RESTORE DATABASE
command.

If the database seeds are the same:
– Deletes the logs if the image is for a non-recoverable database.
– Retains the current database configuration file.
– Sets NEWLOGPATH to the value of the logpath database configuration
parameter if NEWLOGPATH was specified on the RESTORE DATABASE
command; otherwise, copies the current log path to the database
configuration file. Validates the log path: If the path cannot be used
by the
database, changes the database configuration to use the default log
path.

-Confused

Hi Bruce,

On 07.07.11 9:49 , Bruce wrote:
Don't be. You were right! In your case the database parameters should have
been applied to the target database (since your database seeds are different).

If they are not, you might have found a bug.
I suggest to open a PMR.

--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab

On Jul 8, 3:34*pm, Helmut Tessarek <tessa... (AT) evermeet (DOT) cx> wrote:
thanks Helmut!