Dispatcher is topped

[Former Member]

Dear All,

My Dispatcher is stopped, i am trying to connecting sql prompt its giving "ERROR:ORA-01031: insufficient privileges"

My R3trans -d log is

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed with rc=1034

4 ETW000 30476 0.389527

4 ETW000 [dev trc ,00000] server_detach(con_hdl=0,stale=1,svrhp=036C487C) 14 0.389541

4 ETW000 [dev trc ,00000] Detaching from DB Server (con_hdl=0,svchp=036B3008,srvhp=036C487C)

4 ETW000 18 0.389559

4 ETW000 [dev trc ,00000] Deallocating server context handle 036C487C 333 0.389892

4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1034'

4 ETW000 45 0.389937

4 ETW000 [dev trc ,00000] set_ocica() -> OCI or SQL return code 1034 12 0.389949

4 ETW000 [dblink ,00431] ***LOG BY2=>sql error 1034 performing CON [dblink#5 @ 431]

4 ETW000 1821 0.391770

4 ETW000 [dblink ,00431] ***LOG BY0=>ORA-01034: ORACLE not available 19 0.391789

4 ETW000 ORA-27101: shared memory realm does not exist [dblink#5 @ 431]

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'SIT'"

Please help me needfull.'

[Former Member]

Hi chandra,

Restrat your database by BRTOOLS.

and then run R3trans -d command.

Thanks

R.

[Former Member]

R3trans log is:

4 ETW000 [dev trc ,00000] Deallocating server context handle 036C4884 315 0.217605

4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '28000'

4 ETW000 24 0.217629

4 ETW000 [dev trc ,00000] set_ocica() -> OCI or SQL return code 28000 11 0.217640

4 ETW000 [dblink ,00431] ***LOG BY2=>sql error 28000 performing CON [dblink#5 @ 431]

4 ETW000 70 0.217710

bold4 ETW000 [dblink ,00431] **LOG BY0=>ORA-28000: the account is locked [dblink#5 @ 431]bold*

4 ETW000 17 0.217727

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'XIT'"

Edited by: Chandra B. on Oct 12, 2009 3:12 PM

[anindya_bose]

Hi Chandra

Do you have your oracle up? Can you try to restart database once?

Did you make any change recently?

[Former Member]

Its giving following error

SQL> ERROR:

ORA-01031: insufficient privileges

SQL>

SQL> ORA-01031: insufficient privileges

SQL>

BR0280I BRSPACE time stamp: 2009-10-12 14.00.33

BR0279E Return code from 'G:\oracle\SIT\102\BIN\sqlplus /nolog < G:\oracle\SIT\s

apreorg\.sebrbifx.spi': 0

BR0302E SQLPLUS call for database instance SIT failed

BR0306E Start and open of database instance SIT failed

BR0669I Cannot continue due to previous warnings or errors - you can go back to

repeat the last action

BR0280I BRSPACE time stamp: 2009-10-12 14.00.33

BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:

I didnt change any settings

Edited by: Chandra B. on Oct 12, 2009 2:01 PM

[anindya_bose]

Chandra

I suppose you are trying to login with OPS$ authentication and typing the command below in sequence

sqlplus /nolog

connect /as sysdba

shutdown immediate

startup

If that is not the case please follow this steps. If you are trying this but still getting the problem please check the content of the SQLNET.ora file in ORACLE_HOME\NETWORK\ADMIN

it should contain the following line

SQLNET.EXPIRE_TIME = 0

SQLNET.AUTHENTICATION_SERVICES = (NTS)

TCP.NODELAY=YES

Also check if SIDADM is a member of ORA_SID_DBA and ORA_SID_OPER and ORA_DBA groups

Edited by: Anindya Bose on Oct 12, 2009 2:16 PM

[Former Member]

Dear Anindya

First method is not allowing

My sqlnet.ora file as follows:

SQLNET.EXPIRE_TIME = 10

SQLNET.AUTHENTICATION_SERVICES = (NONE)

#TCP.NODELAY=YES

[sunny_pahuja2]

Hi Chandra,

Check SAP Note 400241 - Problems with ops$ or sapr3 connect to Oracle

Thanks

Sunny

[anindya_bose]

Take a backup of existing SQLNET.ora and change the parameter as I mentioned. Lets see what happens..

By the way, did you check if somebody has accidentally changed the SIDADM's groups?

[Former Member]

Dear Anindya,

I have changed the sqlnet.ora file as you said, now its starting Database Thank you, but my dispatcher is still stopped.

and SIDADM having correct groups.

Edited by: Chandra B. on Oct 12, 2009 2:51 PM

[anindya_bose]

ok..

Now fine

so please enter command

sqlplus /nolog

connect /as sysdba

startup

After oracle is up , bring up SAP from MMC

[Former Member]

Dear Anindya,

After starting DB i am starting MMC but still my dispatcher is stopped,

[Former Member]

Hi Chandra

Use the following command at Sqlpls.

ALTER USER <username> ACCOUNT UNLOCK;

Also refer SAP note 951167.

Thanks and regards,

Atil Gaikwad

[anindya_bose]

from SQL try this command

select username,account_status from DBA_USERS:

It will list all the accounts which are locked now. TO unlock user, try command

alter user <username> account unlock;

Then change the password from brtools .

Try to restart SAP from MMC

[Former Member]

Thank you verymuch after unlocking user, my dispatcher has been started its working fine,

Thank you to Anindya, and rest all