Skip to Content

AS ABAP Dev edition 7.52 SP04 error: Invalid profile parameter dbms/type

Hi,

while installing, the following error appears:

INFO 2019-10-29 03:25:34.910 (root/sapinst)
Execute step DeleteLicense of component |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|import_license_adapter|ind|ind|ind|ind|import_license|0|delete_license_abap|ind|ind|ind|ind|deleteLicenseAbap|0

ERROR 2019-10-29 03:25:35.197 (root/sapinst) id=nw.syscopy.license.delete.saplikeyFailed errno=CJS-30265
Deleting SAP license failed, see output of log file: /tmp/sapinst_instdir/NW73/SBC/STANDARD/dev_likey.

ERROR 2019-10-29 03:25:35.210 (root/sapinst) id=nw.syscopy.license.delete.failed errno=CJS-30264
Deleting SAP license failed: Deleting SAP license failed, see output of log file: /tmp/sapinst_instdir/NW73/SBC/STANDARD/dev_likey..

ERROR 2019-10-29 03:25:35.344 (root/sapinst) id=controller.stepExecuted errno=FCO-00011
The step DeleteLicense with step key |offlineadjustment_dialogs|ind|ind|ind|ind|0|0|import_license_adapter|ind|ind|ind|ind|import_license|0|delete_license_abap|ind|ind|ind|ind|deleteLicenseAbap|0|DeleteLicense was executed with status ERROR (Last error reported by the step: Deleting SAP license failed, see output of log file: /tmp/sapinst_instdir/NW73/SBC/STANDARD/dev_likey).

dev_likey content:

---------------------------------------------------
trc file: "dev_likey", trc level: 1, release: "753"
---------------------------------------------------

Tue Oct 29 03:25:35 2019
MtxInit: 0 0 0
*** ERROR => Invalid profile parameter dbms/type (or environment variable dbms_type) = <undef>, cannot load DB library
 [dbcon.c      6885]
*** ERROR => saplikey: failed to load shared library when connecting to the database. [saplikey.c   820]

Do you have any idea how to fix it?

Thanks and ciao,

Flavio

Add a comment
10|10000 characters needed characters exceeded

  • Eventually succeeding with the AS ABAP 7.52 SP04 Developer Edition install: needed to go back to openSUSE Leap 42.3, instead of installing on Leap 15.1.

    Thanks and best regards,

    Flavio

  • The environment variable depend of your Linux distribution & on your shell script.

    Could you check: echo $SHELL

    There is something really strange with your installation, maybe it is better to restart from the beggining slowly, following strictly the newbie guide

  • Hi Frederic,

    thanks for the comments;

    user is root during install, as stated in the blog

    the dbms_type variable is not set, nor echoed. However, the sapinst.txt file seems containing it:

    storageBasedCopy.dbType=syb

    and I can see it set in the big log sapinst_dev.log file :

    dbms/type = syb
    dbs/syb/schema = SAPSR3
    dbs/syb/server = vhcalnplci
    dbs/syb/dbname = NPL
    

    anyway, the same log file reports:

    TRACE      2019-10-29 03:25:34.806 (root/sapinst) (startInstallation) java.lang.String
    saplicense returned 254, output: [, *** SAPLICENSE (Release 753) ERROR ***,     
    ERROR:   Can not set DbSl trace function,     
    DETAILS: DbSlControl(DBSL_CMD_IMP_FUNS_SET) failed with return code 20,     
    RC-INFO: error loading dynamic db-library - check environment for: ,              
    dbms_type = <db-type>  (e.g. ora),              
    DIR_LIBRARY = <path to db-dll>  (e.g. /usr/sap/SID/SYS/exe/run),              
    LD_LIBRARY_PATH = <path do db and sap libs> (e.g. /oracle/SID/lib), ]<br><br>

    How could I set it?

    Thanks again and best regards,

    Flavio

Related questions

0 Answers

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.