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 > Scheduler not active [DB2 Task Center]

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-16-04, 06:51
Tank Tank is offline
Registered User
 
Join Date: Feb 2004
Location: Copenhagen
Posts: 220
Question Scheduler not active [DB2 Task Center]

Hi Everyone

Im having problems with my scheduler. [DB2 Task Center]

It used to work, I have a toolscatalog in a separate db
on the same instance, and i made sure that the DAS cfg
parameter sched_enable is set to ON.

The things I've changed since the last time i used it:

1. I enabled my database for federation support

2. I activated my database to avoid overhead (and have many users
so I really don' t want to deactivate - unless I have to!)

I'm Running DB2 v 8.1 Fpack 4 on Unix 5.2

Has anyone got a clue or a suggestion?

Sincerely Yours

Kristian (Name - not conviction)
__________________
Kristian K. Hansen
Project Supervisor
National Board of Health
Reply With Quote
  #2 (permalink)  
Old 02-16-04, 08:20
dr_suresh20 dr_suresh20 is offline
Registered User
 
Join Date: Sep 2003
Posts: 218
I had a similar problem on our db2 server and it was resolved by re-creating the "toolsdb". I was able to schedule task from task center. Please make sure you have a backup copy as well.

Hope this helps.
Reply With Quote
  #3 (permalink)  
Old 02-17-04, 10:36
Tank Tank is offline
Registered User
 
Join Date: Feb 2004
Location: Copenhagen
Posts: 220
Thank U

It worked fine, deleting the
old tools db and creating a new

Nevertheless it would be nice
to know the underlying problem...

Thanx again

Kris
Reply With Quote
  #4 (permalink)  
Old 02-20-04, 05:44
dr_suresh20 dr_suresh20 is offline
Registered User
 
Join Date: Sep 2003
Posts: 218
I am just guessing here...

This may be due to internal error or some credentials not identified while DAS is started up.

I have never used the DAS configuration parameter called exec_exp_task myself. This parameter specifies whether or not the scheduler executes the tasks that have been scheduled in the past, but have not yet been run. The scheduler only detects expired tasks when it starts up. But, may be in future we can set this parameter to YES and check if scheduler runs hence we need NOT re-create the db again.

Hope this helps.
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