import an existing database

Discussion:

(too old to reply)

unknown

2008-08-22 09:49:55 UTC

Hello together,

in the last week one colluege of me deleted the main server
in the "server config", but he did't delete the dat-files
with the data.

Now my question: How can I get access to this dat-files?
Is it possible to connect to this dat-files or import the
data?

Thank you
Michael

Bret Halford

2008-08-22 15:11:20 UTC

Permalink

Post by unknown
Hello together,
in the last week one colluege of me deleted the main server
in the "server config", but he did't delete the dat-files
with the data.
Now my question: How can I get access to this dat-files?
Is it possible to connect to this dat-files or import the
data?
Thank you
Michael

Is this ASE? I ask because I'm not sure what
you mean by "server config".

If this is ASE and you mean that the master device
was deleted then you have a few options.

You can create a new master device using the dataserver
binary. See the documentation on it in the ASE Utilities
guide for an example. Once rebuilt, you can start the server
with your existing RUN_SERVER file (assuming you used the
same device name). The server will then appear as a newly
installed server.

If you have a dump of the master device, boot using the -m
flag in the RUNSERVER file (single user mode) and load the
dump.

If you don't have a dump of the master device,
consult the earlier errorlog entries to learn the
device names for all the devices. Figure out how large the
devices are. Then use the DISK REINIT command (NOT disk init)
to add those device entries to the sysdevices table without
writing/initializing the devices. Once all the devices
are in place, use the DISK REFIT command. This will scan
the contents of all the devices and rebuild the sysdatabases
and sysusages tables from those devices. You will then be
largely recovered. Some information will have been lost, though.
You will need to add logins back in (the original passwords are
lost), and probably need to add an entry or two in sysservers,
such as the backupserver entry in particular. (then promptly take
a dump of the master database for next time!)

unknown

2008-08-24 06:46:11 UTC

Permalink

Dear Mr. Halfort,

Yes, you are right! We use the ASE 12.5. After deleting of
the main server by my colleague the windows service "Sybase
SQLServer BASE_SIAS" was lost.

What do you mean with the RUN_SERVER file?

Thank you for the pieces of advice. I'll try them on monday
morning and will give you a feedback.

Michael

Post by Bret Halford

Post by unknown
Hello together,
in the last week one colluege of me deleted the main
server in the "server config", but he did't delete the
dat-files with the data.
Now my question: How can I get access to this dat-files?
Is it possible to connect to this dat-files or import
the data?
Thank you
Michael

Is this ASE? I ask because I'm not sure what
you mean by "server config".
If this is ASE and you mean that the master device
was deleted then you have a few options.
You can create a new master device using the dataserver
binary. See the documentation on it in the ASE Utilities
guide for an example. Once rebuilt, you can start the
server with your existing RUN_SERVER file (assuming you
used the same device name). The server will then appear
as a newly installed server.
If you have a dump of the master device, boot using the -m
flag in the RUNSERVER file (single user mode) and load the
dump.
If you don't have a dump of the master device,
consult the earlier errorlog entries to learn the
device names for all the devices. Figure out how large
the devices are. Then use the DISK REINIT command (NOT
disk init) to add those device entries to the sysdevices
table without writing/initializing the devices. Once all
the devices are in place, use the DISK REFIT command.
This will scan the contents of all the devices and rebuild
the sysdatabases and sysusages tables from those devices.
You will then be largely recovered. Some information will
have been lost, though. You will need to add logins back
in (the original passwords are lost), and probably need to
add an entry or two in sysservers, such as the
backupserver entry in particular. (then promptly take a
dump of the master database for next time!)

Jason L. Froebe [TeamSybase]

2008-08-24 07:07:14 UTC

Permalink

Post by unknown
Dear Mr. Halfort,
Yes, you are right! We use the ASE 12.5. After deleting of
the main server by my colleague the windows service "Sybase
SQLServer BASE_SIAS" was lost.
What do you mean with the RUN_SERVER file?
Thank you for the pieces of advice. I'll try them on monday
morning and will give you a feedback.
Michael

Hi Michael,

Can you elaborate more on what occurred? Are you saying the the os on
the machine was rebuilt, the Sybase entries in the windows registry were
deleted, or that the Sybase software and settings were deleted?

It's not clear to us what happened so we're not exactly sure as to how
to help.

--
Jason L. Froebe
TeamSybase
http://www.froebe.net/blog
MyDatabases Free Magazine http://froebe.net/blog/mydatabases-magazine/

unknown

2008-08-26 07:54:20 UTC

Permalink

Post by Jason L. Froebe [TeamSybase]

Post by unknown
Dear Mr. Halfort,
Yes, you are right! We use the ASE 12.5. After
deleting of the main server by my colleague the
windows service "Sybase SQLServer BASE_SIAS" was lost.
What do you mean with the RUN_SERVER file?
Thank you for the pieces of advice. I'll try them on
monday morning and will give you a feedback.
Michael

Hi Michael,
Can you elaborate more on what occurred? Are you saying
the the os on the machine was rebuilt, the Sybase
entries in the windows registry were deleted, or that
the Sybase software and settings were deleted?
It's not clear to us what happened so we're not exactly
sure as to how to help.
--
Jason L. Froebe
TeamSybase
http://www.froebe.net/blog
MyDatabases Free Magazine
http://froebe.net/blog/mydatabases-magazine/

Dear Mr. Froebe,
we changed nothing on the operation system (Windows Server
2000), but my colleague deleted in "server config" (ASE
12.5) the server. Consequently, we lost the windows
service "Sybase SQL Server BASE_SIAS", but the following
- devicedata1.dat with 8.192.000 KB and 2K
- devicedata2.dat with 8.192.000 KB and 2K
- devicedata3.dat with 8.192.000 KB and 2K
- devicedata4.dat with 8.192.000 KB and 2K
- devicedata5.dat with 8.192.000 KB and 2K
- deviceIndex1.dat with 8.192.000 KB and 2K
- deviceIndex2.dat with 8.192.000 KB and 2K
- deviceIndex3.dat with 8.192.000 KB and 2K
- deviceIndex4.dat with 8.192.000 KB and 2K
- deviceIndex5.dat with 8.192.000 KB and 2K
- devicelog.dat with 8.192.000 KB and 2K
- devicelog2.dat with 8.192.000 KB and 2K
- devicetemp1.dat with 8.192.000 KB and 2K
- master.dat with 30.720 KB and 2K
- sybprocs.dat with 102.400 KB and 2K
Currently, I test the pieces of advice from Mr. Halfort,
but we get an error during DISK REFIT.
For further information please see the attached errorlog.
Best regards
MichaelK
[Attachment: errorlog.zip]

Now we tried another way to recover our Data.
We have installed a new, empty database and then we ovewrote
the master.dat with our old. After fixing a few errors we
could start the server again. When we look in the
master..sysdatabases we can see our sias databse, but when
we try to select anything in there we get an error:

"Database `sias` has not been recovered yet"

The same, when we try to use the sp_help command:

"Database `sybsystemprocs` has not been recovered yet"

Is the Sybase Database able to recover the databases
automaticly or must we do anything to recover the data?

Best regards
MichaelK

Luc Van der Veurst

2008-08-26 08:52:35 UTC