Saturday, January 27, 2018

Tidying up the SAP NetWeaver Developer Edition Profiles on Version 751

Tidying up the SAP NetWeaver Developer Edition Profiles on Version 751


Background

After I successfully followed the SAP blog to install my ABAP trial NetWeaver 751 edition on Virtualbox, I noticed the SAP profiles were in an inconsistent state. In that the database profile versions were different to the active profiles.
SAP SCN blog covering installing the ABAP 751 dev edition instance


The actions I took to resolve the profile issue, was as follows.

The Actual Issue


In transaction RZ10 there is an option to run a comparison of profiles in the database against the active running profiles (the active profile is read from the filesystem profile file when the ABAP server starts).



The following differences were noted for the instance profile


       
The two main differences I was interested in for the profiles were the following
Parameter SAPFQDN is missing in file             
 /usr/sap/NPL/SYS/profile/NPL_D00_vhcalnplci    
Parameter SAPLOCALHOSTFULL is missing in file    
 /usr/sap/NPL/SYS/profile/NPL_D00_vhcalnplci    

Also a "rogue" unidentified profile in the database called NPL_ASCS01_VHCALNPLCS


I decided to refresh the database and the way to do that in RZ10 is to import the profiles of active servers.





However this failed with the following error on importing the DEFAULT profile 


So I decided to DELETE the database ONLY version.

I would recommend before changing/deleting profiles to take a backup at the operating system level of the file involved. So for the DEFAULT profile I did this following Linux commands

vhcalnplci:npladm 46> cd /sapmnt/NPL/profile
vhcalnplci:npladm 48> cp DEFAULT.PFL DEFAULT.BACKUP.PFL
vhcalnplci:npladm 50> ls -l
total 24
-rw-r--r-- 1 npladm sapsys 2251 Jan 27 22:05 DEFAULT.BACKUP.PFL
-rw-r--r-- 1 npladm sapsys 2251 Nov 18 12:47 DEFAULT.PFL
-rw-r--r-- 1 npladm sapsys 3847 Nov 18 12:59 dev_dpmon
-rw-r--r-- 1 npladm sapsys 3465 Nov 18 12:47 NPL_ASCS01_vhcalnplci
-rw-rw---- 1 npladm sapsys 6685 Jan 27 22:03 NPL_D00_vhcalnplci

Now I had my backup file I decided to delete the DATABASE version of the DEFAULT profile.

Checking the DEFAULT profile it had been set as an "instance" profile type - so I deleted all versions of this DEFAULT profile in the database.




*The "profile type" in the screenshot has the default profile set as an instance profile.
On the RZ10 main screen, I selected the DEFAULT profile and menu option to delete all.




ANSWER YES to the following

ANSWER NO to the following



I didn't want to delete the file at the operating system level as this was fine. The only problem was the version stored in the database.

Now I corrected the DEFAULT profile in the database by running the import options again.


The DEFAULT profile imported successfully this time.


The red "errors" are for the previous successfully imported profiles and the red messages can be treated as information as the profiles have not changed.

One final thing I did with the profiles was to delete all versions of the profile NPL_ASCS01_VHCALNPLCS


So I was left with just three profiles 


So I then restarted the SAP system

Logged onto npladm and checked the status of the system with the following command

vhcalnplci:npladm 53> sapcontrol -nr 00 -function GetSystemInstanceList

27.01.2018 22:36:00
GetSystemInstanceList
OK
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
vhcalnplci, 0, 50013, 50014, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN
vhcalnplci, 1, 50113, 50114, 1, MESSAGESERVER|ENQUE, GREEN

System was in a running state, indicated by the GREEN status (has we have just changed the profiles ;))


Then Stopped the system with the following command

vhcalnplci:npladm 54> sapcontrol -nr 00 -function StopSystem

27.01.2018 22:36:08
StopSystem
OK

Running the status command a few times until both instances go GRAY (stopped)

vhcalnplci:npladm 55> sapcontrol -nr 00 -function GetSystemInstanceList

27.01.2018 22:38:31
GetSystemInstanceList
OK
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
vhcalnplci, 0, 50013, 50014, 3, ABAP|GATEWAY|ICMAN|IGS, GRAY
vhcalnplci, 1, 50113, 50114, 1, MESSAGESERVER|ENQUE, GRAY

Start the system with the following commands

vhcalnplci:npladm 56> sapcontrol -nr 00 -function StartSystem

27.01.2018 22:39:38
StartSystem
OK


Checking the system status again until the SAP system had started (GREEN status)

vhcalnplci:npladm 60> sapcontrol -nr 00 -function GetSystemInstanceList

27.01.2018 22:42:45
GetSystemInstanceList
OK
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
vhcalnplci, 1, 50113, 50114, 1, MESSAGESERVER|ENQUE, GREEN
vhcalnplci, 0, 50013, 50014, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN


 OR you could use the startsap and stopsap scripts as they are still around (but depreciated).


You may (or may not recall) I mentioned two profile parameters previously, and as a reminder.

Parameter SAPFQDN is missing in file             
 /usr/sap/NPL/SYS/profile/NPL_D00_vhcalnplci    
Parameter SAPLOCALHOSTFULL is missing in file    
 /usr/sap/NPL/SYS/profile/NPL_D00_vhcalnplci  


These are useful for what I wanted to do next with my developer edition ABAP system and will be the subject of another blog...... stay tuned.  ;)










No comments:

Post a Comment

Google +