Do you have enterprise? If so have you also upgraded the enterprise plugin to 3.4.5?
I can’t imagine why you’d be seeing 3.4.4 though. =/ Unless the old one is still running somewhere? Make sure there’s no lingering java processes from the old version. (or restart the server entirely if that’s easier)
No, I’m running the GPL version. I already restarted the server but the problem still exists. I deleted the entire folder of the former version it’s really weired.
with openfire 3.4.5 GPL ver. i have a problem connecting (or creating a fresh new) to Oracle DB. with openfire 3.4.4 it’s OK.
Database and Version:
Oracle
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
JDBC Driver:
Oracle JDBC driver
JDBC Driver Version:
10.2.0.3.0
va Version:
1.6.0_04 Sun Microsystems Inc. – Java HotSpot™ Server VM
Appserver:
jetty-6.1.x
OS / Hardware:
Linux / i386
error.log is attached.
thanks for help.
I am have the exact same issue with Oracle on the mac, tried several Oracle JDBC driver versions.
Java HotSpot™ Client VM (build 1.5.0_13-121, mixed mode, sharing)
Not attaching a log, as it matches azagzin’s log file almost verbatim.
Help…
putting openfire in debug nets:
2008.02.11 10:03:58 Proxool statistics legend: “s - r (a/t/o)” > s=served, r=refused (only shown if non-zero), a=active, t=total, o=offline (being tested)
2008.02.11 10:03:58 000000 (01/01/00) - Connection #1 created on demand = ACTIVE
2008.02.11 10:03:58 A connection failed the validation test with error: java.sql.SQLException: ORA-00923: FROM keyword not found where expected
Seems that there is an issue with whatever SQL is being used to TEST the connection.
You’re kidding me, ORACLE can’t do a SELECT 1?
I swear…
Ok, for now, you can get around this by editing openfire.xml … look for:
.
It baffles me that Oracle won’t allow that…
that did it, i ended up using “select * from dual” for testSQL.
thanks for the help.
Awesome!
From dual? What’s that?
Ah, a dummy table. MySQL seems to have it too. I wonder if all of the others have it?
actually, one could do a select 1 from dual as well.
DUAL is a table which is created by oracle along with the data dictionary. It consists of exactly one column whose name is dummy and one record. The value of that record is X. The owner of dual is SYS but dual can be accessed by every user. As dual contains exactly one row (unless someone fiddled with it), it is guaranteed to return exactly one row in select statements. Therefor, dual is the prefered table to select a pseudo column (such as sysdate
select sysdate from dual).
above paraphrased from:
Unfortunately, it appears it is also not standard. =/ MySQL has it, SQL Server, Sybase, and some others don’t. Arg.
I encountered the same problem with Oracle and was about to post my findings here - shame I didn’t wait till tomorrow to perform the upgrade!
I added <testSQL>SELECT 1 FROM DUAL</testSQL> to the defaultProvider configuration.
I don’t suppose I could ask if we have folk using and whether you had success with 3.4.5:
SQL Server (Microsoft’s server)
Sybase
Postgres
IBM’s DB2
Just for my own comfort, I’d like to hear someone give a thumbs up to each of these. From the research I just did, the rest -should- be fine. (IE, Oracle is the only one that doesn’t like a SELECT without a FROM)
jadestorm wrote:
You’re kidding me, ORACLE can’t do a SELECT 1?
I swear…
It baffles me that Oracle won’t allow that…
How did this not get caught by Jive QA before the release?
Good question. All I can really say about it at this point is, we’ve identified a gap in our QA procedures that needs to be addressed.
Nope - same trouble with DB2 9. Tried updating an Openfire 3.3.3 to 3.4.5.
I’ve spent some hours trying to make the update run. A little bit more testing before getting the release out would have been nice …
I will try the workaround mentioned above. Hope it’ll to the trick.
Let us know if it works so we can make the appropriate adjustment.
I had to make serveral adjustments to your update script to make it work. Would really have helped if you had tested the stuff in advance. You don’t have to buy DB2 for that purpose. The DB2 Community Edition is free - even for commercial use.
Please see attached db2 sql.
One special issue is the size of the vcard column in the jivevcard table. I’ve set the column to VARCHAR(30000) because VARCHAR(2000) won’t work more often than not. VARCHAR(30000) works well for me and so I’ve changed it here to. However you will need a spechial buffer pool for that purpose.
There are also some errors in the asterisks sql scripts as well (update 1 and update 2).
What do you mean by a special buffer pool?
Well - by default you will get an buffer pool named IBMDEFAULTBP with page size 4K while creating a new DB2 database. For the “new” VARCHAR(30000) column this bufferpool is not suitable, because it’s too small. You’ll have to create a new buffer pool with 32K page size. The name is of no importance.
e.g. : CREATE BUFFERPOOL MYBIGBP IMMEDIATE SIZE 1000 PAGESIZE 32 K;
As a second step you have to create a new tablespace using the buffer pool created before.
DB2 will now use the new buffer pool and table space to handle such “big columns” like the VARCHAR(30000) column mentioned above.
e.g.: CREATE REGULAR TABLESPACE MYBIGTS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL MYBIGBP DROPPED TABLE RECOVERY ON;
That’s it.