using onspaces for non-mirrored chunks

Hi all, One chunk is down on the secondary database (in HDR). The chunk is not mirrored. When I try to run the command onspaces to bring it up I get the error: >>>onspaces -s wi_d2dbs -p /informix/prod/online02 -o 1650100 ?O>>>Warning: Bringing chunk back online. >>>Do you really want to continue? (y/n)y >>>Verifying physical disk space, please wait ... >>>Cannot change chunk status. >>>ISAM error: illegal argument to ISAM functionIt seems that this onspaces command does not work with non-mirrored chunks!!! Any suggestion to bring it up online? Regards, Long Nguyen=

Hi, I cannot see you would be able to do this using onspaces. I believe the problem is that the data in this chunk might not be recognized as being identical to the copy in the primary instance. If you are in HDR, the easiest way (but maybe time-consuming) should be to bring down the secondary instance, make a restore from the primary backup and re-setup the HDR. Marcus -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Long Nguyen Sent: Thursday, February 01, 2007 6:38 AM To: ids@iiug.org Subject: using onspaces for non-mirrored chunks [8328] Hi all, One chunk is down on the secondary database (in HDR). The chunk is not mirrored. When I try to run the command onspaces to bring it up I get the error: >>>onspaces -s wi_d2dbs -p /informix/prod/online02 -o 1650100 ?O>>>Warning: Bringing chunk back online. >>>Do you really want to continue? (y/n)y Verifying physical disk space, >>>please wait ... >>>Cannot change chunk status. >>>ISAM error: illegal argument to ISAM functionIt seems that this onspaces command does not work with non-mirrored chunks!!! Any suggestion to bring it up online? Regards, Long Nguyen= **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.

Hi Marcus, That is what we are doing so far, ie bring primary backup tapes to HDR site and restore. But this is an inconvenient operation, especially this problem now often occurs due to accumulative effects of another problem "Possible inconsistencies in table ... - index corrupted - run oncheck -CDI ....." which we have refered to IBM Informix without a solution !. We note one thing that we have both ER and HDR in our environment. Anybody uses both ER and HDR and encountered this sort of problem? Long N ================================================================= "Marcus Haarmann" <marcus.haarmann@ To: ids@iiug.org midoco.de> cc: Sent by: Subject: RE: using onspaces for non-mirrored chunks ids-bounces@iiug. [8329] org 01/02/2007 07:03 PM Please respond to ids Hi, I cannot see you would be able to do this using onspaces. I believe the problem is that the data in this chunk might not be recognized as being identical to the copy in the primary instance. If you are in HDR, the easiest way (but maybe time-consuming) should be to bring down the secondary instance, make a restore from the primary backup and re-setup the HDR. Marcus -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Long Nguyen Sent: Thursday, February 01, 2007 6:38 AM To: ids@iiug.org Subject: using onspaces for non-mirrored chunks [8328] Hi all, One chunk is down on the secondary database (in HDR). The chunk is not mirrored. When I try to run the command onspaces to bring it up I get the error: >>>onspaces -s wi_d2dbs -p /informix/prod/online02 -o 1650100 ?O>>>Warning: Bringing chunk back online. >>>Do you really want to continue? (y/n)y Verifying physical disk space, >>>please wait ... >>>Cannot change chunk status. >>>ISAM error: illegal argument to ISAM functionIt seems that this onspaces command does not work with non-mirrored chunks!!! Any suggestion to bring it up online? Regards, Long Nguyen= **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Hi Lng, In this case, you better try to find the reason for corrupt table first. Maybe the only help would be to unload the corrupt table (if possible), drop it and recreate it. Is this only for one table or for many ? Marcus -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Long Nguyen Sent: Friday, February 02, 2007 12:05 AM To: ids@iiug.org Subject: RE: using onspaces for non-mirrored chunks [8333] Hi Marcus, That is what we are doing so far, ie bring primary backup tapes to HDR site and restore. But this is an inconvenient operation, especially this problem now often occurs due to accumulative effects of another problem "Possible inconsistencies in table ... - index corrupted - run oncheck -CDI ....." which we have refered to IBM Informix without a solution !. We note one thing that we have both ER and HDR in our environment. Anybody uses both ER and HDR and encountered this sort of problem? Long N ================================================================= "Marcus Haarmann" <marcus.haarmann@ To: ids@iiug.org midoco.de> cc: Sent by: Subject: RE: using onspaces for non-mirrored chunks ids-bounces@iiug. [8329] org 01/02/2007 07:03 PM Please respond to ids Hi, I cannot see you would be able to do this using onspaces. I believe the problem is that the data in this chunk might not be recognized as being identical to the copy in the primary instance. If you are in HDR, the easiest way (but maybe time-consuming) should be to bring down the secondary instance, make a restore from the primary backup and re-setup the HDR. Marcus -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Long Nguyen Sent: Thursday, February 01, 2007 6:38 AM To: ids@iiug.org Subject: using onspaces for non-mirrored chunks [8328] Hi all, One chunk is down on the secondary database (in HDR). The chunk is not mirrored. When I try to run the command onspaces to bring it up I get the error: >>>onspaces -s wi_d2dbs -p /informix/prod/online02 -o 1650100 ?O>>>Warning: Bringing chunk back online. >>>Do you really want to continue? (y/n)y Verifying physical disk space, >>>please wait ... >>>Cannot change chunk status. >>>ISAM error: illegal argument to ISAM functionIt seems that this onspaces command does not work with non-mirrored chunks!!! Any suggestion to bring it up online? Regards, Long Nguyen= **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.

Hi Marcus, We have sent all the informixtaion to IBM support people and was told where the page was corrupted but have not got the solution!. The Index corruption and "chunk down (as the system does not know how to do and then get PANIC on the secondary site during HDR process) problem occurs on a number of tables so far. Of these tables we have grouped them into 3 categories from our experience, and solved accordingly: 1. Group 1: those tables which we can run "onmode -d index table_name#index_name" from the secondary site to re-send the index from Prim to Sec (fortunately the Index on the Prim side is never corrupted). Of course we have to make sure they are not used by other online users Or the time of re-sending them is under 1 min. 2. Group2: This particular table is just a normal one but intensively updated from a big online program (fortunately this prog is only run once or 2 times per month) , in which both ER and HDR will be intensively used on other tables together with this table. But only this table has corrupted index when this program is run; and worse the HDR site is usually "panic" and down after that!. In this case we have to disable/re-enable the index on the Prim site (and HDR wil handle the Sec site). 3. Group 3: This table is a very huge table and one of its index is a very large index. It takes 1hr 30 min. to send this index to the Sec site; and this table is on the net, ie being used by all our Net users. To handle this we have to create a cron job to release the job at 12:30am each night. We cannot sen it in daytime. This is all the tasks we have to manually fix our HDR problems so far. Until now we don't know why the only HDR problem we have here is "index corruption" accumualted to the point where "chun ### is down" and "system Panic" and the secodary site database is down. Regards, Long N ============================================================================ "Marcus Haarmann" <marcus.haarmann@ To: ids@iiug.org midoco.de> cc: Sent by: Subject: RE: using onspaces for non-mirrored chunks ids-bounces@iiug. [8334] org 02/02/2007 06:54 PM Please respond to ids Hi Lng, In this case, you better try to find the reason for corrupt table first. Maybe the only help would be to unload the corrupt table (if possible), drop it and recreate it. Is this only for one table or for many ? Marcus -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Long Nguyen Sent: Friday, February 02, 2007 12:05 AM To: ids@iiug.org Subject: RE: using onspaces for non-mirrored chunks [8333] Hi Marcus, That is what we are doing so far, ie bring primary backup tapes to HDR site and restore. But this is an inconvenient operation, especially this problem now often occurs due to accumulative effects of another problem "Possible inconsistencies in table ... - index corrupted - run oncheck -CDI ....." which we have refered to IBM Informix without a solution !. We note one thing that we have both ER and HDR in our environment. Anybody uses both ER and HDR and encountered this sort of problem? Long N ================================================================= "Marcus Haarmann" <marcus.haarmann@ To: ids@iiug.org midoco.de> cc: Sent by: Subject: RE: using onspaces for non-mirrored chunks ids-bounces@iiug. [8329] org 01/02/2007 07:03 PM Please respond to ids Hi, I cannot see you would be able to do this using onspaces. I believe the problem is that the data in this chunk might not be recognized as being identical to the copy in the primary instance. If you are in HDR, the easiest way (but maybe time-consuming) should be to bring down the secondary instance, make a restore from the primary backup and re-setup the HDR. Marcus -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Long Nguyen Sent: Thursday, February 01, 2007 6:38 AM To: ids@iiug.org Subject: using onspaces for non-mirrored chunks [8328] Hi all, One chunk is down on the secondary database (in HDR). The chunk is not mirrored. When I try to run the command onspaces to bring it up I get the error: >>>onspaces -s wi_d2dbs -p /informix/prod/online02 -o 1650100 ?O>>>Warning: Bringing chunk back online. >>>Do you really want to continue? (y/n)y Verifying physical disk space, >>>please wait ... >>>Cannot change chunk status. >>>ISAM error: illegal argument to ISAM functionIt seems that this onspaces command does not work with non-mirrored chunks!!! Any suggestion to bring it up online? Regards, Long Nguyen= **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.