• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 496
  • Last Modified:

sybase 12.5 install a another instance: HP-UX

experts,

has anyone installed dual instances of sybase 12.5 on the same server? any idea of the process for this? it's on an HP-UX platform. I'm a windows MS SQL man myself, so am a little worried about going ahead with an install without the proper knowledge. I'm working my way through the Install guide, but am yet to find anything on a dual install on the same server.

any help would be much appreciated.
0
telliot79
Asked:
telliot79
  • 4
  • 4
3 Solutions
 
Joe WoodhousePrincipal ConsultantCommented:
If they will always run exactly the same version (ie. if you patch/upgrade one, both get patched or upgraded) then this is easy. You install as usual, and then you just create a second instance. Yep, it really is that simple. They both use the same UNIX account, which uses the same environment, paths etc.

Each server has its own RUN_SERVER file, each has its own devices etc, they get an entry each in the interfaces file.

It gets more complicated if you want them to be able to be independent. The best way there is two different directories. You'll then need some way of sourcing a different profile (to set the environment variables to the correct directory(ies)) depending on which one you want to work with.
0
 
telliot79Author Commented:
they don't need to be independent, just need to be running alongside each other. you say, "you install as usual" unfortunatly, I've not installed before, so i'm still a little unsure. I've search most of google and looks like I should use srvbuildres to run this install. is this correct? i'm doing this all from command line as well which is making me realise I'm not such an IT guru.

thanks for the help.
0
 
Joe WoodhousePrincipal ConsultantCommented:
Take a look at the install docs on the Sybase site. You use srvbuildres only for a command-line install. You have to edit a "resource file" which has all the information you'll normally be asked during an interactive install.

If you've never installed Sybase ASE before then you have a number of things to decide before you start - network ports, where the important device files will be and how large, etc.

There is a sample resource file you can copy (and then edit the copies) available at $SYBASE/init/* (I think - doing this from memory).

You really really need to read through the docs first. Forget Google, just go straight to Sybase at http://infocenter.sybase.com/help/topic/com.sybase.dc35890_1254/pdf/installhp.pdf

Note appendix A discusses how to use resource files.

I should also point out in case you're not aware that 12.5 is unsupported and has been for some time.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
telliot79Author Commented:
this is helping. you've confirmed pretty much what I had thought. i should have said, we have our initial instance of sybase installed, I've just got to create a new copy for another testing instance.

and yes, I'm aware 12.5 isn't supported. We'll be migrating to MS SQL at some point in the near future I believe.
0
 
Joe WoodhousePrincipal ConsultantCommented:
"Creating a copy" also means copying databases and the ASE configuration, so you'll have a few more steps beyond simply creating a second instance. None of that is difficult, you just have to remember to do it, and do it correctly. :)
0
 
telliot79Author Commented:
sounds difficult enough... i like my wizards..... next, next, finish.

let me just get my fingers in this document and then i'll award points. thanks again for the help and prompt responses.
0
 
Joe WoodhousePrincipal ConsultantCommented:
Just to set out what a "copy" means:

- create devices the same sizes
- create databases the same sizes, created exactly the same way on the devices (same fragments, same sizes, created in the same order - not actually necessary but so much easier this way)
- dump the databases from the original instance
- load the databases into the copy
- copy the config file from the original - do this while the copy is down, and make sure you have enough resources

You don't have to copy the config but then you won't have a copy...

Good luck! Sorry to hear your site is moving to MS SQL.
0
 
telliot79Author Commented:
Thanks for all the help Joe.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now