This content has been marked as final. Show 10 replies
With Solaris 9, I had two different versions of JAVA JDK. I changed the symbolic file "/usr/java" to point to "/usr/jdk/latest". This has the 1.5 JDK support. I received assistance from a JAVA programmer who pointed out that the version was inconsistent. He suggested that I could change the profile as well. By default, the java version used are the "SUNWj5*" packages that were recently installed.
The updatemanager now works even between reboots. This is good news. I have always wanted "updatemanager" GUI working with the Solaris 9 environment.
While I can get the Sun Connection product to work, I have always had to uninstall and re-install it to get the command "updatemanager" to permanently work. I did not read the notes but here are actions I took to get the install to work:
1. Install the SUNWj5* binaries (I used the pkgadd tar.Z selections)
2. Point the symbolic link "/usr/java" to "/usr/jdk/latest"
3. Install the Sun Connection product
4. Invoke and register it.
5. Try to install some hard patches and reboot it as expected
6. Invoke it again to see if it has version problems (always does)
7. Run the "/var/update_connection/uninstall" script and then run the installation all over again
8. Now the command "updatemanager" is in sync and it works with different rounds of patching
This workaround worked perfectly for me on Solaris 9. The initial install of updatemanager was fine , patching went smoothly, reboot was fine but I was unable to run updatemanager after that. The step of un-installing and re-install update_connection software fixed my "unknown subcommand getdocument" errors.
The problem is caused by patch 112945-46 containing old files.
The solution is to re-apply the SUNWpprou package from the update manager bundle after applying the problem patch, this negates the need to re-install the entire bundle.
What update manager bundle? Where?
You can download the latest Sun Update Connection install bundle from:
Are they going to put out a patch to fix what they broke?
I have the same issue. Got to love the lack of QA. At least I'm very used to it after a couple years. :-)
A new patch should be coming out which should fix this issue, we have no date for this, but will keep you updated.
Just experienced this same issue again and it's already 2010. Guess a patch was not made available, yet.
The groundwork for a fix has been done, but other issues have arisen so the fix has not been released. Please open a support case if you require the fix in the form of a patch.