Home > Archive > Sybase Database > May 2005 > Loading the database dumps in sybase









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Loading the database dumps in sybase
gopal

2005-05-21, 3:23 am

Hi i have database dumps named as "train_2005_03_21.bkp"

I dont how to load this back into database -sybase obviously

Pls help me out with exact command

Cheers

Gopal

Michael Peppler

2005-05-21, 11:23 am

On Fri, 20 May 2005 23:30:45 -0700, gopal wrote:

> Hi i have database dumps named as "train_2005_03_21.bkp"
>
> I dont how to load this back into database -sybase obviously
>
> Pls help me out with exact command


load database <dbname> from "<dump file>"

You'll need to have a database that is large enough for the load to work.

Michael
--
Michael Peppler - mpeppler@peppler.org - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html


will.menton@gmail.com

2005-05-21, 1:23 pm

what michael said - but you need to have backup server running. If you
don't have Backup Server setup already you can do so with srvbuild

Cheers
Bill Menton

Anthony Mandic

2005-05-22, 3:23 am

gopal wrote:
>
> Hi i have database dumps named as "train_2005_03_21.bkp"
>
> I dont how to load this back into database -sybase obviously
>
> Pls help me out with exact command


What Michael and Bill said but you need all these things -

ASE should be running (I assume you mean ASE. Sybase have 3
different database products. If its ASA or ASIQ, please say so).

Backup Server connected to ASE should be running

Your dump should be at the same version of ASE or a supported
earlier version (supported earlier versions will be upgraded).
Newer versions won't load unless they are minor revision numbers
and ASE knows how to deal with them. You'll see a message like
"Database 'XXX' is now online with a lower server version number.
Refer to the higher version release notes on the limitations
of backward compatibility."

The dump must be of the same platform (for binary compatibility.
This advice doesn't apply to the new cross platform dump feature).

The target database must be of the same size or larger in order
to hold the loaded database. A smaller database won't support
the load.

The segment layout need not match. The load will change fragments
as needed. Sometimes this leads to unexpected results. Other times
its useful in that it coalesces adjoining like fragments. One large
single device helps here if you don't know the layout. You may see
a message like "Caution: You have set up this database to include
space on disk NNN for both data and the transaction log. This can
make recovery impossible if that disk fails." This is useful in
that you can learn the original layout.

You need to be "sa" or have the required role to do a load.

The sysusers table in the loaded database may get changed if logins
don't exist or the IDs are different. This can be fixed, however.


Once all these conditions are met you would issue the command -

load database <dbname> from "/path to/dump file name"

Replace <dbname> with the name of your target database. The filename
should include its path. (The example assumes you are on a Unix or
Linux system. On Windoze you would use "d:\path to\dump file name".
Replace "d:" with your drive letter.)

If the dump file isn't valid you will see a message. You'll
also see other error messages if there are problems or normal
messages if its OK. Here's an example -

Server Message: Number 3216, Severity 10
Server 'XXX', Line 1:
Backup Server session id is: 45. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume change
request from the Backup Server.
Server Message: Number 602801, Severity 1
Server 'XXX_BS', Procedure 'bs_read_header', Line 0:
Backup Server: 6.28.1.1: Dumpfile name 'ta_test05139083D3' section number 1
mounted on disk file '/path to/dump_file.db'
Server Message: Number 405801, Severity 1
Server 'VCT_BS', Procedure 'bs_perform_load', Line 0:
Backup Server: 4.58.1.1: Database data_test: 59592 kilobytes LOADed.
...

Once the load completes without error, you would issue this
command -

online database <dbname>

This brings it online and upgrades it if required.

NOTE: I didn't mention dumps stripes or compression etc.

-am © 2005
gopal

2005-05-22, 3:23 am

Hi ,

I am really thankful for the commands, especially to anthony, yes when
i try loading the dumps i get the message as mentioend by Anthony.

Apart from this, i am newbie to sybase installation and i have real
problems setting it up.

I have version sybase 12.5 and O/S is Windows NT Server

When i install it the instllation compelted and it asks if you want to
rebbot the syatem so that instllation is complete,but after rebooting
when it is completing, it crashes

I really dont know how to proceed becuase i have tried installation
more than 10 times..

Anthony Mandic wrote:
> gopal wrote:
>
> What Michael and Bill said but you need all these things -
>
> ASE should be running (I assume you mean ASE. Sybase have 3
> different database products. If its ASA or ASIQ, please say so).
>
> Backup Server connected to ASE should be running
>
> Your dump should be at the same version of ASE or a supported
> earlier version (supported earlier versions will be upgraded).
> Newer versions won't load unless they are minor revision numbers
> and ASE knows how to deal with them. You'll see a message like
> "Database 'XXX' is now online with a lower server version number.
> Refer to the higher version release notes on the limitations
> of backward compatibility."
>
> The dump must be of the same platform (for binary compatibility.
> This advice doesn't apply to the new cross platform dump feature).
>
> The target database must be of the same size or larger in order
> to hold the loaded database. A smaller database won't support
> the load.
>
> The segment layout need not match. The load will change fragments
> as needed. Sometimes this leads to unexpected results. Other times
> its useful in that it coalesces adjoining like fragments. One large
> single device helps here if you don't know the layout. You may see
> a message like "Caution: You have set up this database to include
> space on disk NNN for both data and the transaction log. This can
> make recovery impossible if that disk fails." This is useful in
> that you can learn the original layout.
>
> You need to be "sa" or have the required role to do a load.
>
> The sysusers table in the loaded database may get changed if logins
> don't exist or the IDs are different. This can be fixed, however.
>
>
> Once all these conditions are met you would issue the command -
>
> load database <dbname> from "/path to/dump file name"
>
> Replace <dbname> with the name of your target database. The filename
> should include its path. (The example assumes you are on a Unix or
> Linux system. On Windoze you would use "d:\path to\dump file name".
> Replace "d:" with your drive letter.)
>
> If the dump file isn't valid you will see a message. You'll
> also see other error messages if there are problems or normal
> messages if its OK. Here's an example -
>
> Server Message: Number 3216, Severity 10
> Server 'XXX', Line 1:
> Backup Server session id is: 45. Use this value when executing the
> 'sp_volchanged' system stored procedure after fulfilling any volume

change
> request from the Backup Server.
> Server Message: Number 602801, Severity 1
> Server 'XXX_BS', Procedure 'bs_read_header', Line 0:
> Backup Server: 6.28.1.1: Dumpfile name 'ta_test05139083D3' section

number 1
> mounted on disk file '/path to/dump_file.db'
> Server Message: Number 405801, Severity 1
> Server 'VCT_BS', Procedure 'bs_perform_load', Line 0:
> Backup Server: 4.58.1.1: Database data_test: 59592 kilobytes LOADed.
> ...
>
> Once the load completes without error, you would issue this
> command -
>
> online database <dbname>
>
> This brings it online and upgrades it if required.
>
> NOTE: I didn't mention dumps stripes or compression etc.
>=20
> -am =A9 2005


Anthony Mandic

2005-05-22, 7:23 am

gopal wrote:
>
> I am really thankful for the commands, especially to anthony, yes when
> i try loading the dumps i get the message as mentioend by Anthony.


Which particular message do you get?

> Apart from this, i am newbie to sybase installation and i have real
> problems setting it up.
>
> I have version sybase 12.5 and O/S is Windows NT Server


It might be an idea to download a later EBF (patch) from
Sybase's web site.

> When i install it the instllation compelted and it asks if you want to
> rebbot the syatem so that instllation is complete,but after rebooting
> when it is completing, it crashes


There should be a message in the Sybase ASE's errorlog that
says way. Find it and post it. You will find it under your
Sybase installation directory under ASE12*\install\<servername>.log.
The last lines in the file will have the error message.

> I really dont know how to proceed becuase i have tried installation
> more than 10 times..


Patching it might help. Actually, I'm not certain if ASE 12.5
supports NT. It probably does but it might only support 2000
and 2003. Alternately, check if you have the latest NT service
pack installed. The ASE release bulletin should discuss it.

-am © 2005
gopal

2005-05-22, 7:23 am

I am getting Java.EXE Application Error window message

gopal

2005-05-22, 7:23 am

Hi, when i am configuring the different servers namely

pcib07634_HS, pcib07634_MS, pcib07634_XP, when i start running these as
services, i am unable to run it..

Anthony Mandic

2005-05-23, 3:23 am

gopal wrote:
>
> I am getting Java.EXE Application Error window message


From what? The Install Shield installation program or from
something else?

-am © 2005
Anthony Mandic

2005-05-23, 3:23 am

gopal wrote:
>
> Hi, when i am configuring the different servers namely
>
> pcib07634_HS, pcib07634_MS, pcib07634_XP, when i start running these as
> services, i am unable to run it..


Look in the errorlog of the ASE server (as I described in an
earlier post). It should have a message explaining why. Post that.

-am © 2005
Michael Peppler

2005-05-23, 7:23 am

On Fri, 20 May 2005 23:30:45 -0700, gopal wrote:

> Hi i have database dumps named as "train_2005_03_21.bkp"
>
> I dont how to load this back into database -sybase obviously
>
> Pls help me out with exact command


load database <dbname> from "<dump file>"

You'll need to have a database that is large enough for the load to work.

Michael
--
Michael Peppler - mpeppler@peppler.org - http://www.peppler.org/
Sybase DBA/Developer
Sybase on Linux FAQ: http://www.peppler.org/FAQ/linux.html


gopal

2005-05-23, 9:23 am

Hi I try the following load command

load database train
from "e:/train_2005_03_21"

and i get the foll message

Server Message: Number 3216, Severity 10
Server 'PCIB07634', Line 1:
Backup Server session id is: 11. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume
change request from the Backup Server.
Server Message: Number 402602, Severity 2
Server 'PCIB07634_BS', Procedure 'bs_read_header', Line 0:
Backup Server: 4.26.2.1: Volume validation error: failed to obtain
device information, device: e:/train_2005_03_21 error: No such file or
directory.
Server Message: Number 8009, Severity 16
Server 'PCIB07634', Line 1:
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

Anthony Mandic

2005-05-23, 11:23 am

gopal wrote:
>
> Hi I try the following load command
>
> load database train
> from "e:/train_2005_03_21"
>
> and i get the foll message
>
> Server Message: Number 3216, Severity 10
> Server 'PCIB07634', Line 1:
> Backup Server session id is: 11. Use this value when executing the
> 'sp_volchanged' system stored procedure after fulfilling any volume
> change request from the Backup Server.
> Server Message: Number 402602, Severity 2
> Server 'PCIB07634_BS', Procedure 'bs_read_header', Line 0:
> Backup Server: 4.26.2.1: Volume validation error: failed to obtain
> device information, device: e:/train_2005_03_21 error: No such file or
> directory.


Use "\" as the path separator on windows rather than "/".
So your filename should be "e:\train_2004_03_21.bkp"
(you'll also need the file extension).

-am © 2005
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com