Results 1 to 4 of 4
  1. #1
    Join Date
    Aug 2013
    Posts
    80

    Unanswered: db2start and activate database

    Hi All,
    Just curious after db started, in generally why should we perform activate database ? if yes what's the activities will start by activate database command ? In fact, after db2start, all the application is ready to connect to database. What's the impact if database to activate and running , any performance issues ?

    Thanks.

  2. #2
    Join Date
    May 2010
    Location
    India
    Posts
    84
    Provided Answers: 2
    db2start is for starting db2 instance. Activate database is for starting database. You can have multiple databases under one instance and activate(start)/deactivate(stop) them independently.

    Database started using activate database will be up even when there are no connections to database. If activate database is not used to start database, database is started when first connection attempt is made and stopped when there are no connections to database. Not using activate database to start database could be the possible reason why you are having intermittent slow performance mentioned in your other thread.

  3. #3
    Join Date
    Aug 2013
    Posts
    80
    Hi stiruvee,
    thanks for reply. But the activate database still didn't resolved the performance issue even the database had been activated.

    any others possible reason that causing the slowness ?


    thanks

  4. #4
    Join Date
    Jan 2009
    Location
    Zoetermeer, Holland
    Posts
    746
    When you have J2EE appserver as client (almost always) then the 'activate database' is not a big issue because there are always active connections (connection pool). Normaly the first client who logs on will start the database and that can take some time. When the database is stopped (last client logged off) the package-cache and buffer pools are gone. So when the database is started again by the next client all the cached data from the previous session is gone. Can be avoided by activating the database.

    n.b. when you want to use ATS (db2 task scheduler) you must activate the database, even when you have constant connections.
    Somewhere between " too small" and " too large" lies the size that is just right.
    - Scott Hayes

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •