Quantcast
Channel: SCN : Discussion List - SAP LT Replication Server
Viewing all 562 articles
Browse latest View live
↧

Error while replicating data from MSSQL to HANA

April 1, 2015, 9:32 am
$
0
0

Hello Colleagues,

I have created SLT configuration where the replication has to happen from MSSQL database for NW BPM for 4 tables. I have also applied a transformation function to convert date columns in the BPM tables to right desired format while replicating in HANA.

 

Now when I use the SAP HANA Data Provisioning Editor to replicate the data from these BPM tables, I am getting following error :

Conv.obj. Z_BC_BPEM_EL_RDS_021: Calculation job in sender system could not be started

 

In the configuration I have used Job Options as No of data Transfers Job : 003 , Initial Load Jobs : 002 , No of Calculations Job : 001

We are using SLT 2.0 and BASIS release 740.

 

Please suggest what could be done to remove that.

 

Regards,

Archana

↧
Search

MaxDB to HANA replication via SLT suffers from 8 characters password limitation?

February 18, 2014, 4:48 am
$
0
0

Hi experts,

 

We are trying to replicate data from a NW BPM instance (SAP NW PO (Java) on MaxDB with, let's say, sid PO7) via SLT to SAP HANA.

(Version info: MaxDB 7.9, SLT DMIS 2011 SP5, HANA 1.0 SP6 Rev68.)

So we use the ADBC connection route, via the DBCON table.

 

We want to use the SAPPO7DB user because it is impossible (we think) to have another MaxDB-user connect to the SAPPO7DB (personal) SCHEMA with all the authorizations described in 1778969 - SAP LT Replication Server: Using MaxDB as non-SAP source .

 

So we resort to the SAPPO7DB user who has a password of 8+ characters. Connecting via SQL Studio is no problem, however via DBCON and testing via ABAP report ADBC_CHECK_CONNECTION we get "sql error      4.008- occured:  POS(1) Unknown user name/password combination" errors.

 

When connecting a DUMMY maxdb user with a passowrd of 8 chars, the connection test is successful. With a password of more than 8 chars, the test fails.

 

So is the DBCON connectivity indeed suffering from the ancient 8 characters password limitation?

 

If so, how to fix this? Our workaround would be to change the SAPPO7DB password to a new one of 8 characters in length. Of course, we want the PO system to keep on running, so in which configuration thingy would we need to change this password so the app server can connect to the db? (This is my lack of Java Basis knowledge showing...)

 

Cheers, Wout

↧
↧

SLT view replication

December 18, 2014, 7:53 am
$
0
0


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?

↧

MT* jobs did not create after SLT configuration

September 5, 2014, 11:28 am
$
0
0

Hi,

 

SLT configuration successfully created and all the statuses are in GREEN. However, when i check the SM37 transaction the I did not find the job for

/1LT/IUC_LOAD_MT_* for the created Mass Transfer ID.

 

Did anyone face this issue?

 

Regards,

Sohil Shah

↧

SLT Jobs failed.

April 2, 2015, 1:32 pm
$
0
0

Hi,

 

Using SLT, data is getting replicated into HANA & ECC is the source. SLT jobs got failed.

Master Job status is in "Finished" state and is not getting started.

 

When I checked the application log, the error is "Error during opening SQL connection"

 

Message type__________E (Error)
Message class_________CNV_IUUC_REPLICATION (IUUC replication messages (HANA))
Message number________037
Message variable 1____oppening

 

Also it is not allowing to drop & reload the errored out tables.

 

Process Overview of SLT system:

slt.png

 

Can anyone provide some pointers to resolve this. Thanks.

 

 

-- KRPK

↧
↧

Zero records update for table with SLT replication

April 5, 2015, 11:22 am
$
0
0

Hi Experts,

 

We have replicated eight tables using SLT( from ECC to HANA),  however only two tables are going thru initial load for around 5 hours. The status shows in progress but no records are being updated. Checked in LTRC,  no issues found. The master job is running fine as other tables are updated and getting replicated successfully . Can you please suggest did we missed out any step ? where to check for more details on missing record count. These  2 tables are having data in the source system.


Thanks in advance for the quick reply.


Regards,

Medha

↧

SAP LT replication not working.

April 5, 2015, 4:48 pm
$
0
0

We replicating 17 tables from SAP ECC to HANA using SLT. Out of the 17 tables that we are considering for replication 15 tables got data replicated in HANA. The load job is running for more than 24 hrs and yet to load any data for 2 tables in SAP HANA environment. I have suspend and resumed the job but that did not help to load data in the two tables (FERC_D1, AFVC). The status shows in progress however no records are being updated. Checked LTRC, however, no issues found. The master job is running fine as other tables are updated and replicated. Tables with much higher data volume is also got populated without any issue. Can you please put some light on what should be the approach to load data to these two table?

↧

MSSQL few Source tables not appearing on existing SLT config.

April 6, 2015, 1:09 am
$
0
0

Hi Experts,

 

In my existing SLT configuration few source tables are not appearing in data provisioning->Replicate.

I've checked these tables have not replicated before and also checked under DD02L,DD02T the missing table entries not found but table exists on source system.

Any thoughts ?why SLT not listing few tables only.

Is there any workaround already exists?

Note:Have enough roles for the user and all the tables are coming from same schema(Source system).

Tried of restart but doesn't help.

 

Source system:MSSQL

Target:HANA

 

P.S:Listing all the Tables when new SLT configuration is established b/w MSSQL & HANA.

But i don't want to create new configuration again.

 

Regards,

Reddy Rajesh M.

↧
Search

How to assign filter rules in SLT

July 31, 2014, 2:01 am
$
0
0

Hi Experts,

 

I am loading data from archives into HANA DB using SLT. I have careated a migration object by using the program  IUUC_CREATE_ARCHIVE_OBJECT. Since I don't want to replicate the entire data into my HANA DB, So I have prepared certain filters.

So the problem here is automatic assignment of filter or mapping rules which is done for other migration objects (initial load and replication) by means of table IUUC_***_RUL_MAP will not work for the archive load objects. So in one of the blog I found that we have to  assign corresponding rules to migration object manually. I am not finding any doc/blog which explains how to assign rules manually to a migration object. Guys Could you please explain me how to assign rules manually to a migration object.


Thanks in advance.

↧
↧

SLT won't import more than 107 tables

April 8, 2015, 4:59 am
$
0
0

Hi,

 

currently we have a problem, we are not able to replicate more than 107 tables. I can add more tables to the replication process, but when you refresh the view or even if you change the tab and come back... then... the tables above 107 are gone.

 

So, I have 107 tables:

107.GIF

 

I'm adding additional tables, so I have 522 tables:

522.GIF

Now I hit "Refresh" or change the tab ... and this is what I get

 

107_2.GIF

 

Is there any parameter I should adjust? Any ideas why this happens?

 

Thanks and Regards,

Rafal

↧

What are the disadvantages/limitations of using SLT with SAP Bank Analyzer?

April 9, 2015, 3:13 am
$
0
0

Hi Everyone,

 

i know what the general advantages are for using SLT, however i would like to know the downsides/limitations/Issues/disadvantages

of using SLT specifically for SAP Bank Analyzer into HANA?

 

Appreciate your input.

 

Best,

hratch

↧

ECC to ECC connection in LTRS

April 10, 2015, 7:39 am
$
0
0

Hello,

 

My requirement is to make a configuration between ECC system to another ECC system without changing metadata table's data.

The custom tables which need to be replicated are already present in both the systems.

 

Will this type of configuration start transferring metadata tables (DD02L, DD02T, DD08L) from source ECC to target ECC system automatically?

In ECC to HANA DB connection, it is starting automatically.

 

 

Cheers

Brillion

↧

Structural changes in the source table

April 10, 2015, 12:50 pm
$
0
0

Hi,

 

I've created a Z table called ZSLT with 3 column: MANDT, ID and NAME.

I've inserted one record and after, started the replication. The record was replicated correctly into HANA.

 

 

After, I've added a new column called SURNAME in the source table. I waited 5 minutes and then I inserted a new records. I was expecting that this new column would be reflected in the HANA system, but instead, an error is showed in the iuuc_sync_mon transaction:

 

Z_ZSLT_017: Run 0000000001 aborted due to data inconsistency in 20150410 at 190018

Execution of program /1CADMC/OLC_001000000001654 failed, return code 3

 

As far as I understood, table changes should be reflected automatically, right? Any idea wha might be wrong here?

 

See below the systems version:

 

DMIS 2011_1_731 0007 SAPK-11607INDMIS - Installed on both systems (source and SLT dedicated machine).

HANA SP8 1.00.83.00.395718

 

Thanks and regards,

Roberto Falk

↧
↧

Error in connection

April 13, 2015, 8:01 am
$
0
0

Hello Gurus,

 

I am creating a configuration from ECC to HDB but while creating, I am getting an error "Error occurred when openning db connection".

 

Do I have to configure anything in DBACOCKPIT before creating a configuration? If so, kindly let me know the procedure.

If not then how I can fix this?

 

Cheers

Brillion

↧

SLT replication - Query

April 13, 2015, 3:31 am
$
0
0

We have SLT replication from SQL DB(NON-SAP) to HANA DB(SAP ECC on HANA).

 

Recently there was a change in approach. The source DB undergoes a snapshot replication(refresh of data) on a daily basis at a specified time. When this happens the triggers on the source system are getting wiped out and subsequently the replication goes into an error status. We stop and restart the replication so the triggers are created again. This is a manual approach.

 

I am just wondering if there is a way / provision within SLT that can regenerate the triggers without entering into an error state i..e once source DB gets refreshed, is there a way within SLT that detects this, stops replication and restarts automatically.  I know this is a dumb question but i got to ask. If you think of a better approach at handling this, please do let me know your thoughts.

 

Thanks for reading through.

 

Regards

Kalyan

↧
Search

Options for parallel use of a source table?

April 13, 2015, 2:41 pm
$
0
0

Hello SLT community,

 

the following is to ask you all about parallel use of a source table.

Considering a single source table in a single ABAP system, I have these questions:

 

1) From one SLT server, can separate configurations be defined to replicate this same source table to different targets (subscribers)?

I know up to 4 targets can be defined in the 1:N configuration, but what if I have more than 4 targets? Would multiple configurations for the same table work, provided I have sufficient resources in both source and SLT systems?

 

2) Assuming a table can be replicated via multiple configurations, can different mapping rules be defined in separate configurations for the same source table?

E.g. to filter on the value of a key field to send only a sub-set of records to one target, while using a different configuration with a different mapping rule sends another subset to a different target?

 

3) Can multiple, separate SLT's replicate that same single source table from the source ABAP system in parallel?

E.g. can SLT system 'SL1' replicate the table to system 'EX1' while SLT 'SL2' replicates it to system 'EX2' at the same time?

 

Let me know if all this sounds too complex, maybe I can give better examples.

 

Thanks in advance!

 

Ruben

↧

SLT Replication

April 15, 2015, 2:47 am
$
0
0

Hi,

 

I am replicating one table from SAP system to HANA.

If I change the structure of the table in HANA,

 

will it impact the replication?

 

 

 

Thank you,

 

Regards,

Ranjith.

↧
↧

Issue with LT replication; Source table is mssing (not an SAP source)

April 15, 2015, 3:06 am
$
0
0

Hello Experts,

 

We are facing a strange issue in our LT scenario.

 

Environment: Non-SAP Source --> LT --> HANA

 

This Non SAP configuration was established a year ago.

Now we got a message the source people that 2 new tables has been addd to Source database schema.

 

For bringing that change into HANA side, we are now asked to replicate the new 2 tables.

But whatever I do, I am not able to see this 2 new tables in the HANA Studio Datasprovisioning --> Replicate --> find cource table.

(the LT config seems to be perfectly fine and is up and running)

 

Any suggestion would be very helpful as it is affecting our project a lot.

 

 

Thanks and Regards

Amrith..

↧

SLT and HANA deleting archived data

July 8, 2013, 7:45 am
$
0
0

From the SLT Operations Guide, section 5.2 I can see the following statement

 

5.2 Archiving Data in Source Systems

The trigger-based replication also considers the deletion in source tables by archive activities (since it is not possible to distinguish on the database level between delete actions cause by archiving versus regular deletion of data records). As a consequence, SAP LT Replication Server will also replicate archiving activities as delete actions in the SAP HANA database.

 

In a typical standalone/sidecar implementation of SAP HANA, I would assume that in most cases this is not favorable behavior or a desired function. In typical DW/DataMart implementations, the data should be persisted in the target even after the source system data may have been archived. I can refer back to how BW operates in this caes - any new/changed data is extracted to BW, but any archiving operations do not affect the already extracted data in the target system.

 

I know there is functionality available to load archived data into HANA, but that would seem like a troublsome method to 'put the pieces back together' and get a wholistic picture of all the historical data (online data + archived objects) and would present some interesting challenges in the target (HANA).

 

Is there any way to disable the functionality to replicate deleted data due to archiving? Is there anyone with some experience navigating around this hurdle in a standalone/sidecar scenario that can shed some light as to how they handled this?

 

Thanks,

Justin

↧

APO Demand plan monthly data is not assigned correctly after replication to HANA

April 15, 2015, 11:26 pm
$
0
0

Hi All,

 

We are replicating the APO live-cache toHANA using a APO Data Replication Model. Replication of Planning Data - SAP HANA Live for SAP SCM -

 

Replication of the Planning Book to HANA is working for weekly data. Weeks in HANA reconcile correctly back to the APO Planning Book. However months are not being correctly assigned to the data. All data for each week is being assigned to only one month in HANA.

 

When tested by extraction to a BW cube/DSO first then DSO replicated to HANA the data is correctly assigned to months and weeks. There is something different which is happening in the replication of the APO Replication Model that is not correctly assigning the months.

 

Has anyone had this problem before?

 

Thanks,

Steve.

↧
Viewing all 562 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>