Skip to Content

licence key deletion error while installing sap net weaver 7.5 sp02

I am getting following exception while installing sap nw 7.5 on Ubuntu guest OS on virtual box with host as mac.

<code>ERROR 2018-10-23 15:26:42.943 (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 2018-10-23 15:26:43.042 (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.).

Any idea on what could be the cause for this? Also, this occurs after around 30-35 minutes of starting the installation.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Oct 25, 2018 at 04:31 AM

    Hi

    Could you attach the log file /tmp/sapinst_instdir/NW73/SBC/STANDARD/dev_likey

    Regards

    SS

    Add a comment
    10|10000 characters needed characters exceeded

    • MtxInit: 0 0 0 Loading DB library '/usr/sap/NPL/SYS/exe/run/dbsybslib.so' ... Library '/usr/sap/NPL/SYS/exe/run/dbsybslib.so' loaded Version of '/usr/sap/NPL/SYS/exe/run/dbsybslib.so' is "749.05", patchlevel (0.200) read_con_info_ssfs(): DBSL supports extended connect protocol ==> connect info for default DB will be read from ssfs load of SQLLEN8 SYB library libsybdrvodb8.so successful. database is local: connect_timeout: 3 lib_dbsl 749 12/01/2016 15:41:00 dbsybslib.dll patch info SAP patchlevel 0 SAP patchno 200 Last SYBASE DBSL patchlevel 0 Last SYBASE DBSL patchno 200 Last SYBASE DBSL patchcomment SAP Support Package Stack Kernel 7.49 Patch Level 200 (2435328) spid 71 comm rd ODBC spid 72 unc rd ODBC Driver: Adaptive Server Enterprise (ANSI) Driver release: 16.0.02.05 Driver full version: SAP ASE ODBC Driver/16.0.02.05/16.0 SP02 PL05/P/x86_64/Linux/drv16/Build 1/64-bit/Normal/Sun Nov 13 UTC 14:15:31 2016/SQLLEN8 dbs/syb/cache_size: 200 GetServerInfo version: Adaptive Server Enterprise/16.0 SP02 PL05 HF1/EBF 26759 SMP/P/x86_64/Enterprise Linux/ase160sp02pl05x/2736/64-bit/FBO/Mon Jan 16 23:55:31 2017 INFO: only appcontext supported for session variables for Sybase ASE release 16.0.02.05. GetServerInfo release: 16.0.02.05 GetServerInfo architecture: x86_64 GetServerInfo edition: P GetServerInfo byte width: 64 bit ERROR: -1 in function CheckCodepageType (SQLExecDirect failed) [line 36961] (21) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]WARNING - Fatal Error 823 occu rred at Oct 25 2018 12:21PM. Please note the error and time, and contact a user with System Administrator (SA) authorization. ERROR: -1 in function CheckCodepageType (SQLExecDirect failed) [line 36961] (21) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]WARNING - Fatal Error 823 occu rred at Oct 25 2018 12:21PM. Please note the error and time, and contact a user with System Administrator (SA) authorization. ERROR: -1 in function CheckCodepageType (SQLExecDirect failed) [line 36961] (15601) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]Failed to cache systabstats co ntents for database 'NPL' (5), object 'DBPROPERTIES' (580571217). ERROR: -1 in function CheckCodepageType (SQLExecDirect failed) [line 36961] (15601) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]Failed to cache systabstats co ntents for database 'NPL' (5), object 'DBPROPERTIES' (580571217). ERROR: -1 in function CheckCodepageType (SQLExecDirect failed) [line 36961] Thu Oct 25 12:21:43 2018 (208) [42000] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]DBPROPERTIES not found. Specif y owner.objectname or use sp_help to check whether the object exists (sp_help ma y produce lots of output). DbSlConnect hdl: 0 trace file set Connection 0 opened (DBSL handle 0) ERROR: -1 in function StartSelect (execute) [line 25488] (21) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]WARNING - Fatal Error 823 occu rred at Oct 25 2018 12:21PM. Please note the error and time, and contact a user with System Administrator (SA) authorization. ERROR: -1 in function StartSelect (execute) [line 25488] (21) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]WARNING - Fatal Error 823 occu rred at Oct 25 2018 12:21PM. Please note the error and time, and contact a user with System Administrator (SA) authorization. ERROR: -1 in function StartSelect (execute) [line 25488] (208) [42000] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]SVERS not found. Specify owner .objectname or use sp_help to check whether the object exists (sp_help may produ ce lots of output). sql statement is ==> SELECT VERSION FROM SVERS /* R3::0 T:SVERS */ ***LOG BZA=> table SVERS does not exist on database [dblink 1438] *** ERROR => saplikey: failed to read table SVERS after connecting to the database. [saplikey.c 834] ~

  • Posted on Oct 25, 2018 at 07:31 AM

    Hi

    From the log file SWPM unable to read the table SVERS.

    1. Could you check the DB disk space and also check the DB instance active? is it possible do the full system restart and then retry the same phase.

    2. Is this OS / DB Supported NW 7.5? have you check the same in SAP PAM.

    3. Table SVERS exist in the DB or not? (SVERS not found. Specify owner .objectname or use sp_help to check whether the object exists)

    Regards

    Sriram

    Add a comment
    10|10000 characters needed characters exceeded

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.