Hi,

we are at the point of upgrading to 12.5.0.3, and I wonder whether a bug 
we are experiencing has been fixed in this new version.

We use DirectConnect ( to Oracle), and sp_addexternlogin to specify the 
userid/passwd to be used at the remote end. These settings are per 
Sybase login and per remote destination, and we have two or three dozen, 
as shown by sp_helpexternlogin.  Trouble is, every now and then all 
these settings disappear from the system, and we have to re-enter them 
manually. We can exclude foul play by now, i.e. no one has come to 
delete them.

We are on Solaris, and I suspect we are being hit by one of the last 
manifestations of the multithreading issues there. With DirectConnect, 
there is a parallel Omni-xx process. For the externlogin, uid/pwd 
settings are stored, if I remember well, in the sysattributes table in 
the master database. The parallel process needs to read the table, in 
order to find out how to connect. I can imagine some contention 
happening there, but all this is just guesswork.

Has anybody else experienced this bug ? Is it fixed in 12.5.0.3 ?

Andrew Schonberger

Andrew Schonberger wrote:

> we are at the point of upgrading to 12.5.0.3, and I wonder whether a bug
> we are experiencing has been fixed in this new version.
> 
> We use DirectConnect ( to Oracle), and sp_addexternlogin to specify the
> userid/passwd to be used at the remote end. These settings are per
> Sybase login and per remote destination, and we have two or three dozen,
> as shown by sp_helpexternlogin.  Trouble is, every now and then all
> these settings disappear from the system, and we have to re-enter them
> manually. We can exclude foul play by now, i.e. no one has come to
> delete them.

	How do you know for certain? If they are being deleted (or
	perhaps the table is being truncated), something must be
	doing it. If you can recognise a pattern to when it happens,
	perhaps it might provide a clue. You could also consider
	auditing the relevant system tables and look at permissions
	(I don't think you can revoke permissions on system tables
	but its easy enough to check). A grep thru the installmaster
	script might also be helpful (in case there's a bug somewhere
	that deletes them in another system sproc).

> We are on Solaris, and I suspect we are being hit by one of the last
> manifestations of the multithreading issues there. With DirectConnect,
> there is a parallel Omni-xx process. For the externlogin, uid/pwd
> settings are stored, if I remember well, in the sysattributes table in
> the master database. The parallel process needs to read the table, in
> order to find out how to connect. I can imagine some contention
> happening there, but all this is just guesswork.
> 
> Has anybody else experienced this bug ? Is it fixed in 12.5.0.3 ?

	If its not mentioned in the cover letter have you tried asking
	Sybase Tech Support?

-am	� 2003

--------------090301000902080905050102
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Anthony,

thanks for taking this up. We have found it is a known bug in the Sybase 
problem database:

      http://info.sybase.com/resolution/detail.stm?id_number=10808059
    Problem Description:
    During upgrade to 12.5 the external login rows in sysattributes that
    pertain to external logins to DirectConnect, other ASEs,etc. are
    lost (or deleted) by the upgrade process! These are the rows where
    object_type = 'EL'.
    Resolution:
    CR: 269430
    Title sp_droplogin will also drop ALL external login lines from
    sysattributes Workaround
    Sanitized
    The sp_droplogin stored procedure will drop all external login rows
    from sysattributes regardless of qualified user id.

Andrew


Anthony Mandic wrote:

>Andrew Schonberger wrote:
>
>>we are at the point of upgrading to 12.5.0.3, and I wonder whether a bug
>>we are experiencing has been fixed in this new version.
>>
>>We use DirectConnect ( to Oracle), and sp_addexternlogin to specify the
>>userid/passwd to be used at the remote end. These settings are per
>>Sybase login and per remote destination, and we have two or three dozen,
>>as shown by sp_helpexternlogin.  Trouble is, every now and then all
>>these settings disappear from the system, and we have to re-enter them
>>manually. We can exclude foul play by now, i.e. no one has come to
>>delete them.
>>
>
>	How do you know for certain? If they are being deleted (or
>	perhaps the table is being truncated), something must be
>	doing it. If you can recognise a pattern to when it happens,
>	perhaps it might provide a clue. You could also consider
>	auditing the relevant system tables and look at permissions
>	(I don't think you can revoke permissions on system tables
>	but its easy enough to check). A grep thru the installmaster
>	script might also be helpful (in case there's a bug somewhere
>	that deletes them in another system sproc).
>
>>We are on Solaris, and I suspect we are being hit by one of the last
>>manifestations of the multithreading issues there. With DirectConnect,
>>there is a parallel Omni-xx process. For the externlogin, uid/pwd
>>settings are stored, if I remember well, in the sysattributes table in
>>the master database. The parallel process needs to read the table, in
>>order to find out how to connect. I can imagine some contention
>>happening there, but all this is just guesswork.
>>
>>Has anybody else experienced this bug ? Is it fixed in 12.5.0.3 ?
>>
>
>	If its not mentioned in the cover letter have you tried asking
>	Sybase Tech Support?
>
>-am	� 2003
>


--------------090301000902080905050102
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
Anthony,<br>
<br>
thanks for taking this up. We have found it is a known bug in the Sybase
problem database:<br>
<blockquote>&nbsp; <font size="2" face="Arial"><a href="http://info.sybase.com/resolution/detail.stm?id_number=10808059" target="_blank">
http://info.sybase.com/resolution/detail.stm?id_number=10808059</a>
  </font><br>
  <b><font size="2" face="Arial">Problem Description:</font></b><br>
  <font size="2" face="Arial">During upgrade to 12.5 the external login rows 
in sysattributes that pertain to external logins to DirectConnect, other ASEs,etc.
are lost (or deleted) by the upgrade process! These are the rows where object_type
= 'EL'.</font><br>
  <b><font size="2" face="Arial">Resolution:</font></b><br>
  <font color="#ff0000" size="2" face="Arial">CR: 269430</font><br>
  <font color="#ff0000" size="2" face="Arial"> Title sp_droplogin will also
drop ALL external login lines from sysattributes Workaround</font><br>
  <font color="#ff0000" size="2" face="Arial"> Sanitized</font><br>
  <font color="#ff0000" size="2" face="Arial"> The sp_droplogin stored procedure
will drop all external login rows from sysattributes regardless of qualified
user id.</font><br>
  </blockquote>
Andrew<br>
  <br>
  <br>
Anthony Mandic wrote:<br>
  <blockquote type="cite" cite="mid:3E5542CF.460C9A00@start.com.au">
    <pre wrap="">Andrew Schonberger wrote:<br><br></pre>
    <blockquote type="cite">
      <pre wrap="">we are at the point of upgrading to 12.5.0.3, and I wonder whether a bug<br>we are experiencing has been fixed in this new version.<br><br>We use DirectConnect ( to Oracle), and sp_addexternlogin to specify the<br>userid/passwd to be used at the remote end. These settings are per<br>Sybase login and per remote destination, and we have two or three dozen,<br>as shown by sp_helpexternlogin.  Trouble is, every now and then all<br>these settings disappear from the system, and we have to re-enter them<br>manually. We can exclude foul play by now, i.e. no one has come to<br>delete them.<br></pre>
      </blockquote>
      <pre wrap=""><!----><br>	How do you know for certain? If they are being deleted (or<br>	perhaps the table is being truncated), something must be<br>	doing it. If you can recognise a pattern to when it happens,<br>	perhaps it might provide a clue. You could also consider<br>	auditing the relevant system tables and look at permissions<br>	(I don't think you can revoke permissions on system tables<br>	but its easy enough to check). A grep thru the installmaster<br>	script might also be helpful (in case there's a bug somewhere<br>	that deletes them in another system sproc).<br><br></pre>
      <blockquote type="cite">
        <pre wrap="">We are on Solaris, and I suspect we are being hit by one of the last<br>manifestations of the multithreading issues there. With DirectConnect,<br>there is a parallel Omni-xx process. For the externlogin, uid/pwd<br>settings are stored, if I remember well, in the sysattributes table in<br>the master database. The parallel process needs to read the table, in<br>order to find out how to connect. I can imagine some contention<br>happening there, but all this is just guesswork.<br><br>Has anybody else experienced this bug ? Is it fixed in 12.5.0.3 ?<br></pre>
        </blockquote>
        <pre wrap=""><!----><br>	If its not mentioned in the cover letter have you tried asking<br>	Sybase Tech Support?<br><br>-am	&copy; 2003<br></pre>
        </blockquote>
        <br>
        </body>
        </html>

--------------090301000902080905050102--

Andrew Schonberger wrote:

> We have found it is a known bug in the Sybase problem database:
> 
> http://info.sybase.com/resolution/detail.stm?id_number=10808059

	The link says its related to upgrades. So that would only cover
	in place upgrades and use of the online database command after
	a load. Are either of these used by you when you see it happening?

-am	� 2003