Work process is in running state

[Former Member]

Hi Experts,

Our ECC6.0 is in MSCS clusters Oracle 10.2.0.4 database. When I saw the 3 to 4 work processes of both nodes are in running state then I checked the developer trace of perticular work process. dev_w0, dev_w1 etc

I found the below Error-

C Tue Nov 22 08:36:12 2011

C Application info callback registered.

C Logon as OPS$-user to get SAPSR3's password

C Connecting as /@IIP on connection 0 (nls 0) ... (dbsl 701 170611, UNICODE[2])

C Detaching from DB Server (con_hdl=0,svchp=000000001A2B3768,srvhp=000000001A2B3E38)

C Attaching to DB Server IIP (con_hdl=0,svchp=000000001A2B3768,srvhp=000000001A2B3E38)

C

C Tue Nov 22 08:36:21 2011

C OCIServerAttach(OCI_DEFAULT) failed with SQL error 12154:

C ORA-12154: TNS:could not resolve the connect identifier specified

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

[dbsloci.c 11330]

C SAPUSER or connect error 99=DBSL_ERR_DB, oerr=12154.

B reconnect failed for connection 0

M *** ERROR => ThHdlReconnect: db_reconnect failed (2048) [thxxhead.c 17596]

B db_con_reconnect: reconnecting to connection 0:

B 000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,

B reco = YES, frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

B opening connection 0 ...

Please let me know what mat be the issue

Regards,

Nilesh

[Former Member]

Hello Nilesh,

Below thread can help you to resolve this issue.

Good luck.

Thanks,

Siva Kumar

[Former Member]

Hi,

Please go through the following OSS Note

Note 324714 - DB connect error in TMS after Oracle upgrade/change

<removed_by_moderator>

Do not ask for points, Read the "Rules of Engagement"

Thanking you

With kindest regards

Hussain

Edited by: Juan Reyes on Dec 13, 2011 11:16 AM

[Former Member]

Hi,

My Suspicion is your TNSNAMES.ORA is not configured properly. Please refer the following will be useful to resolve the error.

Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)

- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.

- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.

- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.

- If you are using directory naming:

- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

- Verify that the LDAP directory server is up and that it is accessible.

- Verify that the net service name or database name used as the connect identifier is configured in the directory.

- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier

- If you are using easy connect naming:

- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

- Make sure the host, port and service name specified are correct.

- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

[former_member188883]

Hi,

Please check the following

1) R3trans -d works ?

2) Listener is running or not ?

Regards,

Deepak Kori