If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Warning Proc: db2acd 0 after changing the Alias name on database

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-23-10, 11:13
rockycj rockycj is offline
Registered User
 
Join Date: Feb 2007
Posts: 73
Warning Proc: db2acd 0 after changing the Alias name on database

I'm using DB2 v9.1 LUW. Yesterday we changed the Alias name on a database from PS_TRN to PSFTTRN so the Applications team could load data into the database tables.

Now in the db2diag.log there are Warnings of 'Failed connecting to database
"PS_TRN "' on a regular basis...3:03am, 4:03am, 5:08am, 6:03am, etc.

2010-06-23-03.03.40.109729-300 I36926A405 LEVEL: Warning
> PID : 1491134 TID : 772 PROC : db2acd 0
> INSTANCE: db2inst1 NODE : 000
> FUNCTION: DB2 UDB, Health Monitor,
> HmonMainCB::refreshDbAutonomicSwitches, probe:160 MESSAGE : Failed
> connecting to database "PS_TRN "
> DATA #1 : Hexdump, 4 bytes
> 0x000000011051B70C : FFFF 8A93 ....
>
> 2010-06-23-04.03.39.971808-300 I39210A405 LEVEL: Warning
> PID : 1491134 TID : 772 PROC : db2acd 0
> INSTANCE: db2inst1 NODE : 000
> FUNCTION: DB2 UDB, Health Monitor,
> HmonMainCB::refreshDbAutonomicSwitches, probe:160 MESSAGE : Failed
> connecting to database "PS_TRN "
> DATA #1 : Hexdump, 4 bytes
> 0x000000011051B70C : FFFF 8A93 ....
>
> 2010-06-23-05.08.39.532225-300 I41498A405 LEVEL: Warning
> PID : 1491134 TID : 772 PROC : db2acd 0
> INSTANCE: db2inst1 NODE : 000
> FUNCTION: DB2 UDB, Health Monitor,
> HmonMainCB::refreshDbAutonomicSwitches, probe:160 MESSAGE : Failed
> connecting to database "PS_TRN "
> DATA #1 : Hexdump, 4 bytes
> 0x000000011051B70C : FFFF 8A93 ....
>
> 2010-06-23-06.03.39.801813-300 I42845A405 LEVEL: Warning
> PID : 1491134 TID : 772 PROC : db2acd 0
> INSTANCE: db2inst1 NODE : 000
> FUNCTION: DB2 UDB, Health Monitor,
> HmonMainCB::refreshDbAutonomicSwitches, probe:160 MESSAGE : Failed
> connecting to database "PS_TRN "
> DATA #1 : Hexdump, 4 bytes
> 0x000000011051B70C : FFFF 8A93
>
>
> 2010-06-23-07.13.40.458132-300 I45590A405 LEVEL: Warning
> PID : 1491134 TID : 772 PROC : db2acd 0
> INSTANCE: db2inst1 NODE : 000
> FUNCTION: DB2 UDB, Health Monitor,
> HmonMainCB::refreshDbAutonomicSwitches, probe:160 MESSAGE : Failed
> connecting to database "PS_TRN "
> DATA #1 : Hexdump, 4 bytes
> 0x000000011051B70C : FFFF 8A93


The HEALTH_MON=OFF:
Auto restart enabled (AUTORESTART) = OFF
Automatic maintenance (AUTO_MAINT) = OFF
Automatic database backup (AUTO_DB_BACKUP) = OFF
Automatic table maintenance (AUTO_TBL_MAINT) = OFF
Automatic runstats (AUTO_RUNSTATS) = OFF
Automatic statistics profiling (AUTO_STATS_PROF) = OFF
Automatic profile updates (AUTO_PROF_UPD) = OFF
Automatic reorganization (AUTO_REORG) = OFF

In IBM documentation, I did find that db2acd will still wakeup approximately every 2 hours to check for active database automatic maintenance (which is 1 hour in our case). That is fine and would like to keep it that way.

My question is why is it still looking for PS_TRN database and not PSFTTRN database? Is there a setting somewhere on the config file or somewhere else that should be changed for the db2acd (db2hmon)?

db2 list db directory:

Database alias = PSFTTRN
Database name = PS_TRN

We didn't change the Database name yet because it would have taken to long to drop and restore etc...but I'm wondering if that is causing the problem?

Thank you.

CC

Last edited by rockycj; 06-23-10 at 11:49.
Reply With Quote
  #2 (permalink)  
Old 06-23-10, 13:18
blazer789 blazer789 is offline
Registered User
 
Join Date: Jun 2009
Posts: 221
what procedure did you use to change the database alias?

You don't necessarily have to drop and restore the database to change its name. You can try using db2relocatedb command

db2relocatedb - Relocate Database
Reply With Quote
  #3 (permalink)  
Old 06-23-10, 14:56
rockycj rockycj is offline
Registered User
 
Join Date: Feb 2007
Posts: 73
Thanks for the link. We changed the Alias name not the Database name by doing this:

db2 uncatalog db ps_trn

db2 catalog db ps_trn as psfttrn on /db2_data/database

Database 6 entry:

Database alias = PSFTTRN
Database name = PS_TRN
Local database directory = /db2_data/database
Database release level = b.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =


But I do plan on changing the database name at a later point to PSFTTRN because that need to be the same as the new Alias name. Then I can use your link?

CC
Reply With Quote
  #4 (permalink)  
Old 06-24-10, 00:50
blazer789 blazer789 is offline
Registered User
 
Join Date: Jun 2009
Posts: 221
what database alias does it point to when you take a health snapshot ? Did you try bouncing the instance after the change ?
Reply With Quote
  #5 (permalink)  
Old 06-24-10, 09:32
rockycj rockycj is offline
Registered User
 
Join Date: Feb 2007
Posts: 73
The database alias is pointing to PSFTTRN. We did not want to bounce the instance at the time and cannot do this during the day.


devdb$ db2 get health snapshot for db on psfttrn show detail

Database Health Snapshot

Snapshot timestamp = 06/24/2010 08:21:16.034560

Database name = PS_TRN
Database path = /db2_data/database/db2inst1/NODE0000/SQL00008/
Input database alias = PSFTTRN
Operating system running at database server= AIX 64BIT
Location of the database = Local
Database highest severity alert state = Not yet evaluated

Health Indicators:

Not yet evaluated
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On