How to modify the log mode on Sybase ASE

To modify the log mode on Sybase ASE, you have to follow further steps :

1. Log in on your server with user syb<sid>
2. Launch with a command line tool to connect to ASE database
> isql -Usapsa -P<password> -X
3. On the SQL interface, enter the statements to change log mode

Install SAP HANA Tools for Eclipse

Before developing your SAP HANA XS application, you need to download and set up the necessary tools.

Prerequisites

  • You have downloaded and installed a 32-bit or 64-bit version of Eclipse IDE, version Neon. For more information, see Install Eclipse IDE.
  • You have configured your proxy settings (in case you work behind a proxy or a firewall). For more information, see Install SAP Development Tools for Eclipse → step 3.

TEST C_FIORADM_21 | SAP Certified Technology Associate - SAP Fiori System


SAP Certified Technology Associate - SAP Fiori System - LINK


NO.1 You want to work with the sap gate way performance trace tool (transaction/IWFND? TRACES).
What can you configure?
There are 2 correct answers to this question.
Response:
A. The application server(S) on which the trace is activated
B. The duaration in hours for the active trace
C. The maximum number of entries in the trace
D. The number of days to keep the performance trace data

Increase the System Isolation Level

Prerequisites Increase the System Isolation Level
You have root access to the SAP HANA system.
You are logged on to the system database in the SAP HANA cockpit.
You have the system privilege DATABASE ADMIN.
Internal SAP HANA communication has been appropriately configured for TLS/SSL.
[communication] ssl in the global.ini file must have the value false (default) or systemPKI.

For more information, see Secure Internal Communication and Server-Side TLS/SSL Configuration Properties for Internal Communication in the SAP HANA Security Guide.

If the system is running in an SAP HANA system replication configuration, the system PKI SSFS data file and key file have been copied from the primary system to the same location on the secondary system(s):
$DIR_INSTANCE/../global/security/rsecssfs/data/SSFS_<SID>.DAT
$DIR_INSTANCE/../global/security/rsecssfs/key/SSFS_<SID>.KEY

Procedure Increase the System Isolation Level
1             For every tenant database, create a dedicated OS user and group:
                A             As root user, log on to the server on which the name server of the system database is running.
                B             Create new groups for every tenant database:
                               groupadd <groupname>
                C             Create new users for every tenant database, specifying sapsys as the primary group:
                               useradd -g sapsys <username>
                D             Add every new user to the sidshm group and their own group as secondary groups:
                               usermod -G <sid>shm,<usergroup> <username>
                              
2             Stop all tenant databases in the system.
                               In the system database, execute the SQL statement ALTER SYSTEM STOP DATABASE <databasename>.

3             Configure the system for high isolation.
                               As the operating system user <sid>adm, log on to the server on which the master index server is running and run the following command:

                               python /usr/sap/<SID>/HDB<instance>/exe/python_support/convertMDC.py --change=databaseIsolation --isolation=high
               
                This command runs the following actions:

                               Stops the system
                               Changes the value of the [multidb] database_isolation property in the global.ini file to high
                               Starts the system
                              
4             Assign every database to their respective OS user and group.
                               In the system database, execute the SQL statement ALTER DATABASE <databasename> OS USER '<username>' OS GROUP '<groupname>'
                              
5             Start all tenant databases.
                               In the system database, execute the SQL statement ALTER SYSTEM START DATABASE <database_name>                       
                              
Results Increase the System Isolation Level
               
                The system is now running in high isolation mode. As a result:

                               The processes of individual tenant databases run under dedicated OS users belonging to dedicated OS groups and the processes of the system database run under the <sid>adm user.
                               Internal database communication is authenticated using X.509 client certificates. Depending on how SSL for internal communication is configured, data communication within databases may also be encrypted. For more information about secure internal communication, see the SAP HANA Security Guide.
                               Operations that require operating system access are restricted to users with the correct permissions. For more information, see the section on file and directory permissions with high isolation.
                               New tenant databases can only be created if a dedicated OS user and group exist.

SAP HANA - Secure storage is locked


Sometimes when entering the SAP HANA Studio, it shows us the message:

Secure Storage locked.

Solution:

Info for the certification C_HANATEC_15


Info for the certification C_HANATEC_15

C_HANATEC_15
SAP Certified Technology Associate - SAP HANA 2.0 (SPS03) Link

HA200 – SAP HANA Installation & Operations based on SAP HANA 2.0 SPS03.
HA201 – SAP HANA High Availability and Disaster Tolerance Administration based on SAP HANA 2.0 SPS03.
HA215 – SAP HANA Using Monitoring Performance Tools based on SAP HANA 2.0 SPS03.
HA240 – Authorization, Security and Scenarios based on SAP HANA 2.0 SPS03.
HA250 – Migration to SAP HANA Using DMO based on SAP HANA 2.0 SPS02.

How to start or stop SAP HANA database

login as root:
  /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function Start
  /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function Stop
  /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function GetProcessList

 login as sidad:
  # su - hdbadm
  # ./HDB stop
  # ./HDB start
  # ./HDB --help
  usage: ./HDB { start|stop|reconf|restart|version|info|proc|admin|kill|kill-|term}


  /usr/sap/<SAPSID>/<Instance_Name>/HDB start
  /usr/sap/<SAPSID>/<Instance_Name>/HDB stop
  /usr/sap/HDB/HDB00> HDB info; netstat -nat

 
 Arrancar o parar tenant database desde SYSTEMDB
  ALTER SYSTEM START|STOP DATABASE CSN

SAP HANA Best practices table partitioning

SAP HANA Best practices table partitioning


  • Keep the number of partitioned tables low.
  • Keep the number of partition per table low.
  • Keep the number of key columns low.
  • For SAP Business Suite on HANA, keep the partitions on same host.
  • Repartitioning aaa multiple or a division of current number of partitions.
  • No extra unique constrains.


Display Schema List on SAP HANA Database

SAP users can get the list of all schemas created on SAP HANA database with the schema owner name by executing SQL query on SYS.Schemas view.

Here is the SQLScript SELECT statement for database developers to display and return the list of all schemas on the HANA database.


select
 schema_name,
 schema_owner
from sys.schemas;

-- or using the public synonym

select * from schemas;