A customer using Fiserv DNA wants to create a new AM master, and has the following questions.
We have been using AM with our Fiserv DNA production environment for a
number of years. We are planning to create a new AM instance for use
with a DNA database cloned from production each night.
In our production DNA environment, the Appworx tables are in the
same database as the DNA tables. We use Oracle Data Guard to replicate
that database to a standby database. Each evening, we stop the
replication to the standby and copy it to another server where we use it
as a warehouse. This cloned database contains the production Appworx
tables. The new AM instance would be used with this database. We have
no intention of using the Appworx tables that came over in the cloning
process. We will create a new database to hold the Appworx tables for
the new environment.
Do you have any recommendations or things to watch out for? Do you have other Fiserv DNA customers doing something like this?
We are expecting to have to shut down the new AM instance each day
during the cloning process. We're thinking that we may be able to put
an AM agent talking to the production AM instance on the server housing
the new AM instance to accomplish this.
Some questions have been raised as to the DNA QUEUE tables - those
will diverge from production each day when we create a new clone. We'll
also lose any updates to those DNA QUEUE tables each day. Will that
cause a problem with AM History?