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.

Can I clean rs_systext and rs_exceptscmd manually?

3 posts in General Discussion Last posting was on 2012-03-22 02:13:16.0Z
Eisen Posted on 2012-03-21 07:35:07.0Z
Sender: 40a5.4f697fea.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Can I clean rs_systext and rs_exceptscmd manually?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f6984ab.41c9.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 20 Mar 2012 23:35:07 -0800
X-Trace: forums-1-dub 1332315307 172.20.134.41 (20 Mar 2012 23:35:07 -0800)
X-Original-Trace: 20 Mar 2012 23:35:07 -0800, 172.20.134.41
Lines: 19
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9187
Article PK: 870347

Dear all
Today when I checked the table size as usual, I found
rs_systext grows enormously. I'm curious why it grows so
fast. So I have a check. I found something weird --
1. in rs_systext, there's about 521235 rows with
texttype='C' but only 51 rows' parentid exists in
rs_exceptscmd's cmd_id, does it mean nearly all error
messages in rs_systext are useless?
2. in rs_exceptscmd, the table rowcount is 148147. But only
14 rows's sys_trans_id exists in rs_exceptshdr. does it mean
that the other 148134 rows are useless?
I'm thinking if these data are really useless, can I
purge them manually -- for I can't use rs_delexception to
clean them? And what would be impacted if I clean these two
tables -- rs_systext and rs_exceptscmd manually? Thanks in
advance for your help and advice.

Best Regards
Eisen


"Mark A. Parsons" <iron_horse Posted on 2012-03-22 00:02:26.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
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.rep-server
Subject: Re: Can I clean rs_systext and rs_exceptscmd manually?
References: <4f6984ab.41c9.1681692777@sybase.com>
In-Reply-To: <4f6984ab.41c9.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: <4f6a6c12$1@forums-1-dub>
Date: 21 Mar 2012 16:02:26 -0800
X-Trace: forums-1-dub 1332374546 10.22.241.152 (21 Mar 2012 16:02:26 -0800)
X-Original-Trace: 21 Mar 2012 16:02:26 -0800, vip152.sybase.com
Lines: 30
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9189
Article PK: 870352

rs_systext contains textual data pertaining to exceptions as well as function strings (and possibly some other items, too).

Net result is that you do *not* want to delete rs_systext values based solely on the (non)existence of a parentid in
rs_exceptscmd. If you delete the wrong entries from rs_systext you can find yourself with lots of problems (eg, DSIs
going down due to inability to locate the text for a function string).

I'd suggest you either a) use rs_delexception to cleanup rs_systext or b) take a look at the source code for
rs_delexception if you plan to write your own code to clear out old exceptions (eg, you have some large exceptions which
can't be deleted with rs_delexception because it fills your log).

On 03/21/2012 01:35, Eisen wrote:
> Dear all
> Today when I checked the table size as usual, I found
> rs_systext grows enormously. I'm curious why it grows so
> fast. So I have a check. I found something weird --
> 1. in rs_systext, there's about 521235 rows with
> texttype='C' but only 51 rows' parentid exists in
> rs_exceptscmd's cmd_id, does it mean nearly all error
> messages in rs_systext are useless?
> 2. in rs_exceptscmd, the table rowcount is 148147. But only
> 14 rows's sys_trans_id exists in rs_exceptshdr. does it mean
> that the other 148134 rows are useless?
> I'm thinking if these data are really useless, can I
> purge them manually -- for I can't use rs_delexception to
> clean them? And what would be impacted if I clean these two
> tables -- rs_systext and rs_exceptscmd manually? Thanks in
> advance for your help and advice.
>
> Best Regards
> Eisen


Eisen Posted on 2012-03-22 02:13:16.0Z
Sender: 4656.4f699f4b.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Re: Can I clean rs_systext and rs_exceptscmd manually?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f6a8abc.74fd.1681692777@sybase.com>
References: <4f6a6c12$1@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 21 Mar 2012 18:13:16 -0800
X-Trace: forums-1-dub 1332382396 172.20.134.41 (21 Mar 2012 18:13:16 -0800)
X-Original-Trace: 21 Mar 2012 18:13:16 -0800, 172.20.134.41
Lines: 49
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9191
Article PK: 870353

Hi Mark
Thanks a lot for your guidance. What I mean is -- since
the sys_trans_id is not found in rs_exceptshdr, so I can't
use rs_delexception to clean them in proper way. And I tried
to clean rs_exceptscmd and rs_systext manually 2 hours
before... It seems OK for I only cleaned the rows with
texttype='C' not touch on the 'S' and 'P' rows... Thanks
again for your help.

Best Regards
Eisen

> rs_systext contains textual data pertaining to exceptions
> as well as function strings (and possibly some other items
> , too).
>
> Net result is that you do *not* want to delete rs_systext
> values based solely on the (non)existence of a parentid in
> rs_exceptscmd. If you delete the wrong entries from
> rs_systext you can find yourself with lots of problems (eg
> , DSIs going down due to inability to locate the text for
> a function string).
>
> I'd suggest you either a) use rs_delexception to cleanup
> rs_systext or b) take a look at the source code for
> rs_delexception if you plan to write your own code to
> clear out old exceptions (eg, you have some large
> exceptions which can't be deleted with rs_delexception
> because it fills your log).
>
> On 03/21/2012 01:35, Eisen wrote:
> > Dear all
> > Today when I checked the table size as usual, I
> > found rs_systext grows enormously. I'm curious why it
> > grows so fast. So I have a check. I found something
> > weird -- 1. in rs_systext, there's about 521235 rows
> > with texttype='C' but only 51 rows' parentid exists in
> > rs_exceptscmd's cmd_id, does it mean nearly all error
> > messages in rs_systext are useless?
> > 2. in rs_exceptscmd, the table rowcount is 148147. But
> > only 14 rows's sys_trans_id exists in rs_exceptshdr.
> > does it mean that the other 148134 rows are useless?
> > I'm thinking if these data are really useless, can I
> > purge them manually -- for I can't use rs_delexception
> > to clean them? And what would be impacted if I clean
> > these two tables -- rs_systext and rs_exceptscmd
> > manually? Thanks in advance for your help and advice.
> >
> > Best Regards
> > Eisen