A java-progam (.jar) is calling a webservice, written in C#. I'm able to unzip the jarfile 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. 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".
After installing and configuring application server, the agent on that server started to sent messages like 'The number of active connections is ..' . But.. there are no connections yet on the system (as far as I know)! Grid Control (OMS + agent) = 10.2.05, application server 10.1.2.0.2
Installed and configured application server 10.1.2.0.2 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 […]
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:
– http://support.microsoft.com/kb/918461 (Microsoft? seems to work for VM-ware too…)
– http://www.novell.com/coolsolutions/feature/15345.html (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:
This file contains the Linux boot options and resembles the following:
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791
In the title Linux area of this file, add the clock=pit parameter to the kernel entry. This area should resemble the following:
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791 clock=pit
Save the changes to the file, exit Vi, and then restart the Linux-based virtual machine.
Short one this time, all in favour of getting my green ‘pie’ in Grid Control management server.
Grid Control: 10.2.0.5. Discoverer: 10.1.2.x
In Grid Control, after upgrade to 10.2.0.5, 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 […]
The whole company has to move in the end to Sun Java instead of Jinitiator (also based on Sun Java by the way), so also the Discoverer – application.
Changed the client from Jinitatior 1.3.2 to Sun 5, update 6 (5.0.6). You can download it here by the way.
As of this release you can no longer specify the exact JRE release. Only configure the ‘Family CLSID’.
Configure Discoverer, middle-tier:
1. cd $ORACLE_HOME/discoverer/config
2. backup configuration.xml
3. edit configuration.xml
4. comment out the original Sun JRE tag using the comment tags:
<!– <jvm name=”sun” classid=”clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA” plugin_setup=”http://biserver.domain:7779/jpi/j2re.exe” version=”1.4.2″ versionie=”1,4,2,mn” type=”application/x-java-applet” plugin_page=”http://java.sun.com/products/archive/j2se/1.4.2_06/index.html” disco_archive=”disco5i.jarjar” d4o_archive=”d4o_double.jarjar”/> –>
5. Insert the new Sun JRE tag:
<jvm name=”sun” classid=”clsid:CAFEEFAC-0015-0000-FFFF-ABCDEFFEDCBA” plugin_setup=”http://biserver.domain:7779/jpi/jre5u16.exe” version=”1.5″ versionie=”1,5,0,mn” type=”application/x-java-applet” plugin_page=”http://java.sun.com/javase/downloads/index_jdk5.jsp” disco_archive=”disco5i.jarjar” d4o_archive=”d4o_double.jarjar”/>
Table of the Sun version versus the Family CLSID’s:
1.4.2 : clsid:CAFEEFAC-0014-0002-FFFF-ABCDEFFEDCBA
5.0 : clsid:CAFEEFAC-0015-0000-FFFF-ABCDEFFEDCBA
6.0 : clsid:CAFEEFAC-0016-0000-FFFF-ABCDEFFEDCBA
Oracle quote ———>:
“The behavior will be as follows:
If the user does not have any JRE installed on the client PC, then the JRE installed be what you have configured with the plugin_setup parameter; therefore, we would recommend that you stage the latest minor version within the JRE family.
* For 1.5, it will be 1.5.0_16 (http://java.sun.com/javase/downloads/index_jdk5.jsp).
This would require the Discoverer Administrator to:
* Download the latest jre family Windows executable you plan to use on the Windows clients
* copy or ftp (binary) the executable to the Discoverer middle-tier server at: $ORACLE_HOME/jpi/bin/
You may name it whatever you wish, for example: jre142u18.exe or jre150u16.exe
* Update the plugin_setup=”http://biserver.domain:7779/jpi/jre5u16.exe” (in the file configuration.xml), making sure the executable names match
” <——— end of Oracle quote.