Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When attempting to connect to a Sybase server that is not available
(for example, the Sybase server process is shut down but the Sybase
system hardware is active), SAS/ACCESS will crash and issue the
following errors. This sometimes leaves SAS in an indeterminate state
where further connections to (valid) Sybase servers cannot be made.

Segmentation Violation In Task ( SQL      ]
Fault Occurred at [/export/home/sybase/System12_5/OCS-
12_5/lib/libcomn_r.so:com__errfile_cache_drop+0xcc]

Task Traceback

/export/home/sybase/System12_5/OCS-
12_5/lib/libcomn_r.so:com__errfile_cache_drop+0xcc
/export/home/sybase/System12_5/OCS-
12_5/lib/libtcl_r.so:sybnet_comp_errstr+0x1e8
/export/home/sybase/System12_5/OCS-12_5/lib/libtcl_r.so:sybnet_comp_errs
tr+0x70
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:np_err_string+0x5
8
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:ct__api_errinit+0
x1a4
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:ct__api_errinit+0
x340
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:ct__error+0x108
/export/home/sybase/System12_5/OCS-
12_5/lib/libct_r.so:ct__api_connect_fail+0xe4
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:ct__50cont_connec
t+0x208
/export/home/sybase/System12_5/OCS-
12_5/lib/libcomn_r.so:com__async_iopost+0x524
/export/home/sybase/System12_5/OCS-
12_5/lib/libcomn_r.so:com__async_iopost+0x3e8
/export/home/sybase/System12_5/OCS-
12_5/lib/libcomn_r.so:com__async_iopost+0x1c0
/export/home/sybase/System12_5/OCS-12_5/lib/libcomn_r.so:com_async_poll+
0xc4
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:ct__50cont_connec
t+0x57c
/export/home/sybase/System12_5/OCS-12_5/lib/libct_r.so:ct_connect+0x188
/opt/sas/sas82/hotfix/sasexe/syslx125.82sb10:s_conn+0x2c8
/opt/sas/sas82/hotfix/sasexe/sasiosyb.82sb10:syconn+0x8d0
/opt/sas/sas82/hotfix/sasexe/sasxdbi.82bx03:dbicon+0x7c0
/opt/sas/sas82/hotfix/sasexe/sasxdbi.82bx03:conn+0x308
/opt/sas/sas82/hotfix/sasexe/sassqp.82bx03:sqpconv+0x360
/opt/sas/sas82/hotfix/sasexe/sassqp.82bx03:sqpcon+0x204
/opt/sas/sas82/hotfix/sasexe/sassqxu.82bx03:sqlloop+0x71c
/opt/sas/sas82/hotfix/sasexe/sassqxu.82bx03:sqlloop+0x154
/opt/sas/sas82/hotfix/sasexe/sassql.82bx03:sassql+0x3c0
/opt/sas/sas82/sas:vvtentr+0x6c

This is a problem with the connection handle intermittently getting
trashed if the connection is not made, as is the case if the server is
down. This may cause a Segmentation Violation error when the ctlib
error routine referencing the connection handle is called.

To resolve this problem, apply the HOTFIX.

A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#015017

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at: