SAP Basis Tech Supports

Symptom

GUIDs or TIDs are assigned twice. Depending on how they are used, this may
have various consequences.
Duplicate primary keys in tablesProblem when using GUIDs for identification
Other terms

GUID, TID, PID, SAPSQL_ARRAY_INSERT_DUPREC
Reason and Prerequisites

Your operating system is AIX 4.3 or higher.
Solution

—GUID—
The GUID algorithm has been modified in such a way that the probability
of generating duplicate GUIDs in the R/3 system was reduced.
>=640 kernel patch level 0
620 kernel patch level 1003
46D kernel patch level 1684
45B kernel patch level 933
40B kernel patch level 1022
—TID—
You can switch to using a new TID algorithm by using the profile parameter rfc/use_wp_instead_of_pid. The new algorithm uses the work process number that is unique in an application server instance, instead of using the two lowest value bytes of the process ID (PID). To enable more than one application server instances on a physical server, the parameter value is added to the work process number so that each instance has its own number area.
In this case, note the following:

a) If only one instance is running on a physical server in the system concerned, it is sufficient to set the profile parameter rfc/use_wp_instead_of_pid to 1 in the profile file of the instance on this server.
b) However, if several instances are running simultaneously on one physical server (the instances may also belong to several different SAP systems), the parameter rfc/use_wp_instead_of_pid is added as an offset to the current work process number during the TID calculation.
Proceed as follows:
- Create a list containing all instances of the server.
- Determine how many work processes (=maxWP) are used on the instance
with the most work processes.
- In the profile files, set the parameters rfc/use_wp_instead_of_pid on the individual instances so that they always have a difference larger than maxWP and begin with 1.

For example: In your system landscape,
CRM is the largest instance with 100 work processes, therefore: maxWP = 100. As pitch, you choose 300, for example. The entries in the different profile files would be similar to the following:
HOST: server123
Instance Work processes rfc/use_wp_instead_of_pid
CRM 100 1
SCC 50 300
ABC 75 600
XYZ 10 900
FEW 30 1200
HOST: server456
Instance Work processes rfc/use_wp_instead_of_pid
CRM 100 (2 * aW = 200) 1
SCC 50 300
ABC 75 600
Choose the difference so that the requirements mentioned above
are met, even if an instance receives further
work processes or, if necessary, make sure that the parameter rfc/use_wp_instead_of_pid is also adjusted when you configure the new work processes.
The upper limit for the parameter rfc/use_wp_instead_of_pid is 60000.

The profile parameter rfc/use_wp_instead_of_pid is available as of the
following kernel patch levels:
640 kernel patch level 22
620 kernel patch level 1255
46D kernel patch level 1768
45B kernel patch level 933
40B kernel patch level 1022

Several instances are supported on a physical server as
of the following kernel patch levels:
640 kernel patch level 22
620 kernel patch level 1497
46D kernel patch level 1871
45B kernel patch level 933
40B kernel patch level 1022