Replication error - can not retrieve column information

does anyone have an idea of what generally could be wrong with a pull merge subscription when it errors out with the following:
sql server The merge process could not retrieve column information for table "tablename"
Also, could you tell me where I can get more details of errors (i.e. where the errorlog for replication is located
I found how to output the merge agent errors. Here is the output. Can anyone shed any light on this?
[5/15/2004 6:28:05 PM]BOSERVER-CSC3.vis-csc3: {call sp_MSgetversion }
Connecting to Publisher 'VIVA-SQLHQ.VIS'
Server: VIVA-SQLHQ
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[5/15/2004 6:28:05 PM]VIVA-SQLHQ.VIS: {call sp_MSgetversion }
Percent Complete: 5
Processing article 'viva_visit_qualified_statuses'
Percent Complete: 5
Processing article 'viva_inoffice_statuses'
Percent Complete: 5
Processing article 'Users'
The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
The merge process could not retrieve column information for table 'dbo.viva_inoffice_statuses'.The merge process could not retrieve column information for table 'dbo.Users'.
The merge process could not retrieve column information for table 'dbo.Applicant Requirements'.
Percent Complete: 0
The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The merge process could not retrieve column information for table 'dbo.viva_visit_qualified_statuses'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSenumcolumns (?,?)}
Percent Complete: 0
Category:SQLSERVER
Source: BOSERVER-CSC3
Number: 2812
Message: Could not find stored procedure 'sp_sel_82D17F3FEACB41DE7A9684009ECD4868'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The merge process could not retrieve column information for table 'dbo.viva_inoffice_statuses'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The process was successfully stopped.
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Subscriber 'BOSERVER-CSC3'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Publisher 'VIVA-SQLHQ'
Disconnecting from Distributor 'VIVA-SQLHQ'

replication cache plan

Hi,
I heard that simple delete stmt which deletes no of rows everytime in
replication is not using came plan caching why you have any idea or is there
any option that we can turn on to use cache plan..
Thanks in advance
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1
No, it will use the plan that either the ad hoq sql statements use or the
stored procedure plan.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"pardhiveswar via droptable.com" <u8956@.uwe> wrote in message
news:73eafdf38c451@.uwe...
> Hi,
> I heard that simple delete stmt which deletes no of rows everytime in
> replication is not using came plan caching why you have any idea or is
> there
> any option that we can turn on to use cache plan..
>
> Thanks in advance
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1
>
|||Hillary,
ok if Autoparameterization is not using for simple delete statement in 2000
what we have to do..
is there an option to force sql server...
Thanks in advance
Hilary Cotter wrote:[vbcol=seagreen]
>No, it will use the plan that either the ad hoq sql statements use or the
>stored procedure plan.
>[quoted text clipped - 4 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1
|||Hillary,
Just ignore the above stsmt.
Actually my questions is during replication from sql to sql it will create
stored prodecudres
but from sql to oracle iinstead of stored procedure it will only create sql
stmt so during this time it is not using autoparameterisation for simple
delete stmt(adhoc stmt),is there a way that we can use autoparam...
please let me know if you didn't understand
sorry for the confusion before..
Thanks, in advance
pardhiveswar wrote:[vbcol=seagreen]
>Hillary,
>ok if Autoparameterization is not using for simple delete statement in 2000
>what we have to do..
>is there an option to force sql server...
>Thanks in advance
>[quoted text clipped - 3 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200706/1

Replication and Linked Server Problemes

Hi @.ll,
we have right now big problemes with our replication and linked servers to
oracle.
has anybody an idea what wrong?
if we use a select statement everything works fine, only if we use a update
statement on a table on the SQL Server we see the error.
Just for your info. we use JOIN over 2 tbl on the Linked Server Side.
the error message is :
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'MSDAORA'
was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8000d048
thanks
klaus
Klaus,
apart from the obvious check - is MSDTC started - have a look at these
articles which are designed to troubleshoot this error:
http://support.microsoft.com/default.aspx?kbid=306212
http://support.microsoft.com/kb/280106/EN-US/
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||http://support.microsoft.com/default...;en-us;Q280106
does this help.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com