Hi Zoltan!
I too do suspect 5.5, I have seen this behavior gradually appear since
the upgrade. When we were using 5.3, the only situation causing a full
recovery log was a logpinning client session, in almost all cases caused
by a broken network adapter of corrupted drivers on the client side.
I
Yvonne,
Use the /SQLSERVER=instance option to indicate which
SQL Server instance you want to talk to. Use this for
all backup and restore operations.
For example:
TDPSQLC BACKUP * FULL /SQLSERVER=SERVER1\INSTANCE1
TDPSQL /SQLSERVER=SERVER1\INSTANCE1
For a command-line RESTORE, when
Well, I knew about the object not found part, what was bugging me was
why it was getting to that. However, I opened a call with IBM to find
out, and found this now closed note:
http://www-01.ibm.com/support/docview.wss?rs=0q1=IC68708uid=swg1IC687
08loc=en_UScs=utf-8cc=uslang=en
It appears that
