IDS replication bad sized chunk added

Hi guys, someone out there who can help me ? We have a cluster (Solaris, Primecluster) running IDS 9.21. On the first system we have the primary instance running, on the second system the secondary instance is running. From time to time we stop the replication and use the secondary system as a testsystem. There are several dbspaces, consisting of several chunks and now on the secondary system we have accidently assigned a chunk with half of the size the same chunk has on the primary system. And this chunk has not been assigned on the same devicename (directly on disk instead of on the link) Although I've some experience with Informix on standalone systems, I'm not familiar with replication. In my opinion, I think all devices used must have the same logical names (different physical disks of course)on the primary and the secondary server. How can we correct the situation ? Initialise on secondary system and assign all dbspaces and chunks again and then replicate again ? If this is the correct way can someone give a sequence of commands to execute ? If this is not correct or there is an other way, how should we proceed ? Thanks for any reply. Best regards, Jacques Lapeire

Make sure the chunk is empty, drop it (onspaces -d...) and then add it back with the correct size, etc. Run a fake level 0 to /dev/null. -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of JACQUES LAPEIRE Sent: Sunday, July 29, 2007 10:54 AM To: ids@iiug.org Subject: IDS replication bad sized chunk added [9636] Hi guys, someone out there who can help me ? We have a cluster (Solaris, Primecluster) running IDS 9.21. On the first system we have the primary instance running, on the second system the secondary instance is running. From time to time we stop the replication and use the secondary system as a testsystem. There are several dbspaces, consisting of several chunks and now on the secondary system we have accidently assigned a chunk with half of the size the same chunk has on the primary system. And this chunk has not been assigned on the same devicename (directly on disk instead of on the link) Although I've some experience with Informix on standalone systems, I'm not familiar with replication. In my opinion, I think all devices used must have the same logical names (different physical disks of course)on the primary and the secondary server. How can we correct the situation ? Initialise on secondary system and assign all dbspaces and chunks again and then replicate again ? If this is the correct way can someone give a sequence of commands to execute ? If this is not correct or there is an other way, how should we proceed ? Thanks for any reply. Best regards, Jacques Lapeire ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum. Please do not transmit orders or instructions regarding a UBS account by e-mail. The information provided in this e-mail or any attachments is not an official transaction confirmation or account statement. For your protection, do not include account numbers, Social Security numbers, credit card numbers, passwords or other non-public information in your e-mail. Because the information contained in this message may be privileged, confidential, proprietary or otherwise protected from disclosure, please notify us immediately by replying to this message and deleting it from your computer if you have received this communication in error. Thank you. UBS Financial Services Inc. UBS International Inc. UBS Financial Services Incorporated of Puerto Rico

HDR Replication or ER? For ER there's no such requirement. For HDR, naturally since the secondary server is normally initialized by a restore, it tends to have the same chunk path names, but I know of no requirement. Just the size has to be the same. That said, if the chunk paths and/or offsets are different on the secondary you will be in trouble if one server crashes hard and has to be restored from an archive taken from the other as you may not have those paths available on the target if they were not already reserved for the server and links were not used but rather physical device names. Meanwhile the suggestion to empty the chunk while the secondary is standalone, drop it and recreate it the correct size using a link is a good one on another level. Without the link you'll be in trouble if ever you lose that disk and have to restore to a different structure. Art S. Kagel ----- Original Message ----- From: Jacques Lapeire <ids@iiug.org> At: 7/29 10:54:04 Hi guys, someone out there who can help me ? We have a cluster (Solaris, Primecluster) running IDS 9.21. On the first system we have the primary instance running, on the second system the secondary instance is running. From time to time we stop the replication and use the secondary system as a testsystem. There are several dbspaces, consisting of several chunks and now on the secondary system we have accidently assigned a chunk with half of the size the same chunk has on the primary system. And this chunk has not been assigned on the same devicename (directly on disk instead of on the link) Although I've some experience with Informix on standalone systems, I'm not familiar with replication. In my opinion, I think all devices used must have the same logical names (different physical disks of course)on the primary and the secondary server. How can we correct the situation ? Initialise on secondary system and assign all dbspaces and chunks again and then replicate again ? If this is the correct way can someone give a sequence of commands to execute ? If this is not correct or there is an other way, how should we proceed ? Thanks for any reply. Best regards, Jacques Lapeire ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.