How to change SAP Hana Sql Output results are limited to 5000 Records

How to change SAP Hana Sql Output results are limited to 5000 Records

These are quick fixes that are often overlooked because the products come with standard configurations.

The SAP Hana SQL Output results in ECLIPSE, for example, have a limit of 5000 records.

With the following setup, you can change this number to a higher one.

Windows Tab - > Preference -> General - > Runtime - > Result -> Maximum number of rows displayed in results. 

2147483647 is usually the maximum record that can be achieved.

How to Start and Stop SAP Hana Tenant Database - Its too simple

 

How to Start and Stop SAP Hana Tenant Database - Its too simple 

The easiest way for a startup to get started with HANA and explore the administrative side of a Basis career is to use it. Start by learning the basics, for example 

- SAP Hana Studio - What is that?

- SAP Hana DBAcockpit - What is the difference between SAP Hana Studio?

- What is the use of  SAP Hana DB and where it's being used?

What we need to know right now is how to start and stop. Customer Relationship Management (CRM) SAP 

Also, get to know your surroundings

1. HANA DB Cockpit 

2. HANA Studio 

3. HDBSQL 

Please try the simplest or most direct approach. SAP Basis who have worked in Oracle administration would be able to see the parallels.

1. Login to SAP HANA Studio

2. Open SQL Console on the SID by right click

3. To Start Hana Tenant DB - Just execute 

 Alter System Start Database [ your tenant DB ]

4. To Stop Hana Tenant - Just execute 

Alter System Stop Database ( your tenant DB) 

Inactive objects in SAP - SE80 / SE11

The inactive objects in SAP sometimes cause issues if you don't have practice in housekeeping them. from the system.

This is a quick way to check inactive objects

1. Execute t-code SE80 and navigate to Repository Browser , explan the tab and and select inactive objects. 

You may decide what you plan to do with the listed objects if its required for certain cases for example : - 

1. Future use of a change development that was never executed in Production system

2. Error left unattended without cleaning up by poor development work

3. Part of abandon objects during projects or after migrating a system where one of the pre-steps are forgetten.

4. During transport error developer forgets to correct and remove or mark in STMS unlocked objects.

Where this inactive object topic arises - 

1. During migration of SAP system

2. During upgrade actvity

3. Not required but sometimes its part of Database upgrade checklist

4. Applicable during Homogenous & Hetrogeneous system copy or refresh

5. System migration

6. Upgrade to Hana

What happens if you left it hanging and don't bother: - 

1. Potential issues arises during Upgrade when one of the phases will detect issue and cause problem.

2. Future critical transport to production during an important event get stopped, it could be that clean was only done in DEV but developer forgets to perform the clean up right up to production system.

3. During system migration, it can garbase such as invalid objects are being brought over to new system, this confuses the future owner of the system just in case issues arises,

 SAP Tables for inactive objects you may click here

There are also ABAP Report to access to these invalid objects

RSSHOW_INACTIVE_OBJECTS SAP ABAP Report - Display Inactive Objects

While exploring the above it's always good to explore SAP Note for further information by following the note 

The below is just some reference points.

2486685 - WARNING: INVALID_SAP_OBJECTS during pre_upgrade_checks.sql

How to kill SAP Hana session - It is easy to end or kill SAP Hana session - Quick Tips

How to kill SAP Hana Session

Do you know if it's simple to locate SAP HANA's IDLE connection session? If so, why do you need to do so? It's most likely because of a zombie session or a procedure where the session is no longer in use.

There's also an intriguing technique that I typically employ when dealing with such difficulties -

2092196 - SAP HANA How-To: Terminating Sessions

You may also use keywords like - SAP HANA terminate session connection disconnect cancel kill hang stuck, KBA, HAN-DB-ENG, SAP HANA DB Engines, HAN-DB, SAP HANA Database, HAN-DB-ENG, SAP HANA DB Engines, HAN-DB, SAP HANA Database, HAN-DB-ENG, SAP HANA DB Engines, HAN-DB, SAP HANA Database, The simplest approach to find out your IDLE session is to do the following: -

SELECT CONNECTION_ID, IDLE_TIME FROM M_CONNECTIONS WHERE CONNECTION_STATUS = 'IDLE' AND CONNECTION_TYPE = 'Remote'  ORDER BY IDLE_TIME DESC

Therefore once finding out the session then execute the following ALTER command to end it.

ALTER SYSTEM DISCONNECT SESSION   '{connection_id}'

These checks are necessary if any suspicious jobs, sessions, or remote calls are initiated, and the system is left orphaned.

Prince 2 Agile approach on SAP enterprise projects

 It's strange that in SAP projects, SAP Activate are the content to be used in a guided way to conduct,engage into a project or execute BAU activity that are similar to a project. 

However there's always this craving where Programme Manager whom is in charge of the project managers and would always wants to report to the board or rather the PM itself would like to report to the Board / Stakeholders using Prince 2 framework, reporting structure and its methodology. Although since prince 2 carries Agile word in it, that does not differ so much on SAP Activate. But on a broader audience the world outside SAP  likes Prince 2 Agile approach and mostly merging them with SAP Activate approach. 

This also could be because the board or stakeholder might not live or use SAP, since SAP is mostly related to IT projects. However Prince 2 are applicable broadly on any non IT projects as well. that's the reason why such preference are adapted. 

Having said such , SAP Activate is always the key for running SAP projects regardless implementation, migration, BAU and others. 

In a single word SAP Activate methodology in Agile meaning flexibility to deliver your projects and not getting locked into waterfall methodology.

SAP Patch day August 2021

Insight on SAP Patch day release, applying it and some methods based on my opinion.

Normally in any organization there will be a policy governance to apply security notes supplied by SAP. Sometimes a threshold is being set to only apply CVSS level 9 and above. While other organization will apply all of it. 

You can click the CVSS below to find out the scores and why some organization set to certain standard.  --> Common Vulnerability Scoring System Version 3.0 Calculator

The last time its always difficult to match if the note is applicable, however now SAP patch day states the product version as well. That eases the entire thinking of applying patch.

Just to share  there are two ways or more in applying security notes in an easier way.

1 . Using the conventional way that is by DEV -> snote t-code and follow with the standards

2. Using solution manager 

3. It's also highlighted in your EWA  or TPO that some security notes that are required but not highlighted in SAP patch day, yet those on TPO or EWA report are mainly not for threats but more of a fix DB and SAP or OS related fix. 

But there are more towards it. What if you miss the August Patch and then review somewhere in Dec Patch day release. 

Few options as well,

1. Mostly minor kernel update will overcome almost 50 - 60% secuity patches and some support package update might populate the rest of the released security notes.

2. If you have missed security note for more than a yeear then the easy way out is by quarterly support package update, database update.

3. OR if you are lucky and if your organization practices limited CVSS level patch update for example 9 and obove then its even easier but becomes complicated as testing need to be done if the system is 24/7 and run critical operations. 

Well folks thats all - enjoy with you SAP notes and methods and ways to handle it. 

SAP Hana DB restore and Progress details

SAP Hana DB restore and Progress details 

Finding out the progress of the restore and other relevant details may be of interest in SUSE Linux.

It was easy to check the status of backups in previous SAP ERP solutions, regardless of whether we were using third-party tools in the cloud or on-premise....

Your might remember commands like this  # ps -ef * backup*

and most of the time ending it is easily done if its on oracle 

&> alter database end backup; or view the backup log

Hana, on the other hand, doesn't really change much.

All you need to do is cd or change directories to the drive location and view the backup.

Backup and restore activity is recorded in a log file from beginning to end.

#cd /hana/shared/SID/HDB00/HOSTNAME/trace/DB_SID #ls -lrt *backup*  backup.log

SAP Hana Numeric Error Codes

There's no doubt that SAP Hana will be A large number of numeric error codes, which I thought might be helpful, appeared on my screen. Simple select statements will now be used to extract these codes.

select * from M error codes order by asc;