Friday, 28 June 2019

Database option 'trunc log on chkpt' to 'true' for the SUM process


Issue:

During Upgrade step to start "Execution" and the process tells me: WARNING: 'Database log mode' will not be changed automatically. If you want to disable archiving now, set database option 'trunc log on' to 'true' for the XXX database.
Error occured in Sybase ASE.


Resolution:

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

1. Log in on your server with user syb

2. Launch with a command line tool to connect to ASE database

> isql -Usapsa -P< password > -S< SID > -X

3. On the SQL interface, enter the statements to change log mode

1> use master

2> go

1> sp_dboption <SID>, 'trunc',true

2> go

Database option 'trunc. log on chkpt.' turned OFF for database ''.

Running CHECKPOINT on database '' for option 'trunc. log on chkpt.' to take

effect.

(return status = 0)


1> checkpoint

2> go

After finish the Upgrade change the Setting "true" to "false".

1. Log in on your server with user syb

2. Launch with a command-line tool to connect to ASE database

> isql -Usapsa -P< password > -S< SID > -X
3. On the SQL interface, enter the statements to change log mode

1> use master

2> go

1> sp_dboption <SID> , 'trunc',false

2> go

Database option 'trunc. log on chkpt.' turned OFF for database ''.

Running CHECKPOINT on database '' for option 'trunc. log on chkpt.' to take

effect.

(return status = 0)


1> checkpoint

2> go

This command will ensure that everytime a checkpoint comes along, the Sybase dataserver engine will truncate the transaction log. You should not do this on a production server, as the transaction log is used for performing a complete restoration of data.  You may want to do this when you don't have enough space for keeping transaction data, like on a quality server or development server. 


Monday, 17 June 2019

Stop Running SAP Transport Request(TR).

Steps for stop running TR in SAP.

1.  Execute transaction code STMS_IMPORT.
     Select Goto > Import Monitor.
    Under Execution, Select the transport and right click.
    Choose on Delete entry to stop the running transport.


2. Now Running Transport Request Stoped and redy to Import.

Wednesday, 5 June 2019

SAP Solution manager USER_AUTH_FAILED - SLD authorization issue


Symptom

Error: USER_AUTH_FAILED when entering the username and password? to logon to local SLD.

Environment

    SAP Solution Manager 7.1
    SAP Solution Manager 7.2


Reproducing the Issue

    Execute transaction Solman_Setup.
    Select System Preparation -> Prepare Landscape Description -> step Select SLD (Solution Manager 7.1)
    or Infrastructure Preparation -> Set Up Landscape Management -> step SLD Connections (Solution Manager 7.2)
    Click the Button 'Select Local SLD' where you enter a Username and Password
    Results with USER_AUTH_FAILED.

Cause

Missing authorization for the user which is used to logon to SLD. The user should be a system user too.

Resolution

SAP recommends to use the user 'SLDDSUSER' in step Select SLD (Solution Manager 7.1) / SLD connections (Solution Manager 7.2).
The user SLDDSUSER in the SAP Solution Manager is required by the SLD data suppliers to write technical system information into SLD.

The user in step Select SLD (Solution Manager 7.1) / SLD connections (Solution Manager 7.2) requires UME role: SAP_SLD_DATA_SUPPLIER to create, modify and delete CIM instances of the landscape description subset as a data supplier without access to the SLD User Interface.
For an SLD as of release SAP NetWeaver 7.1 user needs also the role SAP_SLD_CONTENT_SYNC.
For an SLD as of release SAP NetWeaver 7.0 user at least needs the role SAP_SLD_GUEST.

This user should be defined as a System User.

Saturday, 25 May 2019

SAP HANA system High CPU Utilization Caused by Multiple Threads in sse_icc_lib::mgetSearchi_SSE4impl


Symptom

You experience high CPU utilization. In kernel profiler trace or runteimdump you identify multiple threads in callstack:

sse_icc_lib::mgetSearchi_SSE4impl
sse_icc_lib::mgetSearchi_SSE4
TRexUtils::IndexVectorRef::mgetSearch
...
TRexUtils::JobParallelMgetSearch::run()
TRexUtils::Parallel::JobBase::runEx()
TRexUtils::Parallel::JobBase::run
...

or

sse_icc_lib::mgetSearchi_AVX2impl
sse_icc_lib::mgetSearchi_AVX2
TRexUtils::IndexVectorRef::mgetSearch
...
TRexUtils::JobParallelMgetSearch::run()'
TRexUtils::Parallel::JobBase::runEx()
TRexUtils::Parallel::JobBase::run
...

or

sse_icc_lib::mgetSearchi_AVX512impl
sse_icc_lib::mgetSearchi_AVX512
TRexUtils::IndexVectorRef::mgetSearch
...
TRexUtils::JobParallelMgetSearch::run()'
TRexUtils::Parallel::JobBase::runEx()
TRexUtils::Parallel::JobBase::run

Other Terms

SAP HANA, column store, high CPU, secondary index
Reason and Prerequisites

Reason:

Above callstack points to single attribute scan on a column store table.


Solution

This can be alleviated by creating a secondary index on the table and columns to be searched.

Creating the index will improve query performance significantly (factor 10 and more) and reduce CPU consumption, but will also increase memeory consumption as a concatenated attribute will be generated.




 More details : 2321573

Friday, 24 May 2019

SAP HANA sidadm user login error

Symptom

It is reported that when logging in with an adm, and the loging scripts initializing the users environment fail to run correctly and the Admin user cannot be used.

It is also reported that other adm accounts do not have the same problem, even for the same SID.

The following errors are seen when logging in:

:~ # su - adm
su: warning: cannot change directory to /usr/sap//home: Permission denied
-sh: grep: command not found
-sh: warning: setlocale: LC_MESSAGES: cannot change locale (en_US.UTF-8): Permission denied
-sh: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8): Permission denied
-sh: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8): Permission denied
-sh: warning: setlocale: LC_TIME: cannot change locale (en_US.UTF-8): Permission denied
-sh: warning: setlocale: LC_NUMERIC: cannot change locale (en_US.UTF-8): Permission denied
-sh: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_MESSAGES: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_MESSAGES: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_NUMERIC: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_NUMERIC: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_TIME: cannot change locale (en_US.UTF-8)
-sh: warning: setlocale: LC_TIME: cannot change locale (en_US.UTF-8)
-sh: grep: command not found
-sh: grep: command not found
-sh: grep: command not found
-sh: grep: command not found
-sh: grep: command not found
-sh: grep: command not found
-sh: grep: command not found
-sh: sed: command not found
-sh: sed: command not found
-sh: /usr/sap//home/.profile: Permission denied
adm@:/root>


Environment

HANA DB 2.0
Reproducing the Issue

    Log in with the User Account adm (using ssh or su will give the same result).


Cause

The adm user has the following ACL permissions for the /usr directory:

# file: usr
# owner: root
# group: root
user::rwx
user:adm:r--
group::r-x
mask::r-x
other::r-x


Solution

Grant read/write persmissions to the "SID"adm user








More details2780462

Thursday, 23 May 2019

SAP HANA startup fails with a crashdump in hdbdaemon


Symptom

You are starting HANA. During the startup, it fails and you find a crashdump in the daemon process with name similar to daemon.crashdump.044766.trc. Upon checking the crashdump file, you observe the [CRASH_STACK] session have the following content:

[CRASH_STACK] Stacktrace of crash: (no-section-time-available)
----> Pending exceptions (possible root cause) <---- br="">exception 1: no.1000000 (MultiDB/impl/MultiDBConfiguration.cpp:392)
 hdbmdcdispatcher has wrong permissions /usr/sap//HDB00/exe/mdc/hdbmdcdispatcher 33128 != 04550; $condition$=(info.st_mode & 07557) == 04550
NO exception throw location recorded. Stack generation system error.

Unknown pending exception
Throw location of the exception unknown

Environment

    SAP HANA Platform 1.0;
    Multitenant Database Containers is used (mode = multidb);
    Database Isolation Level is set to High (database_isolation = high);

Reproducing the Issue

Start HANA: "HDB Start" or "sapcontrol -nr -function StartSystem"
Cause

Prerequisites: You have HANA 1.0 running with MDC mode and database isolation level set to high.

The error message in the CRASH_STACK indicates that there are wrong permissions in the file /usr/sap//HDB00/exe/mdc/hdbmdcdispatcher.

You can check it by running the following command:

ls - ltrah /usr/sap//HDB00/exe/mdc/hdbmdcdispatcher

The default authorization and owner are below:

-r-sr-x--- 1 root sapsys 8.7M May 14 19:38 hdbmdcdispatcher
 


Resolution

For root cause purposes, you have to check with your OS team who/what changed the ownership and authorizations of the file.

To fix this, you need to run the following commands as root:

    "chown root:sapsys /usr/sap//HDB00/exe/mdc/hdbmdcdispatcher";
    "chmod 04550 /usr/sap//HDB00/exe/mdc/hdbmdcdispatcher";


You can now start the SAP system.





















More details 2792608