Prev: Log Reader Error
Next: Unable to create transactional replication subscription - authenticationissue?
From: Charts on 24 Jan 2007 11:49
I created a transaction replication in SQL 2005, and replication generated
log reader and distribution jobs. They are running fine. For example, the
“replication transaction-log reader” job defined as following.

Type: replication transaction-log reader

Run as
SQL Agent Service account

Command:
-Publisher [servername\instance] -PublisherDB [dbname] -Distributor
[servername\instance] -DistributorSecurityMode 1


However when I manually created a job with exactly the same setting, it
fails with the following message:

"The step is improperly defined and so could not be run. The step failed."

The reason I want to manually create replication job is that I used to have
a replication job in SQL 2000 with multiple step for the replication job in
different databases. I schedule one job instead of multiple replication jobs.

I searched google site, and the error I encountered seems to be a known
issue with SQL 2005. However no one has given a satisfactory answer yet to
make it work. Please help.

Thanks,
Charts


From: Paul Ibison on 24 Jan 2007 14:54
I've only found one reference so far
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=152689&SiteID=1)
which explains that it is a bug to be addressed in a service pack. What I'm
thinking is why don't you create the job as per usual, then use your script
to add in the additional job steps.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com


From: Peter Yang [MSFT] on 24 Jan 2007 22:20
Hello Charts,

If possible, you may want to check if the issue occurs on SQL 2005 SP2 CTP
test environment.
http://www.microsoft.com/sql/ctp.mspx

I'm not quite sure why you want to run log reader job manually. Since it is
related to transction information in the distribute database, there shall
not be multiple jobs to do the same job. Also, it is related to snapshot of
the database being replicated. Therefore, I think it is not recommended to
add this job manually. You may want to create replications for different
databases.

If you have any comments or questions, please feel free to let me know.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

From: Charts on 26 Jan 2007 10:32
Peter,
I tried the same thing in my local computer, which has SQL 2005 SP2 CTP
installed. The same error happened. As far as why I manually created the
replication job. We have more than one hundred databases in the same server
needed for replications. I did manually create each transactional replication
for them. However, to run these jobs under scheduler, you don't want them run
in the same time to overload the server. So in our SQL 2000 server, we have
multiple steps job, each step is the replication log reader or distribution
command, which copied and paste from the replication generated job script for
different database. So that we are able to put hundreds replication jobs into
one job. However this no longer works in SQL 2005 environment. If it is a
bug, we have to wait for future SP to correct it. Any thought about this
issue is appreciated.
Thanks,
Charts.


"Peter Yang [MSFT]" wrote:

> Hello Charts,
>
> If possible, you may want to check if the issue occurs on SQL 2005 SP2 CTP
> test environment.
> http://www.microsoft.com/sql/ctp.mspx
>
> I'm not quite sure why you want to run log reader job manually. Since it is
> related to transction information in the distribute database, there shall
> not be multiple jobs to do the same job. Also, it is related to snapshot of
> the database being replicated. Therefore, I think it is not recommended to
> add this job manually. You may want to create replications for different
> databases.
>
> If you have any comments or questions, please feel free to let me know.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
From: Charts on 26 Jan 2007 10:37
Hi Paul,
The problem is that it won't allow me to run a simple step, even though the
step is exactly same as the one generated by the replication job. I don't
want add more scripts in the replication generated job, since that might
totally crash the replication. Thanks for your help.
Charts


"Paul Ibison" wrote:

> I've only found one reference so far
> (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=152689&SiteID=1)
> which explains that it is a bug to be addressed in a service pack. What I'm
> thinking is why don't you create the job as per usual, then use your script
> to add in the additional job steps.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
>
 |  Next  |  Last
Pages: 1 2
Prev: Log Reader Error
Next: Unable to create transactional replication subscription - authenticationissue?