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.

db load problems

2 posts in Backup and Recovery Last posting was on 2001-04-17 06:43:07.0Z
Raghavendra Kulkarni Posted on 2001-04-16 05:57:49.0Z
From: "Raghavendra Kulkarni" <raghu@antispam.com>
Subject: db load problems
Date: Mon, 16 Apr 2001 11:27:49 +0530
Lines: 51
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Message-ID: <mKaHbRpxAHA.178@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.backup+recovery
NNTP-Posting-Host: 216.160.29.41
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:315
Article PK: 1060832

We are having a strange problem with ASE Sybase 12.0 load database process.

We have an installation of 12.0 on which our development db
"mpsdb_rch03_test" resides using the database devices "tds10" for
data(create size 200mb, allocated space 10mb) and "tds11" for log(create
size 1000mb, allocated space 100mb. We created a dump of this database
"041201.dmp"

We have another installation of Sybase on which we have tried to load
the above created dump. We created a db on the new installation (used
the same name as above) with similar database devices and tried loading
the dump created above. Initially we got an error that said could not
load the database as it was a 112mb database and needed more space. Upon
getting this message I increased the size of the data device(tds10) to
125mb and tried a reload again. This time it was successfull except
Sybase seemed to automatically create an additional entry for log device
using tds10 thereby splitting the log & data on ONE device. In fact we
even received a cautionary message to this effect at the end of the load
process saying it was a potential problem to have both data & log on one
device as a disk crash may render data recovery impossible.

After having successfully completed the load we now tried connecting our
application to this database. BTW when connecting through any SQL
clients we are able to see all the data etc. Conncecting through our
application gives us a strange problem. It immediately launches into
some frenetic disk activity which goes on for about 5 to 10 minutes at
times. At the end of which it comes up with an error message saying
that the transaction log is critically close to being full and to please
dump it before using the db. Dumping the tran log does not actually
help, cause the same process of disk activity and error messages are
repeated. On checking to see what was the size of tran log we observed
that of the originally allocated 100mb on tds11 it had used up about 90%
(close to 90mb) and hence was giving the error. We increased the
allocated size to 200mb and tried once more but came back with the same
results. This time the device seemed to be used up to again about 90% of
capacity or was 190mb full.

Our question is what is it that we are doing wrong? Are there any known
issues with the db dump and load processes? Any pointers would be
helpful currently. I will be posting this query on the Sybase db user
group forum as well.

And ofcourse our original installation continues to work just well with
no untoward increase of sizes of either the data or log devices.


Any hint will be highly appreciated.
Thanks.
Mircea


Anthony Mandic <amandic Posted on 2001-04-17 06:43:07.0Z
Date: Tue, 17 Apr 2001 16:43:07 +1000
From: Anthony Mandic <amandic@*t.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: db load problems
References: <mKaHbRpxAHA.178@forums.sybase.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <7xsHqxwxAHA.165@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.backup+recovery
Lines: 34
NNTP-Posting-Host: 210.9.51.46
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:311
Article PK: 1060826


Raghavendra Kulkarni wrote:

> We have an installation of 12.0 on which our development db
> "mpsdb_rch03_test" resides using the database devices "tds10" for
> data(create size 200mb, allocated space 10mb) and "tds11" for log(create
> size 1000mb, allocated space 100mb. We created a dump of this database
> "041201.dmp"
>
> We have another installation of Sybase on which we have tried to load
> the above created dump. We created a db on the new installation (used
> the same name as above) with similar database devices and tried loading
> the dump created above. Initially we got an error that said could not
> load the database as it was a 112mb database and needed more space.

Your database sizes and segment layouts need to match up. If you
created your copy database with the same or similar create database
statement (the allocated sizes and positions of data and log need
to match. The actual device names aren't consequential).

> Our question is what is it that we are doing wrong? Are there any known
> issues with the db dump and load processes? Any pointers would be
> helpful currently. I will be posting this query on the Sybase db user
> group forum as well.

I would check the EBF level of your sever version too. Get the latest
EBF and install it, if you haven't already done so.

-am © 2001