How to Clear SCOT Error from Production Server?

1. Execute SCOT transaction

2. Go to Utilities

3. Overview of Send orders

4. Go to SOST transaction and Select all error messages. You can use Tab send status for         this and by using the respective tick marks.

5. Select Error Data and Repeat Data.

6. Go to SM37, select the respective Jobs, Copy the Jobs and Release with an authorized user or     your ID.

7. Check with SCOT transaction all error data has cleared.

Do we need to really log-out and log-in again to make authorization changes effective?

Whenever any changes were made to the user authorizations, normally it is required to log-out and log-in again to make these changes effective.

Here is an alternative:

Execute the report RSUSR405 in SE38. This would refresh all user-related buffers and changes to the authorizations are made effective immediately.

How to get List of transactions executed by a User in a specific period of time?

To get the list of transactions executed by a user in a specific period of time:

     1. Go to ST03. Select choose for analysis. Choose only one application server at a time in case       you have multiple application servers. Choose time period of your choice.

     2.  In the next screen from menu choose GO TO-->PROFILES->-USER PROFILES. Here you will get     the list on users who have worked on that application server.

      3. Double click on the required user and you will get all the transactions he/she has executed.

  4.   In case you select TOTAL in step 1 and then follow the steps 2 and 3 you will only get the list      of application server on which the user has worked and not the transaction details.

SAP idle session time out / Logging off inactive users?

To activate automatic logging off, do the following:

1. Go to Profile Maintenance by choosing Tools --> CCMS --> Configuration --> Profile        Maintenance    or the transaction RZ11.

2. Maintain the parameter rdisp/gui_auto_logout. Enter the required number of seconds of inactivity  before the user is logged off automatically.

3.To deactivate automatic logoff, delete the parameter from the profile(s) or set the value '0'.

How to export and import RFC information

This can be used to take backup of RFC destinations before systm copy and can be restored once system copy is over.

1. Login to SAP Server with sidadm user
2. create a file with rfcexp.dat with below mentioned data
export from source system
client=300
file="F:\rfcexp.ctl"
Select * from rfcattrib
Select * from rfcdes
Select * from rfcdoc
Select * from RFCSYSACL
select * RSECACHK
select * RSECACTB

3. Run command R3trans -w rfcexp.log F:\rfcexp.dat
4. Export should be over with RC=0
5. For import create file rfcimp.dat with following content

import
file="F:\rfcexp.ctl"

6. Run Command R3trans -w rfcimp.log rfcimp.dat

RFCs should be imported 

SAPPFPAR : tools to check SAP Server profile

SAP kernel has a little part called sappfpar. This little program is used to check whether your SAP profile has already well configured or not. It will suggest gave you a suggestion if there are any of your set parameter on SAP profile is not fit or not good enough.

To run this command, you need to log on as adm user.

Syntax :
adm$sappfpar check pf=/directory_where_profile_reside/profile_to_check
Here are the sample :
host:adm 6> sappfpar check pf=/sapmnt/profile/_DVEBMGS10_host
================================================================================
Checking profile: /sapmnt//profile/_DVEBMGS10_host
================================================================================
Shared memory disposition overview
===============================================================
Shared memory pools
Key: 10 Pool
Size configured.....: 188000000 ( 179.3 MB)
Size min. estimated.: 185403586 ( 176.8 MB)
Advised Size........: 188000000 ( 179.3 MB)

Key: 40 Pool for database buffers
Size configured.....: 126000000 ( 120.2 MB)
Size min. estimated.: 122104088 ( 116.4 MB)
Advised Size........: 126000000 ( 120.2 MB)

Shared memories inside of pool 10
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.
Key: 13 Size: 40500000 ( 38.6 MB) Alert Area
Key: 14 Size: 20000000 ( 19.1 MB) Presentation buffer
Key: 17 Size: 2672386 ( 2.5 MB) Roll administration
Key: 30 Size: 20480 ( 0.0 MB) Taskhandler runtime admin.
Key: 33 Size: 30720000 ( 29.3 MB) Table buffer, part.buffering
Key: 34 Size: 10240000 ( 9.8 MB) Enqueue table
Key: 51 Size: 3200000 ( 3.1 MB) Extended memory admin.
Key: 54 Size: 20488192 ( 19.5 MB) Export/Import buffer
Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist
Key: 57 Size: 1048576 ( 1.0 MB) Profilparameter in shared mem
Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset

Shared memories inside of pool 40
Key: 42 Size: 10752992 ( 10.3 MB) DB TTAB buffer
Key: 43 Size: 33414392 ( 31.9 MB) DB FTAB buffer
Key: 44 Size: 8838392 ( 8.4 MB) DB IREC buffer
Key: 45 Size: 5766392 ( 5.5 MB) DB short nametab buffer
Key: 46 Size: 20480 ( 0.0 MB) DB sync table
Key: 47 Size: 10241024 ( 9.8 MB) DB CUA buffer
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer
Key: 49 Size: 2769392 ( 2.6 MB) Spool admin (SpoolWP+DiaWP)

Shared memories outside of pools
Key: 1 Size: 2500 ( 0.0 MB) System administration
Key: 2 Size: 33600808 ( 32.0 MB) Disp. administration tables
Key: 3 Size: 114048000 ( 108.8 MB) Disp. communication areas
Key: 4 Size: 513448 ( 0.5 MB) statistic area
Key: 6 Size: 638976000 ( 609.4 MB) ABAP program buffer
Key: 7 Size: 14838 ( 0.0 MB) Update task administration
Key: 8 Size: 134217828 ( 128.0 MB) Paging buffer
Key: 9 Size: 134217828 ( 128.0 MB) Roll buffer
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring
Key: 18 Size: 917604 ( 0.9 MB) Paging adminitration
Key: 19 Size: 50000000 ( 47.7 MB) Table-buffer
Key: 31 Size: 4806000 ( 4.6 MB) Dispatcher request queue
Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 52 Size: 40000 ( 0.0 MB) Message Server buffer
Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes
Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.
Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0
Key: 58900110 Size: 4096 ( 0.0 MB) SCSA area

Nr of operating system shared memory segments: 22

Shared memory resource requirements estimated
===============================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 8

Total Nr of shared segments required.....: 30
System-imposed number of shared memories.: 1000
Shared memory segment size required min..: 638976000 ( 609.4 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)

Swap space requirements estimated
================================================
Shared memory....................: 1475.9 MB
..in pool 10 176.8 MB, 98% used
..in pool 40 116.4 MB, 96% used
..not in pool: 1174.5 MB
Processes........................: 228.8 MB
Extended Memory .................: 4092.0 MB
------------------------------------------------
Total, minimum requirement.......: 5796.7 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 7704.0 MB

Errors detected..................: 0
Warnings detected................: 0

If any errors and Warnings, it will display

Errors detected..................: 1
Warnings detected................: 1

Difference between PFILE and SPFILE? What are their advantages?

Difference between PFILE and SPFILE? What are their advantages?

 PFILE

Until Oracle 8i, we were using a text file called the PFILE (parameter file) for setting the database initialization parameters. This PFILE is read at instance startup time to get specific instance characteristics. The PFILE is text based, and can be edited in an editor like vi on UNIX or Notepad on Windows. Any changes that were made in PFILE would only take effect when the database is restarted,

Since SAP/Oracle recommends using SPFILE over PFILE, I will provide some details on SPFILE to answer your question in more detail.

SPFILE

In Oracle9i, a new feature called SPFILE (server parameter file) was introduced. SPFILE is a binary file that contains the same information as the old PFILE. SPFILE permits dynamic changes without requiring you to restart that instance.

By default, if you do not specify PFILE in your STARTUP command, Oracle will use server parameter file (SPFILE). If you choose to use the traditional text initialization parameter file (PFILE), you must specify the PFILE clause when issuing the STARTUP command.

The SPFILE is different from the PFILE in that it cannot be directly edited. This is because it has a header and footer that contain binary values. Since you cannot change a SPFILE directly, Oracle allows you to manage the SPFILE via the ALTER SYSTEM command.

When you execute the ALTER SYSTEM command, the parameter change is validated immediately, which helps avoid errors associated with entering an incorrect parameter name or an invalid value. In addition, the ALTER SYSTEM allows you to specify whether you want to update the parameter immediately, update just the SPFILE, or both. All these features help avoid human error associated with manually updating a PFILE.

The following example shows how to change the current value of SESSIONS and store the value in the SPFILE.

SQL> ALTER SYSTEM SET SESSIONS=200 SCOPE=SPFILE;

The new part in this command is the parameter SCOPE. You have the following options for this.

SCOPE = SPFILE

(For both static and dynamic parameters, changes are recorded in the spfile, and will take effect in the next restart.)

SCOPE = MEMORY

(For dynamic parameters, changes are applied in memory only. No static parameter change is allowed.)

SCOPE = BOTH

For dynamic parameters, the change is applied in both the server parameter file (SPFILE) and memory. No static parameter change is allowed.)

For dynamic parameters, we can also specify the DEFERRED keyword. When specified, the change is effective only for future sessions.

Now for the first part of your question. Since you are using Oracle 10G, you have to use the ALTER SYSTEM command to change the Oracle parameters as recommended by the SAP Early Watch Alert.