How to register SLES 12 using the SUSEConnect command line

How to register SLES 12 using the SUSEConnect command Line.

Environment

• SUSE Linux Enterprise Server 12
• SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)
• SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)

Solution:

SUSEConnect -r YourActivationCode  -e YourEmailAddress  --debug

To get an overview of the existing options for SUSEConnect, run "SUSEConnect --help":

SLES12:~ # SUSEConnect -help

Usage: SUSEConnect [options]

Register SUSE Linux Enterprise installations with the SUSE Customer Center.

Registration allows access to software repositories including updates,

and allows online management of subscriptions and organizations

Manage subscriptions at https://scc.suse.com

    -p, --product [PRODUCT]  Activate PRODUCT. Defaults to the base SUSE Linux

                                           Enterprise product on this system.

                                           Product identifiers can be obtained with 'zypper products'

                                           Format: //

    -r, --regcode [REGCODE]  Subscription registration code for the

                                          product to be registered.

                                          Relates that product to the specified subscription,

                                         and enables software repositories for that product

        --instance-data  [path to file]

                                          Path to the XML file holding the public key and instance data

                                          for cloud registration with SMT

    -e, --email       email address for product registration

         --url [URL]             URL of registration server (e.g. https://scc.suse.com).

                                         Implies --write-config so that subsequent invocations use the same registration server.

    -s, --status                  get current system registration status in json format

         --status-text          get current system registration status in text format

         --write-config       write options to config file at /etc/SUSEConnect

How to switch operation mode in HANA system replication environment

How to switch operation mode in HANA system replication environment

Symptom :

In HANA system replication environment, you want to switch operation mode.

Environment

SAP HANA 1.0

solution :

Change operation mode from delta_datashipping to logreplay

1. Stop secondary system.

2. Execute the following command on secondary site.

hdbnsutil -sr_register --remoteHost= --remoteInstance= --replicationMode= --operationMode=logreplay --name=SITEB

3. Start secondary system.

Change operation mode from logreplay to delta_datashipping

1. Stop secondary system.

2. Execute the following command on secondary site.

hdbnsutil -sr_register --force_full_replica --remoteHost= --remoteInstance= --replicationMode= --operationMode=delta_datashipping --name=SITEB

3. Start secondary system.

NOTE: Switching operation modes from logreplay to delta_datashipping requires a full data shipping.

More Details Refer : KBA 2500677 

SAP HANA 2.0 SP02 Features Access restrictions in Active/Active (read enabled) system setup

New feature in SAP HANA 2.0 SP 2 Replication state both side are ACTIVE and ACTIVE.

SAP HANA 2.0 SP02 Features Access restrictions in Active/Active (read enabled) system setup

Symptom:

With the SAP HANA 2.0 SPS00 release the secondary instance in an Active/Active (read enabled) system replication setup provides a read-only service. With SAP HANA 2.0 SPS00 and SAP HANA 2.0 SPS01, you will encounter "feature not supported" errors when you try to create/access the following table types on the secondary. Even if you directly connect to the secondary, these restrictions apply.

• row store
• row store tables
• row store global temporary tables
• row store no-logging tables
• column store
• column store global temporary tables
• column store no-logging tablesaa
• Since SAP HANA 2.0 SPS02 release most of these restrictions are gone. As of this version you can access all the above mentioned table type on the Active/Active (read enabled) secondary system, except:

column store no-logging tables

However, row store tables can only be accessed via direct connection to the secondary system; hint-based statement routing from the primary to access row store tables on the secondary will be possible in future releases.

Prerequisite:

Running SAP HANA 2.0 system with Active/Active (read enabled) system setup

Solution

Access to column store no-logging tables will be enabled in future SP.

More Details refer Snote:2391079

Error in SAP Instance '/' of SAP system is in an inconsistent state: the processes do not seem to have been started within the instance

Instance '/' of SAP system is in an inconsistent state: the processes do not seem to have been started in the instance

Symptom:

During the execution of Software Provisioning Manager tool (SWPM), the tool fails with the following error:

sapinst_dev.log

ERROR      (root/sapinst) [iaxxbjsmod.cpp:105] id=nw.getRunningStateInconsistent errno=CJS-30217

Instance '/' of SAP system is in an inconsistent state: the processes do not seem to have been started within the instance.

Resolution:

1. Stop the SWPM tool;

2. Stop the instance (in case it is not stopped already);

3. Make sure sapstartsrv command is not running for the instance. It can be done by running the command:

Example: 

$ ps -ef | grep sapstartsrv

sapadm   4199       1  0 Jan27 ?   00:10:11 /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D

abcadm   5375       1  0 Apr29 ?   00:08:43 /usr/sap/ABC/DVEBMGS00/exe/sapstartsrv pf=/usr/sap/SM1/SYS/profile/START_DVEBMGS00_host -D

abcadm  19285       1  0 Jun15 ?   00:01:19 /usr/sap/ABC/SCS02/exe/sapstartsrv pf=/usr/sap/SM1/SYS/profile/START_SCS02_host -D

abcadm  23002       1  0 May25 ?   00:03:53 /usr/sap/ABC/ASCS01/exe/sapstartsrv pf=/usr/sap/SM1/SYS/profile/START_ASCS01_host -D

abcadm  23005 23706 0 12:52 pts/0  00:00:00 grep sapstartsrv

The first and last lines can be ignored. The first one is the sapstartsrv for the hostctrl, which is not relevant for the issue. The last line is the output for grep command.

Then, there are 3 sapstartsrv running for each instance of the system. Manually stop the process of the instance with issues.

Check if the file /usr/sap/sapservices exists on your system, otherwise create it as described in SAP Note 823941;

Confirm if your system uses start profile or only instance profile;

If it has start profile, then make sure all sapstartsrv commands are pointing to the start profile. In addition, make sure all startup commands showed in the Cause section properly exist into start profile;

If the start profile does not exist on your SAP system, then make sure that all startup commands are properly set for instance profile.

Start the instance once again;

For a test purpose, run the command below. It must return the process below listed.

/usr/sap///exe/sapcontrol -prot NI_HTTP -nr -function GetProcessList

If the output lists the processes status (like example below), it means it has worked and now you can run SWPM tool once again to continue the process.

/usr/sap/ABC/ASCS01/exe/sapcontrol -prot NI_HTTP -nr 01 -function GetProcessList

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server, MessageServer, GREEN, Running, 2015 06 04 21:01:45, 482:39:35, 8452

enserver, EnqueueServer, GREEN, Running, 2015 06 04 21:01:46, 482:39:34, 8488

In case the issue remains and you require further assistance from BC-INS experts, provide the following information:

output of command /usr/sap///exe/sapcontrol -prot NI_HTTP -nr -function GetProcessList in a text file;

/usr/sap/sapservices file;

output of command ps -ef | grep sapstartsrv in a text file;

sapinst_dev.log;

control.xml;

summary.html;

keydb.xml

entire /usr/sap//SYS/profile directory;

entire /usr/sap///work directory

OR

Clean the shared memory in instance

Run the Command

cleanipc  remove  

XX your instance number

both DB and APP instance now you can continue the installation.

Error in SUM phase RESTART-SYSTEM-JAVAONLY

Symptom:

Software Update Manager (SUM) throws the below error in the step: RESTART-SYSTEM-JAVAONLY (Logile: \SUM\sdt\log\SUM\RESTART-SYSTEM-JAVAONLY_XX.LOG)

Apr 28, 2017, 2:40:04 AM [Error ]: Return code condition success evaluated to false for process sap control for action wait for start.

Apr 28, 2017 2:40:04 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not check status of SAP instance with number 0.

Could not check if the instance number on host is started.

Sapcontrol client could not perform action wait for started on instance

Return code condition success evaluated to false for process sap control for action wait for the start.

WaitForStarted webmethod errors out as shown below: (Logfile : SUM>\SUM\sdt\log\SUM\SAPCONTROL_WAITFORSTARTED_XX_YY.OUT

)

Resolution

To fix the issue, kindly perform the below commands:

Run netstat -n to find the free ports in the range 65000 to 10000

Set the parameter icm/admin_port to any one of the free port (e.g. 60000) in the instance profile of the affected instance.

Restart the sapstartsrv for the instance using the command: sapcontrol -nr -user -function RestartService

Repeat the phase in SUM

OR

Use Latest Version SUM tool.

More details Refer Snote: 2328080

SAP HANA STUDIO with Secure storage is locked error

Symptom:

In HANA STUDIO you see "Secure storage is locked" error in Systems tab.

In error log you can see:

Secure storage was unable to retrieve the master password. If secure

storage was created using a different Windows account, you'll have to

switch back to that account. Alternatively, you can use the password

recovery, or delete and re-create secure storage.

Solution:

There are several possibilities and you can try the following process:

Please go to HANA Studio->Windows -> Preferences -> General -> Security -> Secure Storage ->Password, then please click the recover password button and you will get the question when you created the secure storage.

If you can input correct answer then the secure storage will be unlocked.

If the fisrst step is not working please delete added sytems in your HANA studio, afterwards please 

go to HANA Studio->Windows -> Preferences -> General -> Security -> Secure Storage -> Contents tab.

Then please delete the default secure storage. and restart the HANA Studio.

If the aforementioned is not working, please delete .eclipse folder under your HANA STUDIO workspace and try again.