R3trans -X can't connect to ASE server

Symptom

• Execute R3trans -X from a Java stack system return following output:

  This is R3trans version x.xx (release xxx - xx.xx.xx - xx:xx:xx ).
  unicode enabled version 2EETW169 no connect possible:
 "DBMS = SYBASE --- " R3trans finished (0012).

• Trans.log shows "uid=SAPSR3":

     ...

4 ETW000 [ dev trc,00000] Connection 0 failed using DRIVER={Adaptive Server Enterprise};server=;port=4901;uid=SAPSR3;db=;pwd=xxxxxxxx;TextSize=2147483647;CRC=0;FetchArraySize=1000;ReleaseLocksOnCursorClose=1;DynamicPrepare=1;QuotedIdentifier=00 comm rd ODBC;logintimeout=3;ProtocolCapture=cap_p4397_comm_rd;supresstdscontroltokens=1;SuppressRowFormat=

   ...

Environment

•  SAP Adaptive Server Enterprise (SAP ASE) 15.7 and 16.0 for Business Suite
•  SAP NetWeaver (NW) - All versions
•  SAP Business Warehouse (BW) - All versions

Cause

The values of "DB_CONNECT/DEFAULT_DB_USER" in Secure Storage is "SAPSR3" instead of "SAPSR3DB". 

The values of "DB_CONNECT/DEFAULT_DB_PASSWORD" in Secure Storage is SAPSR3's password instead of SAPSR3DB's password. 

Resolution 

 Connect to the host machine with adm login account and then use rsecssfx utility.
Check if current "DB_CONNECT/DEFAULT_DB_USER" is "SAPSR3DB" or not using:


rsecssfx get DB_CONNECT/DEFAULT_DB_USER 

If the value of "DB_CONNECT/DEFAULT_DB_USER" is not "SAPSR3DB", then
 change it to "SAPSR3DB" using:

 rsecssfx put DB_CONNECT/DEFAULT_DB_USER SAPSR3DB -plain

 change "DB_CONNECT/DEFAULT_DB_PASSWORD" to SAPSR3DB's password using:

 rsecssfx put DB_CONNECT/DEFAULT_DB_PASSWORD





More details refer Snote : 2584472

SAP Standard Filesystem Hierarchy.

SAP Standard Filesystem Hierarchy

usr/sap 
/usr/sap/ccms
/usr/sap/SID
/usr/sap/SID/DVEBMGSnn                contain SAP instance specific directories data, log, and work..
/usr/sap/SID/DVEBMGSnn/work
/usr/sap/SID/SYS                               contain profile, global, and exe directory.
/usr/sap/SID/SYS/exe
/usr/sap/SID/SYS/global    -->       /sapmnt/SID/global.
/usr/sap/SID/SYS/profile    -->      /sapmnt/SID/profile.
/usr/sap/trans                                  Transport directory.
/usr/sap/trans/bin                            TPPARAM file (global transport parameter).
/usr/sap/trans/buffer                        Special buffer with the SID of every system in the transport.
 
group (including control information)
/usr/sap/trans/cofiles                        Transport request control file.
/usr/sap/trans/data                            Transport request data file.
/usr/sap/trans/EPS
/usr/sap/trans/EPS/in
/usr/sap/trans/log                              Transport logs, trace and statistic file.
/usr/sap/trans/tmp                             Temporary directory.

                                                 //sapmnt
                                                       |
                                                    SID
                                                       |
                                           +-------+-------+
                                                     | | |
                                             exe global profile
/sapmnt       directory structure for sharing common files to all system belonging into the same group.
/sapmnt/SID              shared directory or link to directory /usr/sap/SID/SYS
/sapmnt/SID/exe        SAP executable application directory.
/sapmnt/SID/global    SAP central system log.
/sapmnt/SID/profile    SAP instance profile.



 

Standard Users in SAP.

Users

SAP*

SAP* is the super user of SAP system and used for doing client copy. SAP* is the only user in the SAP System that does not require a user master record, but that is instead defined in the system code itself. SAP* has by default the password 'pass', as well as unlimited system access authorizations. When you install your SAP System, a user master record is defined for SAP* with the initial password as the master password (set during installation) in clients 000 and 001. The presence of a SAP* user master record deactivates the special properties of SAP* and standard password 'pass'. It has only the password and the authorizations that are specified for it in the user master record.
When temporary license expires only SAP* user is allowed to login to client 000 to install permanent
license.

DDIC
 
It is the maintenance user for ABAP Dictionary and software logistics. It is used for any upgrade or installation type of work like,
1. TMS Configuration,
2. Applying Support Packages,
3. Applying Add-ons,
4. Implementing SAP Notes etc.

• Best practice is not to use DDIC user but create a new user by copying from DDIC.
• DDIC is the only user that is allowed to log on to the SAP System during an upgrade.
• DDIC is hard coded to do some things other IDs cannot and restricted from doing some things that other IDs can.

EARLYWATCH
 
The SAP EarlyWatch service uses this user. This user should only be used for EarlyWatch functions like monitoring and performance analysis.
Default users in each clients,

Client 000
Username: SAP* --> short for SAP Star
Password:
Username: DDIC --> copy of SAP*, short for Data Dictionary
Password:

Client 001
Since Client 001 is a copy of Client 000, it has the same users and passwords as in Client 000.

Client 066
Username: EARLYWATCH
Password: support

New Client
Username: SAP*
Password: pass


 

What is Logical System in SAP?

Logical System

When data is distributed between different systems, each system within a network has to be clearly identifiable. The "logical system" deals with this issue.

A logical system is an application system in which the applications work together on a common database. In SAP terms, the logical system is a client.

Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way. 

The logical system’s naming convention is CLNT such as SDKCLNT100