Hi Guys,

I have 2 identical tables each containing 183 mio records.

One of them is compressed and the other isn't.

The compressed table takes up 16 GB in memory the other 55 GB.

If I look in m_cs_columns under compression_type table 1 has different types for each column (RLE,CLUSTERED,INDIRECT,PREFIXED)

and table 2 has compression_type DEFAULT in all columns.

My guess is that the evalutation of compression_type hasnt run. Because the optimization works fine on the first table.

In table "tables" both tables have AUTO_OPTIMIZE_COMPRESSION_ON set to TRUE and are otherwise totally identical.

Is there any way i can initiate this optimization by a command?

Or do you have any other suggestions?

Best Regards

- Rasmus

Hi Experts,

I have a simple question. I am wondering what is the definition of each "thread type" in the view Hana Administration\Performance\Thread. I skimmed through HANA administration guide and it is mentioned that this column is only relevant for SAP support.

The reason why I want to understand this information is because whenever I log into the HANA system (We have BW on HANA) there are 45 threads are opened under my id even if I am doing nothing in the system. These threads belong to 5 services and they are opened on each node. So you can imagine we have 9 nodes.

I am wondering if they consume memory in the system and how do I rationalize consumption of memory based on this thread if we have multiple idle users logged into the system.

Thanks,

Hi folks,

Is there anyway to gauge how much CPU is being consumed by which application?  For example when I see high CPU during live monitoring of the system I will look at threads and if there is very little connections I can easily see whom is consuming the CPU.  However when I look at SESSIONS and I see several different Appl. Users connecting and running many different ABAP sidecar reports (ie: displayed in Appl. Source column) it's difficult to tell which one could be consuming the most CPU.  ie: I'm concerned that one is consuming much more CPU than the others and I want to identify which one so perhaps we can fine tune it.  Is there anyway to tie CPU to Appl. Source?

Thanks,

-Patrick

Hi all,

I’m looking for some informations about this case:

Variables on SAP Lumira on SAP HANA

I have one preconfigured report on HANA (Manufacturing Order Due Date Adherence which uses “sap.hba.ecc/ MfgOrderItemDueDateAdherenceQuery” query), I open it by SAP lumira. But before the refresh you have to modify the variables. I can’t modify

Do you know why?

I can’t remove the number …

Do you think that into these preconfigured query on SAP HANA, the variables are by default?

(cf attachments Predictive Asset Management_Ouverture_Impossible)

Hello,

as I try to understand some of the concepts of SAP HANA I thought it is a good idea to have a look at the internal attributes. I saw that in M_CS_ALL_COLUMNS all columns are listed. When I made a GROUP BY on INTERNAL_ATTRIBUTE_TYPE with a count(*) I found values for NULL, ROWID, TREX_UDIV, TREX_EXTERNAL_KEY and CONCAT_ATTRIBUTE.

As I could read in several sources all of these values are clear to me:
NULL - it is no internal column

ROWID - Internal unique identifyer of the row

TREX_UDIV - some internal transaction value

TREX_EXTERNAL_KEY - multicolumn primary key index

CONCAT_ATTRIBUTE - Index for multicolumns joins

The problem is that I found another INTERNAL_ATTRIBUTE_TYPE called "UNKNOWN" used in _SYS_REPO and SAPSR1 (BW on HANA). The column names always used following pattern: $_SYS_SHADOW_<COLUMN>$"

Does someone know something about this INTERNAL_COLUMN_TYPE?

Thanks

Patrik

Hi Experts,

As per the posts/Blogs in SDN, Referential Join will act as INNER JOIN when we access the fields from both joined tables.

It will act as LEFT OUTER JOIN if no fields from Right table are accessed and it will not check whether corresponding value is exist in Right table or not assuming referential Integrity is maintained

To test Referential Join I have created a Attribute View with below mentioned tables which have one column Country

TAB1:                                                 TAB2:

Country                                                Country 

INDIA                                                    UK  

SRILANKA                                            US

NEPAL                                                 GERMANY

I have created a Attribute View with Referential Join and I am fetching field only from TAB1 (i.e.TAB1.Country) i.e. I have selected  TAB1.Country as output of the Attribute View.  Since there is no referential integrity maintained and only left table is queried hence Left Outer Join should be applied and all the records from Left table should be displayed.

But there are no records are fetched and displayed (its working as Inner Join even though only Left table is queried)

I am confused in understanding the Referential Join, Could you please explain me how does it work

Regards,

Nag

Hi Folks,

This might be a strange requirement,

hdbsql -i 01 -u system
Password:

Welcome to the SAP HANA Database interactive terminal.

Type:  \h for help with commands
       \q to quit

If i run like this then password is invisible,

But if i run like this i dont get prompted for a password screen where i can enter

hdbsql -i 01 -u system -I temp.sql

* -10709: Connection failed (RTE: Kerberos error. Major: "unspecified ", minor: "No credentials cache found"

I dont want to use it like this :  hdbsql -i 02 -u system -I temp.sql -p *******

Also i dont want to use the existing hdbsuserstore key.

Is there a way to achieve this?

Hi folks,

Suppose I have a query that returns a potentially large result set, such as

SELECT * FROM BUT000;

or

SELECT

    OPBEL,

    VKONT,

    VTREF,

    HVORG,

    TVORG,

    SUM ( BETRH ) AS BETRH

FROM DFKKOP

GROUP BY OPBEL, VKONT, VTREF, HVORG, TVORG;

I don't want to overwhelm the client (front-end, service consumer, ABAP application using a secondary database connection, whatever) with the entire results set but retrieve and display it in chunks of 100. I want to allow forward and backward navigation in the result set: Show me the first 100, then the second 100, the third 100, then back to the second 100, and so on.

I've found two things that come close to what I want:

1) SELECT ... LIMIT ... OFFSET

SELECT * FROM BUT000 -- 1st 100

  LIMIT 100;

SELECT * FROM BUT000 -- 2nd 100

  LIMIT 100 OFFSET 100;

SELECT * FROM BUT000 -- 3rd 100

  LIMIT 100 OFFSET 200;

SELECT * FROM BUT000 -- 2nd 100 again

  LIMIT 100 OFFSET 100;

Disadvantage: Each time I want to retrieve a package, the query is executed again.

2) ADBC package handling

  DATA:

    lr_sql      TYPE REF TO cl_sql_statement,

    lr_result   TYPE REF TO cl_sql_result_set,

    lr_results  TYPE REF TO data.

  CREATE OBJECT lr_sql

    EXPORTING

      con_ref = cl_sql_connection=>get_connection( 'SECONDARY' ).

  lr_result = lr_sql->execute_query( |SELECT * FROM SAPDAT.BUT000| ).

  GET REFERENCE OF lt_results INTO lr_results.

  lr_result->set_param_table( lr_results ).

  DO 3 TIMES.

    CLEAR lt_results.

    lr_result->next_package( 100 ).

  ENDDO.

  lr_result->close( ).

Disadvantage: can only navigate forward to the next package, no backward navigation or free positioning available.

I'd be happy with solutions that solve the problem at the HANA/SQL Script level or at the ABAP level. Who can help?

Thanks,

Thorsten

We plan to implement multi-tenant Hana DB.

However, SAP guide says that all instances in above DB must have the same SID.

But I think it's useless if both our ECC and BW have the same SID (e.g. DEV) on the same box.

Is my understanding wrong?

Thanks!

Hi All,

We have added two columns to a cluster table, BSEG in ECC. Would like to know as to how can this be replicated to HANA in a side car scenario ?

We are using SLT for replication of Data to HANA.

Thanks Much,

Abhishek

Hello Gurus:

Need help with the below issues

1.Security administrator had left the company and if i have to revoke the roles assigned by him to a user i am not able to. Please advise how do i go about it

2. When a user gets a no authorization message i go the trace file and do not see much information there. Please advise.

Thanks

Hi,

I'm new to HANA/XS. I'm trying to create a test Hana application. I have eclipse luna 4.4.1 installed. I have installed Hana plugin from https://tools.hana.ondemand.com/luna (screen shot below):

I have connected to a HANA system, created repository, packages etc. Basically all the necessary things to create a test HANA XS project.

But, when I create .xsapp and .xsaccess I get the following error whenever I try to activate those files:

Unsupported encoding Cp1252, only UTF-8 encoding is supported

Am I missing something? I tried finding similar error in the forum, but I was not successful. Kindly try to help me.

Thanks & Regards,

Lohit

Hi all,

How can we transport HANA DB triggers which are not part of a delivery unit?

Thanks,

Christoph (new to HANA)

Hi All,

As part of Lumira Server installation I have to install UAFL plugin. I have installed the plugin as SIDADM user which should be installed as root. Now I wan't to uninstall the plugin and install again as root.

Help.sap.com has installation guide(http://help.sap.com/businessobject/product_guides/vi01/en/lumS121_install_en.pdf) but no where it mentions how to uninstall UAFL plugin.

Is there way to uninstall plugins on HANA?

Please help

Regards,

Raj

Message was edited by: Tom Flanagan

Hi Friends,

i have a question.

which one is the best option to suggest a client BODS or SLT and why?and the client has no budget issues.

what could be the best reasons/factors to provide so that they can think and take a decision.

Is it possible to use both SAP BI/BW and  SAP HANA at the same time.

Normally if we are using SAP BI/BW as warehouse then it is better to migrate it SAP BW 7.4 powered with HANA instead of installing separate SAP HANA.

But is there a case where we can go for both SAP BW and SAP HANA? If yes, how it would be ? which would be the warehouse ?

Hi,

I have a calcuation view where I like to keep the SAP field descriptions all the way.

It seems to keep the descrptions all the way up until I connect the last node( in this case it is a Join node) to the default projection node.

Once view is completed and activated, the labels stayed in the semantic layer and projection node, but they were gone from all ther nodes below default projection node.

Does anyone know what causes this and how I can prevent this from happening?

By the way we are on Revision 7.0.

thank you.

Hyun Grasso

Hi,

We are looking to setup SLT with SQL Server as source and HANA as destination for a side car setup
Source SQL Server more than a 3 TB Database

A new File group created for all the SLT logging tables on the source SQL Server Database along with a data file corresponding to this filegroup

During the setup of SLT we are looking to specify this filegroup for the logging tables and the only possible option seems to be the *Data class of Tablespace* under the CREATE CONFIGURATION-->Data Transfer Settings

After setting the Filegroup of the source SQL Server under the *Data Class of Tablespace* we are able to start the SLT jobs but the logging tables do not get created on the SLT specific filegroup data file, instead they get created on the default filegroup data files

Has any one come across this before, any suggestions to make it work would be much appreicated

Note: I have already reviewed the SLT Installation guide and SAP notes referred in the guide, none of the them point to my question above especially when we have the source Database on SQL Server, so please do not indicate the same steps

Dear all,

Why my logs in

hana01:/usr/sap/NDB/HDB00/backup/log

are groving so fast (every 20 minutes)?

even when I change my Backup Destinantion to another location /HANA_DATA/hana_backup

-rw-r--r-- 1 ndbadm sapsys 53248 Nov 27 01:23 log_backup_4_0_3600576_3601280

-rw-r--r-- 1 ndbadm sapsys      53248 Nov 27 01:42 log_backup_4_0_3601280_3601984

-rw-r--r-- 1 ndbadm sapsys 53248 Nov 27 01:57 log_backup_4_0_3601984_3602688

-rw-r--r-- 1 ndbadm sapsys 53248 Nov 27 02:13 log_backup_4_0_3602688_3603392

-rw-r--r-- 1 ndbadm sapsys 53248 Nov 27 02:32 log_backup_4_0_3603392_3604096

-rw-r--r-- 1 ndbadm sapsys 45056 Nov 27 02:47 log_backup_4_0_3604096_3604672

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 03:04 log_backup_4_0_3604672_3605440

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 03:22 log_backup_4_0_3605440_3606208

-rw-r--r-- 1 ndbadm sapsys 40960 Nov 27 03:38 log_backup_4_0_3606208_3606720

-rw-r--r-- 1 ndbadm sapsys 65536 Nov 27 03:57 log_backup_4_0_3606720_3607616

-rw-r--r-- 1 ndbadm sapsys 61440 Nov 27 04:17 log_backup_4_0_3607616_3608448

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 04:37 log_backup_4_0_3608448_3609216

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 04:57 log_backup_4_0_3609216_3609984

-rw-r--r-- 1 ndbadm sapsys 65536 Nov 27 05:15 log_backup_4_0_3609984_3610880

-rw-r--r-- 1 ndbadm sapsys 61440 Nov 27 05:37 log_backup_4_0_3610880_3611712

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 05:57 log_backup_4_0_3611712_3612480

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 06:18 log_backup_4_0_3612480_3613440

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 06:38 log_backup_4_0_3613440_3614208

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 06:58 log_backup_4_0_3614208_3614976

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 07:18 log_backup_4_0_3614976_3615936

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 07:38 log_backup_4_0_3615936_3616704

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 07:58 log_backup_4_0_3616704_3617472

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 08:18 log_backup_4_0_3617472_3618432

-rw-r--r-- 1 ndbadm sapsys 57344 Nov 27 08:38 log_backup_4_0_3618432_3619200

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 08:58 log_backup_4_0_3619200_3620160

-rw-r--r-- 1 ndbadm sapsys     106496 Nov 27 09:17 log_backup_4_0_3620160_3621696

-rw-r--r-- 1 ndbadm sapsys     122880 Nov 27 09:32 log_backup_4_0_3621696_3623488

-rw-r--r-- 1 ndbadm sapsys 77824 Nov 27 09:48 log_backup_4_0_3623488_3624576

-rw-r--r-- 1 ndbadm sapsys 73728 Nov 27 10:04 log_backup_4_0_3624576_3625600

-rw-r--r-- 1 ndbadm sapsys 65536 Nov 27 10:22 log_backup_4_0_3625600_3626496

-rw-r--r-- 1 ndbadm sapsys 98304 Nov 27 10:39 log_backup_4_0_3626496_3627904

-rw-r--r-- 1 ndbadm sapsys 77824 Nov 27 10:55 log_backup_4_0_3627904_3628992

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 11:15 log_backup_4_0_3628992_3630208

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 27 11:35 log_backup_4_0_3630208_3631488

-rw-r--r-- 1 ndbadm sapsys 73728 Nov 27 11:55 log_backup_4_0_3631488_3632512

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 12:15 log_backup_4_0_3632512_3633728

-rw-r--r-- 1 ndbadm sapsys     114688 Nov 27 12:35 log_backup_4_0_3633728_3635392

-rw-r--r-- 1 ndbadm sapsys 73728 Nov 27 12:53 log_backup_4_0_3635392_3636416

-rw-r--r-- 1 ndbadm sapsys 77824 Nov 27 13:09 log_backup_4_0_3636416_3637504

-rw-r--r-- 1 ndbadm sapsys     126976 Nov 27 13:25 log_backup_4_0_3637504_3639360

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 27 13:45 log_backup_4_0_3639360_3640640

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 14:06 log_backup_4_0_3640640_3641792

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 14:25 log_backup_4_0_3641792_3643008

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 27 14:46 log_backup_4_0_3643008_3644288

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 15:06 log_backup_4_0_3644288_3645440

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 15:22 log_backup_4_0_3645440_3646400

-rw-r--r-- 1 ndbadm sapsys 73728 Nov 27 15:37 log_backup_4_0_3646400_3647424

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 27 15:56 log_backup_4_0_3647424_3648704

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 16:16 log_backup_4_0_3648704_3649920

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 16:36 log_backup_4_0_3649920_3651072

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 27 16:56 log_backup_4_0_3651072_3652352

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 17:16 log_backup_4_0_3652352_3653568

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 17:37 log_backup_4_0_3653568_3654720

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 17:57 log_backup_4_0_3654720_3655872

-rw-r--r-- 1 ndbadm sapsys 73728 Nov 27 18:15 log_backup_4_0_3655872_3656896

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 18:30 log_backup_4_0_3656896_3657856

-rw-r--r-- 1 ndbadm sapsys 77824 Nov 27 18:47 log_backup_4_0_3657856_3658944

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 27 19:07 log_backup_4_0_3658944_3660224

-rw-r--r-- 1 ndbadm sapsys 69632 Nov 27 19:25 log_backup_4_0_3660224_3661184

-rw-r--r-- 1 ndbadm sapsys 65536 Nov 27 19:40 log_backup_4_0_3661184_3662080

-rw-r--r-- 1 ndbadm sapsys 77824 Nov 27 19:57 log_backup_4_0_3662080_3663168

-rw-r--r-- 1 ndbadm sapsys 94208 Nov 27 20:17 log_backup_4_0_3663168_3664512

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 20:37 log_backup_4_0_3664512_3665664

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 20:57 log_backup_4_0_3665664_3666816

-rw-r--r-- 1 ndbadm sapsys 94208 Nov 27 21:18 log_backup_4_0_3666816_3668160

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 21:38 log_backup_4_0_3668160_3669312

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 21:58 log_backup_4_0_3669312_3670464

-rw-r--r-- 1 ndbadm sapsys 98304 Nov 27 22:22 log_backup_4_0_3670464_3671872

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 22:43 log_backup_4_0_3671872_3673024

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 27 23:03 log_backup_4_0_3673024_3674176

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 23:23 log_backup_4_0_3674176_3675392

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 27 23:40 log_backup_4_0_3675392_3676608

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 00:03 log_backup_4_0_3676608_3677824

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 00:23 log_backup_4_0_3677824_3679040

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 00:43 log_backup_4_0_3679040_3680320

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 01:03 log_backup_4_0_3680320_3681472

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 01:23 log_backup_4_0_3681472_3682688

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 01:43 log_backup_4_0_3682688_3683968

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 02:04 log_backup_4_0_3683968_3685120

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 02:24 log_backup_4_0_3685120_3686336

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 02:44 log_backup_4_0_3686336_3687616

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 03:04 log_backup_4_0_3687616_3688768

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 03:24 log_backup_4_0_3688768_3689984

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 03:44 log_backup_4_0_3689984_3691136

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 04:00 log_backup_4_0_3691136_3692352

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 04:24 log_backup_4_0_3692352_3693632

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 04:44 log_backup_4_0_3693632_3694784

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 05:04 log_backup_4_0_3694784_3696064

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 05:24 log_backup_4_0_3696064_3697280

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 05:45 log_backup_4_0_3697280_3698432

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 06:05 log_backup_4_0_3698432_3699712

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 06:25 log_backup_4_0_3699712_3700928

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 06:45 log_backup_4_0_3700928_3702080

-rw-r--r-- 1 ndbadm sapsys 94208 Nov 28 07:05 log_backup_4_0_3702080_3703424

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 07:25 log_backup_4_0_3703424_3704640

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 07:45 log_backup_4_0_3704640_3705792

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 08:05 log_backup_4_0_3705792_3707072

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 08:25 log_backup_4_0_3707072_3708288

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 08:46 log_backup_4_0_3708288_3709440

-rw-r--r-- 1 ndbadm sapsys 81920 Nov 28 09:06 log_backup_4_0_3709440_3710592

-rw-r--r-- 1 ndbadm sapsys 90112 Nov 28 09:25 log_backup_4_0_3710592_3711872

-rw-r--r-- 1 ndbadm sapsys 86016 Nov 28 09:46 log_backup_4_0_3711872_3713088

-rw-r--r-- 1 ndbadm sapsys 94208 Nov 28 10:06 log_backup_4_0_3713088_3714432

Hi All,

we have created custom tables in HANA Studio and after upgrade we don't see these tables in HANA.

Does custom tables get's deleted after upgrade or this is because of System restart?

Is there any guide or blog post which details the behaviour of custom tables in HANA.

Regards,

Raj

Message was edited by: Tom Flanagan