Problems to connect to SAP since heterogeneous copy

[Former Member]

Hello,

Tonight we made an heterogeneous copy from production environment to development environment and since this copy we can't login on development environment.

Here you're error:

<b>Error in logon balancing routine (rc=82, err=7);

Logon group 'XXXXXX' not found - check spelling and case sensitivity</b>

Note that this is the only host, so balancing is not needed, and SAPLogon configuration hasn't been changed, so it worked before copy.

Is there any logfile where I can check why SAPLogon doesn't work?

Could it be some files or permissions are missed in host system?

Thanks in advance for your help.

Regards,

Carles

[Former Member · Accepted solution]

Hi Carles,

if you don't need logon groups on dev. system, just create a new entry in saplogon, enter the server, SID and system number and it should work.

Regards,

Pascal

[Former Member · Accepted solution]

Hi Pascal,

Thanks dor your post.

I already tried it, but it failed too.

Now I think I've found issue but I don't really know how to fix it. I execute top command on my development system and there isn't any dw.sapSID_DVEBMGS00 process running.

I executed startsap_system2_00 and seems to finish fine, but there weren't any SAP process running.

Any idea?

Thanks in advance for your help.

Regards,

Carles

[Former Member · Accepted solution]

HI Carles,

yes, that explains why you can't connect. Check the startsap log files in the <sid>adm directory and also check the logfiles in the /usr/sap/<SID>/D.../work directory.

Also check if the database is running with "R3trans -x" with the <sid>adm user. This will write a trans.log file in the directory where you executed it. It could be that the copied system has not the same passwords for the connect user.

Regards,

Pascal

[Former Member · Accepted solution]

Here you're log messages:

<i>Trace of system startup/check of R/3 System SPD on Fri Jul 14 09:45:52 METDST 2006

Called command: /home/spdadm/startsap_silvia_00

Starting SAP-Collector Daemon

-

---

saposcol already running

Checking SAP R/3 SPD Database

-

---

Database is not available via /usr/sap/SPD/SYS/exe/run/R3trans -d -w

Starting SAP R/3 SPD Database

-

---

Startup-Log is written to /home/spdadm/startdb.log

Database started

Checking SAP R/3 SPD Database

-

---

Database is running

Starting SAP R/3 Instance

-

---

SAP-R/3-Startup Program V1.7 (92/10/21)

-

---

Starting at 2006/07/14 09:46:05

Startup Profile: "/usr/sap/SPD/SYS/profile/START_DVEBMGS00_silvia"

Execute Pre-Startup Commands

-

---

(125) Local: /usr/sap/SPD/SYS/exe/run/sapmscsa -n pf=/usr/sap/SPD/SYS/profile/SPD_DVEBMGS00_silvia

/usr/sap/SPD/SYS/exe/run/sapmscsa: SCSA is attached and useable.

/usr/sap/SPD/SYS/exe/run/sapmscsa: finished.

(125) Local: rm -f ms.sapSPD_DVEBMGS00

(125) Local: ln -s -f /usr/sap/SPD/SYS/exe/run/msg_server ms.sapSPD_DVEBMGS00

(125) Local: rm -f dw.sapSPD_DVEBMGS00

(125) Local: ln -s -f /usr/sap/SPD/SYS/exe/run/disp+work dw.sapSPD_DVEBMGS00

(125) Local: rm -f co.sapSPD_DVEBMGS00

(125) Local: ln -s -f /usr/sap/SPD/SYS/exe/run/rslgcoll co.sapSPD_DVEBMGS00

(125) Local: rm -f se.sapSPD_DVEBMGS00

(125) Local: ln -s -f /usr/sap/SPD/SYS/exe/run/rslgsend se.sapSPD_DVEBMGS00

Starting Programs

-

---

(153) Starting: local ms.sapSPD_DVEBMGS00 pf=/usr/sap/SPD/SYS/profile/SPD_DVEBMGS00_silvia

(154) Starting: local dw.sapSPD_DVEBMGS00 pf=/usr/sap/SPD/SYS/profile/SPD_DVEBMGS00_silvia

(155) Starting: local co.sapSPD_DVEBMGS00 -F pf=/usr/sap/SPD/SYS/profile/SPD_DVEBMGS00_silvia

(156) Starting: local se.sapSPD_DVEBMGS00 -F pf=/usr/sap/SPD/SYS/profile/SPD_DVEBMGS00_silvia

(125) Waiting for Child Processes to terminate.

(125) **** 2006/07/14 09:46:22 Child 154 terminated with Status 0 . ****

Instance on host silvia started

(125) **** 2006/07/14 09:57:10 Caught Signal to Stop all Programs. ****

(125) Parent Shutdown at 2006/07/14 09:57:12

(125) Stop Child Process: 156

(125) Wait 300 sec for Process 156 terminating...

(125) Stop Child Process: 155

(125) Wait 300 sec for Process 155 terminating...

(125) Stop Child Process: 153

(125) Wait 300 sec for Process 153 terminating...

Execute Post-Shutdown Commands

-

---

(125) Exiting with Return-Code 0. (Ok)</i>

Look at the end of log file: it seems sap processes are killed(!)

Any ide why system do this?

Thanks again for your posts!

Regards,

Carles

[Former Member · Accepted solution]

Hello again,

I did a mistake in my last post: Shutdown was done manually by my colleague, so ignore last message from log file as they're normal.

Thanks in advance for your help.

Regards,

Carles

[Former Member · Accepted solution]

Hi Carles,

ok, Database connect seems good. You still don't see work processes? If not, check the mentioned work directory logs.

Regards,

Pascal

[Former Member · Accepted solution]

in the past i had a similar problem ... my system is on unix ..

we stop sap and then we reviewed the ipcs ... we saw that they were in the queue so we killed the semaphores, that the user of the system had there hung.

after that we start sap and run.