AS400 v5r1 MIMIX Trigger Errors
Tom
issue is that when we switch from the production server to the backup
server using Mimix, many Triggers fail.
Research shows that copying a database from one library to another
requires re-compiling triggers. But if we are using Mimix, everything
should be the same between the two libraries?? MIMIX is telling me it
is not their problem. Same with IBM and the app developers. Has anyone
else had this issue with Mimix?
We are running a client/server application on an iSeries AS400 DB2
v5r1 with PCs running iSeries Access v5r2 ODBC. Our application was
built in Delphi and uses BDE. In our production environment, we have
no issues with Trigger errors. I admit I am not the most knowledgable
user of the iSeries, so let me know if I left out any critical info.
Jonathan Ball
I'm not sure how Mimix handles copying the database.
If it is saving objects on one system and then
restoring them on another, information in the restored
object will point to the trigger program. However, if
that program doesn't exist on the target system, or if
it exists in a different library, you'll get an error
when a database operation attempts to invoke the tirgger.
Peter Sawatzki
jon...@whitehouse.not says...
> I'm not sure how Mimix handles copying the database.
> If it is saving objects on one system and then
> restoring them on another, information in the restored
Mimix uses journaling to update the data on the backup system, so the
triggers have to be disabled on the backup system.
Peter
jb
news:MPG.1a0f50c7d...@news.online.de...
The trigger programs I wrote are also Mimixed so I query a data area in a
library which is not subject to Mimix. If the data area dosnt exist or has
the wrong value the trigger program just ends.
Our Mimix copy shows the correct programs in place as triggers exactly as
expected. This dosnt really solve the OPs problem though.
--
Jonathan.