[cisco-voip] CIPT Optimization job causes ccm.exe to terminate unexpectedly

[Erick Bergquist]

Update to this. Got the cdr files down in size by manually shrinking them. CIPT job still running with no problems.

Thanks Wes

----- Original Message ----
From: Erick Bergquist <erickbe at yahoo.com>
To: Wes Sisk <wsisk at cisco.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Sunday, August 27, 2006 9:09:25 AM
Subject: Re: [cisco-voip] CIPT Optimization job causes ccm.exe to terminate unexpectedly

Ok. Earlier I had stepped through the steps in the SQL job manually and the first step that deals with CDR was step taking awhile and during that job phones and such unregistered but ccm stayed up. The other steps ran fine to without issue. 

The BARS backup was successful and writing to it's destination fine, log showed it truncating cdr fine, etc. 

I ended up fixing it (hopefully) by manually purging the CDR database a few times to get the record count down, then running BARS manually, and after that the CIPT SQL Job step1 is down to 1 minute or so from 8 minutes. And nothing is unregistering/etc when the SQL CIPT job is ran now.

The CDR Database is still at 980 meg and the associated log file about 470 meg. These are the same filesizes as before so with the work done, these do not appear to have gotten smaller in size.

Thanks, Erick

----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Saturday, August 26, 2006 7:22:37 PM
Subject: Re: [cisco-voip] CIPT Optimization job causes ccm.exe to terminate unexpectedly

Yes,

This typically happens when one of the database transaction logs are  
large.  The job spikes the CPU and starves CM for processing time.

1. verify the size of the transaction logs.  Generally around 30-50%  
of corresponding db size is 'normal'.

2. Run the steps of the job manually to make sure you are not getting  
errors from the steps
In SQL Enterprise Manager
Management
SQL Server Agents
Jobs
right click on the job
properties
steps
edit

copy out the text of the step and paste it into SQL Query Analyzer.   
Run that job. Look at the output for anything suspicious.  Also note  
which step is taking so long to complete and taking the most CPU or  
disk I/O.  Investigate that database further.

Last time I ran into this it was because the backup destination
1. had insufficient storage space and
2. had a speed/duplex mismatch
this caused the nightly backup to fail in such a way that BARS never  
shrunk the transaction logs for the CCM and CDR databases.

/Wes

On Aug 26, 2006, at 7:20 PM, Erick Bergquist wrote:

Has anyone seen the CIPT Optimization SQL job cause CCM to crash before?
This is on a CCM 3.3(4)sr2 system w/OS 2000.2-6sr4 (SQL SP3a). Have  
tried to adjust the time of the job away from other tasks so it is  
only thing running and it still crashes. The SQL job completes  
succesfully and is taking 8 to 9 minutes on average to complete. CCM  
fails usually 4 or 5 minutes after job starts.

Thanks, Erick

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip





_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip