Hi Gurus,
We are replicating from ECC to HANA with LTRS only initial load.
I encountered some problems, would need your expertise on this.
Regards
Brillion
hello
i am just reading about the SLT installation options. i know it can be installed on any ABAP system.
i am looking to set up a development environment, and wish to know if it is possible to install the SLT on a BW on HANA system.
it will replicate data from another HANA environment, into the BW on HANA environment.
would this be seen as a non-ABAP source to non-ABAP target extraction? or because it is BW on HANA, it is a non-ABAP source to an ABAP target (as it is BW on HANA).
thanks
g
dear all
i am struggling to find any documentation to prove that a native HANA db source, i.e. a HANA db on its own, without any SAP applications, or ABAP stack sitting over it, is supported for OPD replication into a BW on HANA system. (by the way, the BW on HANA, is not the same HANA as the source).
thanks
g
Hello SLT Experts ,
Depending on the values of a first table I want to use a filter in a second table during the migration , I have found
this piece of code in BOL which it is suppose allow me to read the info of a specific table in this case VBRK
select * from dmc_acspl_select into table lt_acspl_select where migr_obj_alias = 'VBRK'
I have tried to put this code but I am not even able to active it ..., I get statement not accesible , I try to activate the whole function group no luck , same error , use start-of-selection but during migration I get an error .
Do you know what the problem is ? Is there any documentation about programing the includes ? the structures ? etc available regarding this topic somewhere . ?
thank you very much
Hello folks,
i'm about to gather information about SLT for non-SAP source systems from a security perspective and couldn't get
answers for the following issues:
1. I'm wondering if there is a possibility to limit the tables which can be replicated from an oracle or mssql source system ,
as it is done in SAP source systems via IUUC_TAB_ALLOWED.
Is there any similar functionality for non-SAP source systems?
2. I investigated that it's really hard to adjust the authorizations in terms of "least privilege" in the source db.
As mentioned in "note 1771460 - SAP LT Replication Server: Using ORACLE as non-SAP source" the following authorizations are necessary:
- Select from the specific table
- Create a table in the given schema (in order to successfully create the logging table)
=> Since the logging tables are created with the ID of next number in SNUM: IUUC_TABID its hard to adjust the authorizations
- Select from the logging table
=> same as above, hard to adjust the select privileges
- Delete the logging table
=> same as above
- Create database triggers for the specific table
=> which means in term of Oracle guide:
"To create a trigger in any schema on a table in any schema, or on another user's schema (schema.SCHEMA),
you must have the CREATE ANY TRIGGER system privilege.
In addition to the preceding privileges, to create a trigger on DATABASE, you must have the
ADMINISTER DATABASE TRIGGER system privilege."
So the user can create triggers on any table and probably get data which he is not allowed to read!
- Delete the database triggers
"The trigger must be in your schema or you must have the DROP ANY TRIGGER system privilege.
To drop a trigger on DATABASE in another user's schema, you must also have the ADMINISTER DATABASE TRIGGER system privilege."
So the user can drop any trigger on any table
- Create synonyms and views for the specific table
=> Since the synonyms and views are created with the ID of next number in SNUM: IUUC_TABID its hard to adjust the authorizations
- Delete the synonyms and the views
=> same as above
In MSSQL it is similar to that.
How can we make sure to apply the "least privilege" principle in the source db?
3. For HANA Source systems we use encrpyted db connections (connection string with parameter ";CON_PARAM=ENCRYPT=TRUE,sslHostNameInCertificate=")
Is there a similar option for Oracle and MSSQL DBs?
Thanks for your input
Joe
Hello All,
We are replicating data from SAP to Oracle.
For any field of SAP type NUMC or DATS, once it gets replicated to Oracle, those fields are defined as Varchar in Oracle.
I did try to define settings in table IUUC_REPL_TYPMAP, but it makes no difference. I have the impression that this table is only useful for replications to Hana, not to an Oracle DB.
Has anyone witnessed a similar beheviour?
Thanks,
Pawel Mierski
Hi,
We have just updated our DMIS from SP4 to SP7 in order to replicate view as it is supported only from SP6. We are confused with the way how the view works. In LTRS, we created the filter settings for the view. Then tried to add the view in LTRC, but it gave the error "Table class VIEW of table /POSDW/V_AGGRTI is not supported for data provisioning" with the option 'Start Load' or 'Start Replication'. The underlying tables of the view already exists in the target schema in HANA. Then i tried the option 'Create Table or DB view'. It created the view in the hana database and then disappeared from the LTRC table overview. The view structure in HANA is not as per the filter settings, the view structure is same as the source system.
My questions are:-
1) Is Create Table or DB view is only option for adding view? whether other options like Initial Load or Replication will not work for it?
2) Why the view is not created as per the filter settings mentioned in LTRS
3) Why the view is not displayed in the Tables Overview? Is it correct behaviour?
4) What difference does it make if we create the view directly at the HANA database instead of using SLT?
hi,
there are few structure related table chnages on ERP side and due to which SLT replictaion is failing. Our target is Oracle system hence not sure apart from doing init load agian - any other fix settings in SLT that can be used? Though I can see that new field added in ERP - is reflected in SLT as well.
Above are error messages-
We are on SLT SP009 - so advice if any ideas
thanks
Hi,
We are trying to setup SLT based replication to HANA system. In our environment due to few constraints we are planning to use one source system connected to two separate SLT server replicating data to two separate HANA systems. Following is the high level view.
1 source --> 2 SLT --> 2 HANA
As per the guide 1:N SLT replication approach is supported however guide doesn’t explain whether it allows multiple SLT in between 1:N or not.
I have question regarding this setup.
1> Is the following approach supported?
1 source --> 2 SLT --> 2 HANA
2> If we have 2 SLT system connected to single source system then for any single table in source system, will there be two triggers for same table OR single trigger will feed both SLTs?
Thanks
Hi Experts,
Our SLT replication server configuration seems to be incomplete.
We're getting error message "Failed to resolve object based navigation target ".SLT_OBN.OPEN_CONFIGURATION". Use transaction PFCG to define this OBN target in a role or contact your system administrator to assign a role with the relevant OBN entires to your user" when we try to open one of the created SLT configurations from the LTR (Configuration and Monitoring Dashboard) screen. (see attached screenshot).
OBN entries are also maintained for the role SAP_IUUC_REPL_ADMIN.
Am I missing anything?
Thanks & best regards,
Sreenu
Hi Experts,
I have a doubt.please clear it if anybody knows. Once we Stop the Replication in SLT then how we get the missed data from delta ?
If i do replicate again my source system's Log and Trigger tables are
Does the SLT Replication Server Support a non-SAP Target, for example ECC -> SLT -> Operational Data Cache?
Based on the literature I have read, it seems to indicate that this is possible. We are looking for a solution to provide real-time replication from an SAP environment to a data cache.
Has anyone out there configured this type of architectural scenario?
hi,
Has anyone done replictaion from ECC via SLT to Advanced DSO in BW 7.4 /7.5? I have tried but donet get option od real time dtp when loading via ODP to adavcned dso.
please advice if you re aware.
thanks
Nilesh
I am trying to understand the correct handling of SLT during a refresh of a source ECC and target HANA system. I have read through the document titled "Resuming Replication Without Initial Load After System Refresh or OS/DB
Migration" but still have a couple of clarification questions.
1.) It states that all delta data has to be replicated prior to the system copy being taken. Does this mean no user or batch activity is allowed on the source system since that could create further delta data and hence the source system has to be under maintenance?
2.) Does the SLT configuration need to be disabled in the production SLT system prior to the source and target system copy or only in the QA SLT system?
3.) There is an additional step to be performed if the HANA Data Provisioning UI is being used. The table RS_REPLICATION_COMPONENTS needs to be adapted for source and target. Is there a way to simply disable the data provisioning UI in HANA to begin with so it cannot be used? If not, does it just mean if that table is not maintained after refresh replication still works but the HANA UI can no longer be used?
Hi,
We are getting error while Replicating this source system ECC & CRM tables. Trigers are not getting created & giving the error-
DDIC activation failed for one of the structures listed below :
1. BUT_HIER_NODE:
2. EKPO
3. LFA1
Screenshot attached below.
Need some light on this if anyone has seen this situation.
Hi all,
Does anyone have idea of this error? I met this when load table from MSSQL to ABAP. The Chinese characters in the picture mean Incorrect syntax near 'SYNONYM'.
Thanks a lot!
Beat Regards,
Levi Ye
Hi All
We are on SP8 - I want to load a table from sap to hana using slt and the table have sensitive data in one column ..I can drop the column but unfortunately the column is a part of key and if i drop i can't maintain the integrity of the records as this would be duplicate the records without the sensitive info column ..
I was thinking of scrambling the data but i was not sure how it works if the record is an update
Thanks
Dear Team,
We are using ECC and NW 7.4 on Sybase 16 with windows server 2012
Hence we cannot use SRS since it doesn't support Sybase 16 and windows 2012
what are the other methods available to replicate logs to DR kindly suggest
Thanks and Regards,
Praveen
We have our biggest table KONV 1,8 Billion records that has finished loading in the initial load phase in SLT replication.
But it has finished 48 hours ago and is still in status replication (Initial load), records are being logged as I can see them using unprocessed records function. It appears in process in the data transfer monitor but there is no movment in our target database.
Reading was set to type 5 for initial load and then reste to original type 3 after the initial load finished
Runtime objects have been generated.
Any one have any ideas on how we can get the table to go into replication mode?
Hi,
Has anyone successfully connected SAP SLT directly to Hadoop or other big data services where the big data is the target? We have a scenario where our SAP OER will produce millions of records of which we wish to report against but see that the scale, ie number of records plus the data retention requirements will mean a typical SAP BW and or a SAP HANA will not be a viable architecture.
So is SLT a contender, excluding potential license discussions?
Thanks
Brian