Re: O8i/WebDB2.0/OEM install steps

From: Donald Richard <donald.richard_at_cognos.com>
Date: 1999/08/05
Message-ID: <37A9CC45.A716278A_at_cognos.com>


Do you know if there is a way to install Oracle 8.1 client with older support files like Required Support files for 7.3*? This is a new install of Oracle 81 client but the application I am using requires older Support files.

Charles Larry wrote:

> After much frustration I was able to complete an Oracle 8i
> installation. For what it's worth, here is how I got it to work.
>
> The database package I had to install consisted of four products:
>
> Oracle 8i, Release 8.1.5
>
> Oracle 8i Client, Release 8.1.5
>
> Oracle Enterprise Manager, Version 2.0.4
>
> Oracle WebDB Version 2.0.5
>
> I installed these programs on a Dell PowerEdge 4300 with 2 Pentium III
> processors and 512MB RAM. The computer is being used on our project as a
> server machine. The computer's hostname is redtail and the OS is Windows
> NT Server Version 4.0 Service Pack 4. It should be noted that this
> computer had no previous versions of Oracle installed on it. This fact
> makes a _big_ difference in the installation process. I had no issues
> relating to migrating a previous version of an Oracle database to 8i. If
> you have such issues, I suspect these instructions are mostly useless to
> you. Also note that TCP protocol is used on the network to which redtail
> is connected.
>
> Finally, I found that sometimes strange errors came up that seem to
> relate to the Java programs used by the installer. When I
> encountered such problems, I _started_ _over_ by completely cleaning the
> machine of Oracle. I accomplished this by following
> the instructions in the Oracle documentation for creating a "Clean
> Machine" as they call it. Completely ridding your computer of
> Oracle is accomplished by doing the following:
>
> A. Ensure you are logged in on the computer as a user with
> Administrative
> privileges.
> B. Using regedit (at the command prompt, type regedit), go to
> HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE and delete the ORACLE key.
> C. Delete HKEY_LOCAL_MACHINE\SOFTWARE\odbc.
> D. Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, and remove
> all keys there that begin with ORACLE.
>
> E. Open
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
>
> and delete all keys there that begin with ORACLE.
> F. Close regedit.
> G. From the Control Panel, open System.
> H. Click on the 'Environment' tab and
> select the PATH variable. Remove any directory name that has Oracle in
> it. Click Set. Remove any other entries in the
> environment variables that are obviously related to Oracle and delete
> them.
> I. Delete anything from C:\Winnt\Profiles\AllUsers\Start Menu\Programs\
> that starts with Oracle.
> J. Delete C:\Program Files\Oracle (from the Windows NT Explorer or from
> the command prompt).
> K. Reboot your computer.
> L. Delete all ORACLE_BASE directories. This is basically any Oracle
> directory that was created during any install process you did. Note that
> making a mistake in completing the above steps can have serious
> consequences. So, be careful and don't delete anything by accident.
>
> The installation instructions I am giving below
> represent what I had to do to get everything installed on our system,
> but your mileage may vary. There are 50 steps in the
> whole process. Read them all before trying any of them. Installation of
> the packages involved the following steps:
>
> 1. Log in on redtail as a user in the Administrators group.
> 2. Insert the Oracle 8i CD into the drive. The Oracle 8i installer
> automatically runs.
> 3. Click on the 'Install/Deinstall Products' option. The Welcome screen
> pops up.
> 4. Select the 'Next' button. The File Locations screen is displayed.
> 5. Pick the name that will be used for the Oracle Home and enter it in
> the the Name box under the
> Destination label. I chose "HOME1".
> 6. Pick the location of the Oracle Home on the disk you want to use. I
> chose G:\Oracle\HOME1.
> 7. Click Next. A progress dialog box pops up indicated that a product
> list is being loaded. After a few
> seconds, an Available Products screen is displayed.
> 8. Select "Oracle 8i 8.1.5.0.0" (which may be selected by default).
> 9. Click 'Next'. The Installation Types screen is displayed.
> 10. Choose "Typical" (obviously you need the disk space for this option:
> 705MB)
> 11. Click 'Next'. After a short while, the Location for Oracle
> Documentation screen is displayed. I chose
> 'Hard Drive' to have the documentation placed on the disk. Click 'Next'.
> The Database Identification screen is displayed.
> 12. Choose a name for the sample database that will be automatically
> created. This should be of the form "name.domain" where name is the
> database name you want and domain is the name of the computer you are
> installing it on. I chose "starter.redtail" and placed this in the
> Global Database Name field. As you type in the Global Database Name
> field, the other field on the screen (SID) is automatically filled in
> for you. It will contain the "name" portion of the "name.domain" you
> type in the Global Database Name field.
> 13. Click Next. The Summary screen is displayed showing what products
> are about to be installed.
> 14. Click "Install". The Install screen is displayed and files are
> copied from the CD to the disk. Sit back and relax. On the computer I
> was installing this on (named redtail), it took 7.5 minutes. Even after
> the progress bar shows 100%, it will take a few moments before the file
> copy is done. After the file copy, the Configuration Tools screen is
> displayed. It will have two entries. One will be "Net8 Configuration
> Assistant" which will show a status of "succeeded" and a Oracle Database
> Configuration Assistant entry which will show a status of "in
> progress...". A Database creation screen then pops up showing the steps
> that are being taken to set up the "starter" database selected in step
> 12. After the database is created, another dialog pops up showing that
> the Database creation operation has completed. Take note of the Database
> information it displays. It shows the following:
> global database name: starter.redtail
> database system identifier (SID): starter
> SYS account password: change_on_install
> SYSTEM account password: manager
>
> Obviously, the first two items depend on the name you selected in step
> 12 and the name of the host computer you are doing the installation on.
> Select 'OK' in this dialog window.
> 15. After a few moments, the status of the "Oracle Database
> Configuration Assistant" entry in the Configuration Tools display will
> change to "succeeded" and the End of Installation display will appear.
> At this point your options are to Exit or go to 'Next Install'. The
> server software is now installed. Since I will be using redtail for
> client access also, I chose 'Next Install' to proceed with the
> installation of the Oracle 8i
> Client which is on the same CD. After clicking 'Next Install', the File
> Locations screen is displayed.
> 16. The default entry for the name of the Oracle Home will be HOME1
> which was just created in the server software install process and the
> path will likewise be G:\Oracle\HOME1. These selections are fine.
> 17. Click 'Next'. The "Loading Product list" progress dialog displays
> briefly and then the Available Products screen is displayed. This time
> select Oracle Client 8.1.5.0.0
> 18. Click 'Next'. The Installation Types Screen is displayed. Select
> 'Typical' (the default). You'll need another 299MB on your disk for
> this.
> 19. Click 'Next.' After a while, the Summary screen is displayed. It
> shows all the products that will be installed. Click 'Install'. The
> Install screen is displayed. After a few moments, the progress bar will
> show 100%. But, it will take another minute or two
> before the next screen pops up automatically, so wait for it.
> Eventually, the End of Installation screen is displayed. At this point,
> the options are to exit the installer or go to the 'Next Install'. In my
> case, I wanted to use developer tools on the machine where
> the database was installed (tools like ProC/C++) so I chose 'Next
> Install' so that I could install Oracle Programmer.
> 20. Once again, the File Locations screen is displayed. Leave the
> defaults as they are. The files will be placed in the same Oracle Home
> created before (HOME1). Click 'Next'. The Loading Product Information
> pops up momentarily and the Available Products screen is displayed.
> Choose Oracle Programmer 8.1.5.0.0. Click 'Next'. The 'Installation
> Types' screen is displayed. Choose 'Typical' (you'll need 267MB on your
> disk for this.) Click 'Next'. The Summary screen is displayed showing
> the products that will be installed. Click 'Install'. The Install screen
> is displayed. Once again, there may be a delay of a minute or two even
> after the progress bar on the display shows 100%. Just wait and the End
> of Installation screen pops up. That's all the programs from this disk
> that will be installed on this computer. So, click 'Exit' and click
> 'Yes' when the Exit: Are you sure window pops up.
> Close the Oracle 8i installation window and remove the CD from the
> drive.
> 21. Before we move on, we need to edit the initialization parameters for
> the database created during the installation of Oracle 8i. Edit the file
> G:\Oracle\Admin\starter\pfile\init.ora using your favorite text editor.
> I used Notepad. Look for a line that that says log_checkpoint_timeout =
> 1800 Beneath this line add a line that looks like this:
> MAX_ENABLED_ROLES = 25 Save the file and exit the editor. Reboot the
> computer. Make sure you log in as a user from the Administators group.
> Now it is time to handle the most troublesome component to
> install--Oracle WebDB 2.0.5
> 22. The instructions that come with WebDB 2.0
> don't help much when you install it into an Oracle 8i database. Since an
> Oracle 8i database is exactly what we created in the
> steps above we need to follow some special handling instructions
> outlined here. Place the Oracle WebDB CD into the drive.
> This time the installation window does not start up automatically. So,
> click Start->Run and in the 'Open' field, type
> D:\Nt\setup.exe (D is the drive letter of the CD drive on the computer I
> did the installation on). Click 'OK'.
> 23. The Oracle WebDB installer pops up and a window named Oracle
> Installation Settings calls for several pieces of information. First,
> enter your company name in the Company Name field. Then set the Oracle
> Home information. It is important to modify the defaults which are
> presented here. The release notes for Oracle WebDB 2.0 specifically say,
> "If the only Oracle home directory on the machine where you are
> installing WebDB is an Oracle 8i home, the WebDB installer will prompt
> you to install to a different Oracle home. Make sure that you provide
> both a new directory path and a new name for the WebDB Oracle home that
> is different from the Oracle 8i home." In view of this, pick a new name
> and enter it in the 'Name' field. I chose WEBDBHOME. In the Location
> field, type in something new. I chose "G:\Oracle\WEBDBHOME". I left the
> language field as English. Click 'OK'. The screen flashes for a moment,
> and you get back the same Oracle Installation Settings window. The
> Company Name field is blank again but the settings in the Oracle Home
> area reflect what you selected. The location field is now grayed out.
> Type in your company name again in the Company Name field and click
> 'OK'. A window pops up asking which WebDB software you would like to
> install.
> 24. Click 'Custom Install'. Click 'OK'. The Software Asset Manager
> screen is displayed.
> From the 'Available Products' window on the left, click on PL/SQL Web
> Toolkit 4.0.5.4.0, WebDB 2.0.5.6.1, and WebDB
> Listener 2.0.5.6.1 (you will have to use CTRL-click to select multiple
> selections, but you already know that right?) So, now
> you have all three selections highlighted.
> 25. Click the 'Install' button in the middle of the window. The first
> package to be installed is the WebDB PL/SQL Toolkit. A window pops up
> asking for you to enter the SYS user password for the database. In the
> password field enter 'change_on_install'. Click 'OK'. A window pops up
> with 3 fields.
> 26. The 3 fields are the specifications for the WebDB user. Leave all
> the defaults as they are. Just click 'OK'. A 'Specify Database' window
> pops up.
> 27. Since you previously installed an Oracle 8i database, select that
> option from the list (Oracle 8i is the default). Click 'OK'. A
> WebDB Listener window pops up.
> 28. You are asked to specify 'the Data Access Descriptor (DAD)'
> configurations. The four
> boxes are Host Name, Data Access Descriptor Name, WebDB User Name, and
> Port #. Leave the defaults in the first 3
> boxes. But, for me the last one had to be changed. I already have an
> Apache Web server running on port 80 on redtail, so I
> made up a number(that needs to be above 1024). I chose 8000. Click 'OK'.
> The necessary files are copied onto the disk.
> 29. Another WebDB window pops up. Leave all the defaults as they are and
> click 'OK'. An informational dialog pops up telling you that the
> password of the WEBDB user is WEBDB. Don't forget this. Click 'OK'. A
> window pops up asking whether you want to continue the installation. You
> are informed that while the installation is in progress, you cannot
> cancel out of the operation. This is fine. Click 'Yes'. Files are copied
> to the disk. Then a window pops up saying that the PL/SQL Web Toolkit
> installation is completed. Click 'OK'. More files are copied on to the
> disk. When this is done, a window pops up with
> information about how to make additional modifications using WebDB. Also
> a note is given about tnsnames.ora. We'll get to
> that later. Click 'OK'.
> 30. A DOS window pops up showing that rows are being created in the
> database. The output in the
> window will scroll by pretty fast. Don't worry about it. Just sit back
> and wait for it to complete. On the computer I installed it
> on, it took 2 minutes. The DOS window will disappear and the file copy
> will continue. At some point a Window will popup
> asking you if you'd like to install Beta Language files. Since I only
> speak English, I clicked 'No'. A WebDB installation
> completed message pops up. Click 'OK'. The Software Asset Manager window
> is displayed.
> 31. Click 'Exit'. An "Are you sure?" window is displayed. Click 'Yes'.
> 32. Next we have to edit a file called tnsnames.ora which is located in
> the Oracle home that was created for you during the install process
> based on the directory you specified back in step 23. Since I chose
> G:\Oracle\WEBDBHOME in step 23 the file to be edited is
> G:\Oracle\WEBDBHOME\Net80\Admin\Tnsnames.ora That file is currently a
> default configuration, but that configuration needs to be changed. Open
> the Tnsnames.ora file in your favorite text editor. I chose Notepad.
> There will be an entry that looks like the following:
>
> TcpExample.world =
> (DESCRIPTION =
> (ADDRESS_LIST =
> (ADDRESS =
> (PROTOCOL = TCP)
> (Host = Production1)
> (Port = 1521)
> )
> )
> (CONNECT_DATA =(SID = ORCL) )
> )
>
> This entry will serve as a model for the new entry that needs to be
> created. This is a good model for the
> network I am on, which supports TCP. If TCP is not configured for your
> network, this is probably not the entry that needs to
> be changed. Rather than deleting the above entry, make a duplicate copy
> of it within the file and modify this new copy. Modify
> the copy so that it looks like this:
>
> WEBDB.world =
> (DESCRIPTION =
> (ADDRESS_LIST =
> (ADDRESS =
> (PROTOCOL =TCP)
> (Host = redtail)
> (Port = 1521)
> )
> )
> (CONNECT_DATA = (SID = starter) )
> )
>
> Notice that TcpExample.world has been changed to WEBDB.world and that
> Host = Production1 has been changed to Host = redtail. Finally,
> CONNECT_DATA = (SID = ORCL) has been changed to CONNECT_DATA = (SID =
> starter). After making these changes, Save the file and exit the editor.
> 33. Fire up your browser and go to this URL:
> http://redtail:8000/admin_/gateway.htm
> Note that this URL is of the form http://server:port/admin_/gateway.htm
> The server in my case is redtail since that is where
> I installed WebDB. The port is 8000 because that is the port I specified
> during the installation. These values were determined back at step 28.
> 34. That browser window now contains a page titled Oracle WebDB PL/SQL
> Gateway Settings. The first text entry box on the page is under 'Global
> Settings'. It contains the default value 'WebDB'. Leave this box alone.
> The next section of the page is 'Database Access Descriptor Settings'.
> It contains several text entry fields. The only one that needs to be
> changed is the 'Oracle Connect String field'. It currently has the
> default value of 'WEBDB'. Change this to WEBDB.world which is the name
> of the entry you created in step 32. Click the 'Apply' button for this
> section of entries.
> 35. A new page displays in the browser indicating that 'The changes have
> been successfully made!'. WebDB is now configured properly. To test it
> out, enter the following URL in the browser: http://redtail:8000/webdb/
> A window pops up prompting you for a username and password. For the
> username enter 'webdb' and for the password again enter 'webdb'. You
> then will be allowed access and the browser will display a page saying
> "Oracle WebDB" This page will have several links including Browse,
> Build, Administer, Monitor, and Sites. Everything is working OK. The
> hard part is over. Eject the WebDB CD from the drive. 36. Now it is time
> to move on to the installation of Oracle Enterprise Manager. Put the
> Oracle Enterprise Manager 2.0 CD in the drive. The Installer program
> starts automatically. When it does, click the "Begin Installation"
> option. After a few moments, the Welcome screen is displayed. Click
> 'Next'. The file locations screen is displayed. At this point it is
> important to change the defaults which are displayed in the two text
> entry areas under Destination. If you followed all steps above, you will
> see that the defaults are the name and location of the Oracle Home you
> have already set up. The installation guide (a tiny 29 page booklet)
> specifically states: " If you received Oracle Enterprise Manager version
> 2.0 as part of Oracle 8i (Oracle 8.1.5), install the Oracle Enterprise
> Manager Client, Oracle Management Server, and management applications in
> a different home than Oracle 8.1.5." So, you must change those
> defaults. Thus, for the name I used OEM and for the location I used
> G:\Oracle\OEM. After selecting the Name and Path, Click 'Next.'
> The Available Products screen is displayed.
> 37. Select Management Server and Enterprise Manager Client 2.0.4.0.0
> (which is
> the default). Click 'Next'. The Installation Types screen is displayed.
> Select 'Typical'. You need 130MB on your disk for this.
> Click 'Next'. After a few moments, the Summary screen is displayed. It
> shows the products that will be installed. Click 'Install'.
> The Install screen is displayed. Sit back and relax. On the computer I
> installed it on, it took 3 minutes. When it is done, you'll
> notice a DOS window pops up as well as a 'Configuration Assistant'
> window which is used to set up the Repository.
> 38. There are 3 text entry fields on the Select Database for Repository
> window. The first is the User Name to use to log on to the database. The
> user you enter must have DBA privileges. Since I had not set up any such
> user on my own at this point, I chose to use the user that was setup for
> me during the installation of Oracle 8i in the first 20 or so steps
> above. This was given in step 14 when the 'starter' database was setup.
> So, type in SYS for the username. Step 14 above shows that the password
> for this user is change_on_install (with underscores as shown). So, type
> in that password in the Password box. The 'Service' box is the third box
> on this screen. Here you enter the name of the computer you installed
> the database on as well as the port and the name of the database. Back
> around step 12 we indicated that the name of the database was 'starter'.
> It was installed on the computer named redtail which we are also going
> to install Oracle Enterprise Manager. The default port was selected for
> us
> back then and that port is 1521. So, putting that all together, we need
> to type redtail:1521:starter in the Service box. Then,
> click 'Next'.
> 39. Now we see that a warning message is displayed. It says that the
> database will not support an Oracle
> Enterprise Manager V2 repository because init parameter "processes"
> value = 59 is less than the minimum value = 200. The
> dialog box asks if you are sure you want to continue. Well, at this
> point don't panic. We will easily fix this problem a little later.
> So, at this point just press 'Yes' to continue. The 'Repository Login
> information' screen is displayed.
> 40. This screen has three text entry boxes that must be filled in. You
> will need to enter the User name and then in the next two boxes the
> password. For the user name box, you may want to select the default
> which is the name of the computer. But, I chose another name instead.
> The name I chose was REPUSER (for repository user). But, it shouldn't
> matter what you choose. Enter the password to use for this user. You
> make this password up (but, don't forget it!). After typing in the
> password in both password fields, select 'Next'. The Create Repository
> Summary screen is displayed.
> 41. This screen shows the options that will be used to create the
> repository in the starter database. Click Finish. The configuration
> Action Progress window is displayed. It will show the four steps which
> are being taken. When the window displays "Processing completed", click
> on 'Close' within that window. The Configuration Tools window is
> displayed momentarily showing that everything succeeded. Then the End of
> Installation Window is displayed. Click 'Exit'. The "Exit: Do you really
> want to exit?" window is displayed. Click Yes.
> 42. You are back at the screen which popped up when you first put the
> Oracle Enterprise Manager CD in the drive. Close the window and remove
> the CD from the drive.
> 43. Now it is time to go back and fix the problem that came up in step
> 24. To fix this problem, we can use
> Enterprise Manager itself to change the value of the initialization
> parameter it told us was too low. Click Start->Programs. You
> will notice that you now have two entries that say "Oracle". One says
> 'Oracle - HOME1' and the other says 'Oracle - OEM'.
> Select 'Oracle - OEM'->DBA Management Pack->Instance Manager. The Oracle
> Enterprise Manager Login screen pops up.
> A radio button shows two options: "Login to the Oracle Management
> Server" and "Connect directly to a database" (this is the
> default). Select "Connect directly to a database". In the Username field
> you will need to enter the name of a user with DBA
> privileges. Enter "SYS". For the Password field enter "oracle". For the
> Service field, enter the database where you installed the
> repository in the previous steps, which should be the starter database.
> Note that you'll enter this in the format
> host:port:databasename. In my case, it was redtail:1521:starter. From
> the "Connect as" drop-down list select SYSDBA. Select
> 'OK'. The Instance Manager window pops up.
> 44. Notice that the database you are connected to is highlighted in the
> navigation area on the left. Click on "Initialization Parameters" in the
> navigation area. The right half of the window then displays
> the 'Basic Tuning' parameters. The parameter near the end called
> "processes" is the one that Oracle Enterprise Manager was
> complaining about before. Click on the "59" next to the "processes"
> parameter and change it to 200. This is the minimum value
> you were told you needed.
> 45. Click on the 'Save' button below the Basic Tuning parameter list. A
> Save dialog pops up. Here
> you enter a filename. It should be starter.ora since the name of the
> database is 'starter'. Then click 'OK' in the Save dialog. A
> "File Saved Successfully" dialog pops up. Click 'OK' to close this
> dialog.
> 46. To make the parameter change effective you'll need to shutdown the
> starter database and start it back up again. To do this, click on
> 'Database' in the navigation area on the left. You see a traffic light
> indicating Green and the selection to the right of it is 'Open'. Click
> on 'Shutdown'. Then click on 'Apply' at the bottom of the window. A
> 'Shutdown Options' dialog appears with four options. Select 'Immediate'
> (the default) and click on 'OK'. A window pops up showing a progress bar
> indicating that the starter database on port 1521 is in the process of
> being shutdown. It may take a minute or two. When the shutdown
> completes, a dialog window appears with the message "ORACLE instance
> shutdown". Click 'OK'. The traffic light will now indicate Red and the
> option next to it will show 'Shutdown' as selected.
> 47. Now you will need to restart the database. This time when it starts
> up, the new processes=200
> parameter will be in force. To restart the database, click on the 'Open'
> option next to the traffic light. Click on the 'Apply'
> button at the bottom of the window. A Startup Options window pops up.
> 48. Select the 'Local Parameter file' option (the default). Click
> "Browse". An "Open" file selection window is displayed. The only file
> that will be displayed there is 'starter.ora'.
> Select this as the file name and click 'Open'. You are returned to the
> Startup Options window with the path to the starter.ora
> file now displayed in the file name entry box. Click 'OK'. You will see
> a window saying "Startup in progress for" the database.
> 49. After the database is started a dialog window will pop up saying
> "Oracle instance opened. Click 'OK'.
> 50. Now click on Initialization Parameters in the navigation area on the
> left and you will see that the database is indeed running under your new
> processes=200 parameter. We are done with Oracle Enterprise Manager for
> now. Click on the 'File' menu and select 'Exit'. Reboot the computer.
> You are done.
>
> Note that the Readme file for Enterprise Manager seems to have some
> pertinent inforelative to the Server Manager. Read up on this. It will
> probably explain a mystery or two. One important item to note is this
> which is stated in the Readme: "If you are running a Management Server
> and its repository on the same Windows NT mahcine, the OMS will not
> automatically start upon restarting of the machine. You must manually
> start the Management Server, after ensuring the local database has also
> been started." Hmmm. That applies to the installation I just did. I'll
> need to keep that point in mind.
>
> Charles Larry
Received on Thu Aug 05 1999 - 00:00:00 CEST

Original text of this message