[cisco-voip] DST Patch didn't update TypeTimeZone table?

[Ryan Ratliff]

The CCM030X with the highest value X is your current database.  There  
are a few reasons we keep the previous CCM database around but since  
it is so small it's not a big deal.

In your case the CCM0305 db shouldn't be used by anything so it not  
being updated won't cause any problems.

-Ryan

On Mar 12, 2007, at 5:10 PM, Mike Armstrong wrote:

I can confirm the patch did not update CCM0305, but did update  
CCM0306.  Is there any reason we can't just delete older databases?

Mike Armstrong
UF/IFAS CREC
Lake Alfred, FL

> Date: Mon, 12 Mar 2007 15:52:33 -0400
> From: Ryan Ratliff <rratliff at cisco.com>
> Subject: Re: [cisco-voip] DST Patch didn't update TypeTimeZone table?
> To: Jason Aarons ((US)) <jason.aarons at us.didata.com>
> Cc: cisco-voip at puck.nether.net
> Message-ID: <C7C5CAE5-34C9-4922-A38A-226872BEC853 at cisco.com>
> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
> format=flowed
>
> Do they have multiple CCM030X databases by any chance?  If so did any
> of them get updated?
>
> All of the issues I've personally seen have been either the CM DST
> patch never applied or the DevPack was applied after the DST patch
> and the changes were lost.
>
> -Ryan
>
> On Mar 12, 2007, at 3:42 PM, Jason Aarons ((US)) wrote:
>
> I have a customer whose 7940/7960s didn?t update, the final update
> applied following the Field Notices step-by-step was ciscocm.
> 4-1-3-2007-DST-Update.1-0-1.exe, the log file for this patch shows
> Completed Successfully, however checking the SQL Table TypeTimeZone
> on publisher didn?t change to the new values. The operating system
> time and everything else looks good. The log file timestamps show
> nothing was applied after ciscocm.4-1-3-2007-DST-Update.1-0-1.exe,
>
>
>
> Anyone else see ciscocm.4-1-3-2007-DST-Update.1-0-1.exe show
> successful in logs but didn?t really update the tables?
>
>
>
>
>
> Jason Aarons