Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have SQL Server 2008 R2 Merge replication set up.
We have 20+ push subscriptions.
Once in a while I get the following error message during the sync:
Error messages: The merge process could not set the status of the
subscription correctly.
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200963)
Could not find stored procedure 'dbo.sp_MScheckIsPubOfSub'.
(Source: MSSQLServer, Error number: 2812)
I have found the code for the mentioned SP & ran it against the subscriber database & everything worked fine.
My question is: why is this stored procedure getting deleted every now and then by itself ? And how I can troubleshoot this issue?
Please check for orphaned rows for deleted subscriptions in sysmergesubscriptions and delete them. For example, the subscriber that this is failing on may have duplicate entries in sysmergesubscriptions, one being orphaned from a previously deleted subscription.
This has been the cause of this error and solution for clients of mine in the past, ymmv. I hope this helps.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
I want to understand time constraint if i execute any command in single line vs multiple lines in databricks notebook.
Suppose i am running any command(line of codes) in multiple line(cells) and same command i am execute in single line, will it take less time?
Yes. It is impacting the execution time duration.
Simply I am printing the "Hello World" String in two different cells and calculating the execution time using the below code.
val t1 = System.nanoTime
val duration = (System.nanoTime - t1) / 1e9d
Attaching the screenshot for more details.
1) Executing the two print statement in one cell.
2) Executing the two print statement in two separate cells.
Hope that helps.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 years ago.
Improve this question
org.springframework.dao.EmptyResultDataAccessException: Item 0 of 10 did not update any rows: I get this error when trying to update records in an ItemWriter using spring batch. Has anyone seen this error?
This isn't actually related to Spring Batch itself, rather than data access generally.
Please make sure that your db update/insert query is correct.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
Trying to build a routine script in perl that will twice a month on the (15th and the End Of The Month)
Run a query that gets all users that were created within a date interval. (on the 15th get all customers created from the first till that day! and at the end of the month get all users created from 15th to that current day)
Normally Id say this wouldnt be an issue to just do it within the query. However this script will be run twice a month every month! I have to take into consideration shorter months and leap years!
Is there anyway to do this within perl without going into an overly large if condition?
You can use Date::Calc module function Days_in_Month
use Date::Calc qw(:all);
# Days_in_Month
my ($year,$month) = (2013,12);
$days = Days_in_Month($year,$month);
Why tackle this in perl?
cron is perfectly able to run files scripts at checkpoints.
you can then use the date interval from the query, as you would normally.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I would like to know if there is way to consolidate a common spring batch step which is executed at the end of most of my batch jobs.
I know about abstract job but it only let me prepend step not append steps. I would like to see if there is any easy way short of me doing some fancy ApllicationContextAware and then extracting all batch jobs and appending common step to all of them.
Hopefully there is a better way.
If I understand correctly, you need to perform some activity at the end of most jobs.
In that case, you may use a Job Execution Listener.
The afterJob() method is always executed and you can have your processing there. Use the same listener for multiple jobs.
This link will give you an idea.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
What is the difference between DB2 sql codes -913 and -904 with an example?
An SQL code of -913 is UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name
An SQL code of -904 is UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name
A -913 is a deadlock, or two programs trying to get the same resource. The classic example is program 1 updating table B, then A; and program 2 updating table A, then B. Neither program can get to the second resource, so you have a deadlock. To prevent this, all of your programs must modify DB2 tables in the same order (A, then B).
A -904 is an unavailable resource. A dropped table or a locked table.
Both errors give you the name of the deadlocked resource or the unavailable resource.
-913 is SQL0913N Unsuccessful execution caused by deadlock or timeout.
-904 is SQL0904N Unsuccessful execution caused by an unavailable resource.
-904 is specific to DB2 for MVS.