SEO

Hi all

I will be moving Sybase from one Solaris server into another Solaris
server, the IP address and box name will be different. Sybase version
is 12.0 and O/S is 5.8. Does any one know what I need to do in order
to get Sybase up and running again on the new server.

Thanks
Teresa

"Teresa" <tpreto7@sapo.pt> wrote in message
news:6dabc692.0402261357.485192ad@posting.google.c om...
> Hi all
>
> I will be moving Sybase from one Solaris server into another Solaris
> server, the IP address and box name will be different. Sybase version
> is 12.0 and O/S is 5.8. Does any one know what I need to do in order
> to get Sybase up and running again on the new server.

Very roughly, install Sybase from scratch (with same version and EBF) on the
new server and duplicate (at least) the size of master, tempdb and
sybystemprocs. Any user-defined types in model or any extra stored
procedures in sybsystemprocs have to be also copied over. For the syslogins
in the source server, bcp them out and into the target server (except for sa
and anything else in the fresh server). For your databases, look at the way
they were built by looking at sysusages. Your target server should have the
databases in the same creation format as the source server. For each
database, run 'select segmap,size/512 from sysusages where dbid=<dbid>'
where the dbid is found in sysdatabases. Segmap 3=data, 4=log, 7=data+log.
You'll want to duplicate the order of creation of these fragments on your
target server. Eg, if you see 4 data fragments followed by 1 log fragment
followed by 2 data fragments, then on your target server you can run 'create
database mydb on datadev=<value big enough to hold those 4 data fragments>
log on <size of that 1st log segment> for load'. Then 'alter database on
datadev2=<big enough to hold the next 2 data fragments> for load'. And so
forth. Then you can dump your database on the source server and load it into
the target server.

Also, dont forget about the configuration found in sp_configure. Stuff like
total memory, etc has to be on a par with the source server. Pool caches
also are not to be forgotten.

Very rushed but I hope that helps in some way.

Martin

tpreto7@sapo.pt (Teresa) wrote in message news:<6dabc692.0402261357.485192ad@posting.google. com>...
> Hi all
>
> I will be moving Sybase from one Solaris server into another Solaris
> server, the IP address and box name will be different. Sybase version
> is 12.0 and O/S is 5.8. Does any one know what I need to do in order
> to get Sybase up and running again on the new server.
>
> Thanks
> Teresa

Note that if the platform (Solaris) is not changing, and you are using
OS file devices, you can simply copy the device files over to the new
server (after shutting down the source ASE).

First, copy the Sybase SW, then create the new interfaces entry, copy
over the RUN_ and .cfg files (and logs if you want to keep them), then
copy all the device files into identical directory structures*
(because that's where Master will look for them) and you're good to
go.

*If this isn't possible, put -T3608 (recover master only) in the RUN_
file and set "allow updates" in .cfg to 1, then boot ASE and update
sysdevices to set the phynames to their new values. Remove -T3608 and
restart ASE.

Cheerio

mcintma@yahoo.com (Marc M) wrote in message news:<4dcfc40.0402270819.defdd70@posting.google.co m>...
> tpreto7@sapo.pt (Teresa) wrote in message news:<6dabc692.0402261357.485192ad@posting.google. com>...
> > Hi all
> >
> > I will be moving Sybase from one Solaris server into another Solaris
> > server, the IP address and box name will be different. Sybase version
> > is 12.0 and O/S is 5.8. Does any one know what I need to do in order
> > to get Sybase up and running again on the new server.
> >
> > Thanks
> > Teresa
>
> Note that if the platform (Solaris) is not changing, and you are using
> OS file devices, you can simply copy the device files over to the new
> server (after shutting down the source ASE).
>
> First, copy the Sybase SW, then create the new interfaces entry, copy
> over the RUN_ and .cfg files (and logs if you want to keep them), then
> copy all the device files into identical directory structures*
> (because that's where Master will look for them) and you're good to
> go.
>
> *If this isn't possible, put -T3608 (recover master only) in the RUN_
> file and set "allow updates" in .cfg to 1, then boot ASE and update
> sysdevices to set the phynames to their new values. Remove -T3608 and
> restart ASE.
>
> Cheerio

Thank you very much
that is what I though,
I'm using raw devices which should be the same, also both serves
reside on the same disk array. The plan is to just copy the entire
server over to target. But don't I have to update a system table? I'm
not sure ... O/S remains the same only the patch level is different
Thanks again
Teresa