1

Topic: Poor performance after recovery from TSM

I welcome experts DB2. I ask the help.
There is a basis on 500. Translated it  bases on TSM. It is periodically necessary to recover it on other servers.
it is executable so

db2cmd-i-w
db2stop force && db2start
db2 drop database DB_NAME
db2 restore database DB_NAME use tsm options '-fromnode=NODE_NAME ' TAKEN AT 20171001201736 on D: into DB_NAME
db2 update db cfg for DB_NAME using logarchmeth1 TSM:DB2DISK
db2 update db cfg for DB_NAME using logarchopt1 "'-fromnode=NODE_NAME '"
db2 update db cfg for DB_NAME using VENDOROPT "'-fromnode=NODE_NAME '"
db2 update db cfg for DB_NAME using TSM_MGMTCLASS ""
db2 rollforward db DB_NAME to 2017-10-03-06.00.00.000000 using local time
db2 rollforward db DB_NAME complete
db2stop force && db2start

Like  would transit without errors, but discovery any more less large table leads to the strong brakes, the processor and a disk subsystem are loaded. About difficult sql-inquiries generally I am silent. In general the basis is not efficient. Where to dig?

2

Re: Poor performance after recovery from TSM

Service after that launch, what indexes in the order to result.

3

Re: Poor performance after recovery from TSM

NaumOff;
What version DB2? What is "table discovery"? How much the configuration of "other servers" differs from on what the backup copy has been made? Generally at backup copy recovery on new "iron" it is necessary to adjust DB parameters under this "iron".

4

Re: Poor performance after recovery from TSM

NaumOff wrote:

Where to dig?

Good afternoon.
Sometimes happens so that on system with  a storage amount it is not activated one or several buffer pools.
It is necessary to look that appears in db2diag.log after recovery.