1:N SLT replication configuration

Hello Experts,
I am doing a configuration for 1:N SAP HANA replication to setup high available HANA in our environment.
My plan is to replication the tables from the same source ERP into 2 different HANA installations.
I have done the setup using the allow multiple usage flag for both of the configuration and the configurations were created successfully. My problem is that the 2 different mass transfer ID's are using the same logging table in the source system. In the configurations I used a dedicated tablespace where all the logging tables should be create and I was expecting to have 2 different logging tables for the same ERP table but that is not the case.
After successful initial load for VBAK R3 table into the 2 different schema, the delta load is happening only into one if the schema. So it seems if one of the configuration is performed the replication based on the logging table, the second is not doing anything.
Did anybody face similar issue? We are running on DMIS2010 SP10.
Thanks in advance for any help.
BR
Tamas

Hi Tobias,
I was referring to the new 1898479 and there this statement
Note that a switch between 1:1 and 1:N replication is not recommended! It might create some inconsistencies if part of the tables were initially selected for replication in an 1:1 context and later it is switched to 1:N or vice versa. So please only do this if absolutely indispensable!
Maybe there is other note I could use.
BR
Tamas

Similar Messages

SAP LT 2.0 && SLT Replication in HANA : query

Hello LT experts,
I am sure that we could use SAP SLT Replication (Data provisioning method) using HANA with source system as SAP or Non SAP SYSTEMS.
Please advise if the same works with SAP LT.20 for system landscape transformation project.I mean source for SAP LT2.0 would be Non-sap and target ofcourse would be SAP (which could be consolidation of many existing SAP productive systems).
Thank you
Shishupal.

Hi Shishupal,
If I understand correctly, you are looking for difference between SLT in HANA and SAP Landscape Transformation 2.o(SLT again ). Both these two tools are from same framework. But SLT in HANA is used as a replication tool, whereas, as you said we use HANA as a secondary database and the source is may be SAP or NON SAP. In case of SLT 2.0, this tool is used in during company marge, merging company code, merge profit area (used basically when two company merge scenario etc). May be you already know that for SLT in HANA requires DMIS addon in 7.02 netweaver systems like wise for SLT 2.0 DMIS is required for SLT 2.0 ad additionally one more addon component SHC_CONT is required. So we have two things
SLT replication tool
SLT 1.0 or 2.0
Regards,
Rafikul

SLT Replication for the same table from Multiple Source Systems

Hello,
With HANA 1.0 SP03, it is now possible to connect multiple source systems to the same SLT Replication server and from there on to the same schema in SAP HANA - does this mean same table as well? Or will it be different tables?
My doubt:
Consider i am replicating the information from KNA1 from 2 Source Systems - say SourceA and SourceB.
If I have different records in SourceA.KNA1 and SourceB.KNA1, i believe the records will be added during the replication and as a result, the final table has 2 different records.
Now, if the same record appears in the KNA1 tables from both the sources, the final table should hold only 1 record.
Also, if the same Customer's record is posted in both the systems with different values, it should add the records.
How does HANA have a check in this situation?
Please throw some light on this.

Hi Vishal,
i suggest you to take a look to SAP HANA SPS03 Master Guide. There is a comparison table for the three replication technologies available (see page 25).
For Multi-System Support, there are these values:
- Trigger-Based Replication (SLT Replication): Multiple source systems to multiple SAP HANA instances (one source system can be connected to one SAP HANA schema only)
So i think that in your case you should consider BO Data Services (losing real-time analytics capabilities of course).
Regards
Leopoldo Capasso

Inserting a conversion routine in SLT replication from SAP EWM system to HANA

We are a new SAP HANA customer trying to get the 1st report out… having few issues with data replications from SAP EWM system. EWM material conversion use a Kernel level FM to convert material GUID code to human readable material code, HANA does not use this routine so we are exploring whether we can insert ABAP routine to update the SLT replication or conversion logic, for example we can call EWM: CONVERSION_EXIT_MDLPD_OUTPUT routine and update human readable material code into correct data field in HANA. With this HANA can see the reportable material code directly. We came across few SLT specific FM’s in EWM, but need to find an enhancement spot to insert a code. I really appreciate If any of you SLT experts can let us know what would be the best way to do this.

Hi,
well, some correction notes for SP08 were missing. Mea culpa :-) Unfortunately implementation of the notes did not solve all Problems. Now the field length is correct but the field order and "not null"-Status of the fields is still wrong.
Best regards
Harry

SAP SLT Replication

Hi All,
We to need to load the data from the Source (ECC ) to HANA, using the SAP SLT server and need clarifications on below points.
1) Does the SLT replication server will overwrite in target for the changed records in the source
Eg:- If the sales has done on feb is 7 quantity and on march it is 9, will SLT would over write the values as 9 ? if so how to track the history of records in HANA and do a model based on the History of records ?
2) How to create model based on the time, if the user runs the report with Feb as the selection he should be able to see the quantity as 7 and thats why we require the history of records also
Kindly suggest
Thanks,
Shree

Hi Vijayashree,
SLT will overwrite the data in HANA whenever there is a change in the source system for that record.
In order to get the report based on time then every time record has to be inserted for each and every change instead of updating and there should be fields something like valid_from and valid_to.
In case of update then current record valid_to has to be updated with current date and a new record has to be inserted for valid_from as current date and valid_to to future date.
In such cases only we can get history records. With BODS ETL tool, it is easy to accomplish.
With SLT such transformation is not simple. Can we do this using IUUC_REPL_CONTENT by ABAP Include is even question to me.
Lets see what Tobias Koebler suggests!!!!!
Regards
Raj

Error while creating Configuration for SLT replication

Hi All,
I have got Hana trial version system and I am trying to do data replication using SLT.
While doing the configuration using transaction LTR, I am getting error as attached.
Though I am getting an error, entry is getting into the DBCON table but when I trying to check the connection via the report ADBC_TEST_CONNECTION, I am getting error as :-
Could not open connection TMPI07762120130424061216 .
sql error 10.709- occured:
Connection failed (RTE:[89001] Cannot resolve host name 'hanacloud' rc=8: node name or service name not known)
Note:- I am using hanacloud as hostname in hana studio and its working fine there
Can anyone can suggest, what can be the solution for it.
Thanks in advance,
Gopal

Hi Gopal,
Could you please clarify what type of trial system youhave received? Even though you will get the same HANA software but based on the delivery and deployment (On Premise or Cloud (which is again Develop Edition or HANA One for productive cases)), some of the deployment parameters are different. SAP HANA One is SAP HANA in public cloud (currently only at AWS) with hourly pricing and community support for productive and commercial use cases.
By the way, for new SAP HANA One customers:
PROMOTION- February 18- May 30, 2013 - AWS customers who are new to SAP Hana One on the AWS Marketplace will receive $120 of AWS Promotion Credit if they use at least 10 hours of SAP Hana One between February 18 and May 30, 2013. For AWS Marketplace customers who qualify, the Promotional credit will be sent to the email address registered to their AWS Marketplace account. Restrictions apply; see offer terms at https://aws.amazon.com/marketplace/help/201119060 for more details.
Thanks,
Swapan

Regarding replication configurations in oracle 9i

Good Morning...
In my current project,I have 3 databases like A,B and C.now i need to create materialized views on B & C database using dblink(created on A database), then i need to refresh around 70 tables for every 1 hour. so in this regard i need information about replication server configuration & DBLINK & MVIEW's ...

OK. Then you'd need to configure Advanced Replication, not simple one-way materialized view replication.
You'll want to start with the Advanced Replication manual.
Justin

Transactional Replication configure into different domains

Hi team,
We have two domain, we need actual data immediate from domain one to domain two.
In this scenario we are paling to configure the transactional replication from domain one to domain two.
How to configure the transactional replication for different domains.

Replication across non-trusted domains or workgroups can be done using SQL Authentication end to end or you can use Windows Authentication by configuring
pass-through authentication.
Pass-through authentication can be configured by creating a local Windows account on both the Publisher and Subscriber that has
the same username and password. Use this account for the replication agent process account and have the connections to the publisher, distributor, and/or subscriber impersonate this account. Ensure the account
has the permissions required in
Replication Agent Security Model.
This approach is covered in the section Use Windows Authentication to Set Up Replication Between Two Computers Running SQL Server in Non-Trusted Domains in
HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted Domains or Across the Internet.
Brandon Williams (blog |
linkedin)

Replication Configuration issue after migrating from SQL Server 2005 to SQL Server 2008 R2

Hi All,
This weekend we have migrated one of our Core system from SQL Server 2005 SP3 to SQL Server 2008 R2 SP2. Migration went successful. However when we are trying to Configure transaction replication we are getting below Error:
Msg 21854, Level 16, State 1, Procedure sp_MSrepl_addarticle, Line 573
Could not add new article to publication 'abc' because of active schema change activities or a snapshot is being generated.
Background:
Database compability Changed from 90 to 100.
A quick Help would be appreciated.
Best Regards - Viral
Thanks - Viral

Is a snapshot being generated? the message seems to indicate one is.
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

About Secure ACS Database Replication configure

hi
I have INSTALL the acs and the ACS DATABASE HAS replicated complete.
but when I made some change ,the primary ACS has generate *.csv file.
this file can replicated to the secondary ACS.
THANKS

Can you please clarify your issue? The post is not clear.
Regards

1:N Replication Scenario Approach

Hi,
We plan to split HANA and like to consider the parallel run option whereby we build the new hardware and do a migration/restore from existing Production onto the new box. Then we like to switch on SLT for both the existing and new HANA boxes and run the models in parallel to compare the results before we switch off the old one.
This would mean that we need to setup new SLT triggers for the new server whilst the existing triggers are still running.The current configuration for SLT -- Allow Multiple Usage is not selected.How we can perform this in our landscape?What would be the best approach?

Hi Roy,
look at this note. it describes how to setup 1:n once you already created the config without "multiple usage" flagged.
Best,
Tobias
SAP Note 1898479:
SLT replication: Redefinition of existing DB triggers

Skip only Archiving data from ECC to HANA through SLT

Hello,
SLT is configured between ECC6 as source and HANA as target, real time replication is enabled. I have a situation, where I have to skip the replication for only those data which are deleted from the database after archived. But normal deletion process should replicate in HANA.
1st we are archiving some data in ECC6 and after archiving we are deleting those data or moving those data into content server. For this process those data also being deleted from HANA. How to restore those deleted archived data into HANA.
We cann't stop the server in the time of archiving.
Any help on this would be great help.
Thanks,
Shubhrajit C.

Hi Vikram,
are you using a "Side-Car" approach in your scenario?
If yes, I think the best solution is to use SLT for a 1:1 trigger based replication.
BODS is used more for the scenarios where you have to prepare your data (e.g. data cleansing).
Regards,
Florian

SLT refresh/system copy

Hi,
We would be going for a SLT refersh from production to Acceptance.
Please do share any documents related to this.
Thanks,
Rajiv

Hi Rajiv,
Early last year I discussed with my customer approaches how such a refresh could be realized and what needs to be considered.
I can share my thoughts with you, however I have to emphasize that we never tested the procedures in detail. And in nowadays versions of SLT some transactions might be different.
So please keep them as a hint but not as a guideline.
How-to refresh QAS from PRD in SLT scenario?
Landscape:
Production landscape consist of ERP-system PRD, with replication to HANA-database HAP via SLT-server SLP
Quality landscape consist of ERP-system QAS, with replication to HANA-database HAQ via SLT-server SLQ
Scenario:
QAS system should be refreshed with recent PRD data
Approaches:
A.      Refresh QAS from PRD, clean HAQ, repeat replication
B.      Refresh QAS from PRD, HAQ from HAP and SLQ from SLP
A. Detailed steps for approach A: Refresh + repeat replication
** not tested **
1.       Backup PRD
2.       Stop the master replication job in HAQ (transaction LTR -> jobs tab -> Edit -> Stop)
3.       Refresh QAS from ERP backup
4.       Clean up old replication
a.       Delete old configuration in HAQ (transaction LTR)
b.      Delete triggers in refreshed QAS system
i.      Call transaction IUUC_REMOTE à Expert Functions à Delete Triggers à Enter the names of the replicated tables à Execute
If step i. is successful, continue with step c., otherwise go on with next step ii.-iv.
ii.      Determine all triggers
iii.      Execute function module DB_DROP_TRIG in transaction SE37 for every trigger (specify EXEC = X, TABNAME = tabname and TRIG_NAME = trigger name)
iv.      Verify that no triggers remain
Alternative: You can also write a sqlscript for all tables/triggers and run it on db level
c.       Delete logging tables in refreshed QAS system:
d.      List all logging tables: transaction SE11, enter /1CADMC/* à press F4 key; then copy the logging table names to notepad; copy all names into the clipboard
i.      Call transaction IUUC_REMOTE à Expert Functions à Delete Logging Tables à copy the trigger names from clipboard to the input selection à Execute
ii.      Verify that all logging tables have been deleted (as in i.). It seems that the logging tables for DD02L and DD02T will still exist; in this case drop the two logging tables in DB level.
e.      Cleanup SLT server HAQ:
i.      IUUC_REPL_CONFIG:                  Should be empty
ii.      IUUC_REPL_CONPAR:                 Should be empty
iii.      IUUC_REPL_HDR                           Should be empty
iv.      IUUC_REPL_MAP                          Should be empty
v.      IUUC_RS_STATUS                         Should be empty
vi.      IUUC_RS_ORDER                           Should be empty
vii.      IUUC_TABLES                                  Should be empty
viii.      DMC_COBJ                                       Should be empty
ix.      DMC_MT_TABLES                         Should be empty
x.      IUUC_LOGTAB_ID                         Will be filled, so delete the entries with transaction SE16
xi.      DMC_STRUC_ID                             Will be filled, so delete the entries with transaction SE16
xii.      DMC_ACT_REC                                              Will be filled, so delete the entries with transaction SE16
xiii.      Run report DMC_CLEANUP_USAGE in transaction SE38 with flag ‘delete all kinds of zombies’
xiv.      Run report DMC_CLEANUP_USAGE in transaction SE38 with flag ‘delete all kinds of zombies’ and subproject = ZIUUC_<MTID> with <MTID> is the name of the mass transfer id of the configuration
xv.      DMC_MT_HEADER                       Will be filled, so delete the entries with transaction SE16
f.        HANA Studio connect with SYSTEM user to HAQ, go to Catalog > Authorization > Users and delete the user of the replication (cascade option)
5.       Setup new configuration in SLQ
a.       Check RFC connection in transaction SM59 from SLQ to QAS
b.      Transaction LTR: Create new configuration
c.       In the studio, check schema created in HAQ
d.      In the studio, data provisioning, verify that tables DD02L, DD02T and DD08L are replicated
e.      Prepare a text file with all tables to be replicated
f.        In the studio, data provisioning, load the text file and add the tables to the replication
B. Detailed steps for approach B: Consistent Refresh all Systems
** not tested **
1.       Backup all systems
a.      Stop the master replication job in HAP (transaction LTR -> jobs tab -> Edit -> Stop)
b.      Backup first PRD, then HAP and finally SLP
c.       Start the master replication job in HAP again (transaction LTR)
2.       Refresh QAS from ERP backup, no BDLS
3.       Refresh HAQ from HAP backup
4.       Refresh SLQ from SLP backup
5.       Adapt SLT configuration, i.e. RFC connection to QAS in SLQ
6.       Adopt hana server name in SLT configuration(/LTR), can be done inside db connection to HANA(/DBCO)
7.       Update table “SYS_REPL”.”RS_REPLICATION_COMPONENTS” in hana and change the server name and configuration for the SLT replications.
8.       Start the master replication job in HAQ again (transaction LTR)
9.       Run BDLS in QAS to change logical system name (SLT will replicate the changes to HANA)
END *

Error while setting up Transactional Replication

Hi Team,
I am getting below error while configuring Transactional Replication.
Specifically, when I started configuring the distributor that when I am getting below error. I am getting this in GUI as well TSQL script as well.
SQL Server could not configure 'TEST-PC\SQL2K8' as a Distributor.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Destination path D:\SQL2K8DATA is not valid. Unable to list directory contents. Specify a valid destination path.
Changed database context to 'master'. (Microsoft SQL Server, Error: 14430)
Background of the error.
========================
I installed 3 sql instances of "SQL Server 2008 Developer edition, SP3 (x64)".
I started configuring a remote distributor using one of the instance and error started popping up.
Initially I had the replication running fine and I removed it and tried to reconfigure distributor thats when the error starting popping up.
The folder physically exists and the service account has full permissions and I have logged in as service account and trying to setup Transactional Replication.
He is local administrator on the box and also sysadmin login at sql server level.
Not sure why this error is popping up.....
After wasting a lot of time. I tried to install 3 new fresh instances with same service pack level i.e. sp3, but still the error remains the same.
Appreciate if anyone can guide me resolving this issue.
Thank you.

Hi Brandon,
I generated the script and tried again. No Luck. It is throwing error at creation of distribution database itself i.e. exec sp_adddistributiondb .
/****** Scripting replication configuration. Script Date: 2/25/2014 11:43:31 AM ******/
/****** Please Note: For security reasons, all password parameters were scripted with either NULL or an empty string. ******/
/****** Installing the server as a Distributor. Script Date: 2/25/2014 11:43:31 AM ******/
use master
go
exec sp_adddistributor
@distributor = N'TEST-PC\S2',
@password = N'123'
GO
exec sp_adddistributiondb
@database = N'distribution',
@data_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data',
@log_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data',
@log_file_size = 2,
@min_distretention = 0,
@max_distretention = 72,
@history_retention = 48,
@security_mode = 1
GO
Error Message :
Msg 14430, Level 16, State 1, Procedure sp_adddistributiondb, Line 227
Destination path C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data is not valid. Unable to list directory contents. Specify a valid destination path.
use [distribution]
if (not exists (select * from sysobjects where name = 'UIProperties' and type = 'U '))
   create table UIProperties(id int)
if (exists (select * from ::fn_listextendedproperty('SnapshotFolder', 'user', 'dbo', 'table', 'UIProperties', null, null)))
   EXEC sp_updateextendedproperty N'SnapshotFolder', N'\\TEST-PC\repldata', 'user', dbo, 'table', 'UIProperties'
else
   EXEC sp_addextendedproperty N'SnapshotFolder', N'\\TEST-PC\repldata', 'user', dbo, 'table', 'UIProperties'
GO
exec sp_adddistpublisher @publisher = N'TEST-pc\s1',
@distribution_db = N'distribution',
@security_mode = 1,
@working_directory = N'\\TEST-PC\repldata',
@trusted = N'false',
@thirdparty_flag = 0,
@publisher_type = N'MSSQLSERVER'
GO

How to switch off auto start of replication sp's.

hi,
I was checking my sqlserver's master database and found some body has swithched on auto start
of the following sps.
sp_MScleanupmergepublisher
sp_MSrepl_startup
May be some one was exprerimenting with replication.
pls tel me how can i switch them off?
i was hesitating to use this command
"sp_procoption 'spname', 'startup','off'"
, because i thought some on might have configured some thing else also for replication
or there might be some other way to swithch of these replication sp.
yours sincerely

You dont want to stop these.
These are automatically started when SQL Server starts provided you have replication configured.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

1:N SLT replication configuration

Similar Messages

Maybe you are looking for