delay in starting applications through sci

[paddy]

Hi guys,

Need some views over here. Am facing a situation whereby when i try to restart a service(say for an example; TServer), it takes me almost 30 mins to do so. Also recently, the database servers that stores all the genesys database gotten full thus genesys_log database is now in the suspect status. When i googled for the 'suspect' error, it's said that it could have happened due to the space prob and the solution given was to restart the sqlserver and run some script but there's no guarantee tat tis method might work.

Am confused..What should i do in order to change the status of the genesys_log and also what possibly could be the reason of the delay in SCI...Has anyone faced this b4?

Thank you

[René]

Hi,

You're writing about delay when restarting TServer. Does it mean that time between TServer is up and running and time when you started it via SCI is 30 minutes? That sounds very strange... If I do understand you correctly then few things you should check:
- Check TServer log - does it really start at the same time you click "Start" in SCI?
- LCA log - check it receives commands from SCS, check for any errors

About your database issue - I do see any connection between delay in TServer start and full log DB. TServer never connects directly to LOG database - that's job of Message Server.

R.

[kbs]

Theres a lot of possible things to look at:
- What is your logging level? Does it start faster if you set logging to Standard for the suspect applications?
- Where is logging being sent to? If disk, is buffering = true?
- What is the size of your log files (segment option)
- Disk space on the server
- For TServer and Config Server - how many objects are in your environment?
- Has any work been done on the network lately, possibly changing the speed of the NIC?
- For the application in question, what do the logs say? Are there any log entries indicating "waiting for ..." or "could not connect to ..." (I'm paraphrasing, but you get the idea).
- Has it always been this way, or has it recently started? If recent, review what may have changed in your infrastructure (including things you are not directly responsible for).