| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-02-04 : 00:42:18
|
| Marge Lewek writes "I am running backups of the log files. I have been getting the above error in SQL Sever Agent on my log backups. Lets say the last tran backup is set for 6pm.. @ 5 pm it backs up the log then stops and disables the schedule?? I created the jobs through db maintenance plan in sql server 7 EM??No One has been able to answer what this error is. I have searched every where - Even on MS web site nothing comes up when I enter the error message. Checked sysmessages for error # [192] in model it says "The scale must be less than or equal to the precision" whatever that means?I have deleted and recreated the jobs but it still happens.I even created a separte job for each day of the week, but it still happens.Any ideas??? HELP....Thanks in advance" |
|
|
chadmat
The Chadinator
1974 Posts |
|
|
DGMelkin
Starting Member
24 Posts |
Posted - 2002-02-04 : 14:26:26
|
| Try deleting the schedule from the SQL Agent-Jobs tree in EM (and not from the maintenance plan tree) and creating a new one for the same times. We were having problems when creating jobs from scripts where the schedule would disable itself and this was the only way we had to fix it. (That is, without opening a PSS with Microsoft. It was a different problem, but I bet they're related.)-D |
 |
|
|
melewek
Starting Member
4 Posts |
Posted - 2002-02-04 : 14:59:40
|
| Chad - thanks for the info, i too had read about this fix forss2000, but we are ss7....i did try the workaround but it still did not work. i couldn't find anything relating to ss7 and this prob, other than other people with same prob but no resolution.... |
|
|
|
melewek
Starting Member
4 Posts |
Posted - 2002-02-04 : 15:19:44
|
| dgmelkin- thanks, i will give that a try....i'll let you know... |
|
|
|
melewek
Starting Member
4 Posts |
Posted - 2002-02-06 : 09:36:30
|
| d-tried deleting the schedules under the agent and creating new ones.....no luck...same spin error!!! UGH!! |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-02-06 : 10:35:58
|
| Here's an ass-backwards suggestion, maybe it will work: instead of one job that runs every hour (or every 2 hours, whatever the interval), how about creating multiple jobs that run once a day at the alloted time? While it still has to calculate the next interval, the calculation will be dealing with 1 day increments instead of 1 hour increments, and may avoid the error. |
|
|
|
DGMelkin
Starting Member
24 Posts |
Posted - 2002-02-06 : 11:36:26
|
| Sorry to hear that didn't work. I usually avoid the Maintenance plan altogether for backups; I found I had trouble restoring databases on different servers. You could always try creating the backup jobs separately outside of the DB Maintenance plan.Good luck!-D |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-06 : 12:12:54
|
| Marge,Try this,Add 20 minutes to the active END TIME.So if the schedule currently runs from 6am to 6pm change 6pm to 6:20pm.That should fix it.HTH-Chad |
|
|
|
melewek
Starting Member
4 Posts |
Posted - 2002-02-14 : 10:56:11
|
| adding 20 minutes to the end time worked.....thanks to everyone for all the suggestions. |
|
|
|
|
date calculation spin error (192) when job ends for the day