Replication of a database
Do I need to make servers for each master sites of the database, when I want to replicate a data to multi-master sites? I want to replicate the data(some tables) in order to make query and reports from the replicated data. Suppose I have the database of 1 tera byte (using Oracle 8i) and want to partition some tables from the database such that load on server could be decreased. Thanks for any suggestion.
arbin. Nepal
Hi ,
You should post your topic to this forum as well....
Replication
Greetings,
Sim
Similar Messages
-
My
environment is as follows.<o:p></o:p>
We have 3 exchange 2010 servers.<o:p></o:p>
EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
The dag is configured to to communicate to all three.<o:p></o:p>
The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
DREX1 is located in another network. It is in another building connected via vpn. The ip
for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
(These are not the actual address, but the concept is similar)<o:p></o:p>
The dag network configuration is as follows.<o:p></o:p>
DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
and 192.168.100.52<o:p></o:p>
DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
160.100.3.51 and 160.100.3.52<o:p></o:p>
Last Friday, 3/7/14 something happened.<o:p></o:p>
To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
full backups of our exchange databases when I reviewed the backup jobs, the
exchange database backups using dpm2010 failed all weekend long starting at
11:00pm that Friday.<o:p></o:p>
The issue that occurred was that the database copies went to a status of Disconnected and
Resynchronizing, and after about 30 seconds, the status would show
Resynchronizing.<o:p></o:p>
All attempts to resolve this with the research methods failed. Deleting the
logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
Creating a new database worked, creating a database copy worked, but seeding the copy
failed. All with the same pattern, a status of Disconnected and
Resynchronizing, and after about 30 seconds, and the status would show
Resynchronizing.<o:p></o:p>
The database was mounted on EX2, and seeding to EX1
DREX1 has no issues.<o:p></o:p>
All the DAG networks were in a good status, all Green and all up. I could ping from
EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
fix, but after rebooting EX2, it all resolved. It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
was all healthy.<o:p></o:p>
We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
issue occurred; a status of Disconnected and Resynchronizing, and after about
30 seconds, the status would show Resynchronizing.<o:p></o:p>
The database was mounted on EX2 and seeding to EX1 again. I did not notice the
issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
Late Monday morning, my boss and I were looking at more articles, but all the same results,
delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
I mentioned that it was strange because the networks were all up. What made us try the next
scenarios was just "luck" I guess. I made a statement about not remembering
which networks DAG replication took place over. Again, we have a LAN and
a BACKUP network. Bother were listed to use replication, so we decided to
disable replication over the BACKUP network in the EMC. Immediately, the
database copies switch to healthy and started seeding.<o:p></o:p>
Later that evening I enabled replication over the BACKUP network and it failed again with
a status of Disconnected and Resynchronizing, and after about 30 seconds, the
status would show Resynchronizing. I disabled the replication over the
BACKUP network and the database copy went back to healthy<o:p></o:p>
The last round of windows updates were pushed to these boxes the Friday before the
issues began, 2/28/14. I don't believe the updates to be the issue. <o:p></o:p>
Can anyone make any suggestions as to where to look? It worked with the BACKUP
network enabled to so long that is eluding me as to why the issues would start
all of a sudden. I am also confident that the switch configuration for the
BACKUP network has not been changed at all in at least 2-3 months. I am
still open to look at the config. Please help if you can.<o:p></o:p>
<o:p></o:p>
Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
the database copies so that I can be alerted when the status changes. We
use WhatsUpGold 16.2 to monitor the devices. <o:p></o:p>
Thanks for any future assistance.<o:p></o:p>
Ian
IanYou don't have to enable the Replication on Backup Network.
You should collapse your DAG network.
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
Post the result of Below command:
Get-DatabaseAvailabilityGroupNetwork
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
Recommended way to start a merge replication with big database
Hi all
I need to install a merge replication on 2 diferent stores with Sql 2012 server, that are connected via 2 mb vpn and the database is about 4gb. due to the fact we have 2mb for the initial sync and the database is big, What is the recommended way to do that
without using the snapshop agent step? Can I take a backup of the db and restore it in the second server and setup the merge replication ? If so, where I tell the wizards that the databases are already there and do not use the snapshop agent and just start
to replicate ?
Thanks in advance.
JamesCreate the publication and snapshot. Zip up the snapshot and send it via FedEx to the subscriber. Apply the snapshot on the subscriber by pointing to the unzipped snapshot using the altSnapshotFolder parameter of the merge agent.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941 -
Problems starting Replication on large databases - SQL 2012
Hi all,
I have been battling SQL Server for a week trying to get replication up and running, now I realize that most probably I am doing something wrong and I hope that one of you can help pointing me in the right direction.
I want to start replication of a big (180GB) database in my lab environment and every time the end result is errors of the type "The row was not found at the Subscriber when applying the replicated command. (Source: MSSQLServer, Error number: 20598)".
There are more than one database to be replicated and the smaller ones (<= 4GB) have started without problems, a medium database of 21GB had one similar error and has been running for a few days since I found and inserted the missing data in the subscriber
DB.
A couple of facts:
- I have set up the distributor as a remote distributor since the publishers are mirrored databases.
- I assume the distributor setup is OK since all the replicated databases are taking the same 'path' and the smaller ones are working.
- The distributor and the subscriber are set up on the same server.
- All in all the following procedure takes about 3.5-4 hours.
- The database is running in Full Recovery mode
- All log backups on the publisher are turned off for the duration.
Here's what I do:
On the publisher
Create the publication and add all the articles
use [Zaragoza]
exec sp_replicationdboption @dbname = N'Zaragoza',
@optname = N'publish',
@value = N'true'
GO
exec [Zaragoza].sys.sp_addlogreader_agent @job_login = N'NS-LAB-DB-40\SqlServiceUser',
@job_password = N'********', -- Modify Here
@publisher_security_mode = 1,
@job_name = null
GO
-- Adding the transactional publication
exec sp_addpublication @publication = N'Zaragoza_Full',
@description = N'Transactional publication of database ''Zaragoza'' from Publisher ''NS-LAB-DB-38''.',
@sync_method = N'concurrent',
@retention = 0,
@allow_push = N'true',
@allow_pull = N'true',
@allow_anonymous = N'false',
@enabled_for_internet = N'false',
@snapshot_in_defaultfolder = N'true',
@compress_snapshot = N'false',
@ftp_port = 21,
@allow_subscription_copy = N'false',
@add_to_active_directory = N'false',
@repl_freq = N'continuous',
@status = N'active',
@independent_agent = N'true',
@immediate_sync = N'true', -- Needs TRUE
@allow_sync_tran = N'false',
@allow_queued_tran = N'false',
@allow_dts = N'false',
@replicate_ddl = 1,
@allow_initialize_from_backup = N'true', -- Modify Here
@enabled_for_p2p = N'false',
@enabled_for_het_sub = N'false'
GO
/* SHOULD not need this since no snapshots will be generated
exec sp_addpublication_snapshot @publication = N'Zaragoza_Full',
@frequency_type = 1,
@frequency_interval = 1,
@frequency_relative_interval = 1,
@frequency_recurrence_factor = 0,
@frequency_subday = 8,
@frequency_subday_interval = 1,
@active_start_time_of_day = 0,
@active_end_time_of_day = 235959,
@active_start_date = 0,
@active_end_date = 0,
@job_login = N'NS-LAB-DB-40\SqlServiceUser',
@job_password = N'********',
@publisher_security_mode = 1
exec sp_addarticle @publication = N'Zaragoza_Full',
@article = N'__MigrationLog',
@source_owner = N'dbo',
@source_object = N'__MigrationLog',
@type = N'logbased',
@description = null,
@creation_script = null,
@pre_creation_cmd = N'drop',
@schema_option = 0x000000000803509F,
@identityrangemanagementoption = N'manual',
@destination_table = N'__MigrationLog',
@destination_owner = N'dbo',
@vertical_partition = N'false',
@ins_cmd = N'CALL sp_MSins_dbo__MigrationLog',
@del_cmd = N'CALL sp_MSdel_dbo__MigrationLog',
@upd_cmd = N'SCALL sp_MSupd_dbo__MigrationLog'
GO
-- MANY more "EXEC sp_addarticle"....
On the publisher
I recompile the subscription SPs since I had problems with them once.
I use the output from the following statement:
USE Zaragoza;
EXEC sp_scriptpublicationcustomprocs @publication=N'Zaragoza_Full';
On the publisher
I backup the database & log
BACKUP DATABASE Zaragoza TO DISK = 'E:\Backup\Zaragoza_FULL.bkp' WITH INIT, STATS=5;
BACKUP LOG Zaragoza TO DISK = 'E:\Backup\Zaragoza_LOG.bkp' WITH INIT, STATS=5;
On the subscriber
Copy the backups from the publisher
CD /D E:\Backup
COPY /Y \\NS-LAB-DB-38-mirror\Backup\Zaragoza_FULL.bkp .
COPY /Y \\NS-LAB-DB-38-mirror\Backup\Zaragoza_LOG.bkp .
On the subscriber
Restore the database and log backups
USE [master]
GO
RESTORE DATABASE Zaragoza_Sub
FROM DISK = 'E:\Backup\Zaragoza_FULL.bkp'
WITH NORECOVERY, REPLACE, STATS=5,
MOVE 'Zaragoza' TO 'I:\mssql_repl\Zaragoza_Sub\Zaragoza_Sub.mdf',
MOVE 'Zaragoza_log' TO 'I:\mssql_repl\Zaragoza_Sub\Zaragoza_Sub_log.ldf';
GO
RESTORE LOG Zaragoza_Sub
FROM DISK = 'E:\Backup\Zaragoza_LOG.bkp'
WITH RECOVERY, STATS=25;
GO
On the subscriber
Remove all triggers since I noticed that they interfered with the replication SPs
USE Zaragoza_Sub;
DECLARE @Trigger nvarchar(100),
@SQL nvarchar(2000);
DECLARE curTriggers CURSOR
LOCAL FAST_FORWARD FOR
SELECT DISTINCT tr.name TriggerName--, te.type_desc TriggerType, ob.name TableName, tr.is_disabled, c.text
FROM sys.triggers tr INNER JOIN
sys.trigger_events te ON tr.object_id = te.object_id INNER JOIN
sys.objects ob ON tr.parent_id = ob.object_id;
OPEN curTriggers;
FETCH NEXT FROM curTriggers INTO @Trigger;
WHILE @@FETCH_STATUS = 0
BEGIN
SELECT @SQL = 'DROP TRIGGER dbo.' + @Trigger + ';';
EXEC sp_executesql @SQL;
FETCH NEXT FROM curTriggers INTO @Trigger;
END;
CLOSE curTriggers;
DEALLOCATE curTriggers;
On the publisher
Add the subscription and the push agent
-----------------BEGIN: Script to be run at Publisher 'NS-LAB-DB-38'-----------------
use [Zaragoza]
exec sp_addsubscription @publication = N'Zaragoza_Full',
@subscriber = N'NS-LAB-DB-40',
@destination_db = N'Zaragoza_Sub',
@subscription_type = N'Push',
@sync_type = N'initialize with backup', --@sync_type = N'replication support only',
@status = N'active', -- ADD this line
@article = N'all',
@update_mode = N'read only',
@subscriber_type = 0,
@backupdevicetype=N'disk',
@backupdevicename=N'E:\backup\Zaragoza_LOG.bkp';
exec sp_addpushsubscription_agent @publication = N'Zaragoza_Full',
@subscriber = N'NS-LAB-DB-40',
@subscriber_db = N'Zaragoza_Sub',
@job_login = N'NS-LAB-DB-40\SqlServiceUser',
@job_password = N'********', -- Modify Here
@subscriber_security_mode = 1,
@frequency_type = 64,
@frequency_interval = 0,
@frequency_relative_interval = 0,
@frequency_recurrence_factor = 0,
@frequency_subday = 0,
@frequency_subday_interval = 0,
@active_start_time_of_day = 0,
@active_end_time_of_day = 235959,
@active_start_date = 20140618,
@active_end_date = 99991231,
@enabled_for_syncmgr = N'False',
@dts_package_location = N'Distributor';
GO
-----------------END: Script to be run at Publisher 'NS-LAB-DB-38'-----------------
The worst part is that this is only a LAB system, when I apply this to Live I will have to deal with a 24/7 environment with 10,000+ transactions a day, so downtime is a total No-No.
If you are missing any details do not hesitate to ask, I will gladly provide all the details I have.
Have a great day
DSHi Ashwin,
I have tried a few things these last couple of days and here's where I'm at.
I looked through the publisher database for the missing row so I could just copy it over but the row was nowhere to be found. After talking to the developers I found out that the table in question has a clean-up job that deletes records when they are finished
- OK, no problem, the replication should take care of that.
When I then look at the trace from the Distributor I find a bunch of records where the ID of the missing row is used. However, I find it peculiar that the replication first does updates to a record, then deletes it only to continue doing updates afterwards.
A sample from the Trace will explain better:
The SPs are
sp_MSupd_dboMessageDialog => This SP tries to do the failing UPDATE on the table, the second to last parameter is the RowId in the table (1075152)
sp_MSdel_dboMessageDialog => This SP tries to DELETE from the table, the only parameter is the RowId in the table (1075152)
There is one other SP in the replication of this article (table) and it is called sp_MSins_dboMessageDialog and it should be used for inserting records into the table. However it is never called.
RowNumber
EventClassName
TextData
EventSequence
StartTime
EndTime
2899078
RPC:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74255940
2014-08-13 14:22:15.763
NULL
2899372
SP:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74256234
2014-08-13 14:22:16.270
NULL
2899446
SP:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74256312
2014-08-13 14:22:16.270
2014-08-13 14:22:17.923
2899447
RPC:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74256313
2014-08-13 14:22:15.763
2014-08-13 14:22:17.923
2899462
RPC:Starting
exec [sp_MSdel_dboMessageDialog] 1075152
74256328
2014-08-13 14:22:17.927
NULL
2899558
SP:Starting
exec [sp_MSdel_dboMessageDialog] 1075152
74256420
2014-08-13 14:22:17.940
NULL
2899606
SP:Completed
exec [sp_MSdel_dboMessageDialog] 1075152
74256468
2014-08-13 14:22:17.940
2014-08-13 14:22:17.940
2899607
RPC:Completed
exec [sp_MSdel_dboMessageDialog] 1075152
74256469
2014-08-13 14:22:17.927
2014-08-13 14:22:17.940
2915054
RPC:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74272198
2014-08-13 14:22:56.577
NULL
2915118
SP:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74272262
2014-08-13 14:22:56.587
NULL
2915353
SP:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74272497
2014-08-13 14:22:56.587
2014-08-13 14:22:56.597
2915354
RPC:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74272498
2014-08-13 14:22:56.577
2014-08-13 14:22:56.597
2994616
RPC:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74352996
2014-08-13 14:26:13.227
NULL
2994701
SP:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74353159
2014-08-13 14:26:13.647
NULL
2994749
SP:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74353266
2014-08-13 14:26:13.647
2014-08-13 14:26:13.647
2994750
RPC:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74353267
2014-08-13 14:26:13.227
2014-08-13 14:26:15.163
2995292
RPC:Starting
exec [sp_MSdel_dboMessageDialog] 1075152
74353810
2014-08-13 14:26:15.240
NULL
2995331
SP:Starting
exec [sp_MSdel_dboMessageDialog] 1075152
74353849
2014-08-13 14:26:15.250
NULL
2995389
SP:Completed
exec [sp_MSdel_dboMessageDialog] 1075152
74353911
2014-08-13 14:26:15.250
2014-08-13 14:26:15.603
2995390
RPC:Completed
exec [sp_MSdel_dboMessageDialog] 1075152
74353912
2014-08-13 14:26:15.240
2014-08-13 14:26:15.603
3000727
RPC:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74359306
2014-08-13 14:26:29.413
NULL
3000795
SP:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74359374
2014-08-13 14:26:29.423
NULL
3000843
SP:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74359422
2014-08-13 14:26:29.423
2014-08-13 14:26:29.427
3000844
RPC:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74359423
2014-08-13 14:26:29.413
2014-08-13 14:26:29.427
3081879
RPC:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74441576
2014-08-13 14:29:56.223
NULL
3082017
SP:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74441868
2014-08-13 14:29:58.060
NULL
3082209
SP:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74442059
2014-08-13 14:29:58.060
2014-08-13 14:29:58.067
3082210
RPC:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74442060
2014-08-13 14:29:56.223
2014-08-13 14:29:58.070
3082470
RPC:Starting
exec [sp_MSdel_dboMessageDialog] 1075152
74442320
2014-08-13 14:29:58.097
NULL
3082471
SP:Starting
exec [sp_MSdel_dboMessageDialog] 1075152
74442321
2014-08-13 14:29:58.100
NULL
3082519
SP:Completed
exec [sp_MSdel_dboMessageDialog] 1075152
74442369
2014-08-13 14:29:58.100
2014-08-13 14:29:58.100
3082520
RPC:Completed
exec [sp_MSdel_dboMessageDialog] 1075152
74442378
2014-08-13 14:29:58.097
2014-08-13 14:29:58.400
3090751
RPC:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74450665
2014-08-13 14:30:17.940
NULL
3090796
SP:Starting
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74450712
2014-08-13 14:30:17.953
NULL
3090844
SP:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74450760
2014-08-13 14:30:17.953
2014-08-13 14:30:17.957
3090845
RPC:Completed
exec [sp_MSupd_dboMessageDialog] default,default,default,default,0,default,'2014-08-13 12:10:56.503',1075152,0x50
74450761
2014-08-13 14:30:17.940
2014-08-13 14:30:17.953
Correct me if I'm wrong but this seems a bit weird. Why don't I see any INSERT to create the row again after the DELETE?
For the time being, and since this is a test system, I added the parameter "-SkipErrors 20598" to the Distribution Agent and restarted the agent. The replication started by skipping 20 records with that error and then continuing to work fine, as
suspected. I will have to verify with the developers and testers to see if all the data is still available.
Hopefully you will have some great insight into this matter and be able to explain what is happening.
Cheers!
DS -
Migrating the replication-master-site-database to another hardware
Hello folks, hello oracle
we have got the followiong configuration:
--> Database 8.1.7.0
--> Advanced Replication system
--> Single master, snapshot configuration
--> 50 Slave-sides; offline replication once a day
--> per slave side: 50 RO-Snaps, 4 UP-Snaps
an the following problem:
we need to migrate the master database from
an IBM-AIX-host-computer to an HP-UX-host-computer.
the question is:
Wich steps do we have to make?
Is there a documented way or method to do this?
Kind regards
SteffenHello,
thanks for your answer:
the database names are the same.
We made already a full database export und imported it into the target database.
This was not succesfull, because after the import in the target database
the table dba_registered_snapshot was not filled!
Now: what to do?
Kind regards.
Steffen -
Setup Transactional Replication on Mirrored database
Hi All,
Environment details:
SQL server 2005 SP4 on all servers below.
Server A -- PRINCIPAL
Server B -- MIRROR
Server C -- REPLICATED DB (need to set this up from A to C.)
Database: test
Actions done:
1. DB mirroring (without witness) has been setup from Server A to Server B.
I need to setup replication for a subset of tables (say 3) and only some of the columns of these tables.
Questions:
1. Is this possible?
2. Are there steps which I can follow?
NOTE: In our scenario, it is ok for the replication to break when there is a DB mirror failover from Server A to Server B. Requirement is only to setup replication from Server A to Server C.1. We can do the replication provided tables has PK.
2. Once added the publisher and subscriber script out the replication which will help you to drop and recreate as and when needed.
3. Keep distribution On C server
4. If tables are large enough create individual publishers for each of them.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/ -
10gr2 Replication Between 2 databases.
Can anyone provide the best document to replication schemas from one db to another.
thankx.check
Oracle® Database Advanced Replication
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/toc.htm -
Creating standby database and replication of primary database in 9i
Hi,
We have a 9i database on Windows Server.Now recently we are planning to replicate the primary database to standby database once after creating the standby database.Can anyone guide me with the procedure or documentation with this . We were asked to do this without the data guard set-up. Please do help me regarding this ASAP.
Regards,specifiying ASAP isnt a way to get people to help on a volunteer forum.
If you dont have dataguard You need to search for "manual standby apply".
lots and lots and lots of google hits for you but this is the official cookbook
http://docs.oracle.com/cd/B10500_01/server.920/a96653/manual_recovery.htm -
Replication for MMSQL Database
Hi Expert
I want to do simultaneously replication my user data Eg WG55 into another hardisk can their be any way to do it for eg
Online production should be replicated into another hardisk
WG4
WG11.mdf
WG12.ndf
WG13.ndf
WG14.log
regardsHi
In all cases I would recommend upgrading to SQL 2005.
Another option is to use log shipping.
Thanks
N.P.C -
ONLINE DATA REPLICATION ONE DATABASE TO ANOTHER IN ORACLE 9.2.0.1
I have used Oracle 9.2.0.1 version. I have created two database(ORCL, ORCL2).
in my PC. I have created INV user in both database. Currenly I have worked on INV user which is in ORCL database. Is there any technique in Oracle 9.2.0.1 online data replication from One database to another. i.e. If at any point of time my ORCL database is damaged my INV user has been recovered in ORCL2 database.What do you mean by 'Online Data replication'? Do you mean the Oracle Advanced Replication or do you mean the Oracle Dataguard?
Oracle Data Guard Concepts and Administration
Release 2 (9.2)
Part Number A96653-02
Oracle9i Advanced Replication
Release 2 (9.2)
Part Number A96567-01
~ Madrid -
Replication of database views/materialized views from big oracle to mobile client
Hi all,
Has anyone done a replication of a view or a materialized view
from big oracle to oracle lite? I can get replication of a
database table happening(although I cant seem to find the table
when I log into the odb using msql) but it just doesn't seem to
work with views(hence the path I have taken which is to use
materialized views). Anyone? CheersHello,
Yesterday I met the same problem and very sad about this, however, my story is much more complicated (I think so).
I have 6 databases:
2 - 11g
2 - 10g
2 - 9i
Every database of each release has different characterset(UTF8 and AL16UTF16).
I am trying to create Materialized view with FAST REFRESH on Oracle 11g, when master tables are located on 10g database and 9i database.
Materialized view, which points to 9i database, was successfully created.
Materialized view, which points to 10g database, gets ORA-12028
Like you, I tried many notes from METALINK and thought at the begining that the problem is my characterset. But, when the materialized views were successfully built on Oracle 9i database, I understood that the problem is something else.
Did you find the actual reason why this issue does not work??
Thanks,
Alex -
MOVE REPLICATION DATABASE TO NEW SERVER
WE HAVE A PRODUCTION DATABASE THAT WORK'S AS REPLICATION FROM 9 DATABASES, WE ARE GOING TO MOVE DATABASE TO NEW SERVER.
AS DATABASE IS PRODUCTION, WE CAN NOT STOP SERVICES. WE THINK TO CREATE A NEW DATABASE ON NEW SERVER, IMPORT DATA FROM PROD. DATABASE. SIZE APROX 100GB.
QUESTION:
I NEED TO KNOW HOW I CAN STOP SERVICES SHORT TIME. TO CHANGE TO SNEW SERVER.
THANKS FOR YOUR SUGGESTIONSЗдравствуте Ivan.
Before i would do anything like this i would make sure that i have a good valid backup (just in case!).
I would check all the applications that are currently conencting to your ORacle and make sure they are all conneting 'by name' not the IP. Or and then i would check DNS server (make sure nslookup is working) to makesure that everything resolves correctly after the moving DB to another machine.
Then check that the oracle_home etc are in the same directory and check that all paths etc in the configurations are the same.
Hope this helps
Kind Regards -
Can I use Datapump for replication of Delta from one database to another
Good Morning Experts,
I would like to know if can we use Data Pump (expdp and impdp) for replication between two database only for delta and not for complete database on daily basis and how?
Regards,
MSMS,
I assume you are talking about both metadata and data. I don't know of a way to do this. I have heard of dba's using Data Pump import to track differences in metadata, but not to replicate them.
To track differences in metadata you do the following every day:
export full=y ...
import full=y sqlfile=full_todays_data.sql ...
Then from day to day, just diff the .sql file to see what changed. You will see if tables added/dropped columns, new indexes, etc. Based on this, you may be able to come up with a set of expdp/impdp jobs to replicate the modified objects, but there is nothing built in.
Hope this helps
Dean -
Remove replication for only single database.
Hi All,
I need to remove replication for a single database (Remove replication on ABC database from SQL1 to SQL5.)
I did some research and found as follows:
DECLARE @subscriptionDB AS sysname
SET @subscriptionDB = N'AdventureWorks2008R2Replica'USE master
EXEC sp_removedbreplication @subscriptionDB, will this help my requirement.GOPlease help me in getting script to remove replication of particular database from server A to serverB.Thanks in advance.Now, customer came back asking to find out which publications hit that database(ABC) and their corresponding subscriptions.
How to find these publications which hit that database and their corresponding subscriptions, please? -
Hi,
what would be the perfect answer if any one ask what are the methods of database replication.
I really have doubt about the replication.
Is it cloning of existing DB using cold backup, RMAN uutility or exp/imp
OR
Is it disaster recovery solution like dataguard, RAC or stream.
Regards,
DevD!user12138514 wrote:
Hi,
what would be the perfect answer if any one ask what are the methods of database replication.
I really have doubt about the replication.
Is it cloning of existing DB using cold backup, RMAN uutility or exp/imp
OR
Is it disaster recovery solution like dataguard, RAC or stream.
Regards,
DevD!Hi DevD
The best answer as always comes from Oracle docs. Please refer to the following doc:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repoverview.htm#sthref8
Replication is the process of copying and maintaining database objects, such as tables, in multiple databases that make up a distributed database system. Changes applied at one site are captured and stored locally before being forwarded and applied at each of the remote locations. Advanced Replication is a fully integrated feature of the Oracle server; it is not a separate server.
Replication uses distributed database technology to share data between multiple sites, but a replicated database and a distributed database are not the same. In a distributed database, data is available at many locations, but a particular table resides at only one location. For example, the employees table resides at only the ny.world database in a distributed database system that also includes the hk.world and la.world databases. Replication means that the same data is available at multiple locations. For example, the employees table is available at ny.world, hk.world, and la.world.
Maybe you are looking for
-
Connect MBP to web via usb tether to iphone
connect book to web via iPhone with usb
-
Remove open workitem from user inbox after the workflow starts again.
I have heard that there is a possibility to remove a open workitem from the user inbox, after the workflow starts again for the same object (data update), via a termiantion event. I have searched in the sap workflow dokumentation but i could not find
-
Facebook iOS 7.1.2 password Signing in connection server error
Hi When I try to play a game on my ipad that is linked with my facebook, it has a problem with the facebook in Settings. Initially the problem was it had my old email. So what i did I added my old email in my facebook account and tried to enter my pa
-
I am currently using Firefox 19. In the last week I have found that in both Yahoo and Gmail I am unable to attach files using drag and drop; I have not used drag and drop for a little while so I cannot say that it begun with a particular Firefox upda
-
Won't Accept address / Doesn't recognize ID
I'm having two problemw with Aperture set up for the purposes of ordering pictures. First, when I sign in with my Apple ID, it asks me to create an ID. I am using the same ID and password that I have on my computer, Apple TV, iPad and iPhone. Why doe