While connecting to an application server of the same database, you receive a remote logon screen to fill out. This should not occur, since you already logged on to the system.
(This occurs, for example, with Transaction SM51 or SM12)
The system determines the wrong database identifier in 3.0 in the following situations:
* you are using different network cards to access your database.
* you are using a AIX SP/2 system.
* you are using Oracle SQLNet V2.
When setting SAP profile parameters:
rfc/sysname = ... (for 3.0 and 3.1 kernel release) or
rfc/security_key = ... (for 4.0 and 4.5 kernel release) on a character string (for example rfc/security_key = ...ABCDEFGH...) on all shared application servers of the SAP system. The application server must then be restarted to activate the profile parameter changes. By doing this, all servers without a RFC logon screen can be accessed. It is important that the selected character string is a freely selected and unique character string.
The reason for the problem must be found and eliminated by the respective person responsible for the database.
The problem is corrected with Release 3.0A.
Additional key words
RFC
No comments:
Post a Comment