cancel
Showing results for 
Search instead for 
Did you mean: 

Database error -30081 at CON Communication protocol being used: "TCP/IP

Former Member
0 Kudos

Hi,

I have installed SAP ECC 6 EHP5 on Windows server 2008 R2 on Microsoft Cluster 2008. The installation went smooth without any errors. When i check the system log I am getting periodic error mentioned below. The error occurs on the Node not containing the DB cluster Group e.g. SAP SID Group is on Node 2 and DB SID Group is on Node 1. Hence the error occurs on Node 2. Kindly refer the below mentioned SM21 log.

Also sometimes Update is deactivated automatically on Node 2.

Database error -30081 at CON

> SQL30081N A communication error has been detected.

> Communication protocol being used: "TCP/IP". Communication

> API being used: "SOCKETS". Location where the error was

> detected: "192.168.90.209". Communication function detectin

> the error: "connect". Protocol specific error code(s):

> "10060", "", "". SQLSTATE=08001

Database error -30081

Database error -30081 at CON

> SQL30081N A communication error has been detected.

> Communication protocol being used: "TCP/IP". Communication

> API being used: "SOCKETS". Location where the error was

> detected: "192.168.90.209". Communication function detectin

> the error: "connect". Protocol specific error code(s):

> "10060", "", "". SQLSTATE=08001

Database error -30081

Database error -30081 at CON

> SQL30081N A communication error has been detected.

> Communication protocol being used: "TCP/IP". Communication

> API being used: "SOCKETS". Location where the error was

> detected: "192.168.90.209". Communication function detectin

> the error: "connect". Protocol specific error code(s):

> "10060", "", "". SQLSTATE=08001

I would really appreciate the quick response as our go live date is within a week.

Regards,

Ketul Kapadia

Accepted Solutions (1)

Accepted Solutions (1)

former_member189725
Active Contributor
0 Kudos

Is the IP 192.168.90.209 , the service IP for the DB resource group ?

If so , please check if there are packet loss when you ping this IP from the Node 2 i.e SAP resource group location .

Please check with your OS/Cluster and network team , if there is any intermittent network issues.

Former Member
0 Kudos

Yes 192.168.90.209 is the ip of DB2 SID Group. I have checked the Network and its pinging since mornin without any packet loss.

Regards,

ketul Kapadia

former_member189725
Active Contributor
0 Kudos

Did you find any such error in SM21 during the ping operation ?

This seems to be an intermittent issue .

When you find such an error in SM21 , ensure your network is working fine without any loss in data over the network.

Former Member
0 Kudos

There is no time period as such. Sometimes the error comes once in a day. Also since yesterday it has been noticed that the update get deactivated automatically for Node 2. All the transaction get error as 'Update has been delayed'. I am not able to find the root cause of it. Can u suggest where shud i get the trace for such behaviour.

Regards,

Ketul Kapadia

former_member189725
Active Contributor
0 Kudos

Can you please the trace file for the V1 update process under the instance working directory .

This can give you some clue of the reason for update getting delayed or disabled.

Former Member
0 Kudos

Hi,

Following is the sm21 log and the coressponding error in the trace file. I have noticed that Node 2 takes the IP address of Heart beat i.e 172.16.2.2 and not its public ip 192.168.90.205. I think this might be the issue. When i vier the kernel info in SAP it shows the ip address of the heart beat.

SM21 Log

11:49:48 BTC 011 000 DDIC BY L Database error -30081 requires database administrator to intervene

11:49:48 BTC 011 000 DDIC BY 4 Database error -30081 at DEL access to table HRP1213

11:49:48 BTC 011 000 DDIC BY 0 > SQL30081N A communication error has been detected.

11:49:48 BTC 011 000 DDIC BY 0 > Communication protocol being used: "TCP/IP". Communication

11:49:48 BTC 011 000 DDIC BY 0 > API being used: "SOCKETS". Location where the error was

11:49:48 BTC 011 000 DDIC BY 0 > detected: "192.168.90.209". Communication function detectin

11:49:48 BTC 011 000 DDIC BY 0 > the error: "connect". Protocol specific error code(s):

11:49:48 BTC 011 000 DDIC BY 0 > "10060", "", "". SQLSTATE=08001

11:49:50 BTC 011 000 DDIC AB 0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred

11:49:50 BTC 011 000 DDIC AB 1 > Short dump "120105 114950 KHYECCPR DN02_KHP_01 " generated

11:49:50 BTC 011 000 DDIC D0 1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20120105114950KHYECCPRDN02_KHP_01 DDIC 000 )

Corresponding dev_w11 trace file error.

Thu Jan 05 11:49:27 2012

C Table HRP1209 has been successfully created.

C Disconnected from 'KHP'

C Disconnected: con_hdl=11 ; appl_hdl=16295; appl_id="192.168.90.205.55967.1201050619"

C Sqlcode -150 was returned on SQL statement:

C DELETE FROM "HRP1213" WHERE "MANDT" = ? AND "PLVAR" = ? AND "OTYPE" = ? AND "OBJID" = ? -- OPTLEVEL( 5 ) -- Q

C UERY_DEGREE( 1 ) -- LOCATION( SAPLRHWM , 1572 ) -- SYSTEM( KHP , SAPKHP )

C DB message text:

C [IBM][CLI Driver][DB2/NT64] SQL0150N The target fullselect, view, typed table, materialized query table, rang

C e-clustered table, or staging table in the INSERT, DELETE, UPDATE, MERGE, or TRUNCATE statement is a target fo

C r which the requested operation is not permitted. SQLSTATE=42807

C This sqlcode does not neccessarily indicate a problem if the affected table is a virtual table.

C Table HRP1213 is a virtual table for deferred table creation.

C Virtual table HRP1213 needs to be converted to a table.

C opening temporary connection for deferred table creation of table HRP1213

C

C Thu Jan 05 11:49:48 2012

C *** ERROR in DB6Connect[dbdb6.c, 1797] CON = 11 (BEGIN)

C &+*** DbSlModifyDB6( SQLConnect 😞 [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication p

C &+*** rotocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "1

C &+*** 92.168.90.209". Communication function detecting the error: "connect". Protocol specific error code(s): "10060",

C &+*** "", "". SQLSTATE=08001

C &+***

C &+***

C &+*** ABAP location info 'SAPLRHWM', 1572

C &+***

C *** ERROR in DB6Connect[dbdb6.c, 1797] (END)

C *** ERROR => DbSlConnect to 'KHP' as 'SAPKHP' failed

[dbdb6.c 1802]

C {root-id=5CF3FC96F1C61EE18DECA30BAF69A5D4}_{conn-id=00000000000000000000000000000000}_0

B ***LOG BYL=> DBQ action required because of database error -30081 [dbsh 1151]

B SQL code: -30081, SQL text: SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "192.168.90.209". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "", "". SQLSTATE=08001

B ***LOG BY4=> sql error -30081 performing DEL on table HRP1213 [dbtran 7635]

B **LOG BY0=> SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "192.168.90.209". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "", "*". SQLSTATE=08001 [dbtran 7635]

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'

B RSLT: {dbsl=99, tran=1}

B FHDR: {tab='HRP1213', fcode=194, mode=2, bpb=0, dbcnt=0, crsr=0,

B hold=0, keep=1, xfer=0, pkg=0, upto=0, init:b=0,

B init:p=0000000000000000, init:#=0, wa:p=0000000000000000, wa:#=0}

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'

B STMT:

B CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=1, fae:blk=0,

B con:id=0, con:vndr=7, val=2,

B key:#=12, xfer=0, xin:#=62, row:#=0, upto=0, wa:p=0X000007DF0043E07C}

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.

A ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.

A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK completed.

A ** RABAX: level LEV_RX_DB_ALIVE entered.

A ** RABAX: level LEV_RX_DB_ALIVE completed.

A ** RABAX: level LEV_RX_HOOKS entered.

A ** RABAX: level LEV_RX_HOOKS completed.

A ** RABAX: level LEV_RX_STANDARD entered.

A ** RABAX: level LEV_RX_STANDARD completed.

A ** RABAX: level LEV_RX_STOR_VALUES entered.

A ** RABAX: level LEV_RX_STOR_VALUES completed.

A ** RABAX: level LEV_RX_C_STACK entered.

I hope this might be useful.

Also if I want to change the IP of Node 2 how should i do the same.\

Regards,

Ketul Kapadia

former_member189725
Active Contributor
0 Kudos

I would suggest you to work with the cluster administrator for sorting out this issue . Heartbeat IP should never be used by the applications to communicate . The applications should always be available via the service IP of the respective resource group (like SAP group , DB group ) and not the physical IP of the nodes.

Former Member
0 Kudos

Hi,

We have two adapters on Node 2, Public and Heartbeat. When i run the command ping -4 <Hostname node 2> it returns the heartbeat IP as that adapter is preferred. I have maintained the correct IP's in the Host file also.

Public IP : 192.168.90.205

Heartbeat IP :172.2.2.6

When i run the command ping -4 <Hostname node 2> it returns me the 172.2.2.6.

My question is can i interchange the IP's of the network adapter would there be any affect on SAP or Cluster configuration And can this be one of the reason for Database connection issue from Node 2.??

Quick response would be appreciated.

Regards,

KK

Answers (0)