| "not valid for operation" error during WebSphere Commerce migration on iSeries platform
|
Technote
(troubleshooting)
| Problem(Abstract)
|
When checking your migration logs, you see a stack trace
similar to the following:
[2007.10.10 17:43:19] Error: SITE in MYDB not valid for operation.
[2007.10.10 17:43:19] Error: SITE in MYDB not valid for operation.
java.lang.reflect.InvocationTargetException
at java.lang.Throwable.<init>(Throwable.java:240)
at java.lang.Exception.<init>(Exception.java:77)
at
java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:54)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.ibm.commerce.migration.controller.CommandLauncher.launch(CommandLauncher.java:37)
at
com.ibm.commerce.migration.controller.DatabaseMigrator.executeCommand(DatabaseMigrator.java:944)
at
com.ibm.commerce.migration.controller.DatabaseMigrator.migrate(DatabaseMigrator.java:860)
at
com.ibm.commerce.migration.controller.DatabaseMigrator.main(DatabaseMigrator.java:220)
Caused by: com.ibm.db2.jdbc.app.DB2DBException: SITE in MYDB not valid for
operation.
at java.lang.Throwable.<init>(Throwable.java:195)
at java.lang.Exception.<init>(Exception.java:41)
at java.sql.SQLException.<init>(SQLException.java:40)
at
com.ibm.db2.jdbc.app.DB2DBException.<init>(DB2DBException.java:47)
at com.ibm.db2.jdbc.app.DB2StatementRuntimeImpl.SQLExecDirect(Native
Method)
|
| Cause
|
| One reason for this error is that the SITE table in the
database MYDB does not have journaling enabled. This will cause any SQL
statements trying to update the table to fail.
|
| Environment
|
| iSeries
|
| Diagnosing the
problem
|
| You can verify that journaling is enabled on the SITE
table by running the DSPFD (DiSPlay File Descriptor) command on it
and checking Page 4 for the parameter "File is currently Journaled".
|
| Resolving the
problem
|
If you don't have journaling enabled,
enable it for the SITE table.
You may also want to check and find out if you have other tables with a
similar problem. This usually happens after a save/restore of the database
(library).
If this is the only problematic table, you can turn on journaling on
single files (tables) by using the
STRJRNPF (Start Journal Physical File ) command; with this command, you
can only specify one file at a time.
If you have several problematic tables, assuming you have a save file of
your database from before the migration, it is easier to delete the
problematic database. Make sure that journaling exists on the system for
this library, then restore the database.
|
|
|
|
|
Current web document: http://www.ibm.com/support/docview.wss?uid=swg21286622
|