Académique Documents
Professionnel Documents
Culture Documents
Saritha K
26-Nov-2013 11:04
Hi Experts,
My SLT version is 2011_1_731 sp 5. My configuration works fine for small tables but it
becomes slow when it comes to loading large transparent table like CE11000. I followed
steps mentioned in blog " How to improve the initial load" written by Tobias and started
replication with below parametersMy replication remains in initial load process with calculation showing 'S for more than 3hrs
and then it started showing status 'P' when 1LT/MWB_CALCSACP_001_Z_CE11000 started
running.
in table IUUC_PRECALC_OBJ my entries are conv object- CE11000
NUMREC 145000000
in table IUUC_PERF_OPTION my entries are tabname - CE11000
PARALLEL JOBS- 5
SEQNUM - 20
READING TYPE 5
and my SLT Server configuration has below count of jobs No of Data Transfer jobs - 4
Initial load jobs - 7
No of calculation jobs -2
If I do a table health check in its calculation phase ( status P), using tcode- LTRC-> Expert
FunctionsChecks for table CE11000 (mass transfer ID 001) started
Last action is R-Load tables and start replication, status is O-Obtained (Scheduled); "Is Last"
= Yes (from 26.11.2013 05:28:54)
Current action is R-Load tables and start replication; status is O-Obtained (Scheduled)
Log table /1CADMC/00000212 created in sender system, and has 0 records
The following triggers are defined for table CE11000:
- /1LT/00000212INS
Trigger CE11000; status is 2-Activated
Latency data for table CE11000 is not available
Migration object =Z_CE11000_001;Defined? = Yes, Generated? = Yes (X = Yes, blank = No)
No access plan found for table CE11000
Access plan set as 'Not Calculated' in table DMC_MT_TABLES for table CE11000
Checks for table CE11000 finished (mass transfer ID 001)
The troubleshooting activity has detected critical issues
Currently I can see number of records getting updated in the job log of
1LT/MWB_CALCSACP_001_Z_CE11000 but I cannot see any ACC_PLAN_CALC_001_0 jobs.
Please suggest your opinion on below points to accelerate initial load1. options that we can check for monitoring if something in replication is failing apart from
above steps
2. parameters that need to be added additionally incase required
3. any correction notes required to be installed for our mentioned configuration.
Regards,
Saritha
Helpful Answers by Saritha K, Guenter Weber, Saritha K, Guenter Weber, Guenter Weber
1908 Views
Average User Rating
(0 ratings)
Helpful AnswerRe: Parallel Replication taking time using SLT configuration
Alert Moderator
o
Helpful AnswerRe: Parallel Replication taking time using SLT
configuration
Like (0)
Alert Moderator
Like (0)
Alert Moderator
Like (0)
configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT
configuration
Regards,
Saritha
Alert Moderator
Like (0)
Re: Parallel Replication taking time using
SLT configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time
Alert Moderator
Like (0)
Re: Parallel Replication taking
Alert Moderator
Like (0)
Re: Parallel Replication
Alert Moderator
Like (0)
Helpful AnswerRe: Parallel Replication taking time using SLT configuration
Hi Saritha,
this is strange, in such a case this should rather be handled with a OSS message.
Concerning the parallelization of the initial load, that will work without any forther manual
activities. You only need to keep in mind that by default, we don't allow more than three jobs
running in parallel for a certain table. If you need more, the ideal case is that you have
defined the degree of parallelization in transaction iuuc_repl_content before starting the
replication of that table. Otherwise you can define it in transaction MWBMON.
Kind regards,
Guenter
o
Alert Moderator
o
Re: Parallel Replication taking time using SLT configuration
Like (0)
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT configuration
Alert Moderator
configuration
Like (0)
The steps documented for parallel replication of transparent table CE11000 worked out fine for
me. I tried the same steps for cluster table BSEG with reading type '4' this time and it started
out well with creation of 2 access calculation plans, 001 and 002. My job with access plan 002
got over after fetching around 24million records but there has been no update in job log 001 for
more than 19hrs.
Is there some additional setting that needs to be done when we try with replicating of large
cluster tables?
Why is it that replication of transparent table is faster than cluster table replication?
I also saw another approach where in we give selection criteria's based on primary key for
multiple access plans, but here we do not have an idea of how the data is widely distributed
across year, BELNR(Document Number) etc in order to judge the selection criteria.
Please suggest some technique which can be used for faster access of cluster tables into HANA.
Regards,
Saritha
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT
configuration
Alert Moderator
SLT configuration
Like (0)
Re: Parallel Replication taking time using
Like (0)
Re: Parallel Replication taking time
Alert Moderator
Like (0)
Re: Parallel Replication taking
ould there be any additions required in table DMC_ACSPL_SELECT(a new table now available)?
anks,
ritha K
Alert Moderator
Like (0)
Helpful AnswerRe: Parallel
stead:
PROCESSED
R
eal case is that you predefine the parallelization before you even select the corresponding table for
ation. That means, you create a corresponding record in table IUUC_PERF_OPTION, where you would, in the
ple above, specify BELNR as the "parallel fieldname" (which means, the field for which we define
aries to subdivide the records in disjoint subsets). In this case, the field sequence mentioned above would
matically be used. Otherwise, you would need to redefine the secondary index of the logging table after it
y has been created, which is more difficult.
egards,
er
Alert Moderator
Like (0)
2
3
Like (0)
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT configuration
Alert Moderator
Like (0)
configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT
configuration
Hi Tobias,
I would like to know more about the SLT capability when we have a landscape consisting
ECC, BW to be replicated into BW on HANA.
I have some queries around this architecture.
Can we please discuss this offline if possible?
Thanks,
Saritha
Alert Moderator
Like (0)
Re: Parallel Replication taking time using
SLT configuration
Saritha K
26-Nov-2013 11:04
Hi Experts,
My SLT version is 2011_1_731 sp 5. My configuration works fine for small tables but it
becomes slow when it comes to loading large transparent table like CE11000. I followed
steps mentioned in blog " How to improve the initial load" written by Tobias and started
replication with below parametersMy replication remains in initial load process with calculation showing 'S for more than 3hrs
and then it started showing status 'P' when 1LT/MWB_CALCSACP_001_Z_CE11000 started
running.
in table IUUC_PRECALC_OBJ my entries are conv object- CE11000
NUMREC 145000000
in table IUUC_PERF_OPTION my entries are tabname - CE11000
PARALLEL JOBS- 5
SEQNUM - 20
READING TYPE 5
and my SLT Server configuration has below count of jobs No of Data Transfer jobs - 4
Initial load jobs - 7
No of calculation jobs -2
If I do a table health check in its calculation phase ( status P), using tcode- LTRC-> Expert
FunctionsChecks for table CE11000 (mass transfer ID 001) started
Last action is R-Load tables and start replication, status is O-Obtained (Scheduled); "Is Last"
= Yes (from 26.11.2013 05:28:54)
Current action is R-Load tables and start replication; status is O-Obtained (Scheduled)
Log table /1CADMC/00000212 created in sender system, and has 0 records
The following triggers are defined for table CE11000:
- /1LT/00000212INS
Trigger CE11000; status is 2-Activated
Latency data for table CE11000 is not available
Migration object =Z_CE11000_001;Defined? = Yes, Generated? = Yes (X = Yes, blank = No)
No access plan found for table CE11000
Access plan set as 'Not Calculated' in table DMC_MT_TABLES for table CE11000
Checks for table CE11000 finished (mass transfer ID 001)
The troubleshooting activity has detected critical issues
Currently I can see number of records getting updated in the job log of
1LT/MWB_CALCSACP_001_Z_CE11000 but I cannot see any ACC_PLAN_CALC_001_0 jobs.
Please suggest your opinion on below points to accelerate initial load1. options that we can check for monitoring if something in replication is failing apart from
above steps
2. parameters that need to be added additionally incase required
3. any correction notes required to be installed for our mentioned configuration.
Regards,
Saritha
Helpful Answers by Saritha K, Guenter Weber, Saritha K, Guenter Weber, Guenter Weber
1908 Views
Alert Moderator
o
Helpful AnswerRe: Parallel Replication taking time using SLT
configuration
Like (0)
Alert Moderator
Like (0)
Helpful AnswerRe: Parallel Replication taking time using SLT
configuration
Alert Moderator
Like (0)
configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT
configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time using
SLT configuration
Guenter
Alert Moderator
Like (0)
Re: Parallel Replication taking time
Alert Moderator
Like (0)
Re: Parallel Replication taking
jobs. As soon as all access plans are calculated, the overall status of the table will switch to
calculated = 'X', and the initial load will start.
Kind regards,
Guenter
Alert Moderator
Like (0)
Re: Parallel Replication
Alert Moderator
Like (0)
Helpful AnswerRe: Parallel Replication taking time using SLT configuration
o
Re: Parallel Replication taking time using SLT configuration
Like (0)
Hi Guenter,
This time the access plans were calculated without any interruption:) , and I have 4
loads running in parallel currently as in my LTR configuration I have "initial load jobs
count =4"
From iuuc_repl_content, how do I set this parallelization? frm mwbmon, I believe its the
same ways as I stated above right..
Regards,
Saritha
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT configuration
Alert Moderator
Like (0)
configuration
Saritha
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT
configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time using
SLT configuration
Alert Moderator
Like (0)
Like (0)
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT configuration
Alert Moderator
Like (0)
configuration
Tobias
Alert Moderator
Like (0)
Re: Parallel Replication taking time using SLT
configuration
Alert Moderator
Like (0)
Re: Parallel Replication taking time using
SLT configuration
Alert Moderator
o
Like (0)
Like (0)
Like (0)
You didn't yet state where your observed or perceived latency occurs.
Why don't you tell us more about what and where you saw the bad performance?
- Lars
Alert Moderator
Like (0)
Like (0)
Helpful AnswerRe: Troubleshooting latency
M. van Foeken
20-Mar-2013 11:33
I'm currently working on a SAP HANA project where SLT is used to replicate various SAP ECC
table to SAP HANA. I have managed to succesfully replicate various tables where the target
table structure is changed and filters are applied to filter the data which is inserted into SAP
HANA. Unfortunately I'm bumping into an issue with a large table called BSIS. The table
contains approx. 115 mln rows and generates a TIME_OUT. Other tables (largest 23. mln
rows) have been replicated succesfully.
Current behaviour is that during a period of 2400 seconds a dialog process is busy doing a
sequential read on the BSIS table. However after 40 min. it generates a TIME_OUT an start
all over again. Funny thing is that initially the table started to replicate with about 220.000
rows already replicated to SAP HANA. After that the process is looping in a 40 min. procedure
of reading, generating a TIME_OUT and starting all over again.
Does anybody have an idea what we could investigate to troubleshoot? Please let me know
which further information should be added to the discussion to help troubleshoot the issue.
SAP HANA is running op SPS05 rev. 51. DMIS component is 2011 SP3. All necessary
correction notes have been submitted (although the ones on ECC have been submitted after
the initial load for BSIS has started).
I have opened an OSS message but no response from SAP yet ;-(
Thanks for your reply!
With kind regards,
Martijn van Foeken
1644 Views
Tags: sap, hana, slt, time_out, bsis
Average User Rating
(0 ratings)
Re: SLT Replication of BSIS table TIME_OUT
It may be useful to share some information on your schema settings for the replication as
entered in LTR, such as how many data transfer jobs and initial load jobs do you have
configured ?
What status does table BSIS have in the Data Provisioning screen in HANA Studio ?
To troubleshoot, you may be able to get some direct feedback as to why the issues occur by
looking at either transaction MWBMON or IUUC_SYNC_MON ( both SLT transactions ).
Also, take a look at the system log, in both systems if SLT is separate to ECC.
If you know a dialog work process starts to process the replication, but then gives you a
TIME_OUT, have a look at the developer trace for the work process. The dump, visible in
ST22, that occurs when you have the TIME_OUT may also help.
You may need to delete the original load of BSIS in HANA and start again, given that
corrections have been applied to SLT after the initial load.
Is it possible the issue is in HANA ?
Take a look at the Administrator perspective in HANA Studio and check all alerts.
I've not seen a TIME_OUT in ECC for any of our current replication scenarios, but I hope this
feedback helps you to diagnose the issue.
regards
Simon.
o
Alert Moderator
o
Like (0)
It may be useful to share some information on your schema settings for the replication as
entered in LTR, such as how many data transfer jobs and initial load jobs do you have
configured ?
2 initial load job and 10 data jobs
What status does table BSIS have in the Data Provisioning screen in HANA Studio ?
On load for a long time but today it switched to load/error
To troubleshoot, you may be able to get some direct feedback as to why the issues occur by
looking at either
transaction MWBMON or IUUC_SYNC_MON ( both SLT transactions ).
Is there somewhere some explanation about these transactions? I knew them already but
can't find much information about them
Also, take a look at the system log, in both systems if SLT is separate to ECC.
No errors on the SLT system, only on the ECC system. And the only error there is explainable
(TIME_OUT) somehow the data load takes longer then 40 minutes. And that is on the
acceptance system the limit for a proces to take use of a dialog process. 40 minutes
however, is already an extremely big value for a timeout so the question is why the data
load does take so long.
If you know a dialog work process starts to process the replication, but then gives you a
TIME_OUT, have a look at the developer trace for the work process. The dump, visible in
ST22, that occurs when you have the TIME_OUT may also help.
You may need to delete the original load of BSIS in HANA and start again, given that
corrections have been applied to SLT after the initial load.
What do you mean by this? I can empty the BSIS table of course in Hana but that won't
cancel the data
load job itself. And as long as the job runs I cannot kill it to restart it.
Is it possible the issue is in HANA ?
Everything is possible ;-) but I doubt it, the hana system's CPU load is 0 and also the SLT
system does not seem to retrieve any data of this specific table. Other tables were
replicated without issues by the way but BSIS table is the biggest we tried so far. Problem
seems to be that the data load runs in a dialog work process instead of a BTC and that it
takes longer then 40 minutes
Take a look at the Administrator perspective in HANA Studio and check all alerts.
So far I haven't notices any issues in Hana itself
I've not seen a TIME_OUT in ECC for any of our current replication scenarios, but I hope this
feedback helps you to diagnose the issue.
What is the largest table that you replicated to hana?
-----------------------
Like (0)
Alert Moderator
Like (0)
No initially not, however, the table BSAS contains 58.000.000 (which is less then
115.000.000 ofcourse) and this one synced (also without this option) fine in a few hours. As I
understood the 'normal' replication method will already replicate only 10.000 records per
time and with the IUUC_PERF_OPTION you would be able to increase the performance of the
initial load by breaking the whole table in smaller sizes and running multiple replication jobs
together. In our case it is not an performance problem but it occupies an dialog process for
more then 40 minutes (which is our time out for dialog work processes) and then gives a
TIME_OUT shortdump (so it never sends records at all). I monitored the replication of the
BSAS table and there it only occupied a dialog work process on ECC for 20 seconds after
which it started a new process in another dialog work process. So that is a big difference and
looks like the BSAS table was indeed send in parts of 10.000 records and it seems that it
tries to send the whole BSIS table at once (otherwise I cannot explain why it occupies an
work process on ECC for more then 40 minutes).
do you have filtering enabled for your replication?
yes we use filtering on the SLT in transaction 'iuuc_repl_content'. Under "IUUC REPL TABSTG"
we adjusted the table structure to exclude some fields which we do not need. All fields part
of the key are included in the replication though. And under the tab "IUUC *** RUL MAP" we
added an line of code filter for the "beginning of record" event. The line of code we use is 'IF
<WA_R_BSAS>-BUDAT LE '20100930'. SKIP_RECORD. ENDIF.' but both filters are also used on
the BSAS table.
For the BSAS table this means that only 17.000.000 records of the 58.000.000 records are
replicated (without issues) and for the BSIS it means that it should only replicate 37.000.000
of the 115.000.000 records. I don't know if Martijn mentioned it before but the BSIS table did
replicate 200.000 records before the issues started.
We do have on important question, don't know if you have an answer for this?
Currently the BSIS table is still running an initial load. This will never finish since no data is
send from ECC to SLT (all jobs end in a TIME_OUT shortdump). We like to try to add the
'IUUC_PERF_OPTION' option however, in order to do this we need to stop the load. It is easy
to stop (or suspend) an existing replication from the hana studio but you don't have the stop
or suspend options for tables which are on the initial load. So how can we reset this table
replication so that it uses the new configuration?
Kind Regards,
Nico van der Linden
Alert Moderator
Like (0)
Re: SLT Replication of BSIS table TIME_OUT
Good luck
Kris
Alert Moderator
Like (0)
Re: SLT Replication of BSIS table TIME_OUT
Like (0)
Re: SLT Replication of BSIS table
TIME_OUT
Like (0)
Re: SLT Replication of BSIS table TIME_OUT
Like (0)
Re: SLT Replication of BSIS table
TIME_OUT
Like (0)
Re: SLT Replication of BSIS
table TIME_OUT
Kind Regards,
Nico van der Linden
Keerthan Shetty
Jan 23, 2013 5:36 AM
Hi Experts,
We have installed an SAP Hana System(HANA 1.0 SPS5) with an SAP LT
Replication server(DMIS 2011 SP2-3) and SAP source system(DMIS 2011 SP1-3).
The system hosting the SAP LT Replication Server is an SAP system with SAP
NetWeaver 7.02 (Basis Support Package 11) ABAP stack using SAP Kernel 7.20
EXT(64BIT Unicode) and patch level is 400.
we have successfully connected SAP LT Replication server and SAP source system
through RFC.But whenever we create a new configuration schema for connecting
SAP Hana System and SAP LT Replication server: the dynpro dialog raises an
error:
FYR:You can download SAP Hana installation guide from the SAP Service
Marketplace at the Internet address:
https://websmp204.sap-ag.de/~sapidb/011000358700000604912011
Thanx,
Keerthan
See the answer in context
Helpful Answer by Alex Liu
3085 Views
Products: sap_hana Tags: hana, database_connection, replication_server, dmis, db_co
nnection,schema_failed
Average User Rating
(1 rating)
Satyam Poddar Jan 23, 2013 5:56 AM (in response to Keerthan Shetty)
Hi Keerthan,
Have you tried to check the compatibilty of the various components that you have installed,
as mentioned in the SAP installation guide ?
Satyam
o
Alert Moderator
Like (1)
Keerthan Shetty Jan 23, 2013 6:18 AM (in response to Satyam Poddar)
Hi Satyam,
I have installed DMIS - Release (2011_1_700) - Level (3) to the system hosting Replication
Server and DMIS - Release (2011_1_730) - level (3) to the Source system which is a BW
system. The HANA version is HANA 1.0 SPS5. According to the document, they are
compatible with each other.
Alert Moderator
Like (0)
Alex Liu Jan 23, 2013 10:16 AM (in response to Keerthan Shetty)
i knew this problem. before you create a schema via Trascation Code "LTR". Please make
sure: 1) HANA Client is installed in SLT server. 2) Basis Kenerl is installed in SLT server.
Once you have done both condition, you can try to create HANA DB connection in SLT server
via follwing way. 1) RUN DBCO, and filled in connection information. 2) Test this connection
via SE38(Report Name: ADBC_TEST_CONNECTION) If all these condition are ok, you can do
your job in LTR webdynpro and start data replication work.
Alert Moderator
o
o
Like (1)
Keerthan Shetty Jan 24, 2013 8:36 AM (in response to Alex Liu)
Hi,
I installed HANA DBSL and HANA client as well and tried creating the configuration again but
it showed the same error.
I ran the report ADBC_TEST_CONNECTION and it showed the following error.
5767]
please help.
Alert Moderator
Alex Liu Jan 24, 2013 8:53 AM (in response to Keerthan Shetty)
Like (0)
Hello Brother..
You did all things are correct !!! But you forgot a most important thing...
If you look at error message. SAP Basis Kenerl Could not load "dbhdbslib.dll"... What this
error message told you?
Answer is :
1) You told me that you have install HANA Client and DBSL...
2) But System told you it could not load DBSL(hana lib..xxx)
AIX
HP-UX
Linux
LIBPATH
SHLIB_PATH
LD_LIBRARY_PATH
Solaris
LD_LIBRARY_PATH
Windows
PATH
If your SLT was intalled Windows platformm, just add "installation path of hana
client" into this "PATH", and then restart OS and SLT Server.
once you have done this step... i promised that you can go ahead... create a schema and do
SLT data replication work.....
Alert Moderator
Like (0)
Keerthan Shetty Jan 25, 2013 11:08 AM (in response to Alex Liu)
Hi bro ,
we have followed the steps you advised above but still we are not able to create the new
configuration and getting the same error as specified above.please help.
Alert Moderator
Like (0)
Norman Pawelski May 19, 2013 10:56 AM (in response to Keerthan Shetty)
Hello Keerthan,
hopefully you already solved your problem. If not, I have possibly the solution as I had the
same problems like you.
Like (2)
Keerthan Shetty May 23, 2013 9:48 AM (in response to Norman Pawelski)
Hi Norman,
Thank you for your response. But in my case the problem is solved after upgrading the
kernel from 720 ext level 400 to 721 level 40.
Thanx,
Keerthan
Alert Moderator
Naresh Pasumarthy May 24, 2013 5:26 AM (in response to Norman Pawelski)
Had the same issue and was able to resolve by copying the hdbclient tools in to exe
directory.
Like (1)
Thanks
Naresh
Alert Moderator
Like (2)
Eachann Chen Dec 23, 2014 4:25 AM (in response to Norman Pawelski)
Hello Norman,
Best Regards,
Eachann
Alert Moderator
Like (0)
Re: Parallel Replication taking time
Alert Moderator
Like (0)
Re: Parallel Replication taking
ritha K 11-Feb-2014 06:10 (in response to Saritha K)Hi Experts,With the latest version of
T(DMIS_2011_SP6), are there any changes in the steps for parallel replication of transparent/cluster tables?
ould there be any additions required in table DMC_ACSPL_SELECT(a new table now available)?
anks,
ritha K
Alert Moderator
Like (0)
Helpful AnswerRe: Parallel
stead:
PROCESSED
R
eal case is that you predefine the parallelization before you even select the corresponding table for
ation. That means, you create a corresponding record in table IUUC_PERF_OPTION, where you would, in the
ple above, specify BELNR as the "parallel fieldname" (which means, the field for which we define
aries to subdivide the records in disjoint subsets). In this case, the field sequence mentioned above would
matically be used. Otherwise, you would need to redefine the secondary index of the logging table after it
y has been created, which is more difficult.
egards,
er
Keerthan Shetty
Jan 23, 2013 5:36 AM
Hi Experts,
We have installed an SAP Hana System(HANA 1.0 SPS5) with an SAP LT Replication
server(DMIS 2011 SP2-3) and SAP source system(DMIS 2011 SP1-3).
The system hosting the SAP LT Replication Server is an SAP system with SAP NetWeaver
7.02 (Basis Support Package 11) ABAP stack using SAP Kernel 7.20 EXT(64BIT Unicode)
and patch level is 400.
we have successfully connected SAP LT Replication server and SAP source system through
RFC.But whenever we create a new configuration schema for connecting SAP Hana System
and SAP LT Replication server: the dynpro dialog raises an error:
FYR:You can download SAP Hana installation guide from the SAP Service Marketplace at
the Internet address:
https://websmp204.sap-ag.de/~sapidb/011000358700000604912011
Thanx,
Keerthan
See the answer in context
3085 Views
Products: sap_hana Tags: hana, database_connection, replication_server, dmis, db_connection,schema_fail
ed
Satyam Poddar Jan 23, 2013 5:56 AM (in response to Keerthan Shetty)
Hi Keerthan,
Have you tried to check the compatibilty of the various components that you have installed, as
mentioned in the SAP installation guide ?
Satyam
Alert Moderator
Keerthan Shetty Jan 23, 2013 6:18 AM (in response to Satyam Poddar)
Hi Satyam,
Like (1)
I have installed DMIS - Release (2011_1_700) - Level (3) to the system hosting Replication Server and
DMIS - Release (2011_1_730) - level (3) to the Source system which is a BW system. The HANA version
is HANA 1.0 SPS5. According to the document, they are compatible with each other.
Alert Moderator
Like (0)
Alex Liu Jan 23, 2013 10:16 AM (in response to Keerthan Shetty)
i knew this problem. before you create a schema via Trascation Code "LTR". Please make sure: 1)
HANA Client is installed in SLT server. 2) Basis Kenerl is installed in SLT server. Once you have done
both condition, you can try to create HANA DB connection in SLT server via follwing way. 1) RUN DBCO,
and filled in connection information. 2) Test this connection via SE38(Report Name:
ADBC_TEST_CONNECTION) If all these condition are ok, you can do your job in LTR webdynpro and
start data replication work.
Alert Moderator
Like (1)
Keerthan Shetty Jan 24, 2013 8:36 AM (in response to Alex Liu)
Hi,
I installed HANA DBSL and HANA client as well and tried creating the configuration again but it showed
the same error.
I ran the report ADBC_TEST_CONNECTION and it showed the following error.
5767]
please help.
Alert Moderator
Like (0)
Alex Liu Jan 24, 2013 8:53 AM (in response to Keerthan Shetty)
Hello Brother..
You did all things are correct !!! But you forgot a most important
thing...
If you look at error message. SAP Basis Kenerl Could not load "dbhdbslib.dll"... What this error
message told you?
Answer is :
1) You told me that you have install HANA Client and DBSL...
2) But System told you it could not load DBSL(hana lib..xxx)
AIX
HP-UX
LIBPATH
SHLIB_PATH
Linux
LD_LIBRARY_PATH
Solaris
LD_LIBRARY_PATH
Windows
PATH
once you have done this step... i promised that you can go ahead... create a schema and do SLT data
replication work.....
Alert Moderator
Like (0)
Keerthan Shetty Jan 25, 2013 11:08 AM (in response to Alex Liu)
Hi bro ,
followed the steps you advised above but still we are not able to create the
new configuration and getting the same error as specified above.please help.
we have
Alert Moderator
Like (0)
Norman Pawelski May 19, 2013 10:56 AM (in response to Keerthan Shetty)
Hello Keerthan,
hopefully you already solved your problem. If not, I have possibly the solution as I had the same
problems like you.
What I did is to copy file libSQLDBCHDB.so to path /usr/sap/<SID>/DVEBMSG00/exe on the source ERP
System as this file was missing there. Further I set environment variable LD_LIBRARY_PATH to
/usr/sap/<SID>/hdbclient once again.
Like (2)
Keerthan Shetty May 23, 2013 9:48 AM (in response to Norman Pawelski)
Hi Norman,
Thank you for your response. But in my case the problem is solved after upgrading the kernel from 720
ext level 400 to 721 level 40.
Thanx,
Keerthan
Alert Moderator
Like (1)
Naresh Pasumarthy May 24, 2013 5:26 AM (in response to Norman Pawelski)
Had the same issue and was able to resolve by copying the hdbclient tools in to exe directory.
Thanks
Naresh
Alert Moderator
Like (2)
Eachann Chen Dec 23, 2014 4:25 AM (in response to Norman Pawelski)
Hello Norman,
Best Regards,
Eachann