Hi Shiladitya,
Please contact your SAP account manager.
Thanks,
Shakthi Raj Natarajan.
Hi Shiladitya,
Please contact your SAP account manager.
Thanks,
Shakthi Raj Natarajan.
Alright,
I think it's quite clear that we can rule out now any fragmentation effects on the underlying data structures.
It seems that there rather is some kind of waiting situation, e.g. caused by lock contention. that slows down processing.
As I am not an SLT expert at all, I can only recommend a general approach.
So my next step would to check in both source and target system for long running transactions and look for locks that might be involved with those.
It is important to know where the bottleneck occurs here. Since reading on Oracle (which I assume is the source system here) typically is not blocked by record/table locks, I would probably focus on the write-out end of the replication here - the SAP HANA server.
One thing that pops to my mind is that under some rare conditions the savepoint writing can run into issues that then would lead to looping "critical phase"-executions. Those block transactions and should be very short in general.
Martin's script collection (sap note #1969700) contains a script to check the savepoint durations.
While you're at it, you should also run the minicheck script to get a general "health check".
In fact - start with the mini check and use work through the output first
- Lars
As per my understanding the SLT "latency" measure the time between the DML operation and the SLT propagation. SLT can only kick in after a COMMIT. So if a DML operation is committed after 2 hours, it is normal to see a latency of 2 hours. This is normal and doesn't indicate an issue (unless the 2 hours runtime is longer than expected).
Hello P B,
Unless you have SELECT ON schema _SYS_REPO inside object privileges for your user , you cannot see repository related details.
Change Manager view or _SYS_REPO.CHANGE_ENTRIES gives you objects created under a change id , in order to see the subsequent changes made by different user under a change id , you can do select on table SYS_REPO.CHANGE_CONTRIBUTORS.
-Siva
Hello Pawan,
Yes, you can do that.
Thanks
Praneeth
I installed the Moonrise theme and the syntax highlighting settings it recommends and it doesn't play very nicely with SQL files. I guess I'll have to wait until we upgrade HANA and HANA Studio.
Hi is this a know issue? , that the limit and offset clauses don't work on select's used on SAP HANA virtual tables
that are created using SAP HANA smart data access.
on executing
select * from test_virtual table limit 15 offset 0
select * from test_virtual table limit 15 offset 16
I get back the same rows.
any suggestions
best regards
Rakshetha
I am not a SAP customer or partner yet.
So, I do not have a SAP A/C manager
Thanks for your response.
This sounds interesting..Let me go through this and see if it's suitable for us
Your reply doesn't work either.
What's the error message you get? What is the problem with using any of the options?
Please state your problems properly.
- Lars
Lars where can I find more information on the minicheck scripts you are referring to? Is that the same as the note 1969700 SQL statement collection?
Yes, that's the sap note.
Bojan any thoughts?
Hi Colleagues,
We are planning to create Sales Views in HANA and use the results of them to load into Hybris system to improve a performance of a specific program.
Our DS is not in 4.x version, so we cannot use it as ETL.
Do you have any guidance regarding how can we genearate files from HANA's view and save them in a repository?
I can give you further details if you need.
Thank you in advance for all your help.
Regards
Amanda
I don't have practical SLT experience, but some SLT guys got in touch with me some time ago and asked me which timestamp is written into the logging tables and if it is a good idea to measure the latency based on this timestamp. I said, it's the time of the DML operation and it's not a good idea to measure the latency based on this timestamp, because in this case a late COMMIT can massively impact the measured latency. Of course there can also other reasons for the delays - particularly if tables of different applications are involved.
The mini checks are available via SQL: "HANA_Configuration_MiniChecks..." (SAP Note 1969700) and described in detail in SAP Note 1999993.
Hi Amanda,
1) Write store procedure to consume data from your HANA views and update in a table
2) Then schedule EXPORT SQL statement from the command line mode HDBSQL.
EXPORT - SAP HANA SQL and System Views Reference - SAP Library
1 hdbsql -n localhost:30015 -u system -p password
2. EXPORT "SCHEMA_NAME"."TABLE" AS BINARY INTO '/home/hanauser/hana-database-backups/test.csv'
-Siva
Message was edited by: Sivakumar Palaniswamy
Hi Edukondalu,
If you got answers for your questions , please close thread by rewarding them with points.
-Siva
I am adding additional information as I find it.
Looking at the SAP HANA security guide, section 7 on Single Sign On (see here) I can see notes which indicate that for Kerberos and SAML, if the user is authenticated by an external authentication provider, there is a mechanism to map the external identity to the internal identity of a database user.
Unfortunately the notes also mention that this is not supported for "Logon and Assertion tickets" and for "X.509 Client certificates".
Not sure if that is a deal breaker for this question? I wish some HANA and/or Portal experts would chime in.
Thanks Martin. Just to clarify a bit though. These are my assumptions can you tell me if they are correct?
So hypothetically if I create a sales order #100 and an entry gets posted in SAP table VBAK at 9AM in source table...
Assumption 1: the sales order 100 gets posted immediately in the tracking table. Is it safe to assume there is not normally latency writing to the tracking table?
Assumption 2: Latency is not based on this timestamp of getting written into the tracking table.
>>>...and then continuing my example; for whatever the reason the record isn't committed in HANA until 10AM. Who knows why just yet but besides the point for my example....
Assumption 3: Since it's not committed until 10AM this means it's not available in the delta table. I'm assuming when you say DML commit you are referring to when it's INSERTED/COMMITTED into the delta storage table (prior to delta merge)
Assumption 4: the timestamp for DML operation would be 10AM
Assumption 5: This means sales order #100 will NOT be visible to end users running reports off of HANA that utilize VBAK until 10AM.
Thanks!
-Patrick