Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Richard101
Starting Member
30 Posts |
 Posted - 2008-09-18 : 10:33:41
|
| Hi AllBizzare situation here, turning my brain to jelly.We've a sql2k 'prod' server replicating to a sql2k 'reports' server with no problems. Then we've log-shipping from the 'prod' server to a sql2k 'dr' server.On 'dr' there are entries in EM under 'dr/Replication', which is odd as dr01 isn't publishing or subscribing to any replication (oh and btw this isn't the replication-monitor section).If I look at the properties of one of the publications showing on 'dr' there's the description "Transactional publication of BPrices database from Publisher prod"So, the description is right, and names 'prod' as the publisher ('reports' is the only subscriber) - but on 'dr'.Here's why its a problem.Log-shipping is failing for one database (remember thats from 'prod' to 'dr'). But I cannot delete the (read-only) database on 'dr'. Why? because every time I try it says its "locked for replication"!! |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-19 : 08:17:40
|
| Did you figure out why Log shipping is failing? Check restore jobs of log shipping and you can't delete becoz 'dr' might be publisher for other subscriber. |
 |
|
|
Richard101
Starting Member
30 Posts |
Posted - 2008-10-20 : 09:24:15
|
| Hi sodeep et alUPDATEFYI the fix was 'restore database xxx with recovery' to get-out of read-only mode.Full details here ...http://oracle.podzone.org/node/133 |
|
|
|
|
|
|
log-shipping issue