INSTANCE MANAGEMENT:
Instance is managed by using profiles. Profiles will resides in (usr/sap/<SID>/sys/profiles)
There are three types of Profiles
1. Default
2. Startup
3. Instance Profile
As part of post installation we import the profiles of Active servers from RZ10.
The profiles reside at OS level in the directory (usr\sap\<SID>\sys\profile). They can be managed/ edited using a notepad. But the consistency is not checked (say for eg. if we modify the instance profile WP DIA=2000 and there is no error message and versions are not maintained under OS level)
DEV_DVEBMGS00_lolladel.
So these profiles are imported into database management for consistency check and version management.
Startup Profile:
Startup profile consists of startup parameters like
Starting Database
Starting Message Server
Dispatcher + Work.
Do not modify these parameter under any circumstances on OS level.
Default Profile:
It is used to provide global parameters for all the instances, buffer parameters, security parameters (Password, User restrictions), Message server host, enqueue host)
Instance Profile:
This is specific to instance configuration such as work process, timeout parameters etc.
Starting Sequence
1. Startup profile is read by the system to start the engine by starting database, message server and dispatcher in Central Instance.
2. Startup profile is read by the system to start the engine by starting (DISP+WORK) on dialogue instance.
3. There will be only one default profile in the entire system which provides global values.
4. Instance specific profile - This is used to set the instance specific parameters.
Eg. How many profiles are available on a system with 10 Dialogue instances.
Total = 11 (including Central Instance)
11 X 2 per instance (Start + Instance)
22
22 + 1 (Default Instance) = 23
PROFILE MANAGEMENT:
Documentation for profiles are available in RZ10
Profiles resides in the table - TPFYPROPTY
RZ11 is also used to change some parameters dynamically without restarting the system but they will be reset once the system is restarted.
RZ10 changes are permanent
The field type 'T' Specifies the dynamic parameters.
RZ10
There are three types of Administration.
1. Administration data
No need to maintain using this option. It only specifies the path of the parameters.
2. Basic Maintenance:
It is used to maintain the profile parameters without any technical names. GUI based using mouse
3. Extended Maintenance
Used by administrator using parameter names
Specify the input by including new parameters or modify the existing one.
Copy > Save and Activate the profile.
The profile changes are updated at OS level and the existing profile is marked as .BAK and a new profile is created in the profile directory. It will effect only after restarting the Server.
Profiles are changed on SAP recommendation or based on experience. Do not change any of the profiles on trail and error method. System will hang and may not restart.
Instance is managed by using profiles. Profiles will resides in (usr/sap/<SID>/sys/profiles)
There are three types of Profiles
1. Default
2. Startup
3. Instance Profile
As part of post installation we import the profiles of Active servers from RZ10.
The profiles reside at OS level in the directory (usr\sap\<SID>\sys\profile). They can be managed/ edited using a notepad. But the consistency is not checked (say for eg. if we modify the instance profile WP DIA=2000 and there is no error message and versions are not maintained under OS level)
DEV_DVEBMGS00_lolladel.
So these profiles are imported into database management for consistency check and version management.
Startup Profile:
Startup profile consists of startup parameters like
Starting Database
Starting Message Server
Dispatcher + Work.
Do not modify these parameter under any circumstances on OS level.
Default Profile:
It is used to provide global parameters for all the instances, buffer parameters, security parameters (Password, User restrictions), Message server host, enqueue host)
Instance Profile:
This is specific to instance configuration such as work process, timeout parameters etc.
Starting Sequence
1. Startup profile is read by the system to start the engine by starting database, message server and dispatcher in Central Instance.
2. Startup profile is read by the system to start the engine by starting (DISP+WORK) on dialogue instance.
3. There will be only one default profile in the entire system which provides global values.
4. Instance specific profile - This is used to set the instance specific parameters.
Eg. How many profiles are available on a system with 10 Dialogue instances.
Total = 11 (including Central Instance)
11 X 2 per instance (Start + Instance)
22
22 + 1 (Default Instance) = 23
PROFILE MANAGEMENT:
Documentation for profiles are available in RZ10
Profiles resides in the table - TPFYPROPTY
RZ11 is also used to change some parameters dynamically without restarting the system but they will be reset once the system is restarted.
RZ10 changes are permanent
The field type 'T' Specifies the dynamic parameters.
RZ10
There are three types of Administration.
1. Administration data
No need to maintain using this option. It only specifies the path of the parameters.
2. Basic Maintenance:
It is used to maintain the profile parameters without any technical names. GUI based using mouse
3. Extended Maintenance
Used by administrator using parameter names
Specify the input by including new parameters or modify the existing one.
Copy > Save and Activate the profile.
The profile changes are updated at OS level and the existing profile is marked as .BAK and a new profile is created in the profile directory. It will effect only after restarting the Server.
Profiles are changed on SAP recommendation or based on experience. Do not change any of the profiles on trail and error method. System will hang and may not restart.
No comments:
Post a Comment