Consideration in a new Production Environment DB

Dear all,
DB : 10.2.0.4.0
Solaris 10
After installing Oracle DB in a production environment, is there any jobs to be scheduled for proper performance of the DB ?
What has to be considered in db health regard?.
Please guide ?
Kai

The most critical thing is to gather stats regularly
MOS Doc 377152.1 - Best Practices for automatic statistics collection on Oracle 10g
HTH
Srini

Similar Messages

Import Schema into new (production) environment in APEX 4.2

Hello,
I am having troubles with deploying developed application into new environment. I exported application, schema and workspace and I want to import it all to a new machine. Except schema, I have imported and installed it all successfully. But after I import generated script (DDL) trough SQL Workshop->SQL Scripts I am not able to find created scheme.
Let me explain my steps in sequence:
1. I have installed XE 11g Release 2, and APEX 4.2 on the new machine (Win 7).
2. New (ghost) workspace and schema were created (named as TESTWS, TESTSCH).
3. After I logged to a new workspace (TESTWS) I completed importing old schema (DEVSCH) -( I have found that the import and install sequence should be - fist Schema, second Workspace (with mapped schema), and then Application)
4. Finally I have imported old workspace (DEVWS) trough administrator console, and have tried to assign it to old (imported) schema (DEVSCH) but without any success. I was not able to locate imported schema.
I am not sure if there is a missing step or something I have doing wrongly, so please advise what to do in order to import and recognize/locate/see imported scheme into new APEX environment?
Thank you in advance,
BR
Jasmin

No.. Once you import an application into HIGHER version of APEX, it is modified to that version.. This is a suggestion, but I would advise having some sort of version control in this case, so you can go back to a prior version easily...
Thank you,
Tony Miller
Ruckersville, VA

Populate archive logs from production (Solaris) to new production(Linux) db

I want to migrate my production database(Solaris) to different environment(Linux)
After production database migration my production database(Solaris) will be up and running for 2 days.
We are going to check applications for 2 days on temporary production(Linux) database.
For 2 days my primary database(Solaris) will be up and running and generating archive logs. After that i want to populate those 2 days archives to temporary database(Linux).
Question 1: How would i populate 2 days archive logs from primary database(Solaris) to new production environment(Linux)
Is there any way/utility do apply generated archives to different database?\
I would be thankful for any expert suggestion.
Thanks,

Is there any way/utility do apply generated archives to different database?\They have to be applied to the same database (identified by DBID).
As soon as you OPEN the Linux database (and do any transactions therein), it diverges from your Solaris database. You cannot apply archivelogs of the Solaris database to the Linux database.
Hemant K Chitale

Create a new portlet in Deployed Portal in production environment

are there any ways to import or create a new portlet in Deployed Portal in production environment?
Edited by: user8322798 on May 1, 2011 7:26 AM

This can done via WSRP proxy portlets and streaming desktops. First, you'll need to have a WSRP producer setup somewhere. This could be another WLP webapp with portlets, or another server altogether. Or, you can use the JSR 286 WSRP import tool from within the Portal Administration Console (I think it's under Services | WSRP | Import Tool) -- this will allow you upload .war(s) of JSR 168 or 286 portlets, which will be turned into WSRP producer(s).
Then, you can use the Portal Administration Console to register a WSRP Producer, and then add portlets from the producer to your desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14235/chap_fed_books_pages.htm#FPGWP690). Additionally, once the producer has been registered in Portal Adminstration Console, an adminstrator user can use the Dynamic Visitor Tools from within the streaming desktop itself to add wsrp proxy portlets to the desktop (http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14243/dvt.htm#PDGWP691).
It is not possible to add new local .portlet files to a deployed application in production mode. This requires adding the file artifacts to the .ear/.war and redeploy the application.
Greg

Goodnight. as you know apple has evolved considerably until today but there are people who do not have ability to buy new products. in my case I would like to know why the apple do not let the iphone 3g update to iOS 4.3 as are several applications that c

goodnight. as you know apple has evolved considerably until today but there are people who do not have ability to buy new products. in my case I would like to know why the apple do not let the iphone 3g update to iOS 4.3 as are several applications that can not put on my iphone 3g due to this reason. Why does not Apple make a repository with applications for ios 4.2.1? or else do not work in an update to ios 4.3 on iphone 3g?

This has nothing to do with Apple, as Apple does not make the apps.
This is the decision of the app maker.
Contact those app makers and ask them why they do this.

Feasibility for a new production system in the same environment

Dear friends,
Our management has come up with a requirement of expansion of SAP environment to cover up users in a different country for their francise over there. The options we are considering are below:
1. Implementing a whole new setup ( ECC, EP,BI, PI,Trex).
2. Expanding the lease lines between the sites in both the countries and providing access to the present setup itself with enhancement in the current hardware configuration.
or is it a good practice to keep a new Production system in the other country and add a new delivery route for the new production system within the current transport route ? How the license part may be taken care in these cases ?
Your suggestions are welcomed.
Many thanks,
SUJIT

Hi Sujit,
The answer to this question really depends on whether the new country is going to share much of the same configuration with some tailoring to local laws and requirements. If the system is going to be the same, then there is now reason to deploy a new system unless you are reaching technical limits for hardware. For ease of management and usage, then having one system is preferred. You can then upgrade your network to cope with the increased load and hardware as required.
Hope this helps,
Graham

How to move Oracle APPS 12 setup data to new APPS 12 production environment

Dear All
I need to know , how we can move Oracle APPS 12 setup data to new APPS 12 production environment?? What is the easy and secure way, we dont want to do the new installation of APPS 12 and re-setup the things....
cheers

Hi,
Can you please explain more regarding to move setup from DEV to PROD instance.The steps are documented in the iSetup manual, so have you gone through the documentation?
Also we would install PROD with multi tier nodes, and HA cluster. So in that case what would be the change to move the setups from DEV to PROD, as DEV is single node TEST APPS 12 installation.iSetup is helpful in moving the functional setup between the two instances. If you want to create an identical copy of your DEV instance to PROD instance (provided that both instances contain no data), then you can use "Rapid Clone" -- See (Note: 799735.1 - Rapid Clone Documentation Resources, Release 11i and 12).
Regards,
Hussein

Performance tuning for new OFMW environment

Hello
We have just set up a new UAT environment entirely on all Oracle FMW latest products which includes:
1) OS -RHEL V5
2) WebCenter
3) SOA Suite
4) Database
5) IDM
6) HTTP Server
7) WebLogic Server
As as post infrastructure setup plan we need to to performance tuning as well. Shall we do only WLS performance tuning or we need to tune each and every product in order to get optimum results.
Any guide? resource to help?
Pls advice
Regards
Dev

When you install the product soa-suite (and probably webcenter too) a prerequisite check is performed
that gives information about packages and parameters that need to be adjusted on your operating system.
For products that run on WebLogic Server you probably have to tune the JVM, examples can be found here:
- http://middlewaremagic.com/weblogic/?p=6930 (discusses JRockit)
- http://middlewaremagic.com/weblogic/?p=7083 (focuses on Coherence, but the considerations can be applied to other environments as well)
Examples that set-up the SOA-Suite can be found here:
- http://middlewaremagic.com/weblogic/?p=6040 (discusses considerations when installing the SOA suite)
- http://middlewaremagic.com/weblogic/?p=6872 (discusses considerations when adding the web-tier to the SOA suite)
The enterprise deployment guides can help too:
- SOA Suite: http://download.oracle.com/docs/cd/E21764_01/core.1111/e12036/toc.htm
- WebCenter: http://download.oracle.com/docs/cd/E21764_01/core.1111/e12037/toc.htm
These also contain sections on integration with Oracle Identity Management and the Oracle HTTP Server

New production server PLUS upgrade!

After years of groveling, weekly church visits, and burning incense, it appears that I will finally be able to get a new production server for our 3.3 TB data warehouse. They are also going to add 2 TB of space to our main storage array.
In addition, management wants to upgrade from 10.2.0.3 to 11gR2 as part of that migration. Our current server was not able to handle 11g, according to Oracle.
In recent times, I have had to do some very non-standard things as a dba, mostly due to insufficient resources. So these migrations may not be as straightforward as what you read in the docs, and therefore I would like some opinions about how best to achieve the migration to the new box, and to 11gR2.
Our current environment is a Sunfire 6800 Sparc 64 box with 12 900mhz cpus and 16G of ram, and Solaris 10.
Most of our datafiles are housed on a 3.7 TB Sun 2540 storage array, but due to space and performance constraints, it was decided to put one very large and mostly unimportant tablespace (350G) on a 2.1 TB Sun 3511 array. We also put our 2 temporary tablespaces (about 54G) on that array. Also on the 3511 array is our db_recovery_file_dest area, with all of our archived redo logs and flashback logs. Due to lack of space there, I have to direct our RMAN database file backups, archived log backups, and exports to an unsupported Hitachi SAN, which is 8 years old, like our Sunfire 6800.
The new server is a Sun M4000 with Solaris 10, so the OS will not be an issue. It will have 4 4-way 2.5ghz processors and 32G of ram. The newly expanded 2540 array will have enough space to hold us for a few years. It is currently 3.7TB, using 2.6 of that. When expanded, it will be about 5.8TB.
My mission is to move all of the temporary tablespace and other data files (about 1 TB) and the exports (1 TB) to the newly expanded 2540. We will keep the space (2.1 TB) allocated on the 3511 attached to the new server, but it will be used ONLY for recovery-related files; rman backups, flashback logs, archived logs, etc. My goal is to keep at least two full rman backups in that space, along with all the necessary archived log backups. We are supposed to get everything off of the old SAN. So, there will be a lot of file shuffling, nothing new for this shop.
My plan would be to install 10.2.0.3 (same exact version) on the new server, then hook it up to the existing storage arrays. (My boss thinks that will reformat all of the disks on those arrays, but I don't think that is necessarily true. I believe it is possilble to mount each file system on those arrays to the new box, so long as they have been unmounted from the old one. Then again, I am not a Unix Admin)
Next, I would startup-mount the database, move the necessary files to the 2540 using Oracle and Unix commands, then shut down the db. Then, I would install 11gR2 with all patches on the new server, and upgrade the database manually, in place.
If my boss is right and connecting the new server to the existing arrays means re-initializing them, he asked if we could use our last RMAN backup to restore the database in the new environment. I said if we were still running 10g at that time on the new server, and all the file systems were identical, that should be possible. However, I should note that we do NOT use an RMAN catalog (RMAN uses the controlfile). We have no place to put an RMAN catalog. I have never even had a place to test doing a restore with RMAN.
If anyone out there has been through a migration to a new server along with an Oracle upgrade, I would appreciate any ideas on the best way to go about it.

Hi,
Its not recommended to upgrade OS and Database same time. I would recommend :
1) Migrate database from Old Server to new Severs.
-> Install OS, packages, patches, create users, groups, mount points and configure kernel parameters as required.
-> Restore $ORACLE_HOME, inventories, mount all data partitions on same mount points similar to old servers
-> Perform relink for all oracle home binaries using command relink all command.
Refer tech notes:
http://download.oracle.com/docs/cd/B19306_01/install.102/b28053/toc.htm
*Is It Necessary To Relink Oracle Following OS Upgrade? [ID 444595.1]*
*How to Relink Oracle Database Software on UNIX [ID 131321.1]*
2) Then perform an upgrade for your database.
http://download.oracle.com/docs/cd/E11882_01/install.112/e10863/toc.htm#i1011296
http://download.oracle.com/docs/cd/E11882_01/server.112/e10819/toc.htm
Hope helps :)
Regards,
X A H E E R

Best practice for a deplomyent (EAR containing WAR/EJB) in a productive environment

Hi there,
I'm looking for some hints regarding to the best practice deployment in a productive
environment (currently we are not using a WLS-cluster);
We are using ANT for buildung, packaging and (dynamic) deployment (via weblogic.Deployer)
on the development environment and this works fine (in the meantime);
For my point of view, I would like to prefere this kind of Deploment not only
for the development, also for the productive system.
But I found some hints in some books, and this guys prefere the static deployment
for the p-system.
My question now:
Could anybody provide me with some links to some whitepapers regarding best practice
for a deployment into a p-system ??
What is your experiance with the new two-phase-deploment coming up with WLS 7.0
Is it really a good idea to use the static deployment (what is the advantage of
this kind of deployment ???
THX in advanced
-Martin

Hi Siva,
What best practise are you looking for ? If you can be specific on your question we could provide appropriate response.
From my basis experience some of the best practices.
1) Productive landscape should have high availability to business. For this you may setup DR or HA or both.
2) It should have backup configured for which restore has been already tested
3) It should have all the monitoring setup viz application, OS and DB
4) Productive client should not be modifiable
5) Users in Production landscape should have appropriate authorization based on SOD. There should not be any SOD conflicts
6) Transport to Production should be highly controlled. Any transport to Production should be moved only with appropriate Change Board approvals.
7) Relevant Database and OS security parameters should be tested before golive and enabled
8) Pre-Golive , Post Golive should have been performed on Production system
9) EWA should be configured atleast for Production system
10) Production system availability using DR should have been tested
Hope this helps.
Regards,
Deepak Kori

Existing 2003 forest functional level -- 2012 forest functional level in production environment?

Hello experts!
A quick question if it can be one:
Is it possible to raise a forest functional level from 2003 to 2012 in a production environment (only 2003 DCs with existing roles to only 2012 DCs)? If so, is there a standard implementation of the upgrade process
(migration of roles, migration tools, etc.)?
many thanks!
David

hi,
Thanks for posting.
Sorry i don't know if i am understanding your question. Are you talking about upgrading your DC's in your current forest to 2012 then raising the functional level?
If so, first of all you can only raise the forest and domain functional levels when all DC's in the forest and domain are at 2012 or higher.
To get your domain unto 2012 DC's there are a couple of paths you can adopt, but generally the simplest is:
1. Introduce your first 2012 / 2012 R2 DC into your existing domain, this will extend the schema with the additional attributes that are required to 2012 - this is an automatic process during promotion of your first 2012 DC.
2. Go through and start replacing your existing domain controllers. You don't normally do an inlace upgrade, the preferred method would be to use different hardware, built up the new DC to replace your existing one, then demote the existing one - keep going
through this process until all your DC's are 2012.
NB: which ever DC(s) currently holds the FSMO roles you will need to transfer these to one of your new 2012 DC's before you decommission that one.
if i've got what you were asking wrong, please let me know, otherwise hopefully this helps.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
Blog: http://www.windows-support.co.uk
Twitter: LinkedIn:

Weblogic 8.1 Server log size increase in Production environment

Hi,
Issue:: One of the log file is increasing in size and exceeding beyond the size mentioned in the configuration file resulting in application outage.
Issue description:
We are having problems with the log size in the Weblogic 8.1 server. The fileminsize has been mentioned in the config.xml.
New log files like MYsvr.log00001,MYsvr.log00002, MYsvr.log00003, MYsvr.log00004 etc are also being generated appropriately when the max file size has been reached. But simultaneously, one of the files is growing in size, exceeding the limit mentioned in the configuration file. Eg.. the MYsvr.log00001 file is 800MB in size while the other files(MYsvr.log00002, MYsvr.log00003 etc are 10MB in size)
This increase in size of the log has been resulting in an application outage.
More Details:
1. Server: BEA Weblogic 8.1 server
2. Log size is fine in other environements. This is a problem only in the production environment.
3. The entry in the config.xml is as follows:
<Server ListenPort="6313" Name="MYsvr" NativeIOEnabled="true" TransactionLogFilePrefix="./">
<ServerStart Name="MYsvr"/>
<Log FileMinSize="10000" FileName="MYsvr.log" Name="MYsvr"
NumberOfFilesLimited="true" RotationType="bySize"/>
<SSL Name="MYsvr"/>
<ServerDebug Name="MYsvr"/>
<WebServer Name="MYsvr"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="MYsvr"/>
</Server>
Could you please help with this issue ?
Thank you.

Can someone please provide a solution for the issue

Redeploy in cluster in production environment

There is a cluster consisting two node in a production environment. The purpose is to make it possible, to upgrade a deployed application to a new version, with the highest avaibility. Is it possible to do it faster than the standard Redeploy method? Couse it lasts an hour at least, and during that time the application cannot be accessed.
          Ideal would be that it could be done without service breakdown. /On one node the application keeps running, on the other at first it is redeployed, than the while the second is restarting the former stops and then that is redeployed too./
          Is it Possible? Or any other way to solve that?

Hello Mathers,
          Why does it take an hour to redoply your app, are you precompiling JSPs on startup or do you have a vast number of EJBs, lots of connection pools with connections that are all created on deployment etc?
          Can you explain your deployment process and are you using WLS staging?
          A redeployment of the application I am currently working on (three ear files approx 100 EJBs and 3 web apps) takes about 15 minutes on each managed server, so we have about 15 minutes of down time. But I think I can get this down to 5 minutes without too much trouble.
          cheers
          Hussein Badakhchani
          www.orbism.com

MSDN and Production Environment (again)

I started this on another forum before I found this one, but this seems a more suitable place.
The definition of "production environment" seems rather odd. In some responses on this forum it appears to refer to "soft" systems whereas the latest MSDN licence refers to environment and physical kit.
Below is a conversation I had over email with someone from MSDN and I find the whole thing utterly bizarre. I cannot for the life of me see how this helps anyone apart from MS being able to charge for non-production software. It renders having a powerful desktop
for local lab experimentation pointless as you're not allowed to install anything and effectively doubles the hardware cost to small companies if they have to buy a separate server for any testing work (yes, best practice and all that, but budgets...) or pay
out for a Windows Datacenter licence.
Question:
“If a physical machine running one or more virtual machines is used entirely for development and test, then the operating system used on the physical host system can be MSDN software. However, if the physical machine or any of the VMs hosted on that physical
system are used for other purposes, then both the operating system within the VM and the operating system for the physical host must be licensed separately.”
Is this actually saying that if I have a physical server licenced with a purchased (not MSDN) Server 2012 R2, running Hyper-V with, say, a production file server VM on it, that ALL Windows VMs on that machine must have purchased licences even if they
are only for development & testing purposes?
Is this saying that all production and development Windows VMs must be only completely separate hardware, cluster, SAN, etc otherwise you must pay for full licences for the VMs?
Or does it just mean that the bare metal licence (plus any additional ones required for running further production VMs) must be purchased if the VMs are a mix of production and development?
Answer:
We kindly inform that any products licensed under the developer tools model (e.g. SQL/BizTalk developer and/or MSDN) must be installed on their own separate physical hardware.
You are not allowed to run test or development products on a server where production workloads are running at the same time. Kindly run your developer software on a device/host that is dedicated to testing and development.
Explanation:
The Product Use Rights (PUR) say that the developer software is not licensed for use in a production environment. Even if the PUR does not have a separate definition of production environment, a production environment is a set of resources for network, physically
dedicated hardware and software to provide "live" service. If the intent was to say that the same physical server could be used for both development and production - it would say "not licensed for use in a production OSE," instead
it says environment.
See current PUR, page 51:
Developer Tools (User License)
You have the rights below for each license you acquire.
# You must assign each license to a single user.
# Each Licensed User may run an unlimited number of copies of the Developer Tools software and any prior version on any device.
# The Licensed User may use the software for evaluation and to design, develop, test, and demonstrate your programs. These rights include the use of the software to simulate an end user environment to diagnose issues related to your programs.
# The software is not licensed for use in a production environment. # Additional rights provided in license terms included with the software are additive to these product use rights, provided that there is no conflict
with these product use rights, except for superseding use terms outlined below.
Question:
Classifying an entire physical infrastructure as "production" in these days of virtualisation and shared storage really does not make any sense at all. Not using the software for production purposes makes perfect sense, but not being able to locate
it alongside production OS installs is mad. Does this only apply to the server running the VM (CPU and RAM)? If the VHDX is hosted on shared SAN storage does the SAN have to be dedicated to non-production storage?
Answer:
We kindly inform that after double-checking the case we would like to confirm the development software cannot be run on the same hardware with production software.
We have also received a feedback from the responsible team regarding your request about a dedicated SAN (Storage Area Network) for MSDN software.
They have confirmed that the SAN has to be dedicated to the development and testing environment if it is used to run the software acquired through MSDN.
Question:
OK, so if I have my desktop (which is a production environment as I use it for email and other day to day office tasks), can I turn on Hyper-V and install an MSDN Windows Server 2012 instance for development purposes?
Answer:
We kindly inform it is not allowed to install and run software from MSDN subscriptions in production environments. Please do not install MSDN software on a desktop in a production environment:
"[.] The customer will need to run the developer software on a device/host that is dedicated to testing and development.
Explanation:
The Product Use Rights (PUR) say that the developer software is not licensed for use in a production environment. Even if the PUR does not have a separate definition of production environment, a production environment is a set of resources for network, physically
dedicated hardware and software to provide "live" service. If the intent was to say that the same physical server could be used for both development and production - it would say "not licensed for use in a production OSE," instead
it says environment.
See current PUR, page 51:
Developer Tools (User License)
You have the rights below for each license you acquire.
- You must assign each license to a single user.
- Each Licensed User may run an unlimited number of copies of the Developer Tools software and any prior version on any device.
- The Licensed User may use the software for evaluation and to design, develop, test, and demonstrate your programs. These rights include the use of the software to simulate an end user environment to diagnose issues related to your programs.
- The software is not licensed for use in a production environment.
- Additional rights provided in license terms included with the software are additive to these product use rights, provided that there is no conflict with these product use rights, except for superseding use terms outlined below.

Hi Mike,
It sucks that MSDN software can't be run in a production environment, that means you have to have two entirely separate hardware environments, which are costly, and it seems unnecessary.
That's essentially it. I'm not saying for one second that it should be used for production purposes, just that it's physical location shouldn't be relevant. Also, the word "environment" is a very bad choice in the documentation simply because it's very open
to interpretation.
A production environment is defined as an environment that is accessed by end users of an application (such as an Internet Web site) and that is used for more than
Acceptance Testing of that application
or Feedback. Some scenarios that constitute production
environments include:
Environments that connect to a production database.
Environments that support disaster-recovery or backup for a production environment.
Environments that are used for production at least some of the time, such a server that is rotated into production during peak periods of activity.
So I dont think (here's that inconclusive language) but am not sure that your desktop machines count as production environments, based on that, unless end users are connecting to them. (I dearly hope they are not!)
My reading is based on the "Other Guidance" section:
"If a physical machine running one or more virtual machines is used entirely for development and test, then the operating system used on the physical host system can be MSDN software. However, if the physical machine or any of the VMs
hosted on that physical system are used for other purposes, then both the operating system within the VM and the operating system for the physical host must be licensed separately."
<o:p>This is the crux of the matter and the interpretation of "licensed separately". A (to my mind) sensible reading of that would be "if you're running any production purpose VMs on a server then the physical host OS must be a full licence
[presuming it's Server 2012 and not, say, VMWare or Hyper-V 2012] as must all production purpose VMs on that server". This has been getting interpreted by others (I'm not the first) and backed up by MS as meaning that if you want to run any dev/test VMs on
a server that also runs production VMs then you can't use MSDN for those dev/test VMs.</o:p>
Also, there is a section
here, on the MSDN Licensing help page that says (with my added emphasis):
Many
MSDN subscribers use a computer for mixed use—both design, development, testing, and demonstration of your programs (the use allowed under the MSDN subscription license) and some other use. Using the software in any other way, such as for doing email,
playing games, or editing a document is another use and is not covered by the MSDN subscription license.
When this happens, the underlying operating system must also be licensed normally by purchasing a regular copy of Windows such as the one that came with a new OEM PC.
Now to me, it seems this might be saying that the underlying operating system on a work
machine cannot be licensed using MSDN if that work machine is going to be doing non-msdn things in addition to MSDN things. It doesn't say "This can't happen" it just says "When this happens, the underlying
OS must be licensed normally..."
So, based on what I'm reading it seems that this quote from you might not be true:
"We can't install a local MSDN instance of Server 2012 or 8.1 for dev and test under Hyper-V on desktops
because desktops used for email, writing documents, etc are production. "
I wouldn't have expected this to be true either, but this is the response I was given. It may well be
that my question was misunderstood. I hope this is the case otherwise one of the big reasons for turning on Hyper-V on expensive, powerful desktops enabling the running of personal test environments goes out the window!
Thanks for your time on this.

RE: Production Environment Definition

Brad,
We use connected environments so that we do not have a single point of
failure.
We use multiple environments and connect them together in a star topology
for reliability of service. Our servers (23 in total) sit out at branches
in the back of beyond and the WAN connections between the servers are
unreliable. One needs a reliable connection to the Name Service which sits
on each Environment Manager. We have thus created 23 connected
environments with an Environment Manager on each LAN. Connected
environments are still a bit buggy but Tech Support is currently working on
fixing the last of the problems. We are still on ver 2H15 for this reason.
Disadvantages of this topology are that making distributions take a long
time because referenced partitioning cannot be scripted in fscript and
econsole only connects to one environment at a time.
There is a Forté consultant in Denver called Pieter Pretorius who has had a
lot of experience with our connected environments. It may be worth
chatting to him.
Regards,
Richard Stobart
Technical Consultant for Forté
E-mail [email protected]
Quick-mail: [email protected]
Voice: (+ 27 83) 269 1942
(+27 11) 456 2238
Fax: (+ 27 83) 8269 1942
-----Original Message-----
From: Brad Wells [SMTP:[email protected]]
Sent: Tuesday, February 10, 1998 11:52 PM
To: 'Forte Users - Sage'
Subject: Production Environment Definition
Hello again,
We are just starting to look at what it will take to setup a production
Forte environment. I have some general questions regarding
considerations that may affect the environment definition and thought
maybe some of the more experienced users could share some thoughts on the
following:
1) What factors lead to the creation of multiple production environments?
a. How many environments should you use in a production situation?
b. Do people create separate environments for separate business units?
c. Are there performance improvements to be had by restricting the
number of server and client nodes included in a single environment?
d. How do the performance benefits of multiple environments compare to
the additional complexity of managing and maintaining multiple connected
environments?
The initial need is for an environment that will service approximately 50
clients and contain a couple of server nodes (database and service
related). However, as the environment grows, it could easily grow to a
size of 600 clients encompassing approximately 15-20 server nodes.
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as the
environment absorbs applications with high reliability needs. Should the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
Has anyone taken advantage of Forte consulting services in defining the
production environment? Where you satisfied with the results of the
service?
Thanks.
Bradley Wells
[email protected]
Strong Capital Management, Inc
http://www.strong-funds.com

On Tue, 10 Feb 98 13:52:00 PST Brad Wells <[email protected]>
writes:
At this point in time, there is no need for the failover support of
connected environments, but this is something we will need to add as
the
environment absorbs applications with high reliability needs. Should
the
environments be setup and connected right away or can this be easily
added on an "as needed" basis? What other recommendations would you
make?
From the Forte Systems Management point of view, you can add them "asneeded"
fairly easily.
Now from the application source code point of view, implementing
Fail/Over support
is a different story... You will need to check your SO's dialog
durations, handle
DistributedAccessExceptions, "warm-up" your distributed references for
F/O,
design a solution for restoring global transient data, do lots of
testings etc...
So implementing Fail/Over is not only related to systems-management
issues, it can
have some influence on your application(s) source code.
Hope this helps,
Vincent Figari
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]

Consideration in a new Production Environment DB

Similar Messages

Maybe you are looking for