program seg. faults on opening a DB connection

program seg. faults on opening a DB connection

Post by Nysal J » Sun, 06 Jan 2002 19:18:42



I have a CORBA based server(C++) running on AIX 4.3.3 with
DB2 v7.1 fixpack 5 installed.
We have a wrapper class written over DB2 CLI.
The problem is that the server crashes while beginning
a database transaction.The same database library works
properly on Linux.The following is the backtrace from the core file.
Looking forward to hear about possible reasons for the crash.
The trace seems to indicate that the program crashes while attempting
to open a new connection for the transaction. When I tried running a
small
program performing the same thing, it seems to work correctly. Our
server
satisfies every request on separate threads.

Segmentation fault in sqlowque at 0xd0c9ecc4 ($t9)
0xd0c9ecc4 (sqlowque+0x1c) 7c21616e      stwux   r1,r1,r12
(dbx) where
sqlowque(??, ??, ??) at 0xd0c9ecc4
sqlccipcconnr__FP13sqlcc_connectP15sqlcc_comhandleP10sqlcc_cond(??,
??, ??) at 0xd0c83ba4
sqlccconnr__FP13sqlcc_connectP15sqlcc_comhandleP10sqlcc_cond[1]
[fdpr](??, ??, ??) at 0xd0caa46
0
glink.getuid(??, ??) at 0xd0cb2d80
sqle_db2ra_ar_driver__FP10sqle_db2raP17sqle_ar_interface[5] [fdpr](??,
??) at 0xd0c5bd54
sqle_database_connect__FP10sqle_db2raP10sqler_glob[1] [fdpr](??, ??)
at 0xd0c8c1e8
sqleriar__FP10sqle_db2ra(??) at 0xd0c646a0
sqleStartUsingDatabase__FPcciT2N31P10sqlf_dbcfdT1P8sqledscbP5sqlcaT1T3(0x2047cdb4,
0x53000053,
0x1, 0x0, 0x20487e78, 0x2047ceb4, 0x0, 0x0) at 0xd0cb4f10
sqlak_connect__FUsT1[4] [fdpr](??, ??) at 0xd0d8aa1c
sqlacall[3] [fdpr](0x1d001d, 0x50005, 0x20002, 0x0, 0x0) at 0xd0c69a44
clp_connect__FP15CLI_CONNECTINFOP15sqla_program_idUsPcN34P5sqlca(??,
??, ??, ??, ??, ??, ??, ??
) at 0xd0f15d68
CLI_sqlConnect__FP15CLI_CONNECTINFOP5sqlcaP15CLI_ERRLISTINFO(??, ??,
??) at 0xd0e137ac
SQLConnect2__FPP15CLI_CONNECTINFOPUcsT2T3T2T3T2T3Uc[1] [fdpr](??, ??,
??, ??, ??, ??, ??, ??) a
t 0xd0f3dff0
SQLDriverConnect2__FPP15CLI_CONNECTINFOPvPUcsT3T4PsUsUcT9P15CLI_ERRLISTINFO(??,
??, ??, ??, ??,
 ??, ??, ??) at 0xd0dc39d4
SQLConnect1__FPP15CLI_CONNECTINFOPUcsT2T3T2T3(??, ??, ??, ??, ??, ??,
??) at 0xd0dbc968
SQLConnectW(??, ??, ??, ??, ??, ??, ??) at 0xd0ec2f74

 
 
 

program seg. faults on opening a DB connection

Post by Fan Ruo Xi » Mon, 07 Jan 2002 11:56:34


Hi, Nysal,
What does the db2diag.log show when your server crash (Segmentation fault)?
At the same time, does AIX diagnostic information (errpt -a) show something which you
think maybe have some relationship with this?
Regards,

Fan Ruo Xin


> I have a CORBA based server(C++) running on AIX 4.3.3 with
> DB2 v7.1 fixpack 5 installed.
> We have a wrapper class written over DB2 CLI.
> The problem is that the server crashes while beginning
> a database transaction.The same database library works
> properly on Linux.The following is the backtrace from the core file.
> Looking forward to hear about possible reasons for the crash.
> The trace seems to indicate that the program crashes while attempting
> to open a new connection for the transaction. When I tried running a
> small
> program performing the same thing, it seems to work correctly. Our
> server
> satisfies every request on separate threads.

> Segmentation fault in sqlowque at 0xd0c9ecc4 ($t9)
> 0xd0c9ecc4 (sqlowque+0x1c) 7c21616e      stwux   r1,r1,r12
> (dbx) where
> sqlowque(??, ??, ??) at 0xd0c9ecc4
> sqlccipcconnr__FP13sqlcc_connectP15sqlcc_comhandleP10sqlcc_cond(??,
> ??, ??) at 0xd0c83ba4
> sqlccconnr__FP13sqlcc_connectP15sqlcc_comhandleP10sqlcc_cond[1]
> [fdpr](??, ??, ??) at 0xd0caa46
> 0
> glink.getuid(??, ??) at 0xd0cb2d80
> sqle_db2ra_ar_driver__FP10sqle_db2raP17sqle_ar_interface[5] [fdpr](??,
> ??) at 0xd0c5bd54
> sqle_database_connect__FP10sqle_db2raP10sqler_glob[1] [fdpr](??, ??)
> at 0xd0c8c1e8
> sqleriar__FP10sqle_db2ra(??) at 0xd0c646a0
> sqleStartUsingDatabase__FPcciT2N31P10sqlf_dbcfdT1P8sqledscbP5sqlcaT1T3(0x2047cdb4,
> 0x53000053,
> 0x1, 0x0, 0x20487e78, 0x2047ceb4, 0x0, 0x0) at 0xd0cb4f10
> sqlak_connect__FUsT1[4] [fdpr](??, ??) at 0xd0d8aa1c
> sqlacall[3] [fdpr](0x1d001d, 0x50005, 0x20002, 0x0, 0x0) at 0xd0c69a44
> clp_connect__FP15CLI_CONNECTINFOP15sqla_program_idUsPcN34P5sqlca(??,
> ??, ??, ??, ??, ??, ??, ??
> ) at 0xd0f15d68
> CLI_sqlConnect__FP15CLI_CONNECTINFOP5sqlcaP15CLI_ERRLISTINFO(??, ??,
> ??) at 0xd0e137ac
> SQLConnect2__FPP15CLI_CONNECTINFOPUcsT2T3T2T3T2T3Uc[1] [fdpr](??, ??,
> ??, ??, ??, ??, ??, ??) a
> t 0xd0f3dff0
> SQLDriverConnect2__FPP15CLI_CONNECTINFOPvPUcsT3T4PsUsUcT9P15CLI_ERRLISTINFO(??,
> ??, ??, ??, ??,
>  ??, ??, ??) at 0xd0dc39d4
> SQLConnect1__FPP15CLI_CONNECTINFOPUcsT2T3T2T3(??, ??, ??, ??, ??, ??,
> ??) at 0xd0dbc968
> SQLConnectW(??, ??, ??, ??, ??, ??, ??) at 0xd0ec2f74


 
 
 

program seg. faults on opening a DB connection

Post by Nysal J » Tue, 08 Jan 2002 17:04:22


db2diag.log does not show any new entry when the server crashes.
But "errpt -a" shows the following error:

---------------------------------------------------------------------------
LABEL:          CORE_DUMP
IDENTIFIER:     C60BB505

Date/Time:       Mon Jan  7 01:34:49
Sequence Number: 416
Machine Id:      000107338900
Node Id:         tnksrv03
Class:           S
Type:            PERM
Resource Name:   SYSPROC

Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED

Probable Causes
SOFTWARE PROGRAM

User Causes
USER GENERATED SIGNAL

        Recommended Actions
        CORRECT THEN RETRY

Failure Causes
SOFTWARE PROGRAM

        Recommended Actions
        RERUN THE APPLICATION PROGRAM
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
SIGNAL NUMBER
          11
USER'S PROCESS ID:
       26028
FILE SYSTEM SERIAL NUMBER
          12
INODE NUMBER
      788480
PROGRAM NAME
RMServer
ADDITIONAL INFORMATION
sqlowque 164
sqloTQMRe A0
sqlccipcc 45C
sqlccconn 240
sqle_db2r 418
sqle_db2r 1120
sqle_data 59E0
sqleriar_ 680
sqleStart 564
sqlak_con B50
sqlacall 3CC8
clp_conne 56C
CLI_sqlCo B54
SQLConnec D0C
SQLDriver 4C64
SQLConnec 6FC
SQLConnec 6A8
-06-X-90-a 120
wTQ2_3std 110
__ct__19T 40
har_trait 9C
BeginTran B8
??
??
??
execute__ E4
SGlobalTa 810
gine7Mess 1A4
dispatchM 38
tocolAdap 220
 98
 250
 50
 78
_pthread_ D4
??
??

Symptom Data
REPORTABLE
1
INTERNAL ERROR
0
SYMPTOM CODE
PCSS/SPI2 FLDS/RMServer SIG/11 FLDS/sqlowque VALU/164 FLDS/^FX~Pa
---------------------------------------------------------------------------


Quote:> Hi, Nysal,
> What does the db2diag.log show when your server crash (Segmentation fault)?
> At the same time, does AIX diagnostic information (errpt -a) show something which you
> think maybe have some relationship with this?
> Regards,

> Fan Ruo Xin

 
 
 

program seg. faults on opening a DB connection

Post by Fan Ruo Xi » Wed, 09 Jan 2002 13:18:33


db2diag.log should show something. You can change diaglevel to 4 (dbm cfg), reproduce the
error, see if there are any messages in db2diag.log. Try to capture how many db2agent are
running? At the same time, tell me how many line under the semaphore which owner is
db2inst1 when you run $ipcs.
When you do this test, try to kick out those remote connections (tcpip connection). I mean
try not to allow those tcpip connections.
Regards,

Fan RX


> db2diag.log does not show any new entry when the server crashes.
> But "errpt -a" shows the following error:

> ---------------------------------------------------------------------------
> LABEL:          CORE_DUMP
> IDENTIFIER:     C60BB505

> Date/Time:       Mon Jan  7 01:34:49
> Sequence Number: 416
> Machine Id:      000107338900
> Node Id:         tnksrv03
> Class:           S
> Type:            PERM
> Resource Name:   SYSPROC

> Description
> SOFTWARE PROGRAM ABNORMALLY TERMINATED

> Probable Causes
> SOFTWARE PROGRAM

> User Causes
> USER GENERATED SIGNAL

>         Recommended Actions
>         CORRECT THEN RETRY

> Failure Causes
> SOFTWARE PROGRAM

>         Recommended Actions
>         RERUN THE APPLICATION PROGRAM
>         IF PROBLEM PERSISTS THEN DO THE FOLLOWING
>         CONTACT APPROPRIATE SERVICE REPRESENTATIVE

> Detail Data
> SIGNAL NUMBER
>           11
> USER'S PROCESS ID:
>        26028
> FILE SYSTEM SERIAL NUMBER
>           12
> INODE NUMBER
>       788480
> PROGRAM NAME
> RMServer
> ADDITIONAL INFORMATION
> sqlowque 164
> sqloTQMRe A0
> sqlccipcc 45C
> sqlccconn 240
> sqle_db2r 418
> sqle_db2r 1120
> sqle_data 59E0
> sqleriar_ 680
> sqleStart 564
> sqlak_con B50
> sqlacall 3CC8
> clp_conne 56C
> CLI_sqlCo B54
> SQLConnec D0C
> SQLDriver 4C64
> SQLConnec 6FC
> SQLConnec 6A8
> -06-X-90-a 120
> wTQ2_3std 110
> __ct__19T 40
> har_trait 9C
> BeginTran B8
> ??
> ??
> ??
> execute__ E4
> SGlobalTa 810
> gine7Mess 1A4
> dispatchM 38
> tocolAdap 220
>  98
>  250
>  50
>  78
> _pthread_ D4
> ??
> ??

> Symptom Data
> REPORTABLE
> 1
> INTERNAL ERROR
> 0
> SYMPTOM CODE
> PCSS/SPI2 FLDS/RMServer SIG/11 FLDS/sqlowque VALU/164 FLDS/^FX~Pa
> ---------------------------------------------------------------------------


> > Hi, Nysal,
> > What does the db2diag.log show when your server crash (Segmentation fault)?
> > At the same time, does AIX diagnostic information (errpt -a) show something which you
> > think maybe have some relationship with this?
> > Regards,

> > Fan Ruo Xin

 
 
 

program seg. faults on opening a DB connection

Post by Johann Sand » Wed, 09 Jan 2002 20:14:20


Hi,

while it is good advice to set the diagnostic level to 4 for testing
purposes, absence of errors from db2diag.log indicate either the DB2
CLI or the application program is at fault.

Are there still no errors showing up with level 4?

 
 
 

program seg. faults on opening a DB connection

Post by ramkishen » Fri, 12 Apr 2002 10:41:19


Hi Nysal

I am having the exact same problem on the same environment. Have you got
a solution yet? Appreciate any insights you can throw on this.

--
Ram

Posted via dBforums
http://dbforums.com

 
 
 

1. program seg. faults on opening a DB connection

Hi,
One of my friends have sent me following info.
And it worked for me, my problem is solved.

Plese go throught this
---------------------

For the SQLConnect crash problem there is a solution mentioned on
IBM site. refer link below.. You need to increase the stack size
of thread.
http://www-1.ibm.com/support/docview.wss?uid=swg21007191

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

Thanks,
Abhijit

--
Posted via http://dbforums.com

2. Oracle's Metalink web site

3. Error: Failed to create index!!!

4. Seg Fault on program exit with OCI in shared library with dlopen() on Linux

5. is it possible to use access db or excel data in Java programming?

6. Sybase 12 Open Server seg fault with reentrant libs

7. multiple filegroups on same volume and IO scalability

8. pgsql/contrib/seg (Makefile README.seg buffer.c buffer.h seg-validate.pl seg.c seg.sql.in segdata.h segparse.y segscan.l sort-segments.pl)

9. pg_dump Seg Faults

10. Tip of current tree: Seg fault in query

11. OAS install 4.0.7 on Linux, owsctl seg faults