andyjjones
Active Newcomer
- Joined
- Nov 14, 2011
- Messages
- 6
- Reaction score
- 0
- Points
- 0
Why does Tivoli client go into IDLE state when processing large amount of journal entries (+100,000) ??
-
-
Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
Journal backups...
- Thread starter andyjjones
- Start date
marclant
ADSM.ORG Moderator
What do you mean by IDLE state? Do you mean the session on the server is in IdleW? If so, is there more than one session for that client and if so, in what state is the other(s)?
The client usually starts two sessions with the server, one to do queries and updates to the DB (producer) and a second to transfer the data (consumer). With the journal, the producer hardly has any work to do, since the journal determined what to backup already, so the consumer does most of the work. So it would be normal for one of the sessions to go in IdleW.
The client usually starts two sessions with the server, one to do queries and updates to the DB (producer) and a second to transfer the data (consumer). With the journal, the producer hardly has any work to do, since the journal determined what to backup already, so the consumer does most of the work. So it would be normal for one of the sessions to go in IdleW.
