ORA-12537: TNS:connection closed

[Former Member]

Dear Friends,

I am facing issues with one of my application server, It is not connected to the oracle databse. please find the trans.log for your reference, please check and suggest.

4 ETW000 [dev trc ,00000] charset='', chset='WE8DEC', UNI_ASC=FALSE/FALSE 10 0.037607

4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPR3's password 13 0.037620

4 ETW000 [dev trc ,00000] Connecting as /@PAA on connection 0 (nls_hdl 0) ... (dbsl 701 140910)

4 ETW000 13 0.037633

4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet EnvHp ErrHp ErrHpBatc

h

4 ETW000 18 0.037651

4 ETW000 [dev trc ,00000] 0 WE8DEC 0x1b794810 0x1b79c2b0 0x1b79fdf

8

4 ETW000 12 0.037663

4 ETW000 [dev trc ,00000] Allocating service context handle for con_hdl=0 17 0.037680

4 ETW000 [dev trc ,00000] Allocating server context handle 12 0.037692

4 ETW000 [dev trc ,00000] Attaching to DB Server PAA (con_hdl=0,svchp=0x1b79fd28,srvhp=0x1b7a2cc8)

4 ETW000 36 0.037728

4 ETW000 [dev trc ,00000] Fri Oct 14 08:15:48 2011 761990 0.799718

4 ETW000 [dev trc ,00000] OCIServerAttach(OCI_DEFAULT) failed with -1=OCI_ERROR 11 0.799729

4 ETW000 [dev trc ,00000] OCIServerAttach(OCI_DEFAULT) failed with SQL error 12537: 22 0.799751

4 ETW000 [dev trc ,00000] ORA-12537: TNS:connection closed

4 ETW000 14 0.799765

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

4 ETW000 [dev trc ,00000] set_ocica() -> SQL error code 12537 12 0.799802

4 ETW000 [dev trc ,00000] -->oci_get_errmsg (con_hdl=0, rc=12537) 10 0.799812

4 ETW000 [dev trc ,00000] OCIErrorGet -> SQL error code: 12537 10 0.799822

4 ETW000 [dev trc ,00000] ORA-12537: TNS:connection closed

4 ETW000 13 0.799835

4 ETW000 [dev trc ,00000] SAPUSER or connect error 99=DBSL_ERR_DB, oerr=12537. 16 0.799851

4 ETW000 [dblink ,00433] ***LOG BY2=>sql error 12537 performing CON [dblink#4 @ 433] 44 0.799895

4 ETW000 [dblink ,00433] ***LOG BY0=>ORA-12537: TNS:connection closed [dblink#4 @ 433] 17 0.799912

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

Regards,

Karthick

[Former Member · Accepted solution]

Hi,

Did you configured tcp.invited_nodes in sqlnet.ora?

Best regards,

Orkun Gedik

[Former Member]

Hi,

Please tnsping <SID> what is the outcome, Is it a new application instance installed,

Thanks,

Balaji.S

[Former Member]

Hi Friends,

Thanks for your reply.

I found a temp solution for this issue, I reduced the no of work processor in the newly configured server, Then the issue gets resolved.

Dialogue Work process - 50 will be reduced as 20

Background work process - 15 will be reduced as 8

Now the probelm gets resolved, But I need to configure 50 dialogue work process and 15 background process in the server.

Kindly help me how to I will do it also help how we allocate the workprocess to the server. Is there any formula available for allocating the workprocess.

Note : Ram is 30GB and 64bit HP unix, 4cpu's has been installed.

Regards,

Karthckbabu G.G

[Former Member]

Hi,

>> Kindly help me how to I will do it also help how we allocate the workprocess to the server. Is there any formula available for allocating the workprocess.

There are many ways to identify how many work porcesses you need. Please find one of these the ways, below;

ST02 -> Go to -> Current local data -> SAP cursor cache -> ID cache

Check "Id Hits" column value for the work process. This value shouldn't be something around 100. If it is, it means that you don't need more workprocess on the system.

Best regards,

Orkun Gedik

[former_member213250]

Hello Karthick

Unfortunatley there isn't any exact solution for the ORA-errors noticed in the provided logs.

There are few steps need to be considered to eliminate this error.

You may check the following information if ORA-12537 appears:

1) Checking database parameters according to SAP Note: 830576.

2) Ensure that your LISTENER.ORA file references only protocols that you

have installed and configured on your server.

3) Ensure that all SIDs and ORACLE_HOMEs referenced are valid.

4) Remove any invalid entries in the LISTENER.ORA file.

5) Ensure the CONNECT_TIMEOUT_LISTENER=0. After any activity restart the

listener.

6) Search for possible network or network related equipment problems

such as a bad router card. Faulty network equipment is likely to cause

this error (firewalls as well).

Hope above information helps.

BR

Venkat

[Former Member]

Hello,

Is Listener UP ?

thanks