Understand the big picture ...

[Jep]

We plan for 1 (big) server to host both a production and test database
for a system, and some other small db's. Databases to be put on a SAN.

But I don't understand the topics concerning installation and
administration. What can I do and what can't I do, when multiple
databases reside on the same server.

Can there be a setup, so that the test database can be stopped/started
without interupting the production database ??

There must be some Administrative topics I ought to know about??

/Jep

[Jep]

Maybe it is INSTANCE(s) I'm looking for. Can there be more than one
instance on the same server ?? And how do I create these ??

[Knut Stolze]

Jep <do**********@j epweb.dk> wrote:

Maybe it is INSTANCE(s) I'm looking for. Can there be more than one
instance on the same server ??
Yes.
And how do I create these ??

With the command "db2icrt".

--
Knut Stolze
Information Integration
IBM Germany / University of Jena

[Joseph,,,]

In a perfect world, you should like to have a separate server for
production and test systems. If that is not currently feasible, then
I would recommend creating a separate instance of DB2 for your test
databases. It can be a single server and single software installation.
A separate instance is a separate running copy of the DBMS server, listening
on a separate port for connections, and managing its own databases.

This will allow you to stop and start the test and production systems
separately, and also to test changes in the database manager configuration
on the test system isolated from your production databases. It will also
allow you to enforce different security policies in your test and production
systems-- for instance, where I work, all of our DBAs have SYSADM authority
on test instances, but only the DBAs with primary responsibility for DB2
administration have SYSADM on the production instances. You also can
do things like give DBAs SYSCTRL on production systems instead of SYSADM
if the data is sensitive and should be kept confidential from system
administrators.

Hope that helps,

Joseph

Jep <do**********@j epweb.dk> writes:

We plan for 1 (big) server to host both a production and test database
for a system, and some other small db's. Databases to be put on a SAN. But I don't understand the topics concerning installation and
administration . What can I do and what can't I do, when multiple
databases reside on the same server. Can there be a setup, so that the test database can be stopped/started
without interupting the production database ?? There must be some Administrative topics I ought to know about?? /Jep

[P. Saint-Jacques]

Given answers in other notes, build an instance for each db. Each
instance can be started and stopped independently of each other.
When you create the db, I'd create one (prod or test, doesn't matter)
and define it completely.
Once defined and before you populate, backup the db and restore it as
new in the other instance.
You will have to redirect each tablespace container definition as they
cannot coexist in the same defined targets.
HTH, Pierre.

Jep wrote:

We plan for 1 (big) server to host both a production and test database
for a system, and some other small db's. Databases to be put on a SAN.

But I don't understand the topics concerning installation and
administration. What can I do and what can't I do, when multiple
databases reside on the same server.

Can there be a setup, so that the test database can be stopped/started
without interupting the production database ??

There must be some Administrative topics I ought to know about??

/Jep

--
Pierre Saint-Jacques
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.

[Jep]

Thanks a lot - I'm getting closer.

Now I succeded making a new INSTANCE. But I can't create a new
database. It says DB2START not performed. Stop/start makes no
difference.

How do I Start/Stop these instances seperately?? Using the manual on
DB2START mentions node's ?? But what I expected is Instances!

/Jep

[Mark A]

"Jep" <do**********@j epweb.dk> wrote in message
news:d3******** *************** *********@4ax.c om...

Thanks a lot - I'm getting closer.

Now I succeded making a new INSTANCE. But I can't create a new
database. It says DB2START not performed. Stop/start makes no
difference.

How do I Start/Stop these instances seperately?? Using the manual on
DB2START mentions node's ?? But what I expected is Instances!

/Jep

The node name is really an alias for the node/instance. For example, see the
CATALOG LOCAL NODE in the Command Reference guide.

[Sean McKeough]

The "DB2INSTANC E" env variable will control which instance you're
starting/stopping.

Jep wrote:

Thanks a lot - I'm getting closer.

Now I succeded making a new INSTANCE. But I can't create a new
database. It says DB2START not performed. Stop/start makes no
difference.

How do I Start/Stop these instances seperately?? Using the manual on
DB2START mentions node's ?? But what I expected is Instances!

/Jep

[P. Saint-Jacques]

Go to a command window and issue:
db2 get instance
The answer will give you the name of the instance you are currently
attached to. Then issue
db2start ---- This will start that instance.
Then issue the command:
set db2instance=oth erinstancename
db2start
You now havw both instances started.
Use the set db2instance command to ensure you are in the proper instance
that you are concerned with and then issue
db2 create d dbanme ......

Note that in this set up, when you are attached to one instance, you do
not "see" the other instance's objects unless you catalog them properly
in the current instance.
For explanations to this and other issues that may come up, I'd highly
recommend you read the Quick Beginnings Manual for DB2 on the OS that
you are using and then refer to the DB2 Admin. Guide.
We can help you a lot here but some basics are expected and it makes vry
long replies to explain the manual.
HTH, Pierre.
Jep wrote:

Thanks a lot - I'm getting closer.

Now I succeded making a new INSTANCE. But I can't create a new
database. It says DB2START not performed. Stop/start makes no
difference.

How do I Start/Stop these instances seperately?? Using the manual on
DB2START mentions node's ?? But what I expected is Instances!

/Jep

--
Pierre Saint-Jacques
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.