interface supported: job

Showing posts with label job. Show all posts

Friday, March 30, 2012

Not a BUF latch. Error Re-Indexing

We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>
|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:

> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
>
>

Not a BUF latch. Error Re-Indexing

We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
--
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.
>
>

Not a BUF latch. Error Re-Indexing

We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
Advanced Server.
Weekly we have a job that drops all indexes on the database and recreates
them.
This job runs at the same time the daily backup and transaction log execute.
We received following error caused by the re-index:
"Time out occurred while waiting for buffer latch type 4..."
Please help me resolve these latch errors.
Thanks,
SQL Server errorlog
WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
continuing to wait.
Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0.It not good practice to run such major maintenance operations as dropping
and recreating all indexes (I hope you use DBCC DBREINDEX btw) at the same
time as a backup. In general running the operations in parallel will not be
much quicker than running them in series (because your resources, specially
disk I/O, are limited). And if your backup finishes before the reindexing
finishes, part of your indexes will be reindexed and part not, but you don't
know exactly which.
Jacco Schalkwijk
SQL Server MVP
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:AA424678-958D-478E-B6FF-574A7885455B@.microsoft.com...
> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log
> execute.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF
> latch.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC
> 0x962263F0.
>
>|||Hi
What does select @.@.version return for the SQL Server?
Have a look at:
http://support.microsoft.com/kb/310834/en-us
http://support.microsoft.com/kb/309093/EN-US/
Regards
Mike
"Joe K." wrote:

> We have a SQL Server 2000 Enterprise Edition database on a Windows 2000
> Advanced Server.
> Weekly we have a job that drops all indexes on the database and recreates
> them.
> This job runs at the same time the daily backup and transaction log execut
e.
> We received following error caused by the re-index:
> "Time out occurred while waiting for buffer latch type 4..."
> Please help me resolve these latch errors.
> Thanks,
>
> SQL Server errorlog
> WARNING: EC 8a0459e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 9653c3f0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5d4ad9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 45c0b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 462df9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 5a9619e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 8a05b9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cbb9e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 6a9d19e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 89cb39e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC 84cc79e0, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> WARNING: EC b7fd35c8, 0 waited 300 sec. on latch 813f42c8. Not a BUF latc
h.
> Waiting for type 0x4, current count 0xa, current owning EC 0x6A9659E0.
> Time out occurred while waiting for buffer latch type 2,bp 0x3527140, page
> 1:1), stat 0xb, object ID 6:99:0, EC 0x6F6A9520 : 0, waittime 300. Not
> continuing to wait.
> Waiting for type 0x2, current count 0x10002a, current owning EC 0x962263F0
.
>
>

Friday, March 23, 2012

Non-SysAdmins have been denied permission to run CmdExec job steps

Is there a certain role or permission that a user must be given to run jobs?
Thanks.
Ron
Per BOL, under "jobs, running/ Transact SQL".
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role can
start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
ChrisR
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron
|||Under properties of SQL Server Agent there's a setting under the job system
tab:
"Non-sysadmin job step proxy account" - I checked this off and users were OK.
Ron
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron

Non-SysAdmins have been denied permission to run CmdExec job steps

Is there a certain role or permission that a user must be given to run jobs?
Thanks.
RonPer BOL, under "jobs, running/ Transact SQL".
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role can
start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
--
ChrisR
"Ron" wrote:
> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron|||Under properties of SQL Server Agent there's a setting under the job system
tab:
"Non-sysadmin job step proxy account" - I checked this off and users were OK.
Ron
"Ron" wrote:
> Is there a certain role or permission that a user must be given to run jobs?
> Thanks.
> Ron

Non-SysAdmins have been denied permission to run CmdExec job steps

Is there a certain role or permission that a user must be given to run jobs?
Thanks.
RonPer BOL, under "jobs, running/ Transact SQL".
Permissions
Execute permissions default to the public role in the msdb database. A user
who can execute this procedure and is a member of the sysadmin fixed role ca
n
start any job. A user who is not a member of the sysadmin role can use
sp_start_job to start only the jobs he/she owns.
ChrisR
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run job
s?
> Thanks.
> Ron|||Under properties of SQL Server Agent there's a setting under the job system
tab:
"Non-sysadmin job step proxy account" - I checked this off and users were OK
.
Ron
"Ron" wrote:

> Is there a certain role or permission that a user must be given to run job
s?
> Thanks.
> Ronsql

Wednesday, March 21, 2012

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

Look through the resulting code and search for the phrase, "sp_add_jobstep." How many are listed?|||I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.

What could be causing this?
|||bump|||

graemeo wrote:
I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.
What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:
Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

What could be causing this?
|||bump|||

graemeo wrote:
I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.
What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:
Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

What could be causing this?
|||bump|||

graemeo wrote:
I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.
What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:
Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

What could be causing this?
|||bump|||

graemeo wrote:
I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.
What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:
Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!sql

non-existent step?

My package runs fine in Business Studio. When I schedule it the error log message is 'jobmanager tried to run a non-existent step (2) for job ...'

There is only the one step defined in the package schedule. Does anyone know what the problem is?

Right-click on the agent job and select "Script Job as " and select create to new query window.

What could be causing this?
|||bump|||

graemeo wrote:
I am having the same issue. When I look through the code as suggested I only see 4 steps, with step_id's 1 through 4. The step the manager is trying to run, however is listed as step 5.
What could be causing this?

Have you tried recreating the job? What job type is it? (SSIS, Command, etc...)

|||Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

|||

graemeo wrote:
Found the source of the issue - the @.on_success_action parameter of the final step was set to 'go to the next step' and not 'quit with success'. It works now, thanks

Good to know!

Monday, March 12, 2012

Non sa running jobs?

Is there a way for a user to manage ( run, delete, add ) a job if he has not
got sa permission?
Thanks
AlexAlex,
Yes if the user is a member of the SYSADMIN fixed server role. Note however
that membership of this role should be limited as the role enables a user to
do pretty much anything in SQL Server.
HTH
Jerry
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> Is there a way for a user to manage ( run, delete, add ) a job if he has
> not
> got sa permission?
> Thanks
> Alex|||Thanks for this. But the problem we have is SOX compliance !. Us dba's have
been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
The side effect of this is that there are loads of admin tasks we cannot now
do.
Alex
"Jerry Spivey" wrote:
> Alex,
> Yes if the user is a member of the SYSADMIN fixed server role. Note however
> that membership of this role should be limited as the role enables a user to
> do pretty much anything in SQL Server.
> HTH
> Jerry
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > not
> > got sa permission?
> >
> > Thanks
> >
> > Alex
>
>|||Hmmm...that doesn't sound right. You're a DBA but you're not a member of
the SYSADMIN fixed server role? How can you do your job?
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>> Alex,
>> Yes if the user is a member of the SYSADMIN fixed server role. Note
>> however
>> that membership of this role should be limited as the role enables a user
>> to
>> do pretty much anything in SQL Server.
>> HTH
>> Jerry
>> "Alex" <Alex@.discussions.microsoft.com> wrote in message
>> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>> > Is there a way for a user to manage ( run, delete, add ) a job if he
>> > has
>> > not
>> > got sa permission?
>> >
>> > Thanks
>> >
>> > Alex
>>|||Since we don't want SA running jobs (or being in the Sysadmin group), I set
up a login with win authent, sysadmin to run jobs. No one needs the password
to use; just set this user up as the proxy account (under agent properties,
job system), and if any job owner is not a sysadmin, it defaults to this guy.
HTH, mary
"Alex" wrote:
> Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> The side effect of this is that there are loads of admin tasks we cannot now
> do.
> Alex
>
> "Jerry Spivey" wrote:
> > Alex,
> >
> > Yes if the user is a member of the SYSADMIN fixed server role. Note however
> > that membership of this role should be limited as the role enables a user to
> > do pretty much anything in SQL Server.
> >
> > HTH
> >
> > Jerry
> > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > > not
> > > got sa permission?
> > >
> > > Thanks
> > >
> > > Alex
> >
> >
> >|||Yes, try telling this to the auditors!
We are very frustrated. If we need to add a job we will need to apply for
permission to log in as sa, after going through multilevel of sign off from
the senior management - all for running a SQL Profile, or creating
maintenance plan !!
and then all actions will be be logged as well.
Alex
"Jerry Spivey" wrote:
> Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> the SYSADMIN fixed server role? How can you do your job?
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > data.
> > The side effect of this is that there are loads of admin tasks we cannot
> > now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Alex,
> >>
> >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> >> however
> >> that membership of this role should be limited as the role enables a user
> >> to
> >> do pretty much anything in SQL Server.
> >>
> >> HTH
> >>
> >> Jerry
> >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> >> > has
> >> > not
> >> > got sa permission?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >>
> >>
> >>
>
>|||Curious, if the is a reason to suddenly restore a db in the middle of the day
so production activities can resume, is the same process to log in as SA
required?
--
ChrisR
"Alex" wrote:
> Yes, try telling this to the auditors!
> We are very frustrated. If we need to add a job we will need to apply for
> permission to log in as sa, after going through multilevel of sign off from
> the senior management - all for running a SQL Profile, or creating
> maintenance plan !!
> and then all actions will be be logged as well.
> Alex
> "Jerry Spivey" wrote:
> > Hmmm...that doesn't sound right. You're a DBA but you're not a member of
> > the SYSADMIN fixed server role? How can you do your job?
> > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > > have
> > > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > > data.
> > > The side effect of this is that there are loads of admin tasks we cannot
> > > now
> > > do.
> > >
> > > Alex
> > >
> > >
> > > "Jerry Spivey" wrote:
> > >
> > >> Alex,
> > >>
> > >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> > >> however
> > >> that membership of this role should be limited as the role enables a user
> > >> to
> > >> do pretty much anything in SQL Server.
> > >>
> > >> HTH
> > >>
> > >> Jerry
> > >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> > >> > has
> > >> > not
> > >> > got sa permission?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Alex
> > >>
> > >>
> > >>
> >
> >
> >|||I don't recall anything in SOX that states that a DBA can not have sa
rights. Someone is taking the wording way beyond it's intent. SQL2005 will
have roles specifically for this but in 2000 it is not that easy.
--
Andrew J. Kelly SQL MVP
"Alex" <Alex@.discussions.microsoft.com> wrote in message
news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> Thanks for this. But the problem we have is SOX compliance !. Us dba's
> have
> been stripped off sa/SYSADMIN fixed role permission so we can't modify
> data.
> The side effect of this is that there are loads of admin tasks we cannot
> now
> do.
> Alex
>
> "Jerry Spivey" wrote:
>> Alex,
>> Yes if the user is a member of the SYSADMIN fixed server role. Note
>> however
>> that membership of this role should be limited as the role enables a user
>> to
>> do pretty much anything in SQL Server.
>> HTH
>> Jerry
>> "Alex" <Alex@.discussions.microsoft.com> wrote in message
>> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
>> > Is there a way for a user to manage ( run, delete, add ) a job if he
>> > has
>> > not
>> > got sa permission?
>> >
>> > Thanks
>> >
>> > Alex
>>|||Thanks Mary. This could be the escape route we have been looking for!
Alex
"Mary" wrote:
> Since we don't want SA running jobs (or being in the Sysadmin group), I set
> up a login with win authent, sysadmin to run jobs. No one needs the password
> to use; just set this user up as the proxy account (under agent properties,
> job system), and if any job owner is not a sysadmin, it defaults to this guy.
> HTH, mary
> "Alex" wrote:
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify data.
> > The side effect of this is that there are loads of admin tasks we cannot now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> > > Alex,
> > >
> > > Yes if the user is a member of the SYSADMIN fixed server role. Note however
> > > that membership of this role should be limited as the role enables a user to
> > > do pretty much anything in SQL Server.
> > >
> > > HTH
> > >
> > > Jerry
> > > "Alex" <Alex@.discussions.microsoft.com> wrote in message
> > > news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> > > > Is there a way for a user to manage ( run, delete, add ) a job if he has
> > > > not
> > > > got sa permission?
> > > >
> > > > Thanks
> > > >
> > > > Alex
> > >
> > >
> > >|||Andrew
We can run sa tasks, but we need authorisation every time we need to. its
like working with one of your hands tied.
Alex
"Andrew J. Kelly" wrote:
> I don't recall anything in SOX that states that a DBA can not have sa
> rights. Someone is taking the wording way beyond it's intent. SQL2005 will
> have roles specifically for this but in 2000 it is not that easy.
> --
> Andrew J. Kelly SQL MVP
>
> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> news:AD536297-1152-4F9E-A36A-88171E6FA033@.microsoft.com...
> > Thanks for this. But the problem we have is SOX compliance !. Us dba's
> > have
> > been stripped off sa/SYSADMIN fixed role permission so we can't modify
> > data.
> > The side effect of this is that there are loads of admin tasks we cannot
> > now
> > do.
> >
> > Alex
> >
> >
> > "Jerry Spivey" wrote:
> >
> >> Alex,
> >>
> >> Yes if the user is a member of the SYSADMIN fixed server role. Note
> >> however
> >> that membership of this role should be limited as the role enables a user
> >> to
> >> do pretty much anything in SQL Server.
> >>
> >> HTH
> >>
> >> Jerry
> >> "Alex" <Alex@.discussions.microsoft.com> wrote in message
> >> news:3CD1CB0F-42E8-4DA9-A04C-CBD6AE4845CB@.microsoft.com...
> >> > Is there a way for a user to manage ( run, delete, add ) a job if he
> >> > has
> >> > not
> >> > got sa permission?
> >> >
> >> > Thanks
> >> >
> >> > Alex
> >>
> >>
> >>
>
>

Non sa running jobs?

Monday, February 20, 2012

No transaction logs

I have a maintenance plan set up on a database to take transaction log backu
ps every 2 hours. The job runs successfully everyday, but I do not see any
.trn files generated (and the task pad description shows that no transaction
log backups ever took plac
e).
Any idea why? I've never seen this problem on any of my other servers.
Thank you!I'd start by double checking the job / maint plan definition, the recovery
model for the databases and then if needed run a profiler trace to see
whether the BACKUP LOG command is submitted. Also, make sure you define a
report file for the maint plan and check that report file for error
messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Gina" <anonymous@.discussions.microsoft.com> wrote in message
news:01060BCF-B18D-427F-AFB7-86ECE6A8A9DC@.microsoft.com...
> I have a maintenance plan set up on a database to take transaction log
backups every 2 hours. The job runs successfully everyday, but I do not see
any .trn files generated (and the task pad description shows that no
transaction log backups ever took place).
> Any idea why? I've never seen this problem on any of my other servers.
> Thank you!

No Transaction Log Backup after installing SP1

Hello,
after installing SP1 for SQL Server 2005 the sql agent cant execute the
existing management job to backup the transaction log. even if the job is
created new by deleting it in the maintanance plans and recreate it the sql
agent job can not be executed (nor manually or scheduled) the job is always
interrupted in step 2 'Execute Job' with the error "The package execution
failed. The step failed."
Has anyone else an idea to resolve this problem or should i uninstall sp1
(=reinstall sql)
ThanksThe question is WHY is the step failing. There should be extended error
messages in the log files that are generated for the job execution. What
are those messages saying?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Sorcerer" <Sorcerer@.discussions.microsoft.com> wrote in message
news:52149920-7656-4419-A9C2-CA4A641EF232@.microsoft.com...
> Hello,
> after installing SP1 for SQL Server 2005 the sql agent cant execute the
> existing management job to backup the transaction log. even if the job is
> created new by deleting it in the maintanance plans and recreate it the
> sql
> agent job can not be executed (nor manually or scheduled) the job is
> always
> interrupted in step 2 'Execute Job' with the error "The package execution
> failed. The step failed."
> Has anyone else an idea to resolve this problem or should i uninstall sp1
> (=reinstall sql)
> Thanks
>|||Hello,
this is what is written to the log:
Date,Source,Severity,Step ID,Server,Job Name,Step
Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator
Emailed,Operator Net sent,Operator Paged,Retries Attempted
04/21/2006 08:20:00,TransactionLog
Sicherung,Error,0,RMCNAVI1\INSTANZ1,Tran
sactionLog Sicherung,(Job
outcome),,The job failed. The Job was invoked by Schedule 9 (20). The last
step to run was step 1 (Subplan).,00:00:11,0,0,,,,0
04/21/2006 08:20:00,TransactionLog
Sicherung,Error,1,RMCNAVI1\INSTANZ1,Tran
sactionLog
Sicherung,Subplan,,Executed as user: RMC-DE\cluster. The package execution
failed. The step failed.,00:00:11,0,0,,,,0
To be more specific to the problem:
the sp1 was installed on a cluster system (windows 2003 x64 R2 and sql 2005
x64) with three instances (two clustered and one local). after installing th
e
sp1 the agent job could not be executed any longer. on a test system (not
clustered, only one instance) the sp1 was installed and there is no problem
with the agent jobs...|||my fault: forgot to make an initial full backup of the database.
sorry for that.
"Sorcerer" wrote:

> Hello,
> after installing SP1 for SQL Server 2005 the sql agent cant execute the
> existing management job to backup the transaction log. even if the job is
> created new by deleting it in the maintanance plans and recreate it the sq
l
> agent job can not be executed (nor manually or scheduled) the job is alway
s
> interrupted in step 2 'Execute Job' with the error "The package execution
> failed. The step failed."
> Has anyone else an idea to resolve this problem or should i uninstall sp1
> (=reinstall sql)
> Thanks
>

No Transaction Log Backup after installing SP1

Hello,
after installing SP1 for SQL Server 2005 the sql agent cant execute the
existing management job to backup the transaction log. even if the job is
created new by deleting it in the maintanance plans and recreate it the sql
agent job can not be executed (nor manually or scheduled) the job is always
interrupted in step 2 'Execute Job' with the error "The package execution
failed. The step failed."
Has anyone else an idea to resolve this problem or should i uninstall sp1
(=reinstall sql)
ThanksThe question is WHY is the step failing. There should be extended error
messages in the log files that are generated for the job execution. What
are those messages saying?
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Sorcerer" <Sorcerer@.discussions.microsoft.com> wrote in message
news:52149920-7656-4419-A9C2-CA4A641EF232@.microsoft.com...
> Hello,
> after installing SP1 for SQL Server 2005 the sql agent cant execute the
> existing management job to backup the transaction log. even if the job is
> created new by deleting it in the maintanance plans and recreate it the
> sql
> agent job can not be executed (nor manually or scheduled) the job is
> always
> interrupted in step 2 'Execute Job' with the error "The package execution
> failed. The step failed."
> Has anyone else an idea to resolve this problem or should i uninstall sp1
> (=reinstall sql)
> Thanks
>|||Hello,
this is what is written to the log:
Date,Source,Severity,Step ID,Server,Job Name,Step
Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator
Emailed,Operator Net sent,Operator Paged,Retries Attempted
04/21/2006 08:20:00,TransactionLog
Sicherung,Error,0,RMCNAVI1\INSTANZ1,TransactionLog Sicherung,(Job
outcome),,The job failed. The Job was invoked by Schedule 9 (20). The last
step to run was step 1 (Subplan).,00:00:11,0,0,,,,0
04/21/2006 08:20:00,TransactionLog
Sicherung,Error,1,RMCNAVI1\INSTANZ1,TransactionLog
Sicherung,Subplan,,Executed as user: RMC-DE\cluster. The package execution
failed. The step failed.,00:00:11,0,0,,,,0
To be more specific to the problem:
the sp1 was installed on a cluster system (windows 2003 x64 R2 and sql 2005
x64) with three instances (two clustered and one local). after installing the
sp1 the agent job could not be executed any longer. on a test system (not
clustered, only one instance) the sp1 was installed and there is no problem
with the agent jobs...|||my fault: forgot to make an initial full backup of the database.
sorry for that.
"Sorcerer" wrote:
> Hello,
> after installing SP1 for SQL Server 2005 the sql agent cant execute the
> existing management job to backup the transaction log. even if the job is
> created new by deleting it in the maintanance plans and recreate it the sql
> agent job can not be executed (nor manually or scheduled) the job is always
> interrupted in step 2 'Execute Job' with the error "The package execution
> failed. The step failed."
> Has anyone else an idea to resolve this problem or should i uninstall sp1
> (=reinstall sql)
> Thanks
>

Friday, March 30, 2012

Not a BUF latch. Error Re-Indexing

Not a BUF latch. Error Re-Indexing

Not a BUF latch. Error Re-Indexing

Friday, March 23, 2012

Non-SysAdmins have been denied permission to run CmdExec job steps

Non-SysAdmins have been denied permission to run CmdExec job steps

Non-SysAdmins have been denied permission to run CmdExec job steps

Wednesday, March 21, 2012

non-existent step?

non-existent step?

non-existent step?

non-existent step?

non-existent step?

Monday, March 12, 2012

Non sa running jobs?

Non sa running jobs?

Non sa running jobs?

Monday, February 20, 2012

No transaction logs

No Transaction Log Backup after installing SP1

No Transaction Log Backup after installing SP1

interface supported

Blog Archive

About Me