How to move data or log volumes and change data or log volumes path on SAP MaxDB database?

SAP MAXDB move data/log Volumes or chnage data/log volumes path.

Steps:

 1. Stop the database (DBM command db_offline). Copy the volume to the new location/drive (just copy and do not move until the database is started, so  you have a backup!)

2. Change the volume path: for Database Studio: Administration -> Data Area >>> choose volume >>> Edit: Device/File >>> OK for DBMCLI prompt: with DBM command param_put , for example, param_put DataVolumeName0001 F:\sapdb\data\DISKD0001 for

3. Database Manager: Configuration -> Volumes / >>> double-click the volume you want to move >>> set Device/Path >>> OK

4. Repeat step 3) for all affected volumes.

5. Start the database (DBM command db_online). In case the database started successfully to operational state ONLINE, you can delete the volumes from the old location.

6. If the database cannot start up, you can use DBM command param_restore (dbmcli -U c
param_restore 1) to get back the settings from before the change and start the database with the files
in the old location.

Duplicate key error in EDOPROCSPINTDET during NetWeaver upgrade

ISSUE:

While performing an upgrade using the Software Update Manager (SUM) there is an error in the phase MAIN_NEWBAS/TABIM_UPG or in MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC

The error message is with regard to duplicate key error during insert in table EDOPROCSPINTDET

In some cases, the insert fails for table EDOPROCSPINTDET~ in phase SHADOW_IMPORT_INC.
You will see the error similar to: Checks after phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC were negative!

*ERROR* : Detected the following errors:
# /usr/sap//SUM/abap/log/SAPKH61712.
: 4 ETW000 0 d / 0 i / 0 u / 3 = 100% ucf EDOPROCSPINTDET~ 
4ETW000 3 entries for EDOPROCSPINTDET~ merged (___SVNCINV 0001REQ_SENDSVN_CINV SD_INVOICE); as part of view EDOPROCSPINTDETV.
4 ETW000 client 000: 1 4 ETW000 client 001: 1
4 ETW000 client 910: 1 2EETW000 1 duplicate key error during insert into table EDOPROCSPINTDET~ occured 
4 ETW000 0 d / 0 i / 0 u / 0 = 0% ucf EDOPROCSPINTDET~
4 ETW000 0 entries for EDOPROCSPINTDET~ merged (___SVNCINV 0001SENDEDOCSVN_CINV FI_INVOICE); as part of view EDOPROCSPINTDETV.
2EETW000 1 duplicate key error during insert into table EDOPROCSPINTDET~ occured

Solution:

During upgrade:

1. Directly delete the index named EDOPROCSPINTDET~00 on the database for the shadow    table  EDOPROCSPINTDET~.
2. This issue is database engine independent.
3. Contact your database administrator for the database engine specific SQL commands. In most of the databases, the command will look like this: drop index ""."EDOPROCSPINTDET~00";.
If this syntax gives error, adapt it according to the database.
When it is possible on SAP side, you could use function module DB_DROP_INDEX in test mode for index named EDOPROCSPINTDET~001.
The major concern here is to just get rid of the index but without triggering any Dictionary activation or similar SAP-side activity - thus intending to limit interference with upgrade processing.
4. Repeat the phase in SUM.

Post-upgrade:

Check the indexes for the table EDOPROCSPINTDET in SE11.

If the index 001 is existing there, delete the index.

Save the table and activate.

SAP HANA Database Installation failed

SAP HANA DATABASE INSTALLATION FAILED POSSIBLE ERRORS.

Installation of SAP HANA Database failed
Installation failed
error installing
Cannot create Instance
Cannot create instance
Cannot create SecureStore
Getting global.ini
Reading global.ini
Layer 'Default' found
Layer 'System' found
Layer 'Host' not found
Found value 'cryptography/ssfs_key_file_path' = '$(DIR_GLOBAL)/hdb/security/ssfs' in layer 'Default'
Starting external program /usr/sap/XXX/HDB00/exe/hdbnsutil
Command line is: /usr/sap/XXX/HDB00/exe/hdbnsutil -createSecureStore
Output line 1: It is prohibited to execute hdbnsutil as root user
Program terminated with exit code 1
/usr/sap/XXX/HDB00/exe/hdbnsutil call failed

Error Log in the hdbinst.log file :

05:11:19.405 - INFO: -------------------------------------------------------
05:11:19.405 - INFO: Configuring user home ''
05:11:19.405 - INFO: END: Configure Home Dir (start: 05:11:19.405 duration: 00:00:00)
05:11:19.405 - INFO: -------------------------------------------------------
05:11:19.405 - ERR : Cannot create home directory

The sidadm user home dir was not configured.


Solution:

Uninstall the system and install a new one.
Following command uninstall the XXX system via resident hdblcm:

/hana/shared/XXX/hdblcm/hdblcm --uninstall
After the uninstallation, please make sure that:
1. user "xxxadm" does not exist
2. user home directory "/usr/sap/XXX/home" does not exis
3. Then, you can start a new HANA installation.

SOLMAN_SETUP - Web Page Service cannot be reached - 403 Forbidden

Issue
After the update of SAP Solution Manager System to SAP Solution Manager 7.2 SP 08 solman_setup Tcode Webpage showing "Service cannot be reached" "403 - Forbidden" errors.


Solution

Activate some SICF Services are not activated


    call SICF
    navigate to /default_host/sap/bc/ui5_ui5/sap/
    check and activte service bsp_sise_rm_ui5 for Roadmap
    check and activte service bsp_ags_ui5_doc for Help Text

SAP HANA Setting the 'license_usage' parameter.

SAP HANA settings for " License_usage" Parameter.

SAP HANA 2.0 SPS04 a new parameter 'license_usage' in section 'system_information' was introduced in the global.ini configuration file. This note describes the purpose and usage of this parameter.

Solution

The parameter 'license_usage' needs to be set in accordance with the licensing terms of your SAP HANA purchase.

The parameter needs to be set in the system database and every tenant in production systems.   It only needs to be set in installations used for production systems, i.e. whenever the parameter 'usage' in section 'system_information' in global.ini is set to the value 'production'.

In a production system, please set the parameter to one of the following values:

    'full' if you have purchased a SAP HANA full use license for your SAP HANA tenant.
    'runtime' if you have purchased a SAP HANA runtime license for your SAP HANA tenant.
    'administration'  for the system database or if the tenant is exclusively used to run an installation of SAP HANA Cockpit.
    'nonproduction' for tenants that are not used for production but are part of a SAP HANA instance in which other tenants are used for production.