IDS version 11.50.xC6 is currently available.
It has become usual for these fixpacks to bring a lot of new
functionality, besides the usual bug fixing.
From the release notes:
1.5 What's New in Version 11.50.xC6 of IBM Informix Dynamic Server
1.5.1 External Backups on RS Secondary Servers
1.5.2 Dynamically Start, Stop, or Restart Listen Threads
1.5.3 SQL Administration API Portal: Arguments by Functional
Categories
1.5.4 Connection Manager Proxy Support
1.5.5 View Event Alarms in the Scheduler
1.5.6 Improved Transaction Information
1.5.7 Enhancements to the OpenAdmin Tool for IDS
1.5.8 Enhancements to the Schema Manager plug-in for the OpenAdmin
Tool for IDS
1.5.9 Enhancements to Merging Information into a Target Table with
the MERGE Statement
1.5.10 An ALTER FRAGMENT Operation Can Now Force Out Transactions to
Get Exclusive Access to Tables
1.5.11 RETAINUPDATELOCKS Environment Option
1.5.12 New Column Size Field Format for CDC Records
1.5.13 Enhancements to the Enterprise Replication plug-in for the
OpenAdmin Tool for IDS
1.5.14 Enable or Disable Enterprise Replication Event Alarms
1.5.15 XA Transaction Support for Updatable Secondary Servers in a
High-availability Cluster
1.5.16 Deploying Instances with the Deployment Utility
1.5.17 Installing IDS by Using an RPM package (Linux)
1.5.18 Migrating or Upgrading High-availability Clusters
1.5.19 Upgrading to a New Server or Fix pack
1.5.20 Quickly Reverting to Your Source Server After a Failed
Upgrade
1.5.21 Light Scans on Tables
1.5.22 Process Multiple Basic Text Search Queries Simultaneously
1.5.23 Load and Unload Data with External Table
Some of these will probably get blog coverage in a near future.
I wish you all an excelent 2010, full of Informix of course ;)
Regards.
On PPA there are 2 downloads for each version:
Informix Dynamic Server Enterprise Edition V11.50.UC6 Linux x86
English(CZ6QJEN) - View details
Informix Dynamic Server Enterprise Edition V11.50.UC6 Linux X86
English(CZ79IEN) - View details
Informix Dynamic Server Enterprise Edition V11.50.FC6 Linux x86 64 Bit
English(CZ6QKEN) - View details
Informix Dynamic Server Enterprise Edition V11.50.FC6 Linux X86 64
English(CZ79JEN) - View details
Any which is the correct one to download for each version, or what the
differences are? Install method perhaps? (Clicking on View Details doesn't
show anything useful).
thx
Tried the "J" one.
"The wizard cannot continue because of the following error: could not load
wizard specified in /wizard.inf (104)"
I've said this before, but it absolutely *amazes* me why they have to
complicate these installs for everyine with Javashite.
Off to spend a couple of hours trying to debug the wizard.inf message now
... :-(
I still can't get past this error and get 11.5UC6 installed, despite hours
of Googling, if anyone has any suggestions ...?
thanks
Neil
helps. i had a major headache trying to install it finally i installed
a 'proper' java version.
i also had to runit with -debug as in the install script
found out that the debug info was in /tmp/informix/
had to create some sym links to libs which the installer could not
find....
-->> Fernando, i guess its file a bug time...
OR better get the old scripts back not java install.
Java is owned by obstacle nowadays so why sponsor the competition.
Superboer.
On 4 jan, 13:40, "Neil Truby" <neil.tr...@ardenta.com> wrote:
> "Neil Truby"<neil.tr...@ardenta.com> wrote in message
>
> news:7q71lj...@mid.individual.net...
>
>
>
> > "Ian Michael Gumby" <im_gu...@hotmail.com> wrote in message
> -->> Fernando, i guess its file a bug time...
>
> OR better get the old scripts back not java install.
Hear bloody hear!
--
Cheers,
Obnoxio The Clown
http://obotheclown.blogspot.com
I will now proceed to pleasure myself with this fish.
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
IMHO the java installer is the worst possible solution for
a problem that didn't exist.
Regards,
Bogdan BOTEZ.
I haven't install it yet. The typical problemwith the installation
relates to the fact that some Linuxes don't bring a "proper" Java.
This "proper" of course has to be put into quotes. I believe it's
"open-jdk". And this has some known issues. If you don't have Java
installed it will use a JRE bundled in the package. As of yet I didn't
know of other way to force this besides the dirty trick of "mv
/usr/bin/java /usr/bin/java.ori". Art has another solution that I don't
know if it was introduced in this fixpack (check his post please).
As for the filling of a bug there are two problems:
1- I don't have access to it (some IBMers posting here may have).
2- If you're not following the pre-requisites it would not be accepted
(like if you're installing in a non-supported Linux flavour, or if the
requirements reference a standard JRE for example (I didn't check it...)
Regards and good testing for xC6.
| Fernando Nunes <domus...@gmail.com>
Sent by: informix-l...@iiug.org 01/04/2010 09:03 AM |
|
|
I spent ages finding what the "approved" favours of Linux are (for xC3, the
latest for which it's published) - there used to be a link down the side of
www.informix.com that gave this but it's now been replaced by the infinitely
more useful "Informix on Facebook" link ;-) - and the one I'm using, Centos,
isn't there (although it's supposed to be a clone of RHEL).
I'll try some of the others' suggestions ...
Thanks!
|
|
(Just for the record it is "-javahome none)
Makes no difference. Thanks anyway.
Few clarifications to questions / comments:
>> 1. Installer always attempts to use JRE from the PATH first. It enables
>> the installer to start quickly.
In case of Linux, since a standard JRE is not shipped, its recommended to
use "-javahome none"
switch to the installer. It forces the installer to use bundled JRE (ensure
file .jvm.bin is present in the
directory from where installer is launched).
Makes no difference. Perhaps it's something about centOS, though I'd be
surprised.
>> 3. With 11.50.xC6, as far as media types are concerned, RPM support has
>> been reintroduced.
Based on the enclosed part number reference,
- tar file is the same as previous releases of 11.50.
- bin file provides an RPM based installer. See Infocenter
documentation which will be updated
soon with details on this (should be available by 01/05/10)
- we will work to enhance description for bin file.
That gives:
bash +x CZ79IEN.bin
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
tar: jre/jre/javaws/javaws: Cannot create symlink to `../bin/javaws':
Operation not permitted
tar: Error exit delayed from previous errors
The included VM could not be unarchived (TAR). Please try to download
the installer again and make sure that you download using 'binary'
mode. Please do not attempt to install this currently downloaded copy.
Hi Neil,
/* old man ranting */
WHO on this earth, has an advantage of all that very
unnecessary and annoying java installer thing?
Anyone have only 1 reason, why this was created?
I want/need to learn something.
/* end of omr */
Now, what we did when we had problems on SuSE 11.2:
We deinstalled SuSE java completely.
Then the JRE, which comes with the package was installed and
installation of IDS was possible.
But then we did some analysis, created a good old cpio archive,
and alas: Next installation (using the cpio archive) was done in
less than 30 secs, instead of 1.5 minutes!
And yes, we use very fast disks :)
Note to IBM officials:
PLEASE give us a version, where the java thing can be
avoided altogether. Java in first place always means
incompatibilty issues and other unnecessary problems!
dic_k
--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe
Can I suggest we all log a feature request with technical support for a
non-Java, non-RPM, non-anything tarball install option?
--
Cheers,
Obnoxio The Clown
http://obotheclown.blogspot.com
Richard Kofler wrote:
> Note to IBM officials:
> PLEASE give us a version, where the java thing can be
> avoided altogether. Java in first place always means
> incompatibilty issues and other unnecessary problems!
Can I suggest we all log a feature request with technical support for a
non-Java, non-RPM, non-anything tarball install option?
--
Cheers,
Obnoxio The Clown
http://obotheclown.blogspot.com
I will now proceed to pleasure myself with this fish.
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
<Use of Java installer for Informix product>
>
> /* old man ranting */
> WHO on this earth, has an advantage of all that very
> unnecessary and annoying java installer thing?
> Anyone have only 1 reason, why this was created?
> I want/need to learn something.
> /* end of omr */
>
/* Old man speculating */
Customer: "WTF is this 'tarball'? WTF is a gzip?"
IBM PHB: "Dang, how can we have *one* installer for all platforms,
including Windows?"
Fresh faced enthusiastic IBM Intern: "A single Java app works, without
recompilation, on Unix, Linux, MacOS, Windows etc. Write once, run
everywhere!"
IBM PHB: "Make it so!"
/* end of OMS */
--
RGB
- who prefers .tgz to .cpio :-)
Whishfull thinking, in your install app you have to check for windhoze
anyway since it has a registry and deal with that.
If you build an installer for unix/linux(read tar folowed by an
install script to set permissions etc) and one for windhoze you
should be covered.
so you have a lot of extra unneeded crap in the installer.
One could build a java app which does the configuring of an example
instance in java.
That means someone who wants to do a quick install and config is not
bothered with the java crap.
Superboer.
On 5 jan, 16:06, RedGrittyBrick <RedGrittyBr...@spamweary.invalid>
wrote:
Why are you arguing with a hypothetical fresh-faced enthusiastic IBM
Intern who didn't post here and who probably doesn't exist?
;-)
--
RGB
Write once, crash everywhere
I could agree with that, although it would not be politicaly correct of
course...
> Its not that Java is a bad thing, its just that the implementation of
> the java installer is pretty messed up because they (IBM) didn't write a
> good installer.
If that was proved to be true, I could also agree with that.
> If I understand the 'pain', IBM, in their infinite wisdom decided that
> they'd like to simplify everyone's life and offer a nice easy GUI tool.
> Because they don't know what is out there on the customer's machine,
> they decide to bundle a JRE and then install it off and use it instead
> of the java version already on the server.
You don't. I wonder if you bothered to read the thread...
The installer will use any "java" found on the system, and that is the
beginning of most problems. Specially because some "pure" GPL
distributions don't use the "standard" JRE. And apparently (oh, oh
surprise, this "other" java works differently from the "standard")
IBM also provides a way to force the utilization of the bundled JRE.
And Neil apparently had problems with this. Let me tell you I've used
the JAVA installers on Linux, AIX, HP-UX, Tru64 and Solaris, and I don't
recall having problems with the bundled installer. I'm not sure what is
happening with Neil's environment. It can be some xC6 specific issue of
course...
>
> This is a simple thing to fix. Really. But of course being IBM and being
> the fact that certain folks at IBM have brown necks, one knows with 100%
> certainty, they will never get this straight.... but being the optimist
> that I am, lets see if we can try....
>
> First, instead of bundling a JRE, the 'downloader' can do a simple
> command of $> which java . (The $> is an attempt of showing a generic
> Unix/Linux command prompt.) If the result is null or rather the error
> message when one can't find a certain unix program in their $PATH
> environment variable, the IDS install can then ask the
> User/Sysadmin/DBA/wonk/whatever to either correct their PATH shell
> variable to include their java, or to download a JRE of java and then
> add it to their environment variables. NOTE: If the wanker can't
> properly bring down a JRE, install it in to some /opt/blah/blah
> directory, then set their PATH and shell environment to see it, then
> they need to call Art, pay him shit loads of money to do it for them. :-)
>
So... nice lecture. But the fact is that the install script does it more
or less as you describe... Useless talk...
> Then they have Java.
>
> If they do have Java, then the installer can do a check to see which
> version of Java is installed. Again its pretty straight forward... $>
> java -version
>
> Then the installer can check to see if the version they have is the same
> or greater than the version used in the installer.
> Again, if not, the installer can recommend that the wanker go out and
> install a newer version of java in some blah-blah blah directory and
> point to it in their shell environment.
>
> Other companies do this, like err Sun for example.
Nice idea. But what happens when the issue is not the version, but
instead the "flavour"?
The Java vs non-Java installer is an endless discussion. I believe we
all want an installer that works. Even shell script is not standard! And
I remember issues with the shell scripts in the older installers... So
Java vs non-Java will not get us anywhere...
Regards.
P.S.: I haven't installed xC6 (GA version) yet. I did set it up for
silent installation and asked the sysadmins to install it. No errors
reported... This was on HP-UX.
P.S.S.: Neil, the machine notes should mention the supported Linux
versions. By no means I'm suggesting we must use a supported Linux
version for test/development/whatever except production systems. But it
can probably make a difference.
Neil, did you uncompress the *.tar or run the *.bin with user informix?
If not, can you try it?
Thanks for the compliments.
Meanwhile, drop down from the cloud:
http://en.wikipedia.org/wiki/Free_Java_implementations
"Free" linuxes have used different components to avoid the non GPL
portions of JDK/JRE. And this compoments aren't exactly the same, and
don't have the exact behavior of the "classic" JRE.
You can use the one you have installed or ask the installer to use the
bundled one. If that doesn't work that we can consider something is
wrong with the installer and that should be investigated.
For more info search more or less recent threads here.
Regards.
Not a typo, otherwise the narrative wouldn't make any sense!
I know what my speculated FFEII said :-)
--
RGB
> Now, what we did when we had problems on SuSE 11.2:
> We deinstalled SuSE java completely.
> Then the JRE, which comes with the package was installed and
> installation of IDS was possible.
I've done that (uninstalling Java):
[root@localhost crap]# rpm -qa | egrep "java|jdk|jre"
sun-javadb-javadoc-10.4.2-1.1
java-1.4.2-gcj-compat-1.4.2.0-40jpp.115
sun-javadb-common-10.4.2-1.1
sun-javadb-demo-10.4.2-1.1
sun-javadb-client-10.4.2-1.1
sun-javadb-core-10.4.2-1.1
sun-javadb-docs-10.4.2-1.1
Now I get:
[root@localhost crap]# ./ids_install -javahome none
(some java class messages ....)
This application requires a Java Run Time Environment (JRE)
to run. Searching for one on your computer was not successful.
Please use the command line switch -javahome to specify
a valid JRE. For more help use the option -help.
1. Extract the .jvm.bin file manually
2. Run the installer as is with just new PATH settings that you had used in
JRE extraction test. (PATH=.:$PATH; .jvm.bin)
3. . Let the installer use the extracted JRE. How to do it?
a. update path to include the directory
For. example:
export PATH=<your jvm.bin file extracted path>/bin:$PATH
b. Test its effective by running the command
which java (should report <your jvm.bin file extracted
path>/bin/java)
c. Run the installer w/o "javahome none" (w/o quotes) switch. It
should use the extracted JRE.
It all looks a bit odd - still get some Java class messages - but it works.
Sundar also points out that the Linux distro I'm using (CentOS) isn't
supported. A bit odd that it doesn't work as it's supposed to be a clne of
RHEL.
cheers
Neil
Method 1:
In you PATH is a path to java which is installed on the node.
Remove all paths to any java on your node from the PATH.
Run the ids_installer, it will use the java that comes with the product.
Method 2:
run the installer with option "-javahome /tmp"
Both methods worked for me.
Peter