All,
I've been configuring Transactional replication in accordance with the
'High Availability' standards, and it seems the initial snapshots have been
transferred but when looking at my distribution agent I can see this error:
Last Command:
{CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group ('ALA')}
Transaction sequence number and command ID of last execution batch are
0x0001A7C400002F8C000900000000 and 1.
Error Details:
Syntax error or access violation
(Source: MOSS-KIPPER (ODBC); Error number: 37000)
Anyone have a rough idea of what to look at?
James McM
sounds like your table name has some characters in it which are causing
problems.
What is the underlying table name?
You can work around this by right clicking on your publication, selecting
properties, articles, and then click on the browse button (the three
ellipses to the right of your table name), and click on the command tab.
Enter a proc name that looks like this:
sp_MSdel_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Do this for the update and insert procs as well, so they look like this:
sp_MSupd_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
sp_MSins_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Now regenerate and redistribute your snapshot.
You also have the option of doing a no sync subscription, and then doing
validations to determine which tables are out of sync and manually sync
them.
To do a nosync subscription you will need to generate the procs.
To do this change the proc names as illustrated above and then on your
publisher in your publication database.
sp_addpublication 'dummy'
sp_addarticle 'dummy','tablename','tablename'
sp_scriptpublicationcustomprocs 'dummy' and in your results pane you will
find the procs. Copy these procs and run them in your subscription database.
"James McMorrough" <james.mcmorrough@.getrid.sqlpersonnel.com> wrote in
message news:OxNFmtOwEHA.3320@.TK2MSFTNGP14.phx.gbl...
> All,
> I've been configuring Transactional replication in accordance with the
> 'High Availability' standards, and it seems the initial snapshots have
> been
> transferred but when looking at my distribution agent I can see this
> error:
> Last Command:
> {CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group
> ('ALA')}
> Transaction sequence number and command ID of last execution batch are
> 0x0001A7C400002F8C000900000000 and 1.
> Error Details:
> Syntax error or access violation
> (Source: MOSS-KIPPER (ODBC); Error number: 37000)
>
> Anyone have a rough idea of what to look at?
> James McM
>
Monday, March 12, 2012
Error number: 37000
Labels:
accordance,
availability,
configuring,
database,
error,
initial,
ive,
microsoft,
mysql,
number,
oracle,
replication,
server,
sql,
standards,
thehigh,
transactional
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment