RE: Database Instance

2003-12-26 Thread Kean Jacinta
Dear :All

Well we did not buy any application packages.
Currently  we are using open source product ...which
is Apache and Tomcat. 

By the way, have anyone ever have more than 5 database
under a single server ? I heard that the best practice
is to have 1 database n 1 application in a single
server. Is that true ?

Thank
JKean

--- Mercadante, Thomas F
[EMAIL PROTECTED] wrote:
 I would be very careful about doing this if you have
 purchased application
 packages.  Sooner or later, you will want to upgrade
 one of the packages,
 and it will require a different release of Oracle -
 and you will be stuck.
  
 
 Tom Mercadante 
 Oracle Certified Professional 
 
 -Original Message-
 Sent: Wednesday, December 24, 2003 11:24 AM
 To: Multiple recipients of list ORACLE-L
 
 
 One other disadvantage of putting all instances
 together is if you need to
 say bounce the database (for parameter change or
 other maintenance  etc)
 then all other applications will get affected.
 Whereas with separate
 instances other applications will not get affected. 
  
 To some extent one application failing will not
 affect other applications.
 Except if one application does not close its
 connections then it could lead
 to maximum connections (sessions) being reached and
 affecting other
 applications. 
  
 If the nature of the applications is different :
 OLTP, warehousing then you
 cannot really tune the parameters.
  
 On the positive side I think putting instances
 together will lead to some
 memory savings. 
  
 I would suggest : Do not worry about who wants to
 put the instances together
 just list the advantages, disadvantages and make the
 decision. 
 
 [EMAIL PROTECTED] wrote:
 
 
 It is not necessarily true that an error in one
 application will affect all
 applications. If there is a problem with oracle
 instance or the database,
 then all applications might be affected.
 
 Multiple schemas which have the same table names can
 be a problem. If your
 applications uses public synonyms, then you might
 have a big problem.
 
 If everything is working fine now, it seems
 pointless to move things around.
 But this is philosophy. I do believe that isolating
 applications from each
 other as much as possible is usually a good thing.
 Good fences make good neighbors. (usually)
 
 But, if your manager insists on it, you have no
 choice. Just do your best
 to keep the old stuff around in case it becomes
 apparent that the new way
 will not work and you must go back to the old way.
 
  -Original Message-
  Lately, m! y manager want me to remove all the
 databases
  and remain a single instance. I was wondering if i
  move everything into single database then if one
 of
  the application fail due to oracle error , then
 all
  other four application will fail also rite ? 
  
  Each of our web application needs to have 2 schema
 and
  both schema have to be transparent to each other.
  While other application schema will be invisible
 to
  each other. Since i have 5 web app then i will
 need 10
  schema.One major problem is all the 10 schema will
  contain same table name. It will be a mess putting
 so
  much app in a single db . 
  
  Pls correct me if i am wrong and do let me know
 what
  are the pro and cons or maybe you can educate me
 with
  some of the best practice to setup a proper
 production
  server environment.
  
  Thank You
  
  Regards,
  Jkean 
  
   
 -- 
 Please see the official ORACLE-L FAQ:
 http://www.orafaq.net
 -- 
 Author: 
 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).
 
 
 
   _  
 
 Do you Yahoo!?
 Free 

http://us.rd.yahoo.com/slv/mailtag/*http://companion.yahoo.com/
 Pop-Up Blocker - Get it now
 
 


__
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Kean Jacinta
  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: Database Instance

2003-12-26 Thread Sinardy Xing
Not quite true, in 3 tiers architecture, DB should last tier and application in middle 
tier.

Well depend on your company budget and the size of everything and consideration of 
high scalability system, and future upgrade.
Your manager, see everything from cost or license point of view, I believe they 
purchase Oracle base on number of running sessions. I believe for long run 5 Oracle 
databases maintenance quite expensive (in term of tangible cost), I don't know what is 
your company budget, can't comment much.

5 small databases may be ok in one box (exclude applications), but 5 big (or medium) 
databases then I have to disagree with your manager.


Sinardy

-Original Message-
Sent: 26 December 2003 14:59
To: Multiple recipients of list ORACLE-L


Dear :All

Well we did not buy any application packages.
Currently  we are using open source product ...which
is Apache and Tomcat. 

By the way, have anyone ever have more than 5 database
under a single server ? I heard that the best practice
is to have 1 database n 1 application in a single
server. Is that true ?

Thank
JKean

--- Mercadante, Thomas F
[EMAIL PROTECTED] wrote:
 I would be very careful about doing this if you have
 purchased application
 packages.  Sooner or later, you will want to upgrade
 one of the packages,
 and it will require a different release of Oracle -
 and you will be stuck.
  
 
 Tom Mercadante 
 Oracle Certified Professional 
 
 -Original Message-
 Sent: Wednesday, December 24, 2003 11:24 AM
 To: Multiple recipients of list ORACLE-L
 
 
 One other disadvantage of putting all instances
 together is if you need to
 say bounce the database (for parameter change or
 other maintenance  etc)
 then all other applications will get affected.
 Whereas with separate
 instances other applications will not get affected. 
  
 To some extent one application failing will not
 affect other applications.
 Except if one application does not close its
 connections then it could lead
 to maximum connections (sessions) being reached and
 affecting other
 applications. 
  
 If the nature of the applications is different :
 OLTP, warehousing then you
 cannot really tune the parameters.
  
 On the positive side I think putting instances
 together will lead to some
 memory savings. 
  
 I would suggest : Do not worry about who wants to
 put the instances together
 just list the advantages, disadvantages and make the
 decision. 
 
 [EMAIL PROTECTED] wrote:
 
 
 It is not necessarily true that an error in one
 application will affect all
 applications. If there is a problem with oracle
 instance or the database,
 then all applications might be affected.
 
 Multiple schemas which have the same table names can
 be a problem. If your
 applications uses public synonyms, then you might
 have a big problem.
 
 If everything is working fine now, it seems
 pointless to move things around.
 But this is philosophy. I do believe that isolating
 applications from each
 other as much as possible is usually a good thing.
 Good fences make good neighbors. (usually)
 
 But, if your manager insists on it, you have no
 choice. Just do your best
 to keep the old stuff around in case it becomes
 apparent that the new way
 will not work and you must go back to the old way.
 
  -Original Message-
  Lately, m! y manager want me to remove all the
 databases
  and remain a single instance. I was wondering if i
  move everything into single database then if one
 of
  the application fail due to oracle error , then
 all
  other four application will fail also rite ? 
  
  Each of our web application needs to have 2 schema
 and
  both schema have to be transparent to each other.
  While other application schema will be invisible
 to
  each other. Since i have 5 web app then i will
 need 10
  schema.One major problem is all the 10 schema will
  contain same table name. It will be a mess putting
 so
  much app in a single db . 
  
  Pls correct me if i am wrong and do let me know
 what
  are the pro and cons or maybe you can educate me
 with
  some of the best practice to setup a proper
 production
  server environment.
  
  Thank You
  
  Regards,
  Jkean 
  
   
 -- 
 Please see the official ORACLE-L FAQ:
 http://www.orafaq.net
 -- 
 Author: 
 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).
 
 
 
   _  
 
 Do you Yahoo!?
 Free 

http://us.rd.yahoo.com/slv/mailtag/*http://companion.yahoo.com/
 Pop-Up Blocker - Get it now
 
 



RE: Database Instance

2003-12-26 Thread Sinardy Xing
btw, Oracle 10g can add new servers to your database's tier like plug and play (same 
OS).
This is what the guy at Oracle 10g seminar told me. He said what an administrator need 
is Internet browser.


Sinardy

-Original Message-
Sent: 26 December 2003 15:14
To: '[EMAIL PROTECTED]'


Not quite true, in 3 tiers architecture, DB should last tier and application in middle 
tier.

Well depend on your company budget and the size of everything and consideration of 
high scalability system, and future upgrade.
Your manager, see everything from cost or license point of view, I believe they 
purchase Oracle base on number of running sessions. I believe for long run 5 Oracle 
databases maintenance quite expensive (in term of tangible cost), I don't know what is 
your company budget, can't comment much.

5 small databases may be ok in one box (exclude applications), but 5 big (or medium) 
databases then I have to disagree with your manager.


Sinardy

-Original Message-
Sent: 26 December 2003 14:59
To: Multiple recipients of list ORACLE-L


Dear :All

Well we did not buy any application packages.
Currently  we are using open source product ...which
is Apache and Tomcat. 

By the way, have anyone ever have more than 5 database
under a single server ? I heard that the best practice
is to have 1 database n 1 application in a single
server. Is that true ?

Thank
JKean

--- Mercadante, Thomas F
[EMAIL PROTECTED] wrote:
 I would be very careful about doing this if you have
 purchased application
 packages.  Sooner or later, you will want to upgrade
 one of the packages,
 and it will require a different release of Oracle -
 and you will be stuck.
  
 
 Tom Mercadante 
 Oracle Certified Professional 
 
 -Original Message-
 Sent: Wednesday, December 24, 2003 11:24 AM
 To: Multiple recipients of list ORACLE-L
 
 
 One other disadvantage of putting all instances
 together is if you need to
 say bounce the database (for parameter change or
 other maintenance  etc)
 then all other applications will get affected.
 Whereas with separate
 instances other applications will not get affected. 
  
 To some extent one application failing will not
 affect other applications.
 Except if one application does not close its
 connections then it could lead
 to maximum connections (sessions) being reached and
 affecting other
 applications. 
  
 If the nature of the applications is different :
 OLTP, warehousing then you
 cannot really tune the parameters.
  
 On the positive side I think putting instances
 together will lead to some
 memory savings. 
  
 I would suggest : Do not worry about who wants to
 put the instances together
 just list the advantages, disadvantages and make the
 decision. 
 
 [EMAIL PROTECTED] wrote:
 
 
 It is not necessarily true that an error in one
 application will affect all
 applications. If there is a problem with oracle
 instance or the database,
 then all applications might be affected.
 
 Multiple schemas which have the same table names can
 be a problem. If your
 applications uses public synonyms, then you might
 have a big problem.
 
 If everything is working fine now, it seems
 pointless to move things around.
 But this is philosophy. I do believe that isolating
 applications from each
 other as much as possible is usually a good thing.
 Good fences make good neighbors. (usually)
 
 But, if your manager insists on it, you have no
 choice. Just do your best
 to keep the old stuff around in case it becomes
 apparent that the new way
 will not work and you must go back to the old way.
 
  -Original Message-
  Lately, m! y manager want me to remove all the
 databases
  and remain a single instance. I was wondering if i
  move everything into single database then if one
 of
  the application fail due to oracle error , then
 all
  other four application will fail also rite ? 
  
  Each of our web application needs to have 2 schema
 and
  both schema have to be transparent to each other.
  While other application schema will be invisible
 to
  each other. Since i have 5 web app then i will
 need 10
  schema.One major problem is all the 10 schema will
  contain same table name. It will be a mess putting
 so
  much app in a single db . 
  
  Pls correct me if i am wrong and do let me know
 what
  are the pro and cons or maybe you can educate me
 with
  some of the best practice to setup a proper
 production
  server environment.
  
  Thank You
  
  Regards,
  Jkean 
  
   
 -- 
 Please see the official ORACLE-L FAQ:
 http://www.orafaq.net
 -- 
 Author: 
 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 

RE: Database Instance

2003-12-26 Thread Thomas Day

We have 13 databases (and instances) of approximately 17G each on a
RISC/6000.  We have 6 database/instances on a Win2K box.  Two of those are
in the 17G range but the rest are smaller.  But it's not the disk size
that's important, it's the SGA size.



   

  Kean Jacinta 

  jacintakean To:  Multiple recipients of list 
ORACLE-L [EMAIL PROTECTED]
  @yahoo.com  cc: 

  Sent by: Subject: RE: Database Instance  

  ml-errors

   

   

  12/26/2003 01:59 

  AM   

  Please respond   

  to ORACLE-L  

   

   





Dear :All

Well we did not buy any application packages.
Currently  we are using open source product ...which
is Apache and Tomcat.

By the way, have anyone ever have more than 5 database
under a single server ? I heard that the best practice
is to have 1 database n 1 application in a single
server. Is that true ?

Thank
JKean

--- Mercadante, Thomas F
[EMAIL PROTECTED] wrote:
 I would be very careful about doing this if you have
 purchased application
 packages.  Sooner or later, you will want to upgrade
 one of the packages,
 and it will require a different release of Oracle -
 and you will be stuck.


 Tom Mercadante
 Oracle Certified Professional

 -Original Message-
 Sent: Wednesday, December 24, 2003 11:24 AM
 To: Multiple recipients of list ORACLE-L


 One other disadvantage of putting all instances
 together is if you need to
 say bounce the database (for parameter change or
 other maintenance  etc)
 then all other applications will get affected.
 Whereas with separate
 instances other applications will not get affected.

 To some extent one application failing will not
 affect other applications.
 Except if one application does not close its
 connections then it could lead
 to maximum connections (sessions) being reached and
 affecting other
 applications.

 If the nature of the applications is different :
 OLTP, warehousing then you
 cannot really tune the parameters.

 On the positive side I think putting instances
 together will lead to some
 memory savings.

 I would suggest : Do not worry about who wants to
 put the instances together
 just list the advantages, disadvantages and make the
 decision.

 [EMAIL PROTECTED] wrote:


 It is not necessarily true that an error in one
 application will affect all
 applications. If there is a problem with oracle
 instance or the database,
 then all applications might be affected.

 Multiple schemas which have the same table names can
 be a problem. If your
 applications uses public synonyms, then you might
 have a big problem.

 If everything is working fine now, it seems
 pointless to move things around.
 But this is philosophy. I do believe that isolating
 applications from each
 other as much as possible is usually a good thing.
 Good fences make good neighbors. (usually)

 But, if your manager insists on it, you have no
 choice. Just do your best
 to keep the old stuff around in case it becomes
 apparent that the new way
 will not work and you must go back to the old way.

  -Original Message-
  Lately, m! y manager want me to remove all the
 databases
  and remain a single instance. I was wondering if i
  move everything into single database then if one
 of
  the application fail due to oracle error , then
 all
  other four application will fail also rite ?
 
  Each of our web application needs to have 2

Re: RE: Database Instance

2003-12-26 Thread ryan_oracle
i believe tom kyte recommends putting them in one or a few instances and using VPD to 
handle security. He claims it scales better. I believe its in his second book and on 
his website.

However, Thomas is right. You really dont want 13 instances together for maintenance 
reasons. Some may need different parameter settings. 

Are you sure your server can handle all those instances? That could be alot of work 
for one server. I know the trend these days(and we do it) is get 1 powerful server and 
load it with instances to save on oracle's obscene licensing fees.

Best thing to do is possibly analyze how the instances are used and combine them into 
groups of instances. 

Your manager sounds like an idiot. What he should do is the following. 

Manager: 'DBA, what are the pros and cons of putting all instances into one database? 
Please research and get back to me. Also, if we decide to combine them, please write 
up testing scenarios so we can adequately test this approach before implementing it.'

Then he makes a decision. No patience for know it all managers. They cause so many 
problems. 
 
 From: Thomas Day [EMAIL PROTECTED]
 Date: 2003/12/26 Fri AM 08:44:25 EST
 To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
 Subject: RE: Database Instance
 
 
 We have 13 databases (and instances) of approximately 17G each on a
 RISC/6000.  We have 6 database/instances on a Win2K box.  Two of those are
 in the 17G range but the rest are smaller.  But it's not the disk size
 that's important, it's the SGA size.
 
 
 
  
   
   Kean Jacinta   
   
   jacintakean To:  Multiple recipients of list 
 ORACLE-L [EMAIL PROTECTED]
   @yahoo.com  cc:   
   
   Sent by: Subject: RE: Database Instance
   
   ml-errors  
   
  
   
  
   
   12/26/2003 01:59   
   
   AM 
   
   Please respond 
   
   to ORACLE-L
   
  
   
  
   
 
 
 
 
 Dear :All
 
 Well we did not buy any application packages.
 Currently  we are using open source product ...which
 is Apache and Tomcat.
 
 By the way, have anyone ever have more than 5 database
 under a single server ? I heard that the best practice
 is to have 1 database n 1 application in a single
 server. Is that true ?
 
 Thank
 JKean
 
 --- Mercadante, Thomas F
 [EMAIL PROTECTED] wrote:
  I would be very careful about doing this if you have
  purchased application
  packages.  Sooner or later, you will want to upgrade
  one of the packages,
  and it will require a different release of Oracle -
  and you will be stuck.
 
 
  Tom Mercadante
  Oracle Certified Professional
 
  -Original Message-
  Sent: Wednesday, December 24, 2003 11:24 AM
  To: Multiple recipients of list ORACLE-L
 
 
  One other disadvantage of putting all instances
  together is if you need to
  say bounce the database (for parameter change or
  other maintenance  etc)
  then all other applications will get affected.
  Whereas with separate
  instances other applications will not get affected.
 
  To some extent one application failing will not
  affect other applications.
  Except if one application does not close its
  connections then it could lead
  to maximum connections (sessions) being reached and
  affecting other
  applications.
 
  If the nature of the applications is different :
  OLTP, warehousing then you
  cannot really tune the parameters.
 
  On the positive side I think putting instances

RE: Database Instance

2003-12-26 Thread Kean Jacinta
Are there any performance issues arising ? MM I have
no idea abt SGA . When i started installed the dbase i
just follow the default value. 

JKEAN

--- Thomas Day [EMAIL PROTECTED] wrote:
 
 We have 13 databases (and instances) of
 approximately 17G each on a
 RISC/6000.  We have 6 database/instances on a Win2K
 box.  Two of those are
 in the 17G range but the rest are smaller.  But it's
 not the disk size
 that's important, it's the SGA size.
 
 
 
 
 
  
   Kean Jacinta  
 
  
   jacintakean To:  
Multiple recipients of list ORACLE-L
 [EMAIL PROTECTED]
   @yahoo.com  cc:  
 
  
   Sent by:
 Subject: RE: Database Instance  

   ml-errors 
 
  
 
 
  
 
 
  
   12/26/2003 01:59  
 
  
   AM
 
  
   Please respond
 
  
   to ORACLE-L   
 
  
 
 
  
 
 
  
 
 
 
 
 Dear :All
 
 Well we did not buy any application packages.
 Currently  we are using open source product ...which
 is Apache and Tomcat.
 
 By the way, have anyone ever have more than 5
 database
 under a single server ? I heard that the best
 practice
 is to have 1 database n 1 application in a single
 server. Is that true ?
 
 Thank
 JKean
 
 --- Mercadante, Thomas F
 [EMAIL PROTECTED] wrote:
  I would be very careful about doing this if you
 have
  purchased application
  packages.  Sooner or later, you will want to
 upgrade
  one of the packages,
  and it will require a different release of Oracle
 -
  and you will be stuck.
 
 
  Tom Mercadante
  Oracle Certified Professional
 
  -Original Message-
  Sent: Wednesday, December 24, 2003 11:24 AM
  To: Multiple recipients of list ORACLE-L
 
 
  One other disadvantage of putting all instances
  together is if you need to
  say bounce the database (for parameter change or
  other maintenance  etc)
  then all other applications will get affected.
  Whereas with separate
  instances other applications will not get
 affected.
 
  To some extent one application failing will not
  affect other applications.
  Except if one application does not close its
  connections then it could lead
  to maximum connections (sessions) being reached
 and
  affecting other
  applications.
 
  If the nature of the applications is different :
  OLTP, warehousing then you
  cannot really tune the parameters.
 
  On the positive side I think putting instances
  together will lead to some
  memory savings.
 
  I would suggest : Do not worry about who wants to
  put the instances together
  just list the advantages, disadvantages and make
 the
  decision.
 
  [EMAIL PROTECTED] wrote:
 
 
  It is not necessarily true that an error in one
  application will affect all
  applications. If there is a problem with oracle
  instance or the database,
  then all applications might be affected.
 
  Multiple schemas which have the same table names
 can
  be a problem. If your
  applications uses public synonyms, then you might
  have a big problem.
 
  If everything is working fine now, it seems
  pointless to move things around.
  But this is philosophy. I do believe that
 isolating
  applications from each
  other as much as possible is usually a good thing.
  Good fences make good neighbors. (usually)
 
  But, if your manager insists on it, you have no
  choice. Just do your best
  to keep the old stuff around in case it becomes
  apparent that the new way
  will not work and you must go back to the old way.
 
   -Original

Re: RE: Database Instance

2003-12-26 Thread Kean Jacinta
Really hope that i won't screw up the database. If He
really did insist to have single instance, then up to
him to decide. I still have no authority to said no.

JKEAN 
--- [EMAIL PROTECTED] wrote:
 i believe tom kyte recommends putting them in one or
 a few instances and using VPD to handle security. He
 claims it scales better. I believe its in his second
 book and on his website.
 
 However, Thomas is right. You really dont want 13
 instances together for maintenance reasons. Some may
 need different parameter settings. 
 
 Are you sure your server can handle all those
 instances? That could be alot of work for one
 server. I know the trend these days(and we do it) is
 get 1 powerful server and load it with instances to
 save on oracle's obscene licensing fees.
 
 Best thing to do is possibly analyze how the
 instances are used and combine them into groups of
 instances. 
 
 Your manager sounds like an idiot. What he should do
 is the following. 
 
 Manager: 'DBA, what are the pros and cons of putting
 all instances into one database? Please research and
 get back to me. Also, if we decide to combine them,
 please write up testing scenarios so we can
 adequately test this approach before implementing
 it.'
 
 Then he makes a decision. No patience for know it
 all managers. They cause so many problems. 
  
  From: Thomas Day [EMAIL PROTECTED]
  Date: 2003/12/26 Fri AM 08:44:25 EST
  To: Multiple recipients of list ORACLE-L
 [EMAIL PROTECTED]
  Subject: RE: Database Instance
  
  
  We have 13 databases (and instances) of
 approximately 17G each on a
  RISC/6000.  We have 6 database/instances on a
 Win2K box.  Two of those are
  in the 17G range but the rest are smaller.  But
 it's not the disk size
  that's important, it's the SGA size.
  
  
  

 

Kean Jacinta
 

jacintakean To:
  Multiple recipients of list ORACLE-L
 [EMAIL PROTECTED]
@yahoo.com  cc:
 

Sent by:
 Subject: RE: Database Instance  

ml-errors   
 


 


 

12/26/2003 01:59
 

AM  
 

Please respond  
 

to ORACLE-L 
 


 


 

  
  
  
  
  Dear :All
  
  Well we did not buy any application packages.
  Currently  we are using open source product
 ...which
  is Apache and Tomcat.
  
  By the way, have anyone ever have more than 5
 database
  under a single server ? I heard that the best
 practice
  is to have 1 database n 1 application in a single
  server. Is that true ?
  
  Thank
  JKean
  
  --- Mercadante, Thomas F
  [EMAIL PROTECTED] wrote:
   I would be very careful about doing this if you
 have
   purchased application
   packages.  Sooner or later, you will want to
 upgrade
   one of the packages,
   and it will require a different release of
 Oracle -
   and you will be stuck.
  
  
   Tom Mercadante
   Oracle Certified Professional
  
   -Original Message-
   Sent: Wednesday, December 24, 2003 11:24 AM
   To: Multiple recipients of list ORACLE-L
  
  
   One other disadvantage of putting all instances
   together is if you need to
   say bounce the database (for parameter change or
   other maintenance  etc)
   then all other applications will get affected.
   Whereas with separate
   instances other applications will not get
 affected.
  
   To some extent one application failing will not
   affect other applications.
   Except if one application does

RE: Database Instance

2003-12-24 Thread Stephen.Lee

It is not necessarily true that an error in one application will affect all
applications.  If there is a problem with oracle instance or the database,
then all applications might be affected.

Multiple schemas which have the same table names can be a problem.  If your
applications uses public synonyms, then you might have a big problem.

If everything is working fine now, it seems pointless to move things around.
But this is philosophy.  I do believe that isolating applications from each
other as much as possible is usually a good thing.
Good fences make good neighbors. (usually)

But, if your manager insists on it, you have no choice.  Just do your best
to keep the old stuff around in case it becomes apparent that the new way
will not work and you must go back to the old way.

 -Original Message-
 Lately, my manager want me to remove all the databases
 and remain a single instance. I was wondering if i
 move everything into single database then if one of
 the application fail due to oracle error , then all
 other four application will fail also rite ? 
 
 Each of our web application needs to have 2 schema and
 both schema have to be transparent to each other.
 While other application schema will be invisible to
 each other. Since i have 5 web app then i will need 10
 schema.One major problem is all the 10 schema will
 contain same table name. It will be a mess putting so
 much app in a single db . 
 
 Pls correct me if i am wrong and do let me know what
 are the pro and cons or maybe you can educate me with
 some of the best practice to setup a proper production
 server environment.
 
 Thank You
 
 Regards,
 Jkean  
 
 
 
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: [EMAIL PROTECTED]
  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: Database Instance

2003-12-24 Thread anu
One other disadvantage of putting all instances together is if you need to say bounce the database (for parameter change or other maintenanceetc) then all other applications will get affected. Whereas with separate instances other applications will not get affected. 

To some extent one application failing will not affect other applications. Except if one application does not close its connections then it could lead to maximum connections (sessions) being reached and affecting other applications. 

If the nature of the applications is different : OLTP, warehousing then you cannot really tune the parameters.

On the positive side I think putting instances together will lead to some memory savings. 

I would suggest :Do not worry about who wants to put the instances together just list the advantages, disadvantages and make the decision. [EMAIL PROTECTED] wrote:
It is not necessarily true that an error in one application will affect allapplications. If there is a problem with oracle instance or the database,then all applications might be affected.Multiple schemas which have the same table names can be a problem. If yourapplications uses public synonyms, then you might have a big problem.If everything is working fine now, it seems pointless to move things around.But this is philosophy. I do believe that isolating applications from eachother as much as possible is usually a good thing."Good fences make good neighbors." (usually)But, if your manager insists on it, you have no choice. Just do your bestto keep the old stuff around in case it becomes apparent that the new waywill not work and you must go back to the old way. -Original Message- Lately, m!
y manager
 want me to remove all the databases and remain a single instance. I was wondering if i move everything into single database then if one of the application fail due to oracle error , then all other four application will fail also rite ?   Each of our web application needs to have 2 schema and both schema have to be transparent to each other. While other application schema will be invisible to each other. Since i have 5 web app then i will need 10 schema.One major problem is all the 10 schema will contain same table name. It will be a mess putting so much app in a single db .   Pls correct me if i am wrong and do let me know what are the pro and cons or maybe you can educate me with some of the best practice to setup a proper production server environment.  Thank You  Regards, Jkean   
 -- Please see the official ORACLE-L FAQ: http://www.orafaq.net-- Author: <[EMAIL PROTECTED]INET: [EMAIL PROTECTED]Fat City Network Services -- 858-538-5051 http://www.fatcity.comSan Diego, California -- Mailing list and web hosting services-To REMOVE yourself from this mailing list, send an E-Mail messageto: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and inthe message BODY, include a line containing: UNSUB ORACLE-L(or the name of mailing list you want to be removed from). You mayalso send the HELP command for other information (like subscribing).
Do you Yahoo!?
Free Pop-Up Blocker - Get it now

Re: Database Instance

2003-12-24 Thread Barbara Baker
You are (I presume) the keeper of the data,
responsible for its integrity and safety

What you need to present to your manager is what risks
to safety and integrity might be faced if all of the
databases are rolled into one.

How closely tied are the applications for the 5
databases?  If 1 application requires a patch for some
reason and you've rolled all 5 apps into 1 database,
all 5 will need to come down for a patch.  If
separate, you are able to patch up just the instance
requiring the patch and leave the others running.  If
separate, upgrades will also be easier -- you can
upgrade 1 database at a time, mimimizing down time.

All 5 apps will require exact same versions of
database and patch level if rolled into a single
instance.  That may or may not be ok.  If any of these
apps require a maintenance window, all 5 must be
down/restricted at the same time.

A lot of flexibility is compromised when 5 different
apps are merged into a single database.  Exactly how
much difficulty that might cause depends on the apps.

There are a couple of benefits from folding all 5 into
a single db.  The big question is whether these
benefits outweigh the lack of flexibility from havig
all 5 in a single database.

Just some things to thing about.
Good luck!
Barb

--- Kean Jacinta [EMAIL PROTECTED] wrote:
 Dear : All
 
 First and foremost , if i ask stupid question pls
 forgive me coz i new to oralce. I have a question
 here.
 
 I have a server, and this server contains 5 oracle
 database. Each database contains 5 web application
 that are running on live ( production server ). As i
 understand abt oracle , every database that i
 created
 will have 1 instance. So since this server hold 5
 database then i will have 5 instances running.
 
 Lately, my manager want me to remove all the
 databases
 and remain a single instance. I was wondering if i
 move everything into single database then if one of
 the application fail due to oracle error , then all
 other four application will fail also rite ? 
 
 Each of our web application needs to have 2 schema
 and
 both schema have to be transparent to each other.
 While other application schema will be invisible to
 each other. Since i have 5 web app then i will need
 10
 schema.One major problem is all the 10 schema will
 contain same table name. It will be a mess putting
 so
 much app in a single db . 
 
 Pls correct me if i am wrong and do let me know what
 are the pro and cons or maybe you can educate me
 with
 some of the best practice to setup a proper
 production
 server environment.
 
 Thank You
 
 Regards,
 Jkean  
 
 
 
  
 
 __
 Do you Yahoo!?
 New Yahoo! Photos - easier uploading and sharing.
 http://photos.yahoo.com/
 -- 
 Please see the official ORACLE-L FAQ:
 http://www.orafaq.net
 -- 
 Author: Kean Jacinta
   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).


__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Barbara Baker
  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: Database Instance

2003-12-24 Thread Mercadante, Thomas F



I 
would be very careful about doing this if you have purchased application 
packages. Sooner or later, you will want to upgrade one of the packages, 
and it will require a different release of Oracle - and you will be 
stuck.

Tom Mercadante Oracle Certified Professional 

  -Original Message-From: anu 
  [mailto:[EMAIL PROTECTED]Sent: Wednesday, December 24, 2003 11:24 
  AMTo: Multiple recipients of list ORACLE-LSubject: RE: 
  Database Instance 
  One other disadvantage of putting all instances together is if you need 
  to say bounce the database (for parameter change or other 
  maintenanceetc) then all other applications will get affected. 
  Whereas with separate instances other applications will not get affected. 
  
  
  To some extent one application failing will not affect other 
  applications. Except if one application does not close its connections then it 
  could lead to maximum connections (sessions) being reached and affecting other 
  applications. 
  
  If the nature of the applications is different : OLTP, warehousing then 
  you cannot really tune the parameters.
  
  On the positive side I think putting instances together will lead to some 
  memory savings. 
  
  I would suggest :Do not worry about who wants to put the instances 
  together just list the advantages, disadvantages and make the decision. 
  [EMAIL PROTECTED] wrote:
  It 
is not necessarily true that an error in one application will affect 
allapplications. If there is a problem with oracle instance or the 
database,then all applications might be affected.Multiple 
schemas which have the same table names can be a problem. If 
yourapplications uses public synonyms, then you might have a big 
problem.If everything is working fine now, it seems pointless to 
move things around.But this is philosophy. I do believe that isolating 
applications from eachother as much as possible is usually a good 
thing."Good fences make good neighbors." (usually)But, if your 
manager insists on it, you have no choice. Just do your bestto keep the 
old stuff around in case it becomes apparent that the new waywill not 
work and you must go back to the old way. -Original 
Message- Lately, m! y manager want me to remove all the 
databases and remain a single instance. I was wondering if i 
move everything into single database then if one of the application 
fail due to oracle error , then all other four application will fail 
also rite ?   Each of our web application needs to have 2 
schema and both schema have to be transparent to each other. 
While other application schema will be invisible to each other. 
Since i have 5 web app then i will need 10 schema.One major problem 
is all the 10 schema will contain same table name. It will be a mess 
putting so much app in a single db .   Pls correct 
me if i am wrong and do let me know what are the pro and cons or 
maybe you can educate me with some of the best practice to setup a 
proper production server environment.  Thank 
You  Regards, Jkean   <B! R> 
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net-- 
Author: <[EMAIL PROTECTED]INET: [EMAIL PROTECTED]Fat 
City Network Services -- 858-538-5051 http://www.fatcity.comSan Diego, 
California -- Mailing list and web hosting 
services-To 
REMOVE yourself from this mailing list, send an E-Mail messageto: 
[EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and inthe 
message BODY, include a line containing: UNSUB ORACLE-L(or the name of 
mailing list you want to be removed from). You mayalso send the HELP 
command for other information (like subscribing).
  
  
  Do you Yahoo!?Free 
  Pop-Up Blocker - Get it now


Re: Database Instance

2003-12-24 Thread Jared Still
Good counsel. The assumption is made though that 
each database has it's own ORACLE_HOME, which may
not be the case.

Jared

On Wed, 2003-12-24 at 08:39, Barbara Baker wrote:
 You are (I presume) the keeper of the data,
 responsible for its integrity and safety
 
 What you need to present to your manager is what risks
 to safety and integrity might be faced if all of the
 databases are rolled into one.
 
 How closely tied are the applications for the 5
 databases?  If 1 application requires a patch for some
 reason and you've rolled all 5 apps into 1 database,
 all 5 will need to come down for a patch.  If
 separate, you are able to patch up just the instance
 requiring the patch and leave the others running.  If
 separate, upgrades will also be easier -- you can
 upgrade 1 database at a time, mimimizing down time.
 
 All 5 apps will require exact same versions of
 database and patch level if rolled into a single
 instance.  That may or may not be ok.  If any of these
 apps require a maintenance window, all 5 must be
 down/restricted at the same time.
 
 A lot of flexibility is compromised when 5 different
 apps are merged into a single database.  Exactly how
 much difficulty that might cause depends on the apps.
 
 There are a couple of benefits from folding all 5 into
 a single db.  The big question is whether these
 benefits outweigh the lack of flexibility from havig
 all 5 in a single database.
 
 Just some things to thing about.
 Good luck!
 Barb
 
 --- Kean Jacinta [EMAIL PROTECTED] wrote:
  Dear : All
  
  First and foremost , if i ask stupid question pls
  forgive me coz i new to oralce. I have a question
  here.
  
  I have a server, and this server contains 5 oracle
  database. Each database contains 5 web application
  that are running on live ( production server ). As i
  understand abt oracle , every database that i
  created
  will have 1 instance. So since this server hold 5
  database then i will have 5 instances running.
  
  Lately, my manager want me to remove all the
  databases
  and remain a single instance. I was wondering if i
  move everything into single database then if one of
  the application fail due to oracle error , then all
  other four application will fail also rite ? 
  
  Each of our web application needs to have 2 schema
  and
  both schema have to be transparent to each other.
  While other application schema will be invisible to
  each other. Since i have 5 web app then i will need
  10
  schema.One major problem is all the 10 schema will
  contain same table name. It will be a mess putting
  so
  much app in a single db . 
  
  Pls correct me if i am wrong and do let me know what
  are the pro and cons or maybe you can educate me
  with
  some of the best practice to setup a proper
  production
  server environment.
  
  Thank You
  
  Regards,
  Jkean  
  
  
  
   
  
  __
  Do you Yahoo!?
  New Yahoo! Photos - easier uploading and sharing.
  http://photos.yahoo.com/
  -- 
  Please see the official ORACLE-L FAQ:
  http://www.orafaq.net
  -- 
  Author: Kean Jacinta
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).
 
 
 __
 Do you Yahoo!?
 Free Pop-Up Blocker - Get it now
 http://companion.yahoo.com/
 -- 
 Please see the official ORACLE-L FAQ: http://www.orafaq.net
 -- 
 Author: Barbara Baker
   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).
 


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jared Still
  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

RE: Database Instance

2003-12-23 Thread Sinardy Xing
Think of Object Oriented, then 1 db can be an Object, better security, easy to upgrade 
or downgrade, easy to change any setting as you like.
Think of memory, overhead, administration, 1 instance will be better (I think, 
specially backup and recovery)
Think of performance, you can tune each db individually and contention will quite easy 
to maintain.
Think of risk and potential application bug, why your management want to overhaul the 
system?

About the schema that transparent or invisible, you can search Oracle Doc (SQL Plus) 
with key word GRANT or REVOKE (If you decide to merge your databases)

Merry X'mas

Sinardy


-Original Message-
Sent: 24 December 2003 09:49
To: Multiple recipients of list ORACLE-L


Dear : All

First and foremost , if i ask stupid question pls
forgive me coz i new to oralce. I have a question
here.

I have a server, and this server contains 5 oracle
database. Each database contains 5 web application
that are running on live ( production server ). As i
understand abt oracle , every database that i created
will have 1 instance. So since this server hold 5
database then i will have 5 instances running.

Lately, my manager want me to remove all the databases
and remain a single instance. I was wondering if i
move everything into single database then if one of
the application fail due to oracle error , then all
other four application will fail also rite ? 

Each of our web application needs to have 2 schema and
both schema have to be transparent to each other.
While other application schema will be invisible to
each other. Since i have 5 web app then i will need 10
schema.One major problem is all the 10 schema will
contain same table name. It will be a mess putting so
much app in a single db . 

Pls correct me if i am wrong and do let me know what
are the pro and cons or maybe you can educate me with
some of the best practice to setup a proper production
server environment.

Thank You

Regards,
Jkean  



 

__
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Kean Jacinta
  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).

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Sinardy Xing
  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).