You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Frank Otto <ot...@delta-barth.de> on 2009/06/05 12:17:24 UTC

jetspeed 2.2 and sqlbase database: deploy j2-admin -- Invalid program bind variable

Hi,

I want to test jetspeed with unify sqlbase database. I have written an 
sql script for this db. The seed and so one works, but register j2-admin 
failed.


2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] ERROR deployment - Failed to register portlet 
application, j2-admin
org.springframework.jdbc.UncategorizedSQLException: OJB operation; 
uncategorized SQLException for SQL []; SQL state [null]; error code [0]; 
00324 EXE IBV Invalid program bind variable; nested exception is 
java.sql.SQLException: 00324 EXE IBV Invalid program bind variable
	at 
org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:83)
	at 
org.springframework.orm.ojb.OjbAccessor.convertJdbcAccessException(OjbAccessor.java:107)
	at 
org.springframework.orm.ojb.OjbAccessor.convertOjbAccessException(OjbAccessor.java:89)
	at 
org.springframework.orm.ojb.PersistenceBrokerTemplate.execute(PersistenceBrokerTemplate.java:141)
	at 
org.springframework.orm.ojb.PersistenceBrokerTemplate.store(PersistenceBrokerTemplate.java:241)
	at 
org.apache.jetspeed.components.portletregistry.PersistenceBrokerPortletRegistry.registerPortletApplication(PersistenceBrokerPortletRegistry.java:200)
...
Caused by: java.sql.SQLException: 00324 EXE IBV Invalid program bind 
variable
	at 
jdbc.gupta.sqlbase.SqlbaseStatement.SQLException(SqlbaseStatement.java:868)
	at 
jdbc.gupta.sqlbase.SqlbaseStatement.executeCompiled(SqlbaseStatement.java:394)
	at 
jdbc.gupta.sqlbase.SqlbasePreparedStatement.executeUpdate(SqlbasePreparedStatement.java:198)
	at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
	at 
org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAccessImpl.java:216)
...


in jetspeed-ojb.log occurs this at the same time:

2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
executeQuery: jdbc.gupta.sqlbase.SqlbasePreparedStatement@1d52a29
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.RsIterator - 
RsIterator[org.apache.ojb.broker.accesslayer.RsQueryObject[query: 
QueryByCriteria from class 
org.apache.ojb.broker.util.sequence.HighLowSequence  where [tableName = 
SEQ_PARAMETER], class descriptor: 
org.apache.ojb.broker.util.sequence.HighLowSequence]] initialized
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.RsIterator - 
hasNext() -> true
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.cache.MaterializationCache - 
Materialisation of object is finished, push 1objects to cache
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.cache.MaterializationCache - 
Push to cache: 
org.apache.ojb.broker.util.sequence.HighLowSequence{SEQ_PARAMETER,deprecatedColumn}
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.cache.MaterializationCache - 
Clear materialization cache
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
executeUpdate: 
org.apache.ojb.broker.util.sequence.HighLowSequence@1c2ff33[tableName=SEQ_PARAMETER,fieldName=deprecatedColumn,grabSize=20,version=42,maxKey=860,currentKey=840]
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
executeUpdate: jdbc.gupta.sqlbase.SqlbasePreparedStatement@100a384
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.StatementManager 
- closeResources was called
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.cache.MaterializationCache - 
Clear materialization cache
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG 
org.apache.ojb.broker.util.sequence.SequenceManagerHighLowImpl - new 
sequence was 
org.apache.ojb.broker.util.sequence.HighLowSequence@1c2ff33[tableName=SEQ_PARAMETER,fieldName=deprecatedColumn,grabSize=20,version=43,maxKey=860,currentKey=840]
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.core.PersistenceBrokerImpl - 
PB.close was called: org.apache.ojb.broker.core.PersistenceBrokerImpl@3861e6
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.cache.MaterializationCache - 
Clear materialization cache
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
executeInsert: org.apache.jetspeed.om.portlet.impl.InitParamImpl@b1aa09e
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.JdbcAccessImpl - 
executeInsert: jdbc.gupta.sqlbase.SqlbasePreparedStatement@ef2f9f
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.accesslayer.StatementManager 
- closeResources was called
2009-06-05 11:55:17,531 [PortletApplicationManager Descriptor Change 
Monitor Thread] DEBUG org.apache.ojb.broker.cache.MaterializationCache - 
Clear materialization cache


I have no idea which column is wrong. I think is a invalid data type in 
one table, but OJB_HL_SEQ is simple and in my opinion correct.

How can I find out, which INSERT/UPDATE (table) produce this error?


kind regards,

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org