Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

sp_configure

6 posts in General Discussion Last posting was on 2011-02-11 16:48:37.0Z
Raj... Posted on 2011-02-09 04:14:25.0Z
Sender: 54f5.4d52133d.1804289383@sybase.com
From: Raj...
Newsgroups: sybase.public.ase.general
Subject: sp_configure
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4d5214a1.5524.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 8 Feb 2011 20:14:25 -0800
X-Trace: forums-1-dub 1297224865 10.22.241.41 (8 Feb 2011 20:14:25 -0800)
X-Original-Trace: 8 Feb 2011 20:14:25 -0800, 10.22.241.41
Lines: 13
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29937
Article PK: 79166

When I tried to change the config option "allow updates", It
is giving me following warning message. Why is it so ? and
How can I avoid it ?? My sybase version is ASE/12.5.3/EBF
12461 ESD#2/ and Operating System is Windows.



Server 'Servername', Procedure 'sp_configure', Line 695:
Warning: The file '$SYBASE\servername.001' has been
overwritten. To prevent
this rename, move, or delete old configuration files. See
System Administration
Guide for details.


Rob V [ Sybase ] Posted on 2011-02-09 08:04:40.0Z
From: "Rob V [ Sybase ]" <robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
Reply-To: robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY
Organization: Sypron BV / TeamSybase / Sybase
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: sp_configure
References: <4d5214a1.5524.1681692777@sybase.com>
In-Reply-To: <4d5214a1.5524.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d524a98$1@forums-1-dub>
Date: 9 Feb 2011 00:04:40 -0800
X-Trace: forums-1-dub 1297238680 10.22.241.152 (9 Feb 2011 00:04:40 -0800)
X-Original-Trace: 9 Feb 2011 00:04:40 -0800, vip152.sybase.com
Lines: 47
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29940
Article PK: 79171


On 09-Feb-2011 05:14, Raj... wrote:
> When I tried to change the config option "allow updates", It
> is giving me following warning message. Why is it so ? and
> How can I avoid it ?? My sybase version is ASE/12.5.3/EBF
> 12461 ESD#2/ and Operating System is Windows.
>
>
>
> Server 'Servername', Procedure 'sp_configure', Line 695:
> Warning: The file '$SYBASE\servername.001' has been
> overwritten. To prevent
> this rename, move, or delete old configuration files. See
> System Administration
> Guide for details.

The message is harmless. every time you change a setting with
sp_configure, a copy of the previous version of the config file is made
that ends in nnn which runs from 001 to 999. This is only a copy of the
old config file, not the config file itself, which ends in .cfg. These
copies are so that you can restore an earlier configuration, should you
have changed somethign that causes problems, but you cannot remember
what the change was.
You probably have done this more than 999 tmes now, and it will then
cycle arond and create a .001 file again. Because it already existed, it
mentions it overwrites it.
It's perhaps best to just clean up all those copies every once in a
while. Just run "rm <servername>.[0-9]??" in the directory where the
config file is located.

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks& Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter: @rob_verschoor
Sypron B.V., The Netherlands | Chamber of Commerce 27138666
-----------------------------------------------------------------


Bret Halford Posted on 2011-02-09 16:23:34.0Z
From: Bret Halford <bret@sybase.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: sp_configure
References: <4d5214a1.5524.1681692777@sybase.com> <4d524a98$1@forums-1-dub>
In-Reply-To: <4d524a98$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d52bf86$1@forums-1-dub>
Date: 9 Feb 2011 08:23:34 -0800
X-Trace: forums-1-dub 1297268614 10.22.241.152 (9 Feb 2011 08:23:34 -0800)
X-Original-Trace: 9 Feb 2011 08:23:34 -0800, vip152.sybase.com
Lines: 42
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29945
Article PK: 79174


On 2/9/2011 1:04 AM, Rob V [ Sybase ] wrote:
> On 09-Feb-2011 05:14, Raj... wrote:
>> When I tried to change the config option "allow updates", It
>> is giving me following warning message. Why is it so ? and
>> How can I avoid it ?? My sybase version is ASE/12.5.3/EBF
>> 12461 ESD#2/ and Operating System is Windows.
>>
>>
>>
>> Server 'Servername', Procedure 'sp_configure', Line 695:
>> Warning: The file '$SYBASE\servername.001' has been
>> overwritten. To prevent
>> this rename, move, or delete old configuration files. See
>> System Administration
>> Guide for details.
>
> The message is harmless. every time you change a setting with
> sp_configure, a copy of the previous version of the config file is made
> that ends in nnn which runs from 001 to 999. This is only a copy of the
> old config file, not the config file itself, which ends in .cfg. These
> copies are so that you can restore an earlier configuration, should you
> have changed somethign that causes problems, but you cannot remember
> what the change was.
> You probably have done this more than 999 tmes now, and it will then
> cycle arond and create a .001 file again. Because it already existed, it
> mentions it overwrites it.
> It's perhaps best to just clean up all those copies every once in a
> while. Just run "rm <servername>.[0-9]??" in the directory where the
> config file is located.
>
> HTH,
>
> Rob V.

As a minor additional note, a change has been checked in to the
next major release that increases the maximum number of config
files to 999999999. (CR 398491) I'd say it probably is still
best to regularly clean up the older files, although it is good
to keep a bit of history of recent changes.

-bret


Raj... Posted on 2011-02-10 23:16:16.0Z
Sender: 59e3.4d522830.1804289383@sybase.com
From: Raj...
Newsgroups: sybase.public.ase.general
Subject: Re: sp_configure
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4d5471c0.2827.1681692777@sybase.com>
References: <4d524a98$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 10 Feb 2011 15:16:16 -0800
X-Trace: forums-1-dub 1297379776 10.22.241.41 (10 Feb 2011 15:16:16 -0800)
X-Original-Trace: 10 Feb 2011 15:16:16 -0800, 10.22.241.41
Lines: 64
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29955
Article PK: 79184


> On 09-Feb-2011 05:14, Raj... wrote:
> > When I tried to change the config option "allow updates"
> > , It is giving me following warning message. Why is it
> > so ? and How can I avoid it ?? My sybase version is
> > ASE/12.5.3/EBF 12461 ESD#2/ and Operating System is
> Windows. >
> >
> >
> > Server 'Servername', Procedure 'sp_configure', Line 695:
> > Warning: The file '$SYBASE\servername.001' has been
> > overwritten. To prevent
> > this rename, move, or delete old configuration files.
> > See System Administration
> > Guide for details.
>
> The message is harmless. every time you change a setting
> with sp_configure, a copy of the previous version of the
> config file is made that ends in nnn which runs from 001
> to 999. This is only a copy of the old config file, not
> the config file itself, which ends in .cfg. These copies
> are so that you can restore an earlier configuration,
> should you have changed somethign that causes problems,
> but you cannot remember what the change was.
> You probably have done this more than 999 tmes now, and it
> will then cycle arond and create a .001 file again.
> Because it already existed, it mentions it overwrites it.
> It's perhaps best to just clean up all those copies every
> once in a while. Just run "rm <servername>.[0-9]??" in
> the directory where the config file is located.
>
> HTH,
>
> Rob V.
> ----------------------------------------------------------
> ------- Rob Verschoor
>
> Certified Sybase Professional DBA for ASE
> 15.0/12.5/12.0/11.5/11.0 and Replication Server
> 15.0.1/12.5 // TeamSybase
>
> Author of Sybase books (order online at
> www.sypron.nl/shop): "Tips, Tricks& Recipes for Sybase
> ASE" (ASE 15 edition) "The Complete Sybase ASE Quick
> Reference Guide" "The Complete Sybase Replication Server
> Quick Reference Guide"
>
> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter:
> @rob_verschoor Sypron B.V., The Netherlands | Chamber of
> Commerce 27138666
> ----------------------------------------------------------
> -------
>

Thanks Rob,
It worked after clearing files in one server.
But It didn't work in other server. I dont see any
difference between both servers. But It didn't work in one.

Any suggestions/comments ?


Thanks,
Raj..


Rob V [ Sybase ] Posted on 2011-02-11 10:16:33.0Z
From: "Rob V [ Sybase ]" <robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
Reply-To: robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY
Organization: Sypron BV / TeamSybase / Sybase
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: sp_configure
References: <4d524a98$1@forums-1-dub> <4d5471c0.2827.1681692777@sybase.com>
In-Reply-To: <4d5471c0.2827.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d550c81$1@forums-1-dub>
Date: 11 Feb 2011 02:16:33 -0800
X-Trace: forums-1-dub 1297419393 10.22.241.152 (11 Feb 2011 02:16:33 -0800)
X-Original-Trace: 11 Feb 2011 02:16:33 -0800, vip152.sybase.com
Lines: 75
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29956
Article PK: 79185


On 11-Feb-2011 00:16, Raj... wrote:
>> On 09-Feb-2011 05:14, Raj... wrote:
>>> When I tried to change the config option "allow updates"
>>> , It is giving me following warning message. Why is it
>>> so ? and How can I avoid it ?? My sybase version is
>>> ASE/12.5.3/EBF 12461 ESD#2/ and Operating System is
>> Windows.>
>>>
>>> Server 'Servername', Procedure 'sp_configure', Line 695:
>>> Warning: The file '$SYBASE\servername.001' has been
>>> overwritten. To prevent
>>> this rename, move, or delete old configuration files.
>>> See System Administration
>>> Guide for details.
>> The message is harmless. every time you change a setting
>> with sp_configure, a copy of the previous version of the
>> config file is made that ends in nnn which runs from 001
>> to 999. This is only a copy of the old config file, not
>> the config file itself, which ends in .cfg. These copies
>> are so that you can restore an earlier configuration,
>> should you have changed somethign that causes problems,
>> but you cannot remember what the change was.
>> You probably have done this more than 999 tmes now, and it
>> will then cycle arond and create a .001 file again.
>> Because it already existed, it mentions it overwrites it.
>> It's perhaps best to just clean up all those copies every
>> once in a while. Just run "rm<servername>.[0-9]??" in
>> the directory where the config file is located.
>>
>> HTH,
>>
>> Rob V.
>> ----------------------------------------------------------
>> ------- Rob Verschoor
>>
>> Certified Sybase Professional DBA for ASE
>> 15.0/12.5/12.0/11.5/11.0 and Replication Server
>> 15.0.1/12.5 // TeamSybase
>>
>> Author of Sybase books (order online at
>> www.sypron.nl/shop): "Tips, Tricks& Recipes for Sybase
>> ASE" (ASE 15 edition) "The Complete Sybase ASE Quick
>> Reference Guide" "The Complete Sybase Replication Server
>> Quick Reference Guide"
>>
>> rob@NO.SPAM.sypron.nl | www.sypron.nl | Twitter:
>> @rob_verschoor Sypron B.V., The Netherlands | Chamber of
>> Commerce 27138666
>> ----------------------------------------------------------
>> -------
>>
>
> Thanks Rob,
> It worked after clearing files in one server.
> But It didn't work in other server. I dont see any
> difference between both servers. But It didn't work in one.
>
> Any suggestions/comments ?
>
>
> Thanks,
> Raj..

Maybe the config files for that other server are in a different location
than you expect? This has nothing to do with the inside of an ASE server
(config settings etc), but only with the operational environment.
It's all about where those files actually exist, there's nothing else to
it. So you probalby still have a file name YOURSERVER.001 lying around,
maybe under a different $SYBASE -- just do a Unix 'find' and you'll see
where it is.
And as I said before, the message is totally harmless anyway.

HTH,

Rob V.


Bret Halford Posted on 2011-02-11 16:48:37.0Z
From: Bret Halford <bret@sybase.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: sp_configure
References: <4d524a98$1@forums-1-dub> <4d5471c0.2827.1681692777@sybase.com> <4d550c81$1@forums-1-dub>
In-Reply-To: <4d550c81$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d556865@forums-1-dub>
Date: 11 Feb 2011 08:48:37 -0800
X-Trace: forums-1-dub 1297442917 10.22.241.152 (11 Feb 2011 08:48:37 -0800)
X-Original-Trace: 11 Feb 2011 08:48:37 -0800, vip152.sybase.com
Lines: 21
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29957
Article PK: 79188


>
> Maybe the config files for that other server are in a different location
> than you expect? This has nothing to do with the inside of an ASE server
> (config settings etc), but only with the operational environment.
> It's all about where those files actually exist, there's nothing else to
> it. So you probalby still have a file name YOURSERVER.001 lying around,
> maybe under a different $SYBASE -- just do a Unix 'find' and you'll see
> where it is.
> And as I said before, the message is totally harmless anyway.
>
> HTH,
>
> Rob V.

I think there would have to be both YOURSERVER.999 and YOURSERVER.001
around - the .999 file to have the numbering
wrap around to .001, and an existing .001 to be overwritten,
prompting the warning. But I otherwise agree.

-bret