Unable to start sap from MMC...dispatcher dies always

[Former Member]

Hi,

We are in the process of upgrading our solution manager 3.2 to 7...in

that process, we are simulating the upgrade scenario in our

sandbox ...we have installed a new solution manager 3.2 with the same

kernel and patches as that of the running production solman 3.2 ..

both are using windows 2003 + oracle 9.2.0.6

Everything was fine. then, we copied all the database files from

production to sandbox. both are using the same sid (PSM). only thing is

that, the hostnames are different.

After restoring the db on sandbox system, we are able to start the

database. But while starting the sap though sap management console, it

always fails with starting dispatcher.

Here is the logfile entry.

*****************8

C Attaching to DB Server PSM (con_hdl=0,svchp=0968E214,svrhp=0589A9B4)

C Starting user session

(con_hdl=0,svchp=0968E214,srvhp=0589A9B4,usrhp=09693D28)

C Now '/@PSM' is connected (con_hdl 0, nls_hdl 0).

C Got SAPPSM's password from OPS$-user

C Disconnecting from connection 0 ...

C Closing user session (con_hdl=0,svchp=0968E214,usrhp=09693D28)

C Now I'm disconnected from ORACLE

C Connecting as SAPPSM/<pwd>@PSM on connection 0 (nls_hdl 0) ... (dbsl

640 081205)

C Nls CharacterSet NationalCharSet C

EnvHp ErrHp ErrHpBatch

C 0 UTF8 1

09689798 0968E858 0968E2C0

C Starting user session

(con_hdl=0,svchp=0968E214,srvhp=0589A9B4,usrhp=09693D28)

C *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017

[dboci.c 4388]

C *** ERROR => CONNECT failed with sql error '1017'

[dbsloci.c 10573]

B ***LOG BY2=> sql error 1017 performing CON [dbsh#3 @ 1204]

[dbsh 1204 ]

B ***LOG BY0=> ORA-01017: invalid username/password; logon denied

[dbsh#3 @ 1204] [dbsh 1204 ]

B ***LOG BY2=> sql error 1017 performing CON [dblink#2 @ 419]

[dblink 0419 ]

B ***LOG BY0=> ORA-01017: invalid username/password; logon denied

[dblink#2 @ 419] [dblink 0419 ]

***************************8

Tried with SAPNOTE : 50088, but no luck,

Please help to resolve this issue at the earliest

[former_member227600]

Hi,

you got the error

ORA-01017: invalid username/password; logon denied

Which is related to ops$ user .

Login with <sid>adm & run the following command

sqlplus "connect manager /as sysdba"

You will come at sql command prompt

And run

SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER';

If you get the user ops$<sid>adm than its ok otherwise you have to create the user ,please follow the following note for more detail: note -400241

[https://websmp102.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=400241&_NLANG=E]

Karan

[former_member182034]

Hi,

You can try it.

When you restart the service from the MMC snap-in ("Restart Service"), the service tries to restart the instance if "Autostart=1" is set in the start profile, even though the instance is already running. The dispatcher that is started in this way terminates immediately, and the snap-in incorrectly displays the dispatcher as being stopped.

A:

As of 46D patch level 737 and 610 patch level 84, the service starts automatically only when you restart the instance if "Autostart=1" is set in the start profile and the instance has not yet run.

try it.

regards,

jamil

[Former Member]

Hi jamil,

I tried the option of restarting the services manually.

but what i beleive is the authentication problem for the OPS$ user. Though the database SID is same, the hostnames are different. I can see the OPS$ userid entered as OPS$SAPTS\PSMADM ( sapts is the hostname of the producitno system) and the sandbox system name is different(sapsbox)

Probably, we need to generate the password file at the oracle level which will recreate the passwords. But, i'm not sure at the sap front. Tried the nate 50088, but no luck.

Please advise

Regards

Jagadeesh

[Former Member]

Hi Jagadeesh,

Create user OPS$sapsbox\PSMADM as described in the note.

Regards

Ashok

[Former Member]

Hi,

Connecting as SAPPSM/<pwd>@PSM on connection 0 (nls_hdl 0) ... (dbsl

640 081205)

As suggested earlier. create user OPS$SAPSBOX\<SID>ADM user.

(DROP the user OPS$SAPTS\PSMADM)

Create its table OPS$SAPSBOX\<SID>ADM.sapuser. having field user name & password.

Change the password of your schema owner (SAPSR3).

add these entries in OPS$SAPSBOX\<SID>ADM.sapuser table.

give resource,connect access to OPS$SAPSBOX\<SID>ADM user.

Now try to up the SAP system.

Hope this will help.

Shambo

[Former Member]

hi All,

I tried all the options to recreate OPS$<SID>ADM user, but nothing was helpful. Hence i restored the sandbox db backup, and started the sap instance.

Could you please advise as how to refresh the sandbox solution manage client with production solution manager data?

Regards

Jagadeesh

[Former Member]

Hi

Thanks to all who supported on this issue. I did a remote client copy, then copied the os folders to bring all the projects, blue prints, etc.....now i'm starting the 7.0 upgradation.

Let me post you with the results.

Regards

Jagadeesh

[Former Member]

hello sir

u can start with command prompt.login with sidadm in OS level.

open cmd prompt type

"startsap.exe name=sid nr=i.no sapdiahost=hostname''

again if u get error check service in OS level.

i hope this will solve u r problem

Edited by: vasu k on Aug 28, 2008 11:22 AM

[Former Member]

Hi Vasu,

thanks for giving me the direction..however, again it failed with the same error. I checked the os services, everything seems to be fine.

Please advise an alternative

errors:

C:\usr\sap\PSM\SYS\exe\run>startsap name=psm nr=00 sapdiahost=sapsbox

startsap=>sapparam: "SAPSYSTEMNAME": "PSM" <--> "psm"

startsap=>sapparam: "SAPSYSTEMNAME": "PSM" <--> "psm"

STARTSAP failed

Details are written to C:\usr\sap\PSM\SYS\exe\run\startpsm.log

Regards

Jagadeesh