WebSphere Commerce Developer

Troubleshooting: SQLException logged when you publish a store archive

You might encounter an SQLException message when you publish the Aurora starter store.

Problem

When you publish the Aurora starter store, SQLException messages similar to the following example is logged in the FFDC logs in /WAS_installdir/profiles/demo/logs/ffdc:
Reporter:com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement@7ef77ef7
java.sql.SQLException: Table/View 'SEOURLKEYWORD' already exists in Schema 'APP'.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source)
	at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1175)
	at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:816)
	at com.ibm.commerce.seo.loader.SEOURLLoader.prepareDB(SEOURLLoader.java:394)
	at com.ibm.commerce.seo.loader.SEOURLLoader.process(SEOURLLoader.java:160)
	at com.ibm.commerce.seo.loader.SEOURLLoader.process(SEOURLLoader.java:128)
	at com.ibm.commerce.seo.loader.publish.SEOURLLoaderTaskCmdImpl.performExecute(SEOURLLoaderTaskCmdImpl.java:140)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.DataDeployController.executeTarget(DataDeployController.java:239)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.DataDeployController.execute(DataDeployController.java:156)
	at com.ibm.commerce.tools.devtools.publish.tasks.catalog.CatalogDataDeployTaskCmdImpl.performExecute(CatalogDataDeployTaskCmdImpl.java:266)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.DataDeployController.executeTarget(DataDeployController.java:239)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.DataDeployController.execute(DataDeployController.java:156)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.PublishStoreProcessCmdImpl.performExecute(PublishStoreProcessCmdImpl.java:364)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.PublishStoreProcessCmdImpl.run(PublishStoreProcessCmdImpl.java:386)
	at com.ibm.commerce.tools.devtools.publish.datadeploy.ScheduledPublishArchiveCmdImpl.performExecute(ScheduledPublishArchiveCmdImpl.java:83)
	at com.ibm.commerce.command.ECCommandTarget.executeCommand(ECCommandTarget.java:157)
	at com.ibm.websphere.command.TargetableCommandImpl.execute(TargetableCommandImpl.java:139)
	at com.ibm.websphere.command.CacheableCommandImpl.execute(CacheableCommandImpl.java:138)
	at com.ibm.commerce.command.AbstractECTargetableCommand.execute(AbstractECTargetableCommand.java:217)
	at com.ibm.commerce.component.BaseComponentImpl.executeCommand(BaseComponentImpl.java:202)
	at com.ibm.commerce.component.WebAdapterComponentImpl.executeCommand(WebAdapterComponentImpl.java:46)
	at com.ibm.commerce.component.objimpl.WebAdapterServiceBeanBase.executeCommand(WebAdapterServiceBeanBase.java:58)
	at com.ibm.commerce.component.objects.EJSLocalStatelessWebAdapterService_ce749a4a.executeCommand(EJSLocalStatelessWebAdapterService_ce749a4a.java:31)
	at com.ibm.commerce.component.objects.WebAdapterServiceAccessBean.executeCommand(WebAdapterServiceAccessBean.java:160)
	at com.ibm.commerce.scheduler.SchedulerJob.process(SchedulerJob.java:520)
	at com.ibm.commerce.scheduler.SchedulerSecurityPriviledgedAction.run(SchedulerSecurityPriviledgedAction.java:59)
	at com.ibm.commerce.scheduler.SchedulerJob.run(SchedulerJob.java:1068)
	at com.ibm.commerce.threadmanagement.internal.BaseWork.run(BaseWork.java:139)
	at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1150)
	at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:199)
	at com.ibm.ws.asynchbeans.CJWorkItemImpl.run(CJWorkItemImpl.java:188)
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: java.sql.SQLException: Table/View 'SEOURLKEYWORD' already exists in Schema 'APP'.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
	... 40 more
Caused by: ERROR X0Y32: Table/View 'SEOURLKEYWORD' already exists in Schema 'APP'.
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(Unknown Source)
	at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown Source)
	at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(Unknown Source)
	at org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(Unknown Source)
	at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source)
	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
	... 34 more

Solution

You can safely ignore these messages.