RE: Reducing the number of databases

[Saira Somani-Mendelin]

Title: Message









Unfortunately, that’s what we
have! And yes, my resume is on-line Our database configuration and
installation was outsourced and so was the installation of our ERP. So guess
what happened? No consultation with the “support analyst” and now
they want to split the schemas into multiple instances. Go figure J

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mladen
Gogala
Sent: September 19, 2003 2:40 PM
To: Multiple recipients of list
ORACLE-L
Subject: RE: Reducing the number
of databases

 



Additional
money might be saved by having only one database which would assume the role of
QA, development and





production.
That would mean that developers test in production and their own QA. You can
save a bundle on oracle





licenses
that way. In addition to that, if you switch to noarchivelog mode, you can save
a small fortune on the backup





tapes. Smart
thing to do in that situation would be to put your resume online before stuff
hits the fan.





 





 



--
Mladen Gogala
Oracle DBA 



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Guang
Mei
Sent: Friday, September 19, 2003
2:00 PM
To: Multiple recipients of list
ORACLE-L
Subject: RE: Reducing the number
of databases



Here we have 3 environments for most applications (dev, QA
and prod) and all Oracle version are the same (8173 now). It works fine.
And to save Oracle license costs, we also consolidated some db servers
by putting multiple instances on one server machine. No problem
so far.





 





Guang





-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of AK
Sent: Friday, September 19, 2003
12:50 PM
To: Multiple recipients of list
ORACLE-L
Subject: Re: Reducing the number
of databases



I have seen more requirement for
individual development databases ( where ind schema is not possible ) due to
complexity of application . Developers step on each other if they work of same
database . A pl/sql developer is invalidating procedure while a java developer
is trying to make his program work. 





 





-ak





 





 







- Original Message - 





From: Stephane Paquette 





To: Multiple
recipients of list ORACLE-L 





Sent: Friday,
September 19, 2003 8:59 AM





Subject: Reducing
the number of databases





 





Hi,





 





We have around 120 databases. Most
applications have 5 environments (dev, test, integrated test, acceptance, prod)
some applications have more. The applications are a mix of home developped
and bought application (peoplesoft, harvest, compass,...)





New applications are coming in.





New databases will appear soon with
DB2UDB.





 





All servers are unix/aix, there
are 15 production server and around 10 servers for the dev, test,
integrated test and  acceptance databases.





All databases are at 8172 except 6-7
databases and planning to go to 9i in 2004. Off course we see the migration
like a pain.





 





We want to reduce the number of
databases and instances.





To obtain a significative gain I
think we must reduced to around 60 databases.





 





Anybody has done the task to
consolidate on less servers and les databases ?





 





One way to do it would be to go with






    2 instances
of dev





    2 instances
of test





    2 instances
of integrated test





    2 instances
of acceptance





all prod
instances are standalone.





 





Food for thought





    backup





    Oracle
version





    availability





    naming
convention of objects





    security





    ...





 





All feedback is welcome.





 







Stephane
Paquette

Administrateur de bases de donnees

Database Administrator

Standard Life

www.standardlife.ca

Tel. (514) 499-7999 poste 7470 et (514) 925-7187

[EMAIL PROTECTED]







 











 





Note:





This message is for the
named person's use only.  It may contain confidential, proprietary or
legally privileged information.  No confidentiality or privilege is waived
or lost by any mistransmission.  If you receive this message in
error, please immediately delete it and all copies of it from your system,
destroy any hard copies of it and notify the sender.  You must not,
directly or indirectly, use, disclose, distribute, print, or copy any part of
this message if you are not the intended recipient. Wang Trading
LLC and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.  Any
views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorized to state them
to be the views of any such entity.





 





 

RE: Reducing the number of databases

[Guang Mei]

Title: Message



Thanks for the suggestions. I already have planned to move all our 
instances to one server and move all schemas (in all instances) to sys schema. 
This way I can have better use of system tablespace and drop all other 
tablespaces. Also I will put in a cron job to "rm" all database files every 
morning to save some disk spaces.
 
Guang

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of Mladen 
  GogalaSent: Friday, September 19, 2003 2:40 PMTo: 
  Multiple recipients of list ORACLE-LSubject: RE: Reducing the 
  number of databases
  Additional money might be saved by having only one 
  database which would assume the role of QA, development 
and
  production. That would mean that developers test in 
  production and their own QA. You can save a bundle on 
  oracle
  licenses that way. In addition to that, if you switch 
  to noarchivelog mode, you can save a small fortune on the 
  backup
  tapes. Smart thing to do in that situation would be 
  to put your resume online before stuff hits the fan.
   
   
  --Mladen GogalaOracle DBA 
  

-Original Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
Guang MeiSent: Friday, September 19, 2003 2:00 
PMTo: Multiple recipients of list ORACLE-LSubject: RE: 
    Reducing the number of databases
Here we have 3 environments for most applications (dev, 
QA and prod) and all Oracle version are the same (8173 now). It works 
fine. And to save Oracle license costs, we also consolidated some db servers 
by putting multiple instances on one server machine. No 
problem so far.
 
Guang

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of AKSent: 
  Friday, September 19, 2003 12:50 PMTo: Multiple recipients of 
  list ORACLE-LSubject: Re: Reducing the number of 
  databases
  I have seen more requirement for individual 
  development databases ( where ind schema is not possible ) due to 
  complexity of application . Developers step on each other if they work of 
  same database . A pl/sql developer is invalidating procedure while a java 
  developer is trying to make his program work. 
   
  -ak
   
   
  
- Original Message - 
From: 
Stephane Paquette 

To: Multiple recipients of list 
ORACLE-L 
Sent: Friday, September 19, 2003 
8:59 AM
Subject: Reducing the number of 
databases

Hi,
 
We have 
around 120 databases. Most applications have 5 environments (dev, test, 
integrated test, acceptance, prod) some applications have 
more. The 
applications are a mix of home developped and bought application 
(peoplesoft, harvest, compass,...)
New 
applications are coming in.
New 
databases will appear soon with DB2UDB.
 
All servers 
are unix/aix, there are 15 production server 
and around 10 servers for the dev, test, integrated test and 
 acceptance databases.
All 
databases are at 8172 except 6-7 databases and planning to go to 9i in 
2004. Off course we see the migration like a pain.
 
We want to 
reduce the number of databases and instances.
To obtain a 
significative gain I think we must reduced to around 60 
databases.
 
Anybody has 
done the task to consolidate on less servers and les databases 
?
 
One way to 
do it would be to go with 
    2 instances of dev
    2 instances of test
    2 instances of integrated test
    2 instances of acceptance
all prod instances are standalone.
 
Food for 
thought
    backup
    Oracle version
    availability
    naming convention of objects
    security
    ...
 
All feedback is welcome.
 


Stephane 
Paquette
Administrateur 
de bases de donnees
Database 
Administrator
Standard 
Life
www.standardlife.ca
Tel. (514) 499-7999 poste 7470 et (514) 
925-7187
[EMAIL PROTECTED]
 
   
  Note:
  This message is for the named person's use only.  It may contain 
  confidential, proprietary or legally privileged information.  No 
  confidentiality or privilege is waived or lost by any mistransmission.  
  If you receive this message in error, please immediately delete it and 
  all copies of it from your system, destroy any hard copies of it and notify 
  the sender.  You must not, directly or indirectly, use, disclose, 
  distribute, print, or copy any part of this message if 

RE: Reducing the number of databases

[Mladen Gogala]

Title: Message



Additional money might be saved by having only one 
database which would assume the role of QA, development and
production. That would mean that developers test in 
production and their own QA. You can save a bundle on oracle
licenses that way. In addition to that, if you switch 
to noarchivelog mode, you can save a small fortune on the 
backup
tapes. 
Smart thing to do in that situation would be to put your resume online before 
stuff hits the fan.
 
 
--Mladen GogalaOracle DBA 

  
  -Original Message-From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Guang 
  MeiSent: Friday, September 19, 2003 2:00 PMTo: Multiple 
  recipients of list ORACLE-LSubject: RE: Reducing the number of 
  databases
  Here we have 3 environments for most applications (dev, QA 
  and prod) and all Oracle version are the same (8173 now). It works fine. 
  And to save Oracle license costs, we also consolidated some db servers 
  by putting multiple instances on one server machine. No problem 
  so far.
   
  Guang
  
-Original Message-From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]On Behalf Of AKSent: Friday, 
September 19, 2003 12:50 PMTo: Multiple recipients of list 
ORACLE-LSubject: Re: Reducing the number of 
databases
I have seen more requirement for individual 
development databases ( where ind schema is not possible ) due to complexity 
of application . Developers step on each other if they work of same database 
. A pl/sql developer is invalidating procedure while a java developer is 
trying to make his program work. 
 
-ak
 
 

  - Original Message - 
  From: 
  Stephane Paquette 
  
  To: Multiple recipients of list 
  ORACLE-L 
  Sent: Friday, September 19, 2003 8:59 
  AM
  Subject: Reducing the number of 
  databases
  
  Hi,
   
  We have around 
  120 databases. Most applications have 5 environments (dev, test, 
  integrated test, acceptance, prod) some applications have 
  more. The 
  applications are a mix of home developped and bought application 
  (peoplesoft, harvest, compass,...)
  New 
  applications are coming in.
  New databases 
  will appear soon with DB2UDB.
   
  All servers 
  are unix/aix, there are 15 production server and 
  around 10 servers for the dev, test, integrated test and  acceptance 
  databases.
  All databases 
  are at 8172 except 6-7 databases and planning to go to 9i in 2004. Off 
  course we see the migration like a pain.
   
  We want to 
  reduce the number of databases and instances.
  To obtain a 
  significative gain I think we must reduced to around 60 
  databases.
   
  Anybody has 
  done the task to consolidate on less servers and les databases 
  ?
   
  One way to do 
  it would be to go with 
      2 instances of dev
      2 instances of test
      2 instances of integrated test
      2 instances of acceptance
  all prod instances are standalone.
   
  Food for 
  thought
      backup
      Oracle version
      availability
      naming convention of objects
      security
      ...
   
  All feedback is welcome.
   
  
  
  Stephane 
  Paquette
  Administrateur 
  de bases de donnees
  Database 
  Administrator
  Standard 
  Life
  www.standardlife.ca
  Tel. (514) 499-7999 poste 7470 et (514) 
  925-7187
  [EMAIL PROTECTED]
   
 
Note:
This message is for the named person's use only.  It may contain 
confidential, proprietary or legally privileged information.  No 
confidentiality or privilege is waived or lost by any mistransmission.  If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender.  You must not, directly or indirectly, use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Wang Trading 
LLC and any of its subsidiaries each reserve the right to 
monitor all e-mail communications through its networks.  Any views 
expressed in this message are those of the individual sender, except where the 
message states otherwise and the sender is authorized to state them to be the 
views of any such entity.
 
 

RE: Reducing the number of databases

[Guang Mei]

Here 
we have 3 environments for most applications (dev, QA and prod) and 
all Oracle version are the same (8173 now). It works fine. And to save Oracle 
license costs, we also consolidated some db servers by putting multiple 
instances on one server machine. No problem so 
far.
 
Guang

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of AKSent: Friday, 
  September 19, 2003 12:50 PMTo: Multiple recipients of list 
  ORACLE-LSubject: Re: Reducing the number of 
  databases
  I have seen more requirement for individual 
  development databases ( where ind schema is not possible ) due to complexity 
  of application . Developers step on each other if they work of same database . 
  A pl/sql developer is invalidating procedure while a java developer is trying 
  to make his program work. 
   
  -ak
   
   
  
- Original Message - 
From: 
Stephane Paquette 
To: Multiple recipients of list ORACLE-L 

Sent: Friday, September 19, 2003 8:59 
AM
Subject: Reducing the number of 
databases

Hi,
 
We have around 
120 databases. Most applications have 5 environments (dev, test, integrated 
test, acceptance, prod) some applications have more. The applications are a mix 
of home developped and bought application (peoplesoft, harvest, 
compass,...)
New applications 
are coming in.
New databases 
will appear soon with DB2UDB.
 
All servers are 
unix/aix, there are 15 production server and around 10 servers for the dev, 
test, integrated test and  acceptance databases.
All databases 
are at 8172 except 6-7 databases and planning to go to 9i in 2004. Off 
course we see the migration like a pain.
 
We want to 
reduce the number of databases and instances.
To obtain a 
significative gain I think we must reduced to around 60 
databases.
 
Anybody has done 
the task to consolidate on less servers and les databases 
?
 
One way to do it 
would be to go with 
    2 instances of dev
    2 instances of test
    2 instances of integrated test
    2 instances of acceptance
all prod instances are standalone.
 
Food for 
thought
    backup
    Oracle version
    availability
    naming convention of objects
    security
    ...
 
All feedback is 
welcome.
 


Stephane 
Paquette
Administrateur 
de bases de donnees
Database 
Administrator
Standard 
Life
www.standardlife.ca
Tel. (514) 499-7999 poste 7470 et (514) 
925-7187
[EMAIL PROTECTED]
 

RE: Reducing the number of databases

[DENNIS WILLIAMS]

As long as your management doesn't base its decisions on the ratio of
databases per DBA. Otherwise, you may cut the number of databases and then
management will say "why do we need so many DBAs.
 
I can see performing server consolidation. That can reap a real ROI in terms
of Oracle licensing.
 
When you talk of reducing the number of test databases, that worries me.
There was probably a reason these were created in the first place. Probably
to support quality procedures. So if you eliminate some databases, does that
mean some quality steps are skipped? 
 
If you combine databases, you must make sure that the applications are
compatible. Do they have the same uptime requirements? With 3rd party
applications, you are often restricted by the vendor's support for specific
Oracle versions. If you put two applications in the same database, then you
can only upgrade that database if both applications will support the Oracle
version you are upgrading to.
 
Any change involves weighing the effort, risks, and benefits (a.k.a. ROI).
In database consolidation of existing applications, you must weigh the
amount of effort and risks against the benefits you feel you will receive.
With new applications there isn't nearly as much involved in the decision. I
don't know if this is what you had in mind. Fortunately I haven't had a
management-mandated server consolidation project yet.



Dennis Williams 
DBA, 80%OCP, 100% DBA 
Lifetouch, Inc. 
[EMAIL PROTECTED] 

-Original Message-
Sent: Friday, September 19, 2003 11:00 AM
To: Multiple recipients of list ORACLE-L


Hi,
 
We have around 120 databases. Most applications have 5 environments (dev,
test, integrated test, acceptance, prod) some applications have more. The
applications are a mix of home developped and bought application
(peoplesoft, harvest, compass,...)
New applications are coming in.
New databases will appear soon with DB2UDB.
 
All servers are unix/aix, there are 15 production server and around 10
servers for the dev, test, integrated test and  acceptance databases.
All databases are at 8172 except 6-7 databases and planning to go to 9i in
2004. Off course we see the migration like a pain.
 
We want to reduce the number of databases and instances.
To obtain a significative gain I think we must reduced to around 60
databases.
 
Anybody has done the task to consolidate on less servers and les databases ?
 
One way to do it would be to go with 
2 instances of dev
2 instances of test
2 instances of integrated test
2 instances of acceptance
all prod instances are standalone.
 
Food for thought
backup
Oracle version
availability
naming convention of objects
security
...
 
All feedback is welcome.
 

Stephane Paquette


Administrateur de bases de donnees

Database Administrator

Standard Life

www.standardlife.ca

Tel. (514) 499-7999 poste 7470 et (514) 925-7187

[EMAIL PROTECTED] 


 

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: DENNIS WILLIAMS
  INET: [EMAIL PROTECTED]

Fat City Network Services-- 858-538-5051 http://www.fatcity.com
San Diego, California-- Mailing list and web hosting services
-
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Re: Reducing the number of databases

[AK]

I have seen more requirement for individual 
development databases ( where ind schema is not possible ) due to complexity of 
application . Developers step on each other if they work of same database . A 
pl/sql developer is invalidating procedure while a java developer is trying to 
make his program work. 
 
-ak
 
 

  - Original Message - 
  From: 
  Stephane Paquette 
  To: Multiple recipients of list ORACLE-L 
  
  Sent: Friday, September 19, 2003 8:59 
  AM
  Subject: Reducing the number of 
  databases
  
  Hi,
   
  We have around 120 
  databases. Most applications have 5 environments (dev, test, integrated test, 
  acceptance, prod) some applications have more. The applications are a mix of 
  home developped and bought application (peoplesoft, harvest, 
  compass,...)
  New applications 
  are coming in.
  New databases will 
  appear soon with DB2UDB.
   
  All servers are 
  unix/aix, there are 15 production server and around 10 servers for the dev, 
  test, integrated test and  acceptance databases.
  All databases are 
  at 8172 except 6-7 databases and planning to go to 9i in 2004. Off course we 
  see the migration like a pain.
   
  We want to reduce 
  the number of databases and instances.
  To obtain a 
  significative gain I think we must reduced to around 60 
  databases.
   
  Anybody has done 
  the task to consolidate on less servers and les databases 
?
   
  One way to do it 
  would be to go with 
      2 instances of dev
      2 instances of test
      2 instances of integrated test
      2 instances of acceptance
  all prod instances are standalone.
   
  Food for 
  thought
      backup
      Oracle version
      availability
      naming convention of objects
      security
      ...
   
  All feedback is 
  welcome.
   
  
  
  Stephane 
  Paquette
  Administrateur 
  de bases de donnees
  Database 
  Administrator
  Standard 
  Life
  www.standardlife.ca
  Tel. (514) 499-7999 poste 7470 et (514) 
  925-7187
  [EMAIL PROTECTED]