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.

Dump database bug ?

3 posts in General Discussion Last posting was on 2009-12-16 16:38:13.0Z
Kaboum Posted on 2009-12-03 15:54:07.0Z
From: Kaboum <yvesmiron@gmail.com>
Newsgroups: sybase.public.ase.general
Subject: Dump database bug ?
Date: Thu, 3 Dec 2009 07:54:07 -0800 (PST)
Organization: http://groups.google.com
Lines: 23
Message-ID: <79eb235b-c209-4cb0-8399-c0070dc64b61@t18g2000vbj.googlegroups.com>
NNTP-Posting-Host: 64.86.141.133
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1259855647 27912 127.0.0.1 (3 Dec 2009 15:54:07 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 3 Dec 2009 15:54:07 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: t18g2000vbj.googlegroups.com; posting-host=64.86.141.133; posting-account=wFnfIwoAAAA77vcHGM_rC3YQpeOEmq8U
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; MS-RTC LM 8),gzip(gfe),gzip(gfe)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!border2.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!t18g2000vbj.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28731
Article PK: 77973

Hi,

Strange behaviour with dump database:

Version: Adaptive Server Enterprise/12.5.4/EBF 16830 ESD#9.1/P/Solaris
AMD64/OS 5.10/ase1254/2146/64-bit/OPT/Wed Apr 15 03:53:45 2009

Option on the database: select into/bulk, truncate log on ckeckpoint

We start a dump database and after a while it freeze (seems to be at
the logsegment level after backing up all data). This happens when we
have another process modifying data in the same database which become
lock be the dump database. At that point they only way to unlock is to
kill the dump.

Anyone ever had that problem ?
We have the same version of sybase on sun sparc and we never had that
problem. Is is the version of sybase for the Solaris AMD64 that cause
the problem ?

Thanks

dump and the process


Manish Negandhi [TeamSybase] Posted on 2009-12-04 08:08:43.0Z
From: "Manish Negandhi [TeamSybase]" <negandhi.manish@gmail.com>
Newsgroups: sybase.public.ase.general
Subject: Re: Dump database bug ?
Date: Fri, 4 Dec 2009 00:08:43 -0800 (PST)
Organization: http://groups.google.com
Lines: 37
Message-ID: <cc6a2d24-a624-4997-88b8-64536071c8b6@d21g2000yqn.googlegroups.com>
References: <79eb235b-c209-4cb0-8399-c0070dc64b61@t18g2000vbj.googlegroups.com>
NNTP-Posting-Host: 122.248.163.1
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1259914123 12919 127.0.0.1 (4 Dec 2009 08:08:43 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 4 Dec 2009 08:08:43 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: d21g2000yqn.googlegroups.com; posting-host=122.248.163.1; posting-account=bEJXAgoAAAAk-iP4Op4pmmZHkhOwCifj
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648),gzip(gfe),gzip(gfe)
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!border2.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!d21g2000yqn.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28732
Article PK: 77974


On Dec 3, 8:54 pm, Kaboum <yvesmi...@gmail.com> wrote:
> Hi,
>
> Strange behaviour with dump database:
>
> Version: Adaptive Server Enterprise/12.5.4/EBF 16830 ESD#9.1/P/Solaris
> AMD64/OS 5.10/ase1254/2146/64-bit/OPT/Wed Apr 15 03:53:45 2009
>
> Option on the database: select into/bulk, truncate log on ckeckpoint
>
> We start a dump database and after a while it freeze (seems to be at
> the logsegment level after backing up all data). This happens when we
> have another process modifying data in the same database which become
> lock be the dump database. At that point they only way to unlock is to
> kill the dump.
>
> Anyone ever had that problem ?
> We have the same version of sybase on sun sparc and we never had that
> problem. Is is the version of sybase for the Solaris AMD64 that cause
> the problem ?
>
> Thanks
>
>  dump and the process

Possibly , your dump process itself my be locked ? if you can provide
some more details about the problem it will be easier to drill down
further..
-check if value of physical_io column of the sysprocess table is
moving for backup process
-check if your file system has enough space to accomodate dump
-post the output blocked processes from master..sysprocesses
-check for any errors in backupserver / ASE server log

-HTH
Manish Negandhi
[TeamSybase]


Kaboum Posted on 2009-12-16 16:38:13.0Z
From: Kaboum <yvesmiron@gmail.com>
Newsgroups: sybase.public.ase.general
Subject: Re: Dump database bug ?
Date: Wed, 16 Dec 2009 08:38:13 -0800 (PST)
Organization: http://groups.google.com
Lines: 64
Message-ID: <8ede89e6-5afe-470f-ae99-60b4f0efd9ee@z7g2000vbl.googlegroups.com>
References: <79eb235b-c209-4cb0-8399-c0070dc64b61@t18g2000vbj.googlegroups.com> <cc6a2d24-a624-4997-88b8-64536071c8b6@d21g2000yqn.googlegroups.com>
NNTP-Posting-Host: 64.86.141.133
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1260981494 18378 127.0.0.1 (16 Dec 2009 16:38:14 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 16 Dec 2009 16:38:14 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: z7g2000vbl.googlegroups.com; posting-host=64.86.141.133; posting-account=wFnfIwoAAAA77vcHGM_rC3YQpeOEmq8U
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; MS-RTC LM 8),gzip(gfe),gzip(gfe)
X-Original-Bytes: 3572
Path: forums-1-dub!forums-master!newssvr.sybase.com!news-sj-1.sprintlink.net!news-peer1.sprintlink.net!nntp1.phx1.gblx.net!nntp.gblx.net!nntp.gblx.net!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!z7g2000vbl.googlegroups.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28776
Article PK: 78018

On Dec 4, 3:08 am, "Manish Negandhi [TeamSybase]"

<negandhi.man...@gmail.com> wrote:
> On Dec 3, 8:54 pm, Kaboum <yvesmi...@gmail.com> wrote:
>
>
>
>
>
> > Hi,
>
> > Strange behaviour with dump database:
>
> > Version: Adaptive Server Enterprise/12.5.4/EBF 16830 ESD#9.1/P/Solaris
> > AMD64/OS 5.10/ase1254/2146/64-bit/OPT/Wed Apr 15 03:53:45 2009
>
> > Option on the database: select into/bulk, truncate log on ckeckpoint
>
> > We start a dump database and after a while it freeze (seems to be at
> > the logsegment level after backing up all data). This happens when we
> > have another process modifying data in the same database which become
> > lock be the dump database. At that point they only way to unlock is to
> > kill the dump.
>
> > Anyone ever had that problem ?
> > We have the same version of sybase on sun sparc and we never had that
> > problem. Is is the version of sybase for the Solaris AMD64 that cause
> > the problem ?
>
> > Thanks
>
> >  dump and the process
>
> Possibly , your dump process itself my be locked ?  if you can provide
> some more details about the problem  it will be easier to drill down
> further..
> -check if value of physical_io column of the sysprocess table is
> moving for backup process
> -check if your file system has enough space to accomodate dump
> -post the output blocked processes from master..sysprocesses
> -check for any errors in backupserver / ASE server log
>
> -HTH
> Manish Negandhi
> [TeamSybase]- Hide quoted text -
>
> - Show quoted text -

Thank you for your response Manish, much appreciated.
We try to reproduce the problem but could'nt yet. Still trying and we
will keep you posted.
But what we realized is that there was a process that was recreating a
index on a big table which
was lock by the dump. As for the dump, nothing was moving, no i/o, no
erreors from backup server log
and the dump was about 2/3 done.
When we did our test, the process that was recreating the index was
lock but only for a few seconds once in a while.
the dump did succeed and the index was recreated.

We will try on the original environnement when available and we'll
keep you inform.

Thank you again and
Have a nice day