R3trans finished (0012)

[former_member182034]

Dear All,

I am getting below issue when I try to run ./startsap -t all.

2EETW169 no connect possible: "DBMS = SYBASE --- ".R3trans finished (0012)

database is running fine while I searched about this issue and applied the solutions(scn reply and SAP notes) but still facing this issue.

please tell me which Information, you have required to resolve this issue?

Regards,

[former_member182657]

Hi,

What about with telnet <server name> 4901 .Please share the results .

Regards,

[former_member182034]

hi Gaurav,

the new output of startsap is

XYZadm> startsap
Checking XYZ database
Database is not available via R3trans
---------------------------------------------------------
Trying to start XYZ database ...
Log file: /home/XYZ/startdb.log
XYZ database started
Starting Startup Agent sapstartsrv
FAIL: Timeout
Startup of Instance Service failed
See /home/xyz/startsap_DVEBMGS04.log for details.

4901 port is configured and working find.

hi Ganesh,

all parameters are configured correctly.

Regards,

[former_member182657]

Hi Abdul,

Could you re-share trans.log , startdb.log & startsap_DVEBMGS04.log files.

Thanks,

[former_member182034]

hi,

right now i m seeing these notes.

1762827 - "Startup of Instance Service failed" in UNIX or Linux environment

2043875 - Error:" Starting Startup Agent sapstartsrv failed" after upgrading to EHP 7

Regards,

[former_member182034]

Dear,

i have applied above notes butfacing below issue.

Unable to open trace file sapstartsrv.log. (Error 11 Resource temporarily unavailable

(this issue is mentioned 1762827)

FYI... i have changed the kernel mode from thread to process... (is it relate to this issue or not)

Regards,

[Sriram2009]

Hi Abdul

Before executing the command check the Sybase DB status?

BR

SS

[former_member182034]

Dear All,

For SCN users,

I was checking some logs were not being updated...one more task which i did and that was,,

Live IP ws assigned to eth0 and local ws assigned to eth1. today we hv assigned local to oth0 and checked the logs which were updated and i found issue which relates to log file

really first i checked the trans.log and there were not showing this error.so, today i increase the size of log file and issue resolved.

As per Gaurav's reply

Are you able to resolve host name of system by ping from the network ?

that time, ping was working fine but your reply relates to this solution.