ORA-12547 Terminating with error code 14

[shradhasampat]

Hello,

While stopping the solution manager 7.1 on oracle  11.2.0.2 through stopsap script it gives me below error while trying to stop SAP:

1.

********************************

ERROR:

ORA-12547: TNS:lost contact

SP2-0640: Not connected

ERROR:

ORA-12547: TNS:lost contact

ORA-12547: TNS:lost contact

------------------------------ Wed Oct 31 16:22:43 PDT 2012

Connect to the database to check the database state:

R3trans check finished with return code: 0

Database is still running

*** ERROR: shutdown failed

/usr/sap/SID/SYS/exe/run/stopdb: Terminating with error code 13

*************************************

The database is still up along with the listener.

But when I individually stop the three one by one, it stops without any error.

1.Stop SAP instance

2.Stop listener

3.Stop database

2. Also the similar is the issue with startsap as mentioned below :

********************************************

Database is not available via R3trans

-------------------------------------------

Trying to start SID database ...

Log file: /home/sidadm/startdb.log

No SQL*Net V2 connect to SID available.

Check that the listener is running: "lsnrctl status".

Start the listener as user orasid: "lsnrctl start".

/usr/sap/SID/SYS/exe/run/startdb: Terminating with error code 14

DB startup failed

please send the tracefile /home/sidadm/startsap.trc to support

********************************************

But if i start following one by one it starts with no error :

1. Start db using startup

2. start listener using lsnrctl start LISTENER_SID

3. start sap startsap

I have already gone through few forum suggestion & tried registering listener with oracle using "alter system register" still i get the same problem.

I have attached my network admin files, kindly request your help to solve the same.

listener.txt.zip

sqlnet.txt.zip

tnsnames.txt.zip

[former_member185239]

Hi shrada,

1. check the environment variable TNS_ADMIN value.

     let me know the value.

2. Shutdown the database with with command

     shutdown abort.

3. kill all the process of oracle and listener at os level.

4.To start oracle :

sqlplus /nolog

connect /as sysdba

startup nomount.

    (capature the output and paste it in your reply.

alter database mount

    ( capture the output and paste it in your next reply)

alter database open.

    (capture the output and paste it in your next reply)

[pankaj_pabreja]

Hi  Shraddha,

Checkout the tnsping <DBSID> command at your OS level and let us know the output.

Also , have you modified your network files while attaching here and hide the SID of the system?

Regards,

Pankaj Pabreja

[Former Member]

Hi,

It looks like permission problem. Better to run sapdba_role.sql once. I think it is going to solve your issue.

Regards,

Lakshmi

[shradhasampat]

Hello Pankaj,

Yes i had modified my network files to hide the SID  .

The output of tnsping SID on my central system is :

TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 04-JAN-2013 15:17:00

Copyright (c) 1997, 2010, Oracle.  All rights reserved.

Used parameter files:

/usr/sap/SID/SYS/profile/oracle/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = host)(PORT = 1527)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = SID)))

OK (10 msec)

Thanks

Shradha

[shradhasampat]

Hello Lakshmi,

I have already sapdba_role.sql once still get same error.

Thanks

Shradha

[Former Member]

Hi ,

   Please ensure that tnsnames,listener,sqlnet.ora file in /oracle/SID/112_64/network/admin is same as in /sapmnt/sid/profile/oracle.

If not, try to sync each other and check whether it works.

Thanks and Regards,

Vimal

[Reagan]

Hello

I suggest you to stop the database normally.

Have you done any changes to the system before this like Kernel upgrade ?

One you have stopped the database switch to sidadm and start the database.

Before that make sure the listener is running.

startsap db

Also check the output of R3trans -d

Also check the user groups of the users sidadm and orasid.

Issue the command id under the respective users.

Cheers

RB

[shradhasampat]

Hello RB,

I tried the above steps but still startsap db is throwing error.

Please check startdb.log & groups to which the users belong

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

hostlxsid:/home/sidadm # more /home/sidadm/startdb.log

------------------------------ Fri Nov 2 11:08:02 PDT 2012

LOGFILE FOR STARTING ORACLE

Trying to start sid database ...

------------------------------ Fri Nov 2 11:08:02 PDT 2012

checking required environment variables

ORACLE_HOME  is >/oracle/sid/112_64<

ORACLE_SID   is >sid<

------------------------------ Fri Nov 2 11:08:02 PDT 2012

check initora

------------------------------ Fri Nov 2 11:08:02 PDT 2012

check initora

------------------------------ Fri Nov 2 11:08:02 PDT 2012

checking V2 connect

TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 02-NOV-2012 11:08

:03

Copyright (c) 1997, 2010, Oracle.  All rights reserved.

Used parameter files:

/usr/sap/sid/SYS/profile/oracle/sqlnet.ora

Used TNSNAMES adapter to residve the alias

Attempting to contact (DESCRIPTION = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL

= TCP)(HOST = hostlxsid)(PORT = 1527)) (CONNECT_DATA = (SERVER = DEDICATED) (SER

VICE_NAME = sid)))

OK (10 msec)

tnsping: V2 connect to sid

------------------------------ Fri Nov 2 11:08:03 PDT 2012

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

------------------------------ Fri Nov 2 11:08:03 PDT 2012

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

------------------------------ Fri Nov 2 11:08:03 PDT 2012

starting database

SQL*Plus: Release 11.2.0.2.0 Production on Fri Nov 2 11:08:03 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

ERROR:

ORA-12547: TNS:lost contact

ORA-12547: TNS:lost contact

------------------------------ Fri Nov 2 11:08:04 PDT 2012

Connect to the database to verify, that the database is now open

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

Groups ::

****************************

hostlxsid:/oracle/sid # groups

dba sapinst oper

hostlxsid:/oracle/sid # id

uid=1002(orasid) gid=1002(dba) groups=1000(sapinst),1002(dba),1003(oper)

hostlxsid:/home/sidadm # id

uid=1001(sidadm) gid=1001(sapsys) groups=1000(sapinst),1001(sapsys),1002(dba),1003(oper)

hostlxsid:/home/sidadm # groups

sapsys sapinst dba oper

*********************************

Also R3trans -d when db is down gives  RC 12 which I think is fine, it works fine once db is up & running :

hostlxsid:/home/sidadm # R3trans -d

This is R3trans version 6.22 (release 720 - 03.06.11 - 17:57:00).

unicode enabled version

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

R3trans finished (0012).

Thanks

Shradha

[Reagan]

Hello Shradha

Can you provide me the output of trans.log file please ?

Cheers

RB

[shradhasampat]

Hello RB,

R3trans -d ends with 0000

Thanks

Shradha

[Reagan]

Hello Shradha

The problem looks more likely with the start and stop scripts.

Suggest you to update the kernel or replace the scripts and try.

Cheers

RB

[shradhasampat]

Hello RB,

System recently got updated so the exe got updated with it but still I face the same problem.

Could it be related to Listener ? Did you get a chance to look at the network files that i have attached to original post ?

Thanks

Shradha

[Reagan]

Hello Shradha

Please add the group sapsys to the orasid user and then try.

Cheers

RB

[Former Member]

Please start your sap system as usual and attach satrtdb.log file.

Regards

Roman

[shradhasampat]

Please find the startdb.log below :

hostlxsid:/home/sidadm # more /home/sidadm/stopdb.log

------------------------------ Thu Nov 1 12:30:13 PDT 2012

LOGFILE FOR STOPPING ORACLE

Trying to stop sid database ...

------------------------------ Thu Nov 1 12:30:13 PDT 2012

checking required environment variables

ORACLE_HOME  is >/oracle/sid/112_64<

ORACLE_SID   is >sid<

------------------------------ Thu Nov 1 12:30:13 PDT 2012

Connect to the database to check the database state:

R3trans check finished with return code: 0

Database is running

Continue with stop procedure

------------------------------ Thu Nov 1 12:30:13 PDT 2012

Forceing a log switch and then stop the database

SQL*Plus: Release 11.2.0.2.0 Production on Thu Nov 1 12:30:13 2012

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

ERROR:

ORA-12547: TNS:lost contact

SP2-0640: Not connected

ERROR:

ORA-12547: TNS:lost contact

ORA-12547: TNS:lost contact

------------------------------ Thu Nov 1 12:30:14 PDT 2012

Connect to the database to check the database state:

R3trans check finished with return code: 0

Database is still running

*** ERROR: shutdown failed

[Reagan]

Hello

The stopdb.log and startdb.log barely gives you an indications about the underlying issue.

I suspect a permission issue here for the sidadm user to connect to the database and shut it down.

Cheers

/ RB /

[former_member189797]

Hello Shradha,

Please check the Note

505630 - Composite SAP Note ORA-12547

Regards,

Gaurav

[shradhasampat]

Thanks Gaurav for your efforts !!

I have gone through these notes & tried as per current oracle release & scenario change of queuesize but still I had the same problem.

Thanks

Shradha

[former_member182034]

hi sampat,

ORA-12547: TNS:lost contact

please check below notes

Note 505630 - Composite SAP Note ORA-12547

SAP note 131561

Terminating with error code 14

please start the listener services.

Regards,

[shradhasampat]

Thanks Abdul for your efforts !!

I have gone through these notes & tried as per current oracle release & scenario change of queuesize but still I had the same problem.

Thanks

Shradha

[Former Member]

hi,

try this,

http://www.dba-oracle.com/t_ora_12547_tns_lost_contact.htm