Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2013-03-22T15:29:17Z by SystemAdmin
SystemAdmin
SystemAdmin
17917 Posts
ACCEPTED ANSWER

Pinned topic db2fodc -preupgrade errors

‏2013-03-22T15:24:15Z |
This is on DB2 9.7.6 WSE 64-bit on W2k8 R2.
I am testing the upgrade procedures for DB2 10.1 and trying to perform the "Gathering pre-upgrade diagnostic information" step which calls
for db2fodc -preupgrade -db on all databases. I have been only semi-successful at that.

The sample database went OK:
C:\Program Files\IBM\SQLLIB\BIN>db2fodc -preupgrade -db sample
**********************WARNING***********************
  • This tool should be run with caution. *
  • It can cause significant performance *
  • degradation, especially on busy systems with a *
  • high number of active connections *
  • *
  • Run times indicated below are estimates based *
  • on test runs. Your actual run times might vary, *
  • dependent on factors such as your hardware *
  • specifications, operating system configuration, *
  • and current workload *
****************************************************
Script is running with following parameters
DATABASE : sample
COLLECTION_MODE : LIGHT
FODCPATH : C:\ProgramData\\IBM\DB2\DB2C00\DB2\FODC_Preupgrade_2013-03-21-16.19.36.356000_0000
DYNAMIC_SQL_LIMIT : 20
DYN_SQL_FILE :
COLLECTION_DURATION : 20
COLLECTION_ITERATION : 5
MEMBERS :
DB2PD_OPTIONS : "-agent -apinfo -active -tran -locks -bufferpools -dbptnmem -memset -mempool -sort -fcm hwm -dyn "

But the TOOLSDB and a database for another application did not:

C:\Program Files\IBM\SQLLIB\BIN>db2fodc -preupgrade -db toolsdb
**********************WARNING***********************
  • This tool should be run with caution. *
  • It can cause significant performance *
  • degradation, especially on busy systems with a *
  • high number of active connections *
  • *
  • Run times indicated below are estimates based *
  • on test runs. Your actual run times might vary, *
  • dependent on factors such as your hardware *
  • specifications, operating system configuration, *
  • and current workload *
****************************************************
Script is running with following parameters
DATABASE : toolsdb
COLLECTION_MODE : LIGHT
FODCPATH : C:\ProgramData\\IBM\DB2\DB2C00\DB2\FODC_Preupgrade_2013-03-21-16.37.53.055000_0000
DYNAMIC_SQL_LIMIT : 20
DYN_SQL_FILE :
COLLECTION_DURATION : 20
COLLECTION_ITERATION : 5
MEMBERS :
DB2PD_OPTIONS : "-agent -apinfo -active -tran -locks -bufferpools -dbptnmem -memset -mempool -sort -fcm hwm -dyn "
The process cannot access the file because it is being used by another process.
The system cannot find the file C:\ProgramData\\IBM\DB2\DB2C00\DB2\FODC_Preupgrade_2013-03-21-16.37.53.055000_0000\db2fodc.log.
The system cannot find the file C:\ProgramData\\IBM\DB2\DB2C00\DB2\FODC_Preupgrade_2013-03-21-16.37.53.055000_0000\db2fodc.log.
The system cannot find the file C:\ProgramData\\IBM\DB2\DB2C00\DB2\FODC_Preupgrade_2013-03-21-16.37.53.055000_0000\db2fodc.log.
The system cannot find the file C:\ProgramData\\IBM\DB2\DB2C00\DB2\FODC_Preupgrade_2013-03-21-16.37.53.055000_0000\db2fodc.log.
...and so on. It ultimately does finish, but I am not sure if I can trust the results.

I have verified and the file referenced is there, which leads me to believe it may be some kind of rights issue or, that the "\\" in the file name is a problem for the file system. It does not seem to be for command line utilities like "dir" or "type" or "find", but it is a problem for Windows Explorer.

Two questions:
1) How do I know when db2fodc -preupgrade has successfully finished its run and its results are complete and valid.
2) Is there something I am doing incorrectly? Or is this a bug in the program?
Updated on 2013-03-22T15:29:17Z at 2013-03-22T15:29:17Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    17917 Posts
    ACCEPTED ANSWER

    Re: db2fodc -preupgrade errors

    ‏2013-03-22T15:29:17Z  in response to SystemAdmin
    I did find that DB2INSTPROF registry setting was set to C:\ProgramData\\IBM\DB2\DB2C00. I have corrected it, and I am re-running db2fodc - I'll update the post with the new results.