This section provides answers to the most commonly asked questions related to the installation of Objectivity/DB.
If you will only be delivering software, without any preloaded databases, then all you have to do is create a "master" federated database containing the schema(s) that you compiled your code with. You copy the federated database, some of the Objectivity/DB runtime libraries (listed in the Database Administration manuals) and your own software and installation material onto the delivery vehicle (tape, CD, tar/ZIP file etc.)During the installation of your software you start one or more lock server and Advanced Multithreaded Server processes, then run ooinstallfd to make the federated database available. You then install your Objectivity/DB applications and start them up; or allow end users to install and start them.If you also want to deliver some preloaded databases (e.g. with configuration data, libraries or other groups of objects) then you use oocopydb to produce files that can be copied to your delivery vehicle. You then run ooattachdb after running ooinstallfd at the installation site.
You need to gather as much information as you can about the state of the system as you can. This topic is covered in the High Availability Deployment Review (a Professional Services Package). Each new release of Objectivity/DB introduces additional tools to help you and Objectivity's Customer Support Engineers diagnose and correct a problem. Some sites own very sensitive information, so special arrangements may need to be made to reproduce the error off-site with synthetic data.
Yes, by special arrangement. Many of the Professional Services Packages are designed to help minimize downtime. Prevention is a lot less painful than a cure. Please contact Customer Support for further details. |
|||
