Welcome to Installing Oracle 11r2 on Windows 2008R2 Server Part 3 of the series
"Doing a Complete install of Siebel 18.104.22.168 on Oracle 11 r2, Win 2008R2. All from Scratch"
In this part we will
- Configure the Oracle Listener
- Verify and Configure Windows Services
- Configure the Windows Firewall
- Do Connectivity Tests
The listener will provide access to the database instance we just created in Part 2. If you desire one listener can cater to more than on database instance on the same port, or you can chose to create multiple listeners on different ports, on for each database instance on the box. The latter provides better granularity control. That's how I will do my install.
To Install an Oracle database we will go through the following steps
- Install the Oracle Database Software This was completed in Part 1 Here
- Configure the Oracle Database This was completed in Part 2 Here
- Configure the Listener
- Verify & Configure Windows Services
- Configure Windows Firewall
- Do Connectivity Tests
To Configure an oracle listener you need to run the netca from a command prompt. Follow the screenshots, and step guide below to configure the database for use as a Siebel development server.
We want to do Listener Configuration. Hit Next
We want to Add a Listener. Hit Next
Provide a Name for the Listener, if you use "One Listener Many Database Instances" then the default name should be fine. I don't, so I'll name the Listener SIEB8DEVDB_LSN. Hit Next
Choose the Supported Protocols (TCP)- Hit Next
Choose a port, I'll use the default for this listener. You need to remember this information. Hit Next
Select No to Configuring more Listeners. Hit Next.
Configuration Complete. Hit Next and Exit the dbca. Notice that dbca will output information to the command prompt it was started from.
We need to verity the Oracle services in the services control panel, we want to ensure that the database instance starts before the listener. This is achieved by setting the Listener service to Delayed Start, see the screenshot below.
Make the required changes to the windows firewall on the windows server.
Test local connectivity to the database instance:
And a real connection to the database too:
The database server is now installed, configured and working.
If you want install an sql developer (or toad if that’s your favorite tool) on the server, just in case you need another type of tool to access the database (I prefer toad – but that’s just me.) SQL Developer is a nice tool too! And I may be switching tools going forward, as the SQL Developer is a free tool, whereas TOAD is quite expensive.
We will get back to the database while installing things on the Siebel server.
I'm still doing the writeup of the Siebel Server Installation....