We have archived logs, ful/incremental/incremental delta backups. For testing purposes, we want to test a tablespace restore (and we chose a tablespace residing on just the data partitions) up the last incremental delta. This is a DPF environment and UDB ESE FP14 (aka v8.2.7).
We've deactivated the db and then issued:
db2_all '<<+0<db2 restore db fdsu01 tablespace(FDSS001_ALL) online incremental auto from /db2backup/fdsu01 taken at 20070618210018 into fdsu01 without prompting"
with the result being:
Authentication successful.

(and that's all.)
And then we issue:
db2_all '<<-0<db2 restore db fdsu01 tablespace(FDSS001_ALL) online incremental auto from /db2backup/fdsu01 taken at 20070618210018 into fdsu01 without prompting'
with the result being:
rah: omitting logical node 0

Authentication successful.

Authentication successful.
/usr/bin/ksh: syntax error at line 1 : `(' unexpected

Authentication successful.
/usr/bin/ksh: syntax error at line 1 : `(' unexpected

We are confounded as to why there seems to be no restore activity and why should there be any syntax error on the 2nd execution when the only difference was -0 from +0.

Is the issue the incremental auto?
Ruby

Found out the answer that since we NOT ONLY changed the data in a table within the tablespace BUT we also created another table within the tablespace past the last backup (incremental delta) whichh thus the Catalog was changed, the info displayed in a list tablespaces show detail, Minimum recovery time, shows that the "timestamp" is past the last backup. So it looks like DB2 is doing a restore but it can't.

It would have been nice had we seen some informational "warning" that a restore couldn't be done.