HI All,
We need your experience to identify the root cause of the issue.
Database Version : 11.7
OS : IBM Aix 6
We have Replication plus product installed on our system. We have Source database and single target which reside on DR server.
During Database Service pack upgrade we have shut down the Source database after Target database perfectly in Sync, later we used to shut down the database target database.
Once upgrade completed, we started the source database everything came up fine and started target database and, but we found error saying, "target database got modified after its created" not able to sync target databases with Source, please find attached for error screen shot.
This issue happened On Jan'24 and we have raised case with Progress vendor but still case is open.
We have encountered similar type of issue where database going to pre-transition state if target database shutdown more than 3 hours database.
When Source and target database are down and in server no users, crontab jobs and control-m schedular jobs also stopped.
Once database restarted on Source side after verification within shorter time, we started target database during that time no application users or jobs not released on server but how it is possible target database got modified?
Source.repl.properties file
====================
[server]
control-agents=agent1
database=prdsl
transition=manual
transition-timeout=600 # doesn't matter if transition is manual
defer-agent-startup=10080
agent-shutdown-action=recovery
[control-agent.agent1]
name=agent1
database=prdslc
host=mfgpro
port=4212
connect-timeout=120
replication-method=async
critical=0
[transition]
database-role=normal
Target repl properties
=============
[server]
control-agents=agent1
database=prdslc
transition=manual
defer-agent-startup=1440
repl-keep-alive=300
schema-lock-action=wait
agent-shutdown-action=recovery
transition-timeout=600
minimum-polling-delay=10
maximum-polling-delay=501
[control-agent.agent1]
name=agent1
database=prdslc
host=mfgpro
port=4212
maximum-message=32
connect-timeout=120
replication-method=async
critical=1
[agent]
name=agent1
database=prdslc
listener-minport=10000
listener-maxport=11000
We need your experience to identify the root cause of the issue.
Database Version : 11.7
OS : IBM Aix 6
We have Replication plus product installed on our system. We have Source database and single target which reside on DR server.
During Database Service pack upgrade we have shut down the Source database after Target database perfectly in Sync, later we used to shut down the database target database.
Once upgrade completed, we started the source database everything came up fine and started target database and, but we found error saying, "target database got modified after its created" not able to sync target databases with Source, please find attached for error screen shot.
This issue happened On Jan'24 and we have raised case with Progress vendor but still case is open.
We have encountered similar type of issue where database going to pre-transition state if target database shutdown more than 3 hours database.
When Source and target database are down and in server no users, crontab jobs and control-m schedular jobs also stopped.
Once database restarted on Source side after verification within shorter time, we started target database during that time no application users or jobs not released on server but how it is possible target database got modified?
Source.repl.properties file
====================
[server]
control-agents=agent1
database=prdsl
transition=manual
transition-timeout=600 # doesn't matter if transition is manual
defer-agent-startup=10080
agent-shutdown-action=recovery
[control-agent.agent1]
name=agent1
database=prdslc
host=mfgpro
port=4212
connect-timeout=120
replication-method=async
critical=0
[transition]
database-role=normal
Target repl properties
=============
[server]
control-agents=agent1
database=prdslc
transition=manual
defer-agent-startup=1440
repl-keep-alive=300
schema-lock-action=wait
agent-shutdown-action=recovery
transition-timeout=600
minimum-polling-delay=10
maximum-polling-delay=501
[control-agent.agent1]
name=agent1
database=prdslc
host=mfgpro
port=4212
maximum-message=32
connect-timeout=120
replication-method=async
critical=1
[agent]
name=agent1
database=prdslc
listener-minport=10000
listener-maxport=11000