Error at Quick Launch : Unable to begin processing transformation

[omm]

When I double click the Table Input step and run the preview button, I am able to see the output. But, for the same step when I right click and go the contextual menu, select the preview and run the Quick Launch, I am getting this error.

Unable to begin processing transformation
Error writing log record to table [log_wh_drug_dmsn]
Couldn't execute SQL: LOCK TABLE log_wh_drug_dmsn IN ACCESS EXCLUSIVE MODE
ERROR: relation "log_wh_drug_dmsn" does not exist

[Env: WinXp,kettle 3.2.3,Java 1.6]

I am a newbie and have no clue why this is happening? Any suggestions? Please share

Thanks,
Om

------------------------
STACKTRACE
------------------------
org.pentaho.di.core.exception.KettleTransException:
Unable to begin processing transformation
Error writing log record to table [log_wh_drug_dmsn]
Couldn't execute SQL: LOCK TABLE log_wh_drug_dmsn IN ACCESS EXCLUSIVE MODE
ERROR: relation "log_wh_drug_dmsn" does not exist

at org.pentaho.di.trans.Trans.beginProcessing(Trans.java:1464)
at org.pentaho.di.trans.Trans.prepareExecution(Trans.java:523)
at org.pentaho.di.ui.spoon.trans.TransGraph.debug(TransGraph.java:2930)
at org.pentaho.di.ui.spoon.delegates.SpoonTransformationDelegate.executeTransformation(SpoonTransformationDelegate.java:896)
at org.pentaho.di.ui.spoon.Spoon$27$1.run(Spoon.java:6182)
at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.pentaho.di.ui.spoon.Spoon.readAndDispatch(Spoon.java:977)
at org.pentaho.di.ui.spoon.Spoon.start(Spoon.java:5698)
at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:455)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.pentaho.commons.launcher.Launcher.main(Launcher.java:110)
Caused by: org.pentaho.di.core.exception.KettleTransException:
Error writing log record to table [log_wh_drug_dmsn]
Couldn't execute SQL: LOCK TABLE log_wh_drug_dmsn IN ACCESS EXCLUSIVE MODE
ERROR: relation "log_wh_drug_dmsn" does not exist

at org.pentaho.di.trans.Trans.beginProcessing(Trans.java:1439)
... 16 more
Caused by: org.pentaho.di.core.exception.KettleDatabaseException:
Couldn't execute SQL: LOCK TABLE log_wh_drug_dmsn IN ACCESS EXCLUSIVE MODE
ERROR: relation "log_wh_drug_dmsn" does not exist
at org.pentaho.di.core.database.Database.execStatement(Database.java:1558)
at org.pentaho.di.core.database.Database.execStatement(Database.java:1504)
at org.pentaho.di.core.database.Database.execStatements(Database.java:1675)
at org.pentaho.di.core.database.Database.lockTables(Database.java:4404)
at org.pentaho.di.trans.Trans.beginProcessing(Trans.java:1224)
... 16 more
Caused by: org.postgresql.util.PSQLException: ERROR: relation "log_wh_drug_dmsn" does not exist
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1592)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1327)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:192)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:451)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:336)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:328)
at org.pentaho.di.core.database.Database.execStatement(Database.java:1527)

[slawomir.chodnicki]

Hi there,

to me it looks as if you configured logging for your transformation, but did not create the logging tables. In the transformation settings, check the logging settings. If you configured a logging table, make sure that the right DB connection is used for logging, too. Click the SQL button in the settings dialog to automatically create the logging tables, in case they are missing.

Job logging is configured the same way, in case you want it. All settings are accessible from the logging tab of the job settings dialog.

Cheers

Slawo

[omm]

Thanks for the PERFECT reply.
Yep. After creating the log table, it worked fine.