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.

Issue while upgrading RS from 12.6 to 15.6 - Fixed

2 posts in General Discussion Last posting was on 2011-10-03 08:36:07.0Z
Jayadeva Posted on 2011-10-01 08:07:57.0Z
Sender: 5c73.4e86c94e.1804289383@sybase.com
From: Jayadeva
Newsgroups: sybase.public.rep-server
Subject: Issue while upgrading RS from 12.6 to 15.6 - Fixed
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4e86ca5d.5caa.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 1 Oct 2011 01:07:57 -0700
X-Trace: forums-1-dub 1317456477 10.22.241.41 (1 Oct 2011 01:07:57 -0700)
X-Original-Trace: 1 Oct 2011 01:07:57 -0700, 10.22.241.41
Lines: 66
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9070
Article PK: 870234

Below issue notice while upgrading replication server 12.6
to 15.6

Error msg while upgrading
Warning: Changing an object or column name could break
existing stored procedur
es, cached statements or other compiled objects.
...SQL Server message: msg 249, level 16, state 1

WARNING: "Syntax error during explicit conversion of VARCHAR
value '500M' to a
INT field.
"
Press <return> to continue.


In error Log
E. 2011/10/01 15:40:47. ERROR #36 GLOBAL RS(GLOBAL RS) -
cnvrsion.c(323)
String '500M', at line 3680 in file
'eneric/cfg/cfginit.c', could not be converted to a long.

Issue noticed
Reason 1:
1> select * from rs_config where charvalue='500M'
2> go
optionname objid charvalue

status comments
------------------------------
------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
memory_limit 0x0000000000000000 500M
0
max memory that will be allocated, in megabytes

Reason 2:
1> rs_configure 'memory_limit'
2> go

Config Name Config Value Run Value
-------------------------- ----------------------
--------------------------
memory_limit 500M 500M
Description

----------------------------------------------------------------------
max memory that will be allocated, in megabytes

Fixed by increasing the memory
1> rs_configure 'memory_limit'
2> go

Config Name Config Value Run Value
-------------------------- ----------------------
--------------------------
memory_limit 2047 500M
Description

----------------------------------------------------------------------
max memory that will be allocated, in megabytes

Later restarted the replication server by editing the old
runfile of 12.6.


Luc Van der Veurst Posted on 2011-10-03 08:36:07.0Z
From: "Luc Van der Veurst" <dba_azvub@hotmail.com>
Newsgroups: sybase.public.rep-server
References: <4e86ca5d.5caa.1681692777@sybase.com>
Subject: Re: Issue while upgrading RS from 12.6 to 15.6 - Fixed
Lines: 110
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-Forwarded: by - (DeleGate/5.8.7)
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e8973f7$1@forums-1-dub>
Date: 3 Oct 2011 01:36:07 -0700
X-Trace: forums-1-dub 1317630967 10.22.241.152 (3 Oct 2011 01:36:07 -0700)
X-Original-Trace: 3 Oct 2011 01:36:07 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9071
Article PK: 870235

The memory_limit value should have been specified as '500', not '500M'.

I don't have a 12.6 repserver anymore, so I could only see what
happens on 15.2/15.6.

The deprecated procedure rs_configure accepts '500M' as value for
memory limit, but the repserver command doesn't :

On a 15.6 system :

1> configure replication server set memory_limit to '2100M';
Msg 15198, Level 12, State 0
Server 'RSP_CODA_c'
Invalid config option value: '2100M'.

On a 15.2 system :

1> configure replication server set memory_limit to '1000M';
Msg 36, Level 12, State 0
Server 'RSP_MT_1_b'
String '1000M', at line 1560 in file 'eneric/ddl/ddlmisc.c', could not be
converted to a long.

sp_configure 'memory_limit', '1000M'

does not give an error, but since the option requires a reboot, it's most
likely
that the server will report an error when rebooted.

However, the correct syntax is :

sp_configure 'memory_limit', '1000'

12.6 could deal with the extra M, 15.x can't.

If you correct the value of memory_limit, my guess is that the upgrade will
succeed afterwards (at least the memory problem should been solved).

hth,
Luc.

<Jayadeva> wrote in message news:4e86ca5d.5caa.1681692777@sybase.com...
> Below issue notice while upgrading replication server 12.6
> to 15.6
>
> Error msg while upgrading
> Warning: Changing an object or column name could break
> existing stored procedur
> es, cached statements or other compiled objects.
> ...SQL Server message: msg 249, level 16, state 1
>
> WARNING: "Syntax error during explicit conversion of VARCHAR
> value '500M' to a
> INT field.
> "
> Press <return> to continue.
>
>
> In error Log
> E. 2011/10/01 15:40:47. ERROR #36 GLOBAL RS(GLOBAL RS) -
> cnvrsion.c(323)
> String '500M', at line 3680 in file
> 'eneric/cfg/cfginit.c', could not be converted to a long.
>
> Issue noticed
> Reason 1:
> 1> select * from rs_config where charvalue='500M'
> 2> go
> optionname objid charvalue
>
> status comments
> ------------------------------
> ------------------
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ------
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> memory_limit 0x0000000000000000 500M
> 0
> max memory that will be allocated, in megabytes
>
> Reason 2:
> 1> rs_configure 'memory_limit'
> 2> go
>
> Config Name Config Value Run Value
> -------------------------- ----------------------
> --------------------------
> memory_limit 500M 500M
> Description
>
> ----------------------------------------------------------------------
> max memory that will be allocated, in megabytes
>
> Fixed by increasing the memory
> 1> rs_configure 'memory_limit'
> 2> go
>
> Config Name Config Value Run Value
> -------------------------- ----------------------
> --------------------------
> memory_limit 2047 500M
> Description
>
> ----------------------------------------------------------------------
> max memory that will be allocated, in megabytes
>
> Later restarted the replication server by editing the old
> runfile of 12.6.