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.

dbbackup fails - suspect

10 posts in General Discussion Last posting was on 2008-02-01 19:34:19.0Z
Michele Hardy Posted on 2008-01-28 17:01:51.0Z
Sender: 116f.479e0857.1804289383@sybase.com
From: Michele Hardy
Newsgroups: ianywhere.public.general
Subject: dbbackup fails - suspect
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <479e0a7f.11a1.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 28 Jan 2008 09:01:51 -0800
X-Trace: forums-1-dub 1201539711 10.22.241.41 (28 Jan 2008 09:01:51 -0800)
X-Original-Trace: 28 Jan 2008 09:01:51 -0800, 10.22.241.41
Lines: 22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6697
Article PK: 4949

We are unable to make a backup copy of one of our databases.
This was done nightly via a cron job which essentially
creates a script with the following lines:

BACKUP DATABASE
DIRECTORY '/mnt/XXXXX/backup';
QUIT;

which it passes as a script to dbisqlc

This started failing, with no real indication as to why.
Based on the timing of things, we believe the issue is
related to a temporary database space that no longer exists.
Essentially, a temporary database space, workspace.db, was
created via a script that terminated and did not remove the
space. Sometime later, the actual disk file workspace.db was
removed and we have no backup of it. There was no valuable
data in it, so that's not the issue. The issue is we can't
backup the database because workspace.db no longer exists.

So my question is, how do we get the database to no longer
reference the temporary space, workspace.db?


"Nick Elson" < Posted on 2008-01-28 17:33:45.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <479e0a7f.11a1.1681692777@sybase.com>
Subject: Re: dbbackup fails - suspect
Lines: 37
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <479e11f9$1@forums-1-dub>
Date: 28 Jan 2008 09:33:45 -0800
X-Trace: forums-1-dub 1201541625 10.22.241.152 (28 Jan 2008 09:33:45 -0800)
X-Original-Trace: 28 Jan 2008 09:33:45 -0800, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6698
Article PK: 4946

You use of temporary database is a bit confusing.

Was workspace.db a seperate database?
Or a dbspace (and if so was it part of the database
you are trying to backup)?

Also... What indications do you have that this
file is the source of your backup woes?

You may also want to spell out exactly how
you removed the file 'workspace.db'.

<Michele Hardy> wrote in message news:479e0a7f.11a1.1681692777@sybase.com...
> We are unable to make a backup copy of one of our databases.
> This was done nightly via a cron job which essentially
> creates a script with the following lines:
>
> BACKUP DATABASE
> DIRECTORY '/mnt/XXXXX/backup';
> QUIT;
>
> which it passes as a script to dbisqlc
>
> This started failing, with no real indication as to why.
> Based on the timing of things, we believe the issue is
> related to a temporary database space that no longer exists.
> Essentially, a temporary database space, workspace.db, was
> created via a script that terminated and did not remove the
> space. Sometime later, the actual disk file workspace.db was
> removed and we have no backup of it. There was no valuable
> data in it, so that's not the issue. The issue is we can't
> backup the database because workspace.db no longer exists.
>
> So my question is, how do we get the database to no longer
> reference the temporary space, workspace.db?


Michele Posted on 2008-01-29 21:32:52.0Z
Sender: 2c95.479f6479.1804289383@sybase.com
From: Michele
Newsgroups: ianywhere.public.general
Subject: Re: dbbackup fails - suspect missing dbspace is the issue
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <479f9b84.31d6.1681692777@sybase.com>
References: <479e11f9$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 29 Jan 2008 13:32:52 -0800
X-Trace: forums-1-dub 1201642372 10.22.241.41 (29 Jan 2008 13:32:52 -0800)
X-Original-Trace: 29 Jan 2008 13:32:52 -0800, 10.22.241.41
Lines: 72
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6700
Article PK: 4948

As part of attempting a large unload of data, a temporary
dbspace was created to hold a temporary table that
identified which data to unload. (It's a long story...) This
was the command used to create it:

CREATE DBSPACE workspace AS '$HOME/dbspace/workspace.db'

Sometime later, the workspace.db file was inadvertenly
removed via the rm command. Ever since then, the backup will
not work. Whenever the backup runs, it fails immediately,
with the following error:

Error in file "/home/livedb/bin/dss2nfsbackup.sql" at line 3
Database backup not started

Executing command:
% BACKUP DATABASE
% DIRECTORY '/mnt/red1data/backup_dss2';
*** ERROR *** Error in file
"/home/livedb/bin/dss2nfsbackup.sql" at line 3
*** ERROR *** Database backup not started
% // Error: Error in file
"/home/livedb/bin/dss2nfsbackup.sql" at line 3
// Database backup not started
//
% // ( /home/livedb/bin/dss2nfsbackup.sql )

Also, anytime the database is started, we see an error in
/var/log/messages as follows:

SQLAnywhere(dss2): Cannot open dbspace 'workspace' from file
'/home/livedb/dbspace/workspace.db'

> You use of temporary database is a bit confusing.
>
> Was workspace.db a seperate database?
> Or a dbspace (and if so was it part of the database
> you are trying to backup)?
>
> Also... What indications do you have that this
> file is the source of your backup woes?
>
> You may also want to spell out exactly how
> you removed the file 'workspace.db'.
>
> <Michele Hardy> wrote in message
> > news:479e0a7f.11a1.1681692777@sybase.com... We are
> > unable to make a backup copy of one of our databases.
> > This was done nightly via a cron job which essentially
> creates a script with the following lines: >
> > BACKUP DATABASE
> > DIRECTORY '/mnt/XXXXX/backup';
> > QUIT;
> >
> > which it passes as a script to dbisqlc
> >
> > This started failing, with no real indication as to why.
> > Based on the timing of things, we believe the issue is
> > related to a temporary database space that no longer
> > exists. Essentially, a temporary database space,
> > workspace.db, was created via a script that terminated
> > and did not remove the space. Sometime later, the actual
> > disk file workspace.db was removed and we have no backup
> > of it. There was no valuable data in it, so that's not
> > the issue. The issue is we can't backup the database
> because workspace.db no longer exists. >
> > So my question is, how do we get the database to no
> > longer reference the temporary space, workspace.db?
>
>


"Nick Elson" < Posted on 2008-01-29 22:01:05.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <479e11f9$1@forums-1-dub> <479f9b84.31d6.1681692777@sybase.com>
Subject: Re: dbbackup fails - suspect missing dbspace is the issue
Lines: 87
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <479fa221$1@forums-1-dub>
Date: 29 Jan 2008 14:01:05 -0800
X-Trace: forums-1-dub 1201644065 10.22.241.152 (29 Jan 2008 14:01:05 -0800)
X-Original-Trace: 29 Jan 2008 14:01:05 -0800, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6701
Article PK: 4950

I would try dropping that dbspace if you can.
The SQL should be this simple

drop dbspace workspace;

With recent Sybase Central versions you can graphically just
delete that from the dbspaces treeview.

Let me know if that fails and what error you are seeing ....

<Michele> wrote in message news:479f9b84.31d6.1681692777@sybase.com...
> As part of attempting a large unload of data, a temporary
> dbspace was created to hold a temporary table that
> identified which data to unload. (It's a long story...) This
> was the command used to create it:
>
> CREATE DBSPACE workspace AS '$HOME/dbspace/workspace.db'
>
> Sometime later, the workspace.db file was inadvertenly
> removed via the rm command. Ever since then, the backup will
> not work. Whenever the backup runs, it fails immediately,
> with the following error:
>
> Error in file "/home/livedb/bin/dss2nfsbackup.sql" at line 3
> Database backup not started
>
> Executing command:
> % BACKUP DATABASE
> % DIRECTORY '/mnt/red1data/backup_dss2';
> *** ERROR *** Error in file
> "/home/livedb/bin/dss2nfsbackup.sql" at line 3
> *** ERROR *** Database backup not started
> % // Error: Error in file
> "/home/livedb/bin/dss2nfsbackup.sql" at line 3
> // Database backup not started
> //
> % // ( /home/livedb/bin/dss2nfsbackup.sql )
>
> Also, anytime the database is started, we see an error in
> /var/log/messages as follows:
>
> SQLAnywhere(dss2): Cannot open dbspace 'workspace' from file
> '/home/livedb/dbspace/workspace.db'
>
>
>
>> You use of temporary database is a bit confusing.
>>
>> Was workspace.db a seperate database?
>> Or a dbspace (and if so was it part of the database
>> you are trying to backup)?
>>
>> Also... What indications do you have that this
>> file is the source of your backup woes?
>>
>> You may also want to spell out exactly how
>> you removed the file 'workspace.db'.
>>
>> <Michele Hardy> wrote in message
>> > news:479e0a7f.11a1.1681692777@sybase.com... We are
>> > unable to make a backup copy of one of our databases.
>> > This was done nightly via a cron job which essentially
>> creates a script with the following lines: >
>> > BACKUP DATABASE
>> > DIRECTORY '/mnt/XXXXX/backup';
>> > QUIT;
>> >
>> > which it passes as a script to dbisqlc
>> >
>> > This started failing, with no real indication as to why.
>> > Based on the timing of things, we believe the issue is
>> > related to a temporary database space that no longer
>> > exists. Essentially, a temporary database space,
>> > workspace.db, was created via a script that terminated
>> > and did not remove the space. Sometime later, the actual
>> > disk file workspace.db was removed and we have no backup
>> > of it. There was no valuable data in it, so that's not
>> > the issue. The issue is we can't backup the database
>> because workspace.db no longer exists. >
>> > So my question is, how do we get the database to no
>> > longer reference the temporary space, workspace.db?
>>
>>


Michele Posted on 2008-01-30 16:32:42.0Z
Sender: 2c95.479f6479.1804289383@sybase.com
From: Michele
Newsgroups: ianywhere.public.general
Subject: Re: dbbackup fails - suspect missing dbspace is the issue
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <47a0a6aa.4886.1681692777@sybase.com>
References: <479fa221$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 30 Jan 2008 08:32:42 -0800
X-Trace: forums-1-dub 1201710762 10.22.241.41 (30 Jan 2008 08:32:42 -0800)
X-Original-Trace: 30 Jan 2008 08:32:42 -0800, 10.22.241.41
Lines: 97
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6705
Article PK: 4954

I've tried this via SQL and also Sybase Central. Here's the
Details of the Sybase Central error.

[Sybase][ODBC Driver][Adaptive Server Anywhere]Permission
denied: you do not have permission to use the "DROP DBSPACE"
statement
SQLCODE: -121
SQLSTATE: 42000

> I would try dropping that dbspace if you can.
> The SQL should be this simple
>
> drop dbspace workspace;
>
> With recent Sybase Central versions you can graphically
> just delete that from the dbspaces treeview.
>
> Let me know if that fails and what error you are seeing
> ....
>
>
>
> <Michele> wrote in message
> > news:479f9b84.31d6.1681692777@sybase.com... As part of
> > attempting a large unload of data, a temporary dbspace
> > was created to hold a temporary table that identified
> > which data to unload. (It's a long story...) This was
> the command used to create it: >
> > CREATE DBSPACE workspace AS '$HOME/dbspace/workspace.db'
> >
> > Sometime later, the workspace.db file was inadvertenly
> > removed via the rm command. Ever since then, the backup
> > will not work. Whenever the backup runs, it fails
> > immediately, with the following error:
> >
> > Error in file "/home/livedb/bin/dss2nfsbackup.sql" at
> > line 3 Database backup not started
> >
> > Executing command:
> > % BACKUP DATABASE
> > % DIRECTORY '/mnt/red1data/backup_dss2';
> > *** ERROR *** Error in file
> > "/home/livedb/bin/dss2nfsbackup.sql" at line 3
> > *** ERROR *** Database backup not started
> > % // Error: Error in file
> > "/home/livedb/bin/dss2nfsbackup.sql" at line 3
> > // Database backup not started
> > //
> > % // ( /home/livedb/bin/dss2nfsbackup.sql )
> >
> > Also, anytime the database is started, we see an error
> > in /var/log/messages as follows:
> >
> > SQLAnywhere(dss2): Cannot open dbspace 'workspace' from
> > file '/home/livedb/dbspace/workspace.db'
> >
> >
> >
> >> You use of temporary database is a bit confusing.
> >>
> >> Was workspace.db a seperate database?
> >> Or a dbspace (and if so was it part of the database
> >> you are trying to backup)?
> >>
> >> Also... What indications do you have that this
> >> file is the source of your backup woes?
> >>
> >> You may also want to spell out exactly how
> >> you removed the file 'workspace.db'.
> >>
> >> <Michele Hardy> wrote in message
> >> > news:479e0a7f.11a1.1681692777@sybase.com... We are
> >> > unable to make a backup copy of one of our databases.
> >> > This was done nightly via a cron job which
> essentially >> creates a script with the following lines:
> > >> > BACKUP DATABASE
> >> > DIRECTORY '/mnt/XXXXX/backup';
> >> > QUIT;
> >> >
> >> > which it passes as a script to dbisqlc
> >> >
> >> > This started failing, with no real indication as to
> why. >> > Based on the timing of things, we believe the
> issue is >> > related to a temporary database space that
> no longer >> > exists. Essentially, a temporary database
> space, >> > workspace.db, was created via a script that
> terminated >> > and did not remove the space. Sometime
> later, the actual >> > disk file workspace.db was removed
> and we have no backup >> > of it. There was no valuable
> data in it, so that's not >> > the issue. The issue is we
> can't backup the database >> because workspace.db no
> longer exists. > >> > So my question is, how do we get the
> database to no >> > longer reference the temporary space,
> workspace.db? >>
> >>
>
>


"Nick Elson" < Posted on 2008-01-30 17:23:17.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <479fa221$1@forums-1-dub> <47a0a6aa.4886.1681692777@sybase.com>
Subject: Re: dbbackup fails - suspect missing dbspace is the issue
Lines: 104
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47a0b285@forums-1-dub>
Date: 30 Jan 2008 09:23:17 -0800
X-Trace: forums-1-dub 1201713797 10.22.241.152 (30 Jan 2008 09:23:17 -0800)
X-Original-Trace: 30 Jan 2008 09:23:17 -0800, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6706
Article PK: 4953

So you are not using an account with the DBA priviledge.
You will need to find someone who has that and log in
with that account first.

<Michele> wrote in message news:47a0a6aa.4886.1681692777@sybase.com...
> I've tried this via SQL and also Sybase Central. Here's the
> Details of the Sybase Central error.
>
> [Sybase][ODBC Driver][Adaptive Server Anywhere]Permission
> denied: you do not have permission to use the "DROP DBSPACE"
> statement
> SQLCODE: -121
> SQLSTATE: 42000
>
>> I would try dropping that dbspace if you can.
>> The SQL should be this simple
>>
>> drop dbspace workspace;
>>
>> With recent Sybase Central versions you can graphically
>> just delete that from the dbspaces treeview.
>>
>> Let me know if that fails and what error you are seeing
>> ....
>>
>>
>>
>> <Michele> wrote in message
>> > news:479f9b84.31d6.1681692777@sybase.com... As part of
>> > attempting a large unload of data, a temporary dbspace
>> > was created to hold a temporary table that identified
>> > which data to unload. (It's a long story...) This was
>> the command used to create it: >
>> > CREATE DBSPACE workspace AS '$HOME/dbspace/workspace.db'
>> >
>> > Sometime later, the workspace.db file was inadvertenly
>> > removed via the rm command. Ever since then, the backup
>> > will not work. Whenever the backup runs, it fails
>> > immediately, with the following error:
>> >
>> > Error in file "/home/livedb/bin/dss2nfsbackup.sql" at
>> > line 3 Database backup not started
>> >
>> > Executing command:
>> > % BACKUP DATABASE
>> > % DIRECTORY '/mnt/red1data/backup_dss2';
>> > *** ERROR *** Error in file
>> > "/home/livedb/bin/dss2nfsbackup.sql" at line 3
>> > *** ERROR *** Database backup not started
>> > % // Error: Error in file
>> > "/home/livedb/bin/dss2nfsbackup.sql" at line 3
>> > // Database backup not started
>> > //
>> > % // ( /home/livedb/bin/dss2nfsbackup.sql )
>> >
>> > Also, anytime the database is started, we see an error
>> > in /var/log/messages as follows:
>> >
>> > SQLAnywhere(dss2): Cannot open dbspace 'workspace' from
>> > file '/home/livedb/dbspace/workspace.db'
>> >
>> >
>> >
>> >> You use of temporary database is a bit confusing.
>> >>
>> >> Was workspace.db a seperate database?
>> >> Or a dbspace (and if so was it part of the database
>> >> you are trying to backup)?
>> >>
>> >> Also... What indications do you have that this
>> >> file is the source of your backup woes?
>> >>
>> >> You may also want to spell out exactly how
>> >> you removed the file 'workspace.db'.
>> >>
>> >> <Michele Hardy> wrote in message
>> >> > news:479e0a7f.11a1.1681692777@sybase.com... We are
>> >> > unable to make a backup copy of one of our databases.
>> >> > This was done nightly via a cron job which
>> essentially >> creates a script with the following lines:
>> > >> > BACKUP DATABASE
>> >> > DIRECTORY '/mnt/XXXXX/backup';
>> >> > QUIT;
>> >> >
>> >> > which it passes as a script to dbisqlc
>> >> >
>> >> > This started failing, with no real indication as to
>> why. >> > Based on the timing of things, we believe the
>> issue is >> > related to a temporary database space that
>> no longer >> > exists. Essentially, a temporary database
>> space, >> > workspace.db, was created via a script that
>> terminated >> > and did not remove the space. Sometime
>> later, the actual >> > disk file workspace.db was removed
>> and we have no backup >> > of it. There was no valuable
>> data in it, so that's not >> > the issue. The issue is we
>> can't backup the database >> because workspace.db no
>> longer exists. > >> > So my question is, how do we get the
>> database to no >> > longer reference the temporary space,
>> workspace.db? >>
>> >>
>>
>>


"Nick Elson" < Posted on 2008-02-01 19:34:19.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <479fa221$1@forums-1-dub> <47a0a6aa.4886.1681692777@sybase.com> <47a0b285@forums-1-dub>
Subject: Re: dbbackup fails - suspect missing dbspace is the issue
Lines: 142
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47a3743b$1@forums-1-dub>
Date: 1 Feb 2008 11:34:19 -0800
X-Trace: forums-1-dub 1201894459 10.22.241.152 (1 Feb 2008 11:34:19 -0800)
X-Original-Trace: 1 Feb 2008 11:34:19 -0800, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6710
Article PK: 4956

Okay I just reproduced the permission error [in a recent 8.0.3]
even with dba.

That occurs because you have tables defined that lived
in that dbspace and their existence now are preventing
the DROP dbspace operation.

The text of the error message could have been a little
more descriptive but that is going to be your main
issue.

So you are going to need to resort to a backup
of that without those compromised tables
[and translate the transaction log and remove
all references to them and their dbspace]
or you are going to need to rebuild that database
without those tables.

For the rebuild consider doing the following [after hours
or off-line after taking a safety copy of the file]:

dbunload -ar -e table1,...,tablen -c "....;dbf=<database file
name/>"

where you will need to know the tables to exclude.
To find out what those are, just unload the schema
with
dbunload -n -r reload.sql -c "...."
and look for the string

'in workspace'

"Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@> wrote in message
news:47a0b285@forums-1-dub...
> So you are not using an account with the DBA priviledge.
> You will need to find someone who has that and log in
> with that account first.
>
> <Michele> wrote in message news:47a0a6aa.4886.1681692777@sybase.com...
>> I've tried this via SQL and also Sybase Central. Here's the
>> Details of the Sybase Central error.
>>
>> [Sybase][ODBC Driver][Adaptive Server Anywhere]Permission
>> denied: you do not have permission to use the "DROP DBSPACE"
>> statement
>> SQLCODE: -121
>> SQLSTATE: 42000
>>
>>> I would try dropping that dbspace if you can.
>>> The SQL should be this simple
>>>
>>> drop dbspace workspace;
>>>
>>> With recent Sybase Central versions you can graphically
>>> just delete that from the dbspaces treeview.
>>>
>>> Let me know if that fails and what error you are seeing
>>> ....
>>>
>>>
>>>
>>> <Michele> wrote in message
>>> > news:479f9b84.31d6.1681692777@sybase.com... As part of
>>> > attempting a large unload of data, a temporary dbspace
>>> > was created to hold a temporary table that identified
>>> > which data to unload. (It's a long story...) This was
>>> the command used to create it: >
>>> > CREATE DBSPACE workspace AS '$HOME/dbspace/workspace.db'
>>> >
>>> > Sometime later, the workspace.db file was inadvertenly
>>> > removed via the rm command. Ever since then, the backup
>>> > will not work. Whenever the backup runs, it fails
>>> > immediately, with the following error:
>>> >
>>> > Error in file "/home/livedb/bin/dss2nfsbackup.sql" at
>>> > line 3 Database backup not started
>>> >
>>> > Executing command:
>>> > % BACKUP DATABASE
>>> > % DIRECTORY '/mnt/red1data/backup_dss2';
>>> > *** ERROR *** Error in file
>>> > "/home/livedb/bin/dss2nfsbackup.sql" at line 3
>>> > *** ERROR *** Database backup not started
>>> > % // Error: Error in file
>>> > "/home/livedb/bin/dss2nfsbackup.sql" at line 3
>>> > // Database backup not started
>>> > //
>>> > % // ( /home/livedb/bin/dss2nfsbackup.sql )
>>> >
>>> > Also, anytime the database is started, we see an error
>>> > in /var/log/messages as follows:
>>> >
>>> > SQLAnywhere(dss2): Cannot open dbspace 'workspace' from
>>> > file '/home/livedb/dbspace/workspace.db'
>>> >
>>> >
>>> >
>>> >> You use of temporary database is a bit confusing.
>>> >>
>>> >> Was workspace.db a seperate database?
>>> >> Or a dbspace (and if so was it part of the database
>>> >> you are trying to backup)?
>>> >>
>>> >> Also... What indications do you have that this
>>> >> file is the source of your backup woes?
>>> >>
>>> >> You may also want to spell out exactly how
>>> >> you removed the file 'workspace.db'.
>>> >>
>>> >> <Michele Hardy> wrote in message
>>> >> > news:479e0a7f.11a1.1681692777@sybase.com... We are
>>> >> > unable to make a backup copy of one of our databases.
>>> >> > This was done nightly via a cron job which
>>> essentially >> creates a script with the following lines:
>>> > >> > BACKUP DATABASE
>>> >> > DIRECTORY '/mnt/XXXXX/backup';
>>> >> > QUIT;
>>> >> >
>>> >> > which it passes as a script to dbisqlc
>>> >> >
>>> >> > This started failing, with no real indication as to
>>> why. >> > Based on the timing of things, we believe the
>>> issue is >> > related to a temporary database space that
>>> no longer >> > exists. Essentially, a temporary database
>>> space, >> > workspace.db, was created via a script that
>>> terminated >> > and did not remove the space. Sometime
>>> later, the actual >> > disk file workspace.db was removed
>>> and we have no backup >> > of it. There was no valuable
>>> data in it, so that's not >> > the issue. The issue is we
>>> can't backup the database >> because workspace.db no
>>> longer exists. > >> > So my question is, how do we get the
>>> database to no >> > longer reference the temporary space,
>>> workspace.db? >>
>>> >>
>>>
>>>
>
>


Reg Domaratzki (iAnywhere Solutions) Posted on 2008-01-28 18:15:34.0Z
From: "Reg Domaratzki \(iAnywhere Solutions\)" <FirstName.LastName@ianywhere.com>
Newsgroups: ianywhere.public.general
References: <479e0a7f.11a1.1681692777@sybase.com>
Subject: Re: dbbackup fails - suspect
Lines: 44
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; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <479e1bc6$1@forums-1-dub>
Date: 28 Jan 2008 10:15:34 -0800
X-Trace: forums-1-dub 1201544134 10.22.241.152 (28 Jan 2008 10:15:34 -0800)
X-Original-Trace: 28 Jan 2008 10:15:34 -0800, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6699
Article PK: 4947

If you execute "select * from sys.sysfile", you'll see a list of all the
defined dbspaces in your database. The "system" dbspace is created by
default, but others in the list are dbspaces that you have created. You can
remove a dbspace from this list by executing "DROP DBSPACE dbspace_name"
where dbspace_name is the value in the dbpsace_name column in the SYSFILE
table.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"

<Michele Hardy> wrote in message news:479e0a7f.11a1.1681692777@sybase.com...
> We are unable to make a backup copy of one of our databases.
> This was done nightly via a cron job which essentially
> creates a script with the following lines:
>
> BACKUP DATABASE
> DIRECTORY '/mnt/XXXXX/backup';
> QUIT;
>
> which it passes as a script to dbisqlc
>
> This started failing, with no real indication as to why.
> Based on the timing of things, we believe the issue is
> related to a temporary database space that no longer exists.
> Essentially, a temporary database space, workspace.db, was
> created via a script that terminated and did not remove the
> space. Sometime later, the actual disk file workspace.db was
> removed and we have no backup of it. There was no valuable
> data in it, so that's not the issue. The issue is we can't
> backup the database because workspace.db no longer exists.
>
> So my question is, how do we get the database to no longer
> reference the temporary space, workspace.db?


Michele Posted on 2008-01-29 22:03:32.0Z
Sender: 2c95.479f6479.1804289383@sybase.com
From: Michele
Newsgroups: ianywhere.public.general
Subject: Re: dbbackup fails - suspect
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <479fa2b4.32d6.1681692777@sybase.com>
References: <479e1bc6$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 29 Jan 2008 14:03:32 -0800
X-Trace: forums-1-dub 1201644212 10.22.241.41 (29 Jan 2008 14:03:32 -0800)
X-Original-Trace: 29 Jan 2008 14:03:32 -0800, 10.22.241.41
Lines: 48
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6702
Article PK: 4951

Tried that. We keep getting permission errors.

> If you execute "select * from sys.sysfile", you'll see a
> list of all the defined dbspaces in your database. The
> "system" dbspace is created by default, but others in the
> list are dbspaces that you have created. You can remove
> a dbspace from this list by executing "DROP DBSPACE
> dbspace_name" where dbspace_name is the value in the
> dbpsace_name column in the SYSFILE table.
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer
> Version 8 Please reply only to the newsgroup
>
> iAnywhere Developer Community :
> http://www.ianywhere.com/developer iAnywhere Documentation
> : http://www.ianywhere.com/developer/product_manuals ASA
> Patches and EBFs : http://downloads.sybase.com/swd/base.do
> -> Choose SQL Anywhere Studio
> -> Set filter to "Display ALL platforms IN ALL MONTHS"
>
>
> <Michele Hardy> wrote in message
> > news:479e0a7f.11a1.1681692777@sybase.com... We are
> > unable to make a backup copy of one of our databases.
> > This was done nightly via a cron job which essentially
> creates a script with the following lines: >
> > BACKUP DATABASE
> > DIRECTORY '/mnt/XXXXX/backup';
> > QUIT;
> >
> > which it passes as a script to dbisqlc
> >
> > This started failing, with no real indication as to why.
> > Based on the timing of things, we believe the issue is
> > related to a temporary database space that no longer
> > exists. Essentially, a temporary database space,
> > workspace.db, was created via a script that terminated
> > and did not remove the space. Sometime later, the actual
> > disk file workspace.db was removed and we have no backup
> > of it. There was no valuable data in it, so that's not
> > the issue. The issue is we can't backup the database
> because workspace.db no longer exists. >
> > So my question is, how do we get the database to no
> > longer reference the temporary space, workspace.db?
>
>


"Nick Elson" < Posted on 2008-01-30 15:02:44.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <479e1bc6$1@forums-1-dub> <479fa2b4.32d6.1681692777@sybase.com>
Subject: Re: dbbackup fails - suspect
Lines: 56
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <47a09194$1@forums-1-dub>
Date: 30 Jan 2008 07:02:44 -0800
X-Trace: forums-1-dub 1201705364 10.22.241.152 (30 Jan 2008 07:02:44 -0800)
X-Original-Trace: 30 Jan 2008 07:02:44 -0800, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6704
Article PK: 4952

You need DBA permissions to do that.

If that is not your issue, then what error do you get
and during which operation do you get that?

<Michele> wrote in message news:479fa2b4.32d6.1681692777@sybase.com...
> Tried that. We keep getting permission errors.
>
>> If you execute "select * from sys.sysfile", you'll see a
>> list of all the defined dbspaces in your database. The
>> "system" dbspace is created by default, but others in the
>> list are dbspaces that you have created. You can remove
>> a dbspace from this list by executing "DROP DBSPACE
>> dbspace_name" where dbspace_name is the value in the
>> dbpsace_name column in the SYSFILE table.
>>
>> --
>> Reg Domaratzki, Sybase iAnywhere Solutions
>> Sybase Certified Professional - Sybase ASA Developer
>> Version 8 Please reply only to the newsgroup
>>
>> iAnywhere Developer Community :
>> http://www.ianywhere.com/developer iAnywhere Documentation
>> : http://www.ianywhere.com/developer/product_manuals ASA
>> Patches and EBFs : http://downloads.sybase.com/swd/base.do
>> -> Choose SQL Anywhere Studio
>> -> Set filter to "Display ALL platforms IN ALL MONTHS"
>>
>>
>> <Michele Hardy> wrote in message
>> > news:479e0a7f.11a1.1681692777@sybase.com... We are
>> > unable to make a backup copy of one of our databases.
>> > This was done nightly via a cron job which essentially
>> creates a script with the following lines: >
>> > BACKUP DATABASE
>> > DIRECTORY '/mnt/XXXXX/backup';
>> > QUIT;
>> >
>> > which it passes as a script to dbisqlc
>> >
>> > This started failing, with no real indication as to why.
>> > Based on the timing of things, we believe the issue is
>> > related to a temporary database space that no longer
>> > exists. Essentially, a temporary database space,
>> > workspace.db, was created via a script that terminated
>> > and did not remove the space. Sometime later, the actual
>> > disk file workspace.db was removed and we have no backup
>> > of it. There was no valuable data in it, so that's not
>> > the issue. The issue is we can't backup the database
>> because workspace.db no longer exists. >
>> > So my question is, how do we get the database to no
>> > longer reference the temporary space, workspace.db?
>>
>>