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.

workspace hangs on save stored procs

6 posts in General Discussion Last posting was on 2008-03-13 16:50:30.0Z
Gareth Davies Posted on 2008-03-12 19:47:01.0Z
From: Gareth Davies <gruff@sitemaker.cc>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
Subject: workspace hangs on save stored procs
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: <47d83335$1@forums-1-dub>
Date: 12 Mar 2008 11:47:01 -0800
X-Trace: forums-1-dub 1205351221 10.22.241.152 (12 Mar 2008 11:47:01 -0800)
X-Original-Trace: 12 Mar 2008 11:47:01 -0800, vip152.sybase.com
Lines: 15
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:623
Article PK: 1088305

My Workspace (2.01 with ASE 12.5.2) has just started hanging when I try
to save changes to stored procs.

I did sp_who and one of the sybase spids is sleeping with cmd = "LOG
SUSPEND".

I have no problem dropping and recreating stored procs using SQL
Advantage. As far as I can tell there's no problem with the transaction
log. (I've tried dumping it with no_log anyway, makes no difference)

Any ideas what's going on?

Thanks

Gareth


Samir Nigam Posted on 2008-03-12 21:16:51.0Z
From: "Samir Nigam" <samir_dot_nigam@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47d83335$1@forums-1-dub>
Subject: Re: workspace hangs on save stored procs
Lines: 37
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47d84843$1@forums-1-dub>
Date: 12 Mar 2008 13:16:51 -0800
X-Trace: forums-1-dub 1205356611 10.22.241.152 (12 Mar 2008 13:16:51 -0800)
X-Original-Trace: 12 Mar 2008 13:16:51 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:625
Article PK: 1088301

Gareth,

Few questions..

Are you seeing this problem with specific stored procedure or any stored
procedure (a simple one created from scratch). We do have some extra code
around the saving stored procedure changes. You can preview that code when
you save the stored procedure, save it in a sql file, and run it outside of
WorkSpace. Does that also hang?

I have limited knowledge of ASE, but curious if somehow one of the logs used
during the stored procedure compilation and save, could be getting filled
up. Have you checked if some other log (other than your db transaction log)
is near capacity and therefore running into this problem.

Regards,
Samir

"Gareth Davies" <gruff@sitemaker.cc> wrote in message
news:47d83335$1@forums-1-dub...
> My Workspace (2.01 with ASE 12.5.2) has just started hanging when I try to
> save changes to stored procs.
>
> I did sp_who and one of the sybase spids is sleeping with cmd = "LOG
> SUSPEND".
>
> I have no problem dropping and recreating stored procs using SQL
> Advantage. As far as I can tell there's no problem with the transaction
> log. (I've tried dumping it with no_log anyway, makes no difference)
>
> Any ideas what's going on?
>
> Thanks
>
> Gareth


Gareth Davies Posted on 2008-03-13 10:31:30.0Z
From: Gareth Davies <gruff@sitemaker.cc>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
Subject: Re: workspace hangs on save stored procs
References: <47d83335$1@forums-1-dub> <47d84843$1@forums-1-dub>
In-Reply-To: <47d84843$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: <47d90282$1@forums-1-dub>
Date: 13 Mar 2008 02:31:30 -0800
X-Trace: forums-1-dub 1205404290 10.22.241.152 (13 Mar 2008 02:31:30 -0800)
X-Original-Trace: 13 Mar 2008 02:31:30 -0800, vip152.sybase.com
Lines: 53
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:627
Article PK: 1088339

Thanks. It was hanging immediately I click the save button.

I discovered it was the master database's transaction log that was full.
I cleared it and everything unfroze.

We don't normally dump the transaction on the master DB as it's not
normally necessary. Perhaps it needs setting to automatically do this
when full? Your advice appreciated.

Regards

Gareth

Samir Nigam wrote:
> Gareth,
>
> Few questions..
>
> Are you seeing this problem with specific stored procedure or any stored
> procedure (a simple one created from scratch). We do have some extra code
> around the saving stored procedure changes. You can preview that code when
> you save the stored procedure, save it in a sql file, and run it outside of
> WorkSpace. Does that also hang?
>
> I have limited knowledge of ASE, but curious if somehow one of the logs used
> during the stored procedure compilation and save, could be getting filled
> up. Have you checked if some other log (other than your db transaction log)
> is near capacity and therefore running into this problem.
>
> Regards,
> Samir
>
> "Gareth Davies" <gruff@sitemaker.cc> wrote in message
> news:47d83335$1@forums-1-dub...
>> My Workspace (2.01 with ASE 12.5.2) has just started hanging when I try to
>> save changes to stored procs.
>>
>> I did sp_who and one of the sybase spids is sleeping with cmd = "LOG
>> SUSPEND".
>>
>> I have no problem dropping and recreating stored procs using SQL
>> Advantage. As far as I can tell there's no problem with the transaction
>> log. (I've tried dumping it with no_log anyway, makes no difference)
>>
>> Any ideas what's going on?
>>
>> Thanks
>>
>> Gareth
>
>


Samir Nigam Posted on 2008-03-13 16:42:55.0Z
From: "Samir Nigam" <samir_dot_nigam@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47d83335$1@forums-1-dub> <47d84843$1@forums-1-dub> <47d90282$1@forums-1-dub>
Subject: Re: workspace hangs on save stored procs
Lines: 66
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47d9598f$1@forums-1-dub>
Date: 13 Mar 2008 08:42:55 -0800
X-Trace: forums-1-dub 1205426575 10.22.241.152 (13 Mar 2008 08:42:55 -0800)
X-Original-Trace: 13 Mar 2008 08:42:55 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:629
Article PK: 1088303

Great to hear that you found the problem.

I am probably not the best person to advise on the database transaction log
dump or truncate. If you don't mind, please post your question to
sybase.public.ase.general newsgroup. ASE experts monitor that newsgroup and
would be able to give you solid suggestions.

Regards,
Samir

"Gareth Davies" <gruff@sitemaker.cc> wrote in message
news:47d90282$1@forums-1-dub...
> Thanks. It was hanging immediately I click the save button.
>
> I discovered it was the master database's transaction log that was full. I
> cleared it and everything unfroze.
>
> We don't normally dump the transaction on the master DB as it's not
> normally necessary. Perhaps it needs setting to automatically do this
> when full? Your advice appreciated.
>
> Regards
>
> Gareth
>
>
>
> Samir Nigam wrote:
>> Gareth,
>>
>> Few questions..
>>
>> Are you seeing this problem with specific stored procedure or any stored
>> procedure (a simple one created from scratch). We do have some extra code
>> around the saving stored procedure changes. You can preview that code
>> when you save the stored procedure, save it in a sql file, and run it
>> outside of WorkSpace. Does that also hang?
>>
>> I have limited knowledge of ASE, but curious if somehow one of the logs
>> used during the stored procedure compilation and save, could be getting
>> filled up. Have you checked if some other log (other than your db
>> transaction log) is near capacity and therefore running into this
>> problem.
>>
>> Regards,
>> Samir
>>
>> "Gareth Davies" <gruff@sitemaker.cc> wrote in message
>> news:47d83335$1@forums-1-dub...
>>> My Workspace (2.01 with ASE 12.5.2) has just started hanging when I try
>>> to save changes to stored procs.
>>>
>>> I did sp_who and one of the sybase spids is sleeping with cmd = "LOG
>>> SUSPEND".
>>>
>>> I have no problem dropping and recreating stored procs using SQL
>>> Advantage. As far as I can tell there's no problem with the transaction
>>> log. (I've tried dumping it with no_log anyway, makes no difference)
>>>
>>> Any ideas what's going on?
>>>
>>> Thanks
>>>
>>> Gareth
>>


Gareth Davies Posted on 2008-03-13 10:52:04.0Z
From: Gareth Davies <gruff@sitemaker.cc>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
Subject: Re: workspace hangs on save stored procs
References: <47d83335$1@forums-1-dub> <47d84843$1@forums-1-dub> <47d90282$1@forums-1-dub>
In-Reply-To: <47d90282$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: <47d90754@forums-1-dub>
Date: 13 Mar 2008 02:52:04 -0800
X-Trace: forums-1-dub 1205405524 10.22.241.152 (13 Mar 2008 02:52:04 -0800)
X-Original-Trace: 13 Mar 2008 02:52:04 -0800, vip152.sybase.com
Lines: 153
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:628
Article PK: 1088336

It happened again within a few more saves. Looks like my master DB
needs entending to cope. This is it currently:

name db_size owner dbid
created status

---- ------- -----
----------- ------- ------

master 6.0 MB sa
1 Jan 11, 2007 mixed log and data


device_fragments size usage
created free kbytes
---------------- ---- -----
------- -----------
master 6.0 MB data and log Jan 11
2007 3:48PM 910

device segment














------ -------














master default














master logsegment














master system

Gareth Davies wrote:
> Thanks. It was hanging immediately I click the save button.
>
> I discovered it was the master database's transaction log that was full.
> I cleared it and everything unfroze.
>
> We don't normally dump the transaction on the master DB as it's not
> normally necessary. Perhaps it needs setting to automatically do this
> when full? Your advice appreciated.
>
> Regards
>
> Gareth
>
>
>
> Samir Nigam wrote:
>> Gareth,
>>
>> Few questions..
>>
>> Are you seeing this problem with specific stored procedure or any
>> stored procedure (a simple one created from scratch). We do have some
>> extra code around the saving stored procedure changes. You can preview
>> that code when you save the stored procedure, save it in a sql file,
>> and run it outside of WorkSpace. Does that also hang?
>>
>> I have limited knowledge of ASE, but curious if somehow one of the
>> logs used during the stored procedure compilation and save, could be
>> getting filled up. Have you checked if some other log (other than your
>> db transaction log) is near capacity and therefore running into this
>> problem.
>>
>> Regards,
>> Samir
>>
>> "Gareth Davies" <gruff@sitemaker.cc> wrote in message
>> news:47d83335$1@forums-1-dub...
>>> My Workspace (2.01 with ASE 12.5.2) has just started hanging when I
>>> try to save changes to stored procs.
>>>
>>> I did sp_who and one of the sybase spids is sleeping with cmd = "LOG
>>> SUSPEND".
>>>
>>> I have no problem dropping and recreating stored procs using SQL
>>> Advantage. As far as I can tell there's no problem with the
>>> transaction log. (I've tried dumping it with no_log anyway, makes no
>>> difference)
>>>
>>> Any ideas what's going on?
>>>
>>> Thanks
>>>
>>> Gareth
>>
>>


Samir Nigam Posted on 2008-03-13 16:50:30.0Z
From: "Samir Nigam" <samir_dot_nigam@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <47d83335$1@forums-1-dub> <47d84843$1@forums-1-dub> <47d90282$1@forums-1-dub> <47d90754@forums-1-dub>
Subject: Re: workspace hangs on save stored procs
Lines: 158
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47d95b56$1@forums-1-dub>
Date: 13 Mar 2008 08:50:30 -0800
X-Trace: forums-1-dub 1205427030 10.22.241.152 (13 Mar 2008 08:50:30 -0800)
X-Original-Trace: 13 Mar 2008 08:50:30 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:630
Article PK: 1088307

Yes, looks like your master db is too small (probably the default
configuration) and increasing master db size would help resolve the problem.
You can do that from Sybase Central or use "alter database" command.

Regards,
Samir

"Gareth Davies" <gruff@sitemaker.cc> wrote in message
news:47d90754@forums-1-dub...
> It happened again within a few more saves. Looks like my master DB needs
> entending to cope. This is it currently:
>
> name db_size owner dbid
> created status
> ---- ------- -----
> ----------- ------- ------
>
> master 6.0 MB sa 1 Jan 11, 2007 mixed log and
> data
>
> device_fragments size usage created
> free kbytes
> ---------------- ---- -----
> ------- -----------
> master 6.0 MB data and log Jan 11
> 2007 3:48PM 910
>
> device segment
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------ -------
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> master default
>
>
>
>
>
>
>
>
>
>
>
>
>
> master logsegment
>
>
>
>
>
>
>
>
>
>
>
>
>
> master system
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Gareth Davies wrote:
>> Thanks. It was hanging immediately I click the save button.
>>
>> I discovered it was the master database's transaction log that was full.
>> I cleared it and everything unfroze.
>>
>> We don't normally dump the transaction on the master DB as it's not
>> normally necessary. Perhaps it needs setting to automatically do this
>> when full? Your advice appreciated.
>>
>> Regards
>>
>> Gareth
>>
>>
>>
>> Samir Nigam wrote:
>>> Gareth,
>>>
>>> Few questions..
>>>
>>> Are you seeing this problem with specific stored procedure or any stored
>>> procedure (a simple one created from scratch). We do have some extra
>>> code around the saving stored procedure changes. You can preview that
>>> code when you save the stored procedure, save it in a sql file, and run
>>> it outside of WorkSpace. Does that also hang?
>>>
>>> I have limited knowledge of ASE, but curious if somehow one of the logs
>>> used during the stored procedure compilation and save, could be getting
>>> filled up. Have you checked if some other log (other than your db
>>> transaction log) is near capacity and therefore running into this
>>> problem.
>>>
>>> Regards,
>>> Samir
>>>
>>> "Gareth Davies" <gruff@sitemaker.cc> wrote in message
>>> news:47d83335$1@forums-1-dub...
>>>> My Workspace (2.01 with ASE 12.5.2) has just started hanging when I try
>>>> to save changes to stored procs.
>>>>
>>>> I did sp_who and one of the sybase spids is sleeping with cmd = "LOG
>>>> SUSPEND".
>>>>
>>>> I have no problem dropping and recreating stored procs using SQL
>>>> Advantage. As far as I can tell there's no problem with the
>>>> transaction log. (I've tried dumping it with no_log anyway, makes no
>>>> difference)
>>>>
>>>> Any ideas what's going on?
>>>>
>>>> Thanks
>>>>
>>>> Gareth
>>>
>>>