Knowabouts regarding C# webservices connecting Oracle database


A java-progam (.jar) is calling a webservice, written in C#. I’m able to unzip the jarfile or load it in JDeveloper to detect which service it is calling, but how do I know the service is listening to that name? Especially it’s not documented and I don’t have a clue about the name of the wsdl-file.

But, I’m an administrator, and in my case I’m able to log in on the Windows-server where the webservice reside. And I’m looking for a service which might be called ‘HummingBirdService’.
– Start –> run –> inetmgr
– The Internet Information Services (IIS) Manager is started.
– Browse to the tree below the node-name, to ‘Web Sites’ –> ‘Default Web Site’ –>and (yes!)  ‘HummingBirdServices’.
(when you rightclick this by the way, the directory of the files on the right side is shown at the button ‘properties’)
– On the right side of this window the file ‘HummingBirdServiceHost.svc’ resides .
– Right click on this filename (still in the inetmgr !) and choose browse…
A browser opens and the method to call your service is shown by means of an URL.


A webservice, written in C#, is calling an Oracle Database. Oracle 9i client has been installed.
Message appears: “System.Data.OracleClient requires Oracle client software version 8.1.7 or greater”.

What is missing here is the data provider for .NET. The standard is missing that option.
To correct this: download the ODAC-install for 9i here (at the bottom of the page the last time I looked). This is a which includes the data provider for .NET.
Then install (custom option, same home as the standard the oracle data provider for .NET in oracle

By | September 28th, 2009|Categories: App. Server|Tags: , |0 Comments

Grid Control: number of active connections is….

Just for my collection of Grid Control messages, bugs and what so ever – for my effort (between my normal business) to get the ‘pie’ completely green and as few ‘critical’ errors as possible, which is sometimes a very depressive task:

After installing and configuring application server, the agent on that server started to sent messages like ‘The number of active connections is ..’  and a high number, too high for the metric.  But.. there are no connections yet on the system (as far as I know)!  Grid Control (OMS + agent) = 10.2.05, application server



1. “Change the value of the parameter KeepAlive to ‘Off’ in httpd.conf” —>  (nice! and what if this is not to be recommended for the application..).
2. “Restart all components using opmnctl stopall and then opmnctl startall” —> I tried to just stop and start the http-server and the agent, but that didn’t work.
3. “Check the current value of the active connections metric using the metric browser.” —>

What the heck is a metric browser, and how to use this…

Just try it out:

a. vi <AGENT_HOME>/sysman/config/  (make a backup in advance..)

b. uncomment the following line:


c. reload the agent through:

<AGENT_HOME>/bin/emctl reload agent

d. check the metric browser:




By | September 23rd, 2009|Categories: grid control|Tags: |2 Comments

OID gives status NONE. Error: sgslunlListen: Bind Failed On Communication Endpoint

Installed and configured application server  on VM-ware with guest-OS Suse Linux 9. All worked fine, until a (hard) reboot by system admin. OID can’t connect to the default port 13060.

Error in $ORACLE_HOME/ldap/log/oidldapd01.log :

“Bind Failed On Communication Endpoint”  and “Dispatcher Process unable to bind to port”

Because it was a rough shutdown, I cleaned up all the necessary things like ods.ods_process, state-directory, ‘netstat -a’ etc., all the things the note 329808.1 (Troubleshooting OID) also is mentioning.  Ldapbind still didn’t want to connect.

Even thought of note 444873, about not setting the ‘setuid’ on the mountpoint, and checking the firewall. Permissions of the files perhaps…

Eventually I just ran $ORACLE_HOME/ again in the ORACLE_HOME of the infra. Problem solved…. Aaargh !! How on earth is it possible!  Most likely I made a mistake while installing (I was root too at that moment) and ran only at the middle-tier. Can’t think of any other reason for the time being unfortunately.

Had to be sleeping at the time, or just getting old..  No comment on the last remark please 🙂

By | September 10th, 2009|Categories: App. Server|Tags: , , |2 Comments

VM-time out of sync, runs too fast with guest-O.S. Suse Linux 9 / 10

Grid Control is calling  >> “Difference between OMS system time and Agent system time is 121 mins and has exceeded the critical threshold 120 mins”

The system time runs too fast on a (Suse) Linux-based (kernel 2.6) virtual machine, while the ntp has been configured. There are a lot of documents regarding this kind of issues. For explanation and understanding a few documents we used: (Microsoft? seems to work for VM-ware too…) (time not syncing with ntp-server)

Next option for me when all above should not be working, but didn’t have to use it:

Solution we implemented, seemed to work:
– add the clock=pit parameter to the kernel entry (for explanation, see below)
– in addition add the option ‘burst iburst‘ to the ntp-configuration.

To see by the way how the ntp is working:
# watch ntpq -p

Clock=pit for the GRUB bootloader
In the guest operating system, open the /boot/grub/menu.lst file by using a text editor such as Vi. For example, type the following command from a console, and then press ENTER:
vi /boot/grub/menu.lst
This file contains the Linux boot options and resembles the following:
title Linux
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791
initrd (hd0,4)/initrd
title windows
In the title Linux area of this file, add the clock=pit parameter to the kernel entry. This area should resemble the following:
title Linux
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791 clock=pit
initrd (hd0,4)/initrd
Save the changes to the file, exit Vi, and then restart the Linux-based virtual machine.


By | September 9th, 2009|Categories: grid control|Tags: , |0 Comments

Discoverer shows down in Grid Control while up.

Short one this time, all in favour of getting my green ‘pie’ in Grid Control management server.

Grid Control: Discoverer: 10.1.2.x
In Grid Control, after upgrade to, a Discoverer target shows down in the list, while it’s functioning quite well.

It seemed an old bug (Grid Ctrl 10.1.04) is still not fixed:
– Note: 332363.1


1- Remove the Application Server target which owns the Discoverer component (10.1.2) in the Grid Control

2- Stop the agent

3- Backup the file %CENTRAL_AGENT_ORACLE_HOME%/sysman/admin/metadata/oracle_discoverer.xml file.

Replace this file by:

%BI_ORACLE_HOME%/sysman/admin/metadata/oracle_discoverer.xml file

BI_ORACLE_HOME corresponds to the Oracle_Home where Discoverer 10.1.2 is installed.

4- Restart the agent

5- Rediscover the Application Server target on the host, by typing (Agent-environment)  ‘agentca -d’.

By | September 9th, 2009|Categories: grid control|Tags: , |2 Comments