Search results

  1. J

    Target replication Database got modified .

    Thanks Tom. We don't have proper logs to share but I'm asking on what situation will encounter this error "target database got modified". How to reproduce the same issue in test environment, please help on the steps
  2. J

    Target replication Database got modified .

    Thanks Tom. The logs I have provided for Feb month only. As stated our Backup will start late night and complete morning around 2AM. Only concern we have when the source and target are in downstate once database started with 2 to 3 mins difference we are seeing target database modified. When...
  3. J

    Target replication Database got modified .

    Hi Tom, Here is the error message. Source log error details: [2024/02/17@11:22:58.663-0500] P-56099336 T-1 I RPLS 152: (10842) Connecting to Fathom Replication Agent agent1. [2024/02/17@11:23:01.693-0500] P-56099336 T-1 I RPLS 152: (10507) The Fathom Replication Server has...
  4. J

    Target replication Database got modified .

    i have attached it.
  5. J

    Target replication Database got modified .

    My Bad..:oops: I have attached now, please share your inputs.
  6. J

    Target replication Database got modified .

    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...
  7. J

    Is DR up to date.

    Rob- To answers to your questions. What causes a filled AI extent to be copied to an archive directory and the original file marked as empty? Are you using the AI File Management Daemon (aiarchiver)? Yes we are using AI archiver with on-demand mode only archive once Ai file Fills up and switch...
  8. J

    Is DR up to date.

    Hi Tom - I have found in target database is matching with Source last Ai extent which archived. The last block received at: Tue Mar 14 10:39:14 2023 Activity information: Blocks received: 45588157 Blocks processed...
  9. J

    Is DR up to date.

    Hi Tom Thanks for the details. To answer to your question Aside from that - why on earth do you have 243 after-image extents on the target? That is an unheard of a number of after-image extents. Please explain why that is. This set up is suggested by the progress vendor long back 3 years...
  10. J

    Is DR up to date.

    HI ALL, I would like to know whether our Replication database DR is Sync with Production. In Source database last Ai extents archived is mfgprod.a27. But in DR target database last Ai file copied is mfgprod.a243. Whenever we check replication status showing "normal processing" and Blocks...
  11. J

    How to Avoid Rebasing databases.

    Thanks Tom for your response initially we used to have two targets due to some reasons they made to 1.
  12. J

    How to Avoid Rebasing databases.

    HI All, Gud mng... Progress database version 11.7.4. OS is AIX 7.1. We have 2 servers Prod and DR with Open edge replication plus enabled. Source DB size db1 is 800gb db2 is 50gb db3 is 15gb db4 is 10gb. Target DB size db1 is 800gb db2 is 50gb db3 is 15gb db4 is 10gb Activity : Management...
  13. J

    Never expiry Password for SQL user id

    HI All, Is there any sql query where we can set password as never expiry for SQl user id. Progress version : 9.1e OS version : Aix 5.3
  14. J

    BROKER: Could not spawn a server. (1890)

    Thanks Rob. Can i set -Mpb parameter to 50, so 50 ports can be used and i will reduce maxport and minport to 13000 to 13500.
  15. J

    BROKER: Could not spawn a server. (1890)

    Thanks Rob. Please find attached screenshot for the error we received during application connection and also i have attached promon report for issue first occurrence and last one. Error in Database : prdslc =================================== 23:18:59 SRV 18: Connection timed out on...
  16. J

    BROKER: Could not spawn a server. (1890)

    Thanks Rob.. Application team contacted QAD vendor and they suggested us to enlarge ports and to add max/min port for SQl Broker also. we are going to implement the same after Change freeze window in next week. Once again we faced application connectivity and found below findings on our...
  17. J

    BROKER: Could not spawn a server. (1890)

    Please let us know what exactly it is causing this error users are facing error again.
  18. J

    BROKER: Could not spawn a server. (1890)

    HI Tom, we have only SQL broker for connecting SQL connections. prdslc.pf file -B 70000 # Number of (8K) Blocks in database buffer -bibufs 200 # Number of before-image buffers -aibufs 300 # Number of after-image buffers #-Mi 2 # Min processes on a client server -Ma 15 # Max number of REMOTE...
  19. J

    BROKER: Could not spawn a server. (1890)

    proserve /progdata/prd/slcdb1/prdslc -m3 -Mi 3 -Ma 5 -Mn 4 -Mpb 4 -S prdslcoi -ServerType SQL proserve /progdata/prd/slcbard1/prdslcb -m3 -Mi 3 -Ma 5 -Mn 4 -Mpb 4 -S prdslcboi -ServerType SQL
  20. J

    BROKER: Could not spawn a server. (1890)

    -B 70000 # Number of (8K) Blocks in database buffer -bibufs 200 # Number of before-image buffers -aibufs 300 # Number of after-image buffers #-Mi 2 # Min processes on a client server -Ma 15 # Max number of...
Back
Top