db mounting problem

[Ken Ross]

I must first admit that I am a complete nube when it comes to Sybase [but
have used MS SQL for years] and I've just had a very vexing problem
dropped in my lap that I hope someone here can help with.

I was given a Sybase .db file and asked to "attach" it an and query some
data from it. At the time I didn't even have Sybase so I downloaded and
installed the ASE 15 Developer Edition.

Not knowing quite were to start, I tried using the Mount feature to
"attach" the .db file. That resulted in an error that basically said I
had a bad/missing Manifest file. All I have is the .db file so if this IS
something I can Mount and it needs a Manifest to do so, I'm probably
pooched because I don't have it.

Of course, my total ignorance of the situation is such that I don't even
know if a .db file is something that CAN be Mounted or if I need to take
an enitrely different approach.

I hope this rambling account is enough for someone to recognize what I'm
up against and can offer me a suggestion or two. I really need to find a
way to get to the data and time is very short. Nothing like "mission
impossible" :)

Thanks all.

Ken

[Rob Verschoor]

Most likely that file is a 'database dump' and you need to load it:

- make sure the Backup Server is running (for its name, run 'sp_helpserver
SYB_BACKUP' --> the name this returns is the Backup Server you need to run)

- create a database named xyz on 'your-db-device' = 10
create database xyz on 'your-db-device' = 10

- from within the master database, run "load database xyz from
'pathname-to-your-.db-file' "
This will likely tell you that database xyz is too small and must be at
least X Mb (unless it was a small database in which case you're almost ready
and jump to the last step below)

- drop database xyz and recreate it with the for load option:
create database xyz on 'your-db-device' = X for load

- repeat the load database command

- when ready, run the final step: "online database xyz"

...and now you should be ready to access the database.

Incidentally, you really need to start reading some documentation about
ASE -- pick up a copy of the 'System Administration Guide' which describes
lots of other DBA-type things you will likely need in the near future. It's
located here: http://sybooks.sybase.com/nav/detail.do?docset=1299

HTH,

Rob V.
-------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 12.5/12.0/11.5/11.0
and Replication Server 12.5 / TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (new edition!)
"The Complete Sybase ASE Quick Reference Guide" (new edition!)
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:***@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., P.O.Box 10695, 2501HR Den Haag, The Netherlands
-------------------------------------------------------------

Post by Ken Ross
I must first admit that I am a complete nube when it comes to Sybase [but
have used MS SQL for years] and I've just had a very vexing problem
dropped in my lap that I hope someone here can help with.
I was given a Sybase .db file and asked to "attach" it an and query some
data from it. At the time I didn't even have Sybase so I downloaded and
installed the ASE 15 Developer Edition.
Not knowing quite were to start, I tried using the Mount feature to
"attach" the .db file. That resulted in an error that basically said I
had a bad/missing Manifest file. All I have is the .db file so if this IS
something I can Mount and it needs a Manifest to do so, I'm probably
pooched because I don't have it.
Of course, my total ignorance of the situation is such that I don't even
know if a .db file is something that CAN be Mounted or if I need to take
an enitrely different approach.
I hope this rambling account is enough for someone to recognize what I'm
up against and can offer me a suggestion or two. I really need to find a
way to get to the data and time is very short. Nothing like "mission
impossible" :)
Thanks all.
Ken

[Ken Ross]

This post might be inappropriate. Click to display it.

[Bret Halford]

Hi Ken,

Run the following:

sp_configure "allow updates", 1
go
use master
go
update sysservers set srvnetname = "KROSSXPKA_BS" where srvname =
"SYB_BACKUP"
go
sp_configure "allow updates", 0
go

The local backupserver always has a logical srvname of "SYB_BACKUP", but the
srvnetname
is the name actually looked for in the interfaces file.

Attempting to load the file as an ASE dump file is a good thing to try, but
you should also be prepared for
the possibility that the file you have isn't an ASE database dump, but rather
an ASA
(Sybase Adaptive Server Anywhere, a different product entirely) database
file.

-bret

Post by Ken Ross
Rob,
Thanks MUCH for the reply. However, as luck would have it I'm having
trouble here as well.
- When I issue the "sp_helpserver SYB_BACKUP" command the name that I get
back for the backup server is "SYB_BACKUP". However, if I look in
Configure Servers I see that the backup server name is "KROSSXPKA_BS"
(the name of my computer with "_BS" appended).
- I tried creating the database as you described but couldn't figure out
what to supply as "your-db-device". By looking through reference doc
online I found I could supply "default" as the device which seemed to
work EXCEPT that I couldn't supply the "=10" size parameter (isql would
error). So, I created the "xyz" database against the default device with
the default size (3 MB).
- When I tried the first Load command I receive an isql error saying that
kernel Connectivity Library (Directory Control Layer) Error: Error
returned by service provider.
(InterfacesDriver): Requested server name not found.
server Error: 7220, Severity: 11, State: 1
server Site 'SYB_BACKUP' not found in interfaces file.
server Error: 7235, Severity: 17, State: 0
server No other query entry found for the remote server SYB_BACKUP -
site SYB_BACKUP. Aborting this site handler, as no remote server
responded. Please make sure the remote server is accepting connections.
I've searched doc and online to try and find out what might be causing
this and just haven't found it. I uninstalled and reinstalled ASE,
selecting "full install" and letting it do its default configuration, and
I get exactly the same results.
I have also noticed that when I run sp_helpserver without any parameters
I get a list of various "servers" but the KROSSXPKA_BS is not included
'KROSSXPKA'
'KROSSXPKA_XP'
'SYB_BACKUP'
'SYB_EJB'
'SYB_JSAGENT'
'SYB_JSTASK'
'loopback'
I hope you can help me get past this - thanks again for your time.
Ken

Post by Rob Verschoor
- make sure the Backup Server is running (for its name, run
'sp_helpserver SYB_BACKUP' --> the name this returns is the Backup
Server you need to run)
- create a database named xyz on 'your-db-device' = 10
create database xyz on 'your-db-device' = 10
- from within the master database, run "load database xyz from
'pathname-to-your-.db-file' "
This will likely tell you that database xyz is too small and must be
at least X Mb (unless it was a small database in which case you're
almost ready and jump to the last step below)
create database xyz on 'your-db-device' = X for load
- repeat the load database command
- when ready, run the final step: "online database xyz"
...and now you should be ready to access the database.
Incidentally, you really need to start reading some documentation
about ASE -- pick up a copy of the 'System Administration Guide'
which describes lots of other DBA-type things you will likely need in
http://sybooks.sybase.com/nav/detail.do?docset=1299
HTH,
Rob V.
-------------------------------------------------------------
Rob Verschoor
Certified Sybase Professional DBA for ASE 12.5/12.0/11.5/11.0
and Replication Server 12.5 / TeamSybase
"Tips, Tricks & Recipes for Sybase ASE" (new edition!)
"The Complete Sybase ASE Quick Reference Guide" (new edition!)
"The Complete Sybase Replication Server Quick Reference Guide"
http://www.sypron.nl
Sypron B.V., P.O.Box 10695, 2501HR Den Haag, The Netherlands
-------------------------------------------------------------

Post by Ken Ross
I must first admit that I am a complete nube when it comes to Sybase [but
have used MS SQL for years] and I've just had a very vexing problem
dropped in my lap that I hope someone here can help with.
I was given a Sybase .db file and asked to "attach" it an and query
some data from it. At the time I didn't even have Sybase so I
downloaded and installed the ASE 15 Developer Edition.
Not knowing quite were to start, I tried using the Mount feature to
"attach" the .db file. That resulted in an error that basically said
I had a bad/missing Manifest file. All I have is the .db file so if
this IS something I can Mount and it needs a Manifest to do so, I'm
probably pooched because I don't have it.
Of course, my total ignorance of the situation is such that I don't
even know if a .db file is something that CAN be Mounted or if I need
to take an enitrely different approach.
I hope this rambling account is enough for someone to recognize what
I'm up against and can offer me a suggestion or two. I really need to
find a way to get to the data and time is very short. Nothing like
"mission impossible" :)
Thanks all.
Ken

[Ken Ross]

Thanks Bret,

I've been continuously digging and after doing a Google search for the
version number I found in the db file header I now believe that this may
very well be a SQL Anywhere file [created under version 8]. I've just
installed version 10 of SQL Anywhere so we'll see how it goes from here.

Again, thanks for the assist.

Ken

Post by Bret Halford
Hi Ken,
sp_configure "allow updates", 1
go
use master
go
update sysservers set srvnetname = "KROSSXPKA_BS" where srvname =
"SYB_BACKUP"
go
sp_configure "allow updates", 0
go
The local backupserver always has a logical srvname of "SYB_BACKUP",
but the srvnetname
is the name actually looked for in the interfaces file.
Attempting to load the file as an ASE dump file is a good thing to
try, but you should also be prepared for
the possibility that the file you have isn't an ASE database dump, but
rather an ASA
(Sybase Adaptive Server Anywhere, a different product entirely)
database file.
-bret

[Ken Ross]

Ok, just to tie off this thread we WERE able to determine that the .db file
is in fact a SQL Anywhere file (apparently the .db extension is commonly
used for Sybase SQL Anywhere files).

The database we are working with is from version 8.0 and the current 10.0
product is not able to open databases created prior to 10.0. It does,
however, have a migration wizard that can convert the database through a
series of scripting activities.

You can also still download version 9 of SQL Anywhere and that IS capable
of opening a version 8 data file.

Ken