dbexport DOWN
Posted in 2007
User on Solaris 10 with IDS 10.00.FC5W5 and HDR reported dbexport failing with "No owner present for the table in systables" and the instance crashing with an assert failure (read_record: decompress_row, rsread.c line 2834). One reply pointed to a known dirty-read/remainder-page bug (119881) fixable via patch or upgrade; others noted the message itself says to contact IBM support. Everett Mills suspected running dbexport on the HDR secondary was unsupported and suggested switching it to standard mode (onmode -d standard), but then found it did seem to work. No definitive resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Error Codes & Troubleshooting, Migration, Import/Export & Data Conversion, Internationalization & Character Sets
Hello to all: Dbexport of my BDs does not finish satisfactorily. The error message that shows to me is the following one: No owner present for the table in systables Also in some ooportunidades the instance falls and it shows the following message to me of error: 00:36:05 Assert Failed: read_record: decompress_row, source = 0x151370018, target = 0x210bc50a8 00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68) Thread(213, sqlexec, 20434b068, 4) File: rsread.c Line: 2834 00:36:05 Results: Record not read 00:36:05 Action: Please notify IBM Informix Technical Support. 00:36:05 Stack for thread: 213 sqlexec I hope that can help me to solve the problem. Thank you very much _________________________________________________________________ Sé uno de los primeros a testar el Windows Live Messenger beta. http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
Your bug might be....
Bug: 119881 ASSERT FAILED: READ_RECORD: DECOMPRESS_ROW, SOURCE = A086018,
TARGET = A3294A4 WHEN USING DIRTY READ ISOLATION
Description:
This is caused by a query with isolation level of dirty read. One process
inserts a row with varchars and a rowsize large enough to cause a
remainder
page. A query comes along with dirty read isolation level and happens to
read the home row buffer in memory, but the SL_INDIR flag has not been set
on the home row data page.
If you are 7.3X. Anyway, if you have informix support, they can give you
a patch for it or you can upgrade.
"Juan Pablo" <in4mixperu@hotmail.com>
Sent by: ids-bounces@iiug.org
05/01/2007 11:19 AM
Please respond to
ids@iiug.org
To
ids@iiug.org
cc
Subject
dbexport DOWN [9048]
Hello to all:
Dbexport of my BDs does not finish satisfactorily. The error message that
shows to me is the following one:
No owner present for the table in systables
Also in some ooportunidades the instance falls and it shows the following
message to me of error:
00:36:05 Assert Failed: read_record: decompress_row, source = 0x151370018,
target = 0x210bc50a8
00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
Thread(213, sqlexec, 20434b068, 4)
File: rsread.c Line: 2834
00:36:05 Results: Record not read
00:36:05 Action: Please notify IBM Informix Technical Support.
00:36:05 Stack for thread: 213 sqlexec
I hope that can help me to solve the problem.
Thank you very much
_________________________________________________________________
Sé uno de los primeros a testar el Windows Live Messenger beta.
http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
As it says in the output: Action: Please notify IBM Informix Technical Support. Art S. Kagel ----- Original Message ----- From: Juan Pablo <ids@iiug.org> At: 5/01 12:20:10 Hello to all: Dbexport of my BDs does not finish satisfactorily. The error message that shows to me is the following one: No owner present for the table in systables Also in some ooportunidades the instance falls and it shows the following message to me of error: 00:36:05 Assert Failed: read_record: decompress_row, source = 0x151370018, target = 0x210bc50a8 00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68) Thread(213, sqlexec, 20434b068, 4) File: rsread.c Line: 2834 00:36:05 Results: Record not read 00:36:05 Action: Please notify IBM Informix Technical Support. 00:36:05 Stack for thread: 213 sqlexec I hope that can help me to solve the problem. Thank you very much _________________________________________________________________ Sé uno de los primeros a testar el Windows Live Messenger beta. http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
ok!
Also thanks
bye
>From: "ART KAGEL, BLOOMBERG/ 731 LEXIN" <kagel@bloomberg.net>
>Reply-To: ids@iiug.org
>To: ids@iiug.org
>Subject: Re: dbexport DOWN [9050]
>Date: Tue, 1 May 2007 12:32:00 -0400 (EDT)
>
>As it says in the output: Action: Please notify IBM Informix Technical
>Support.
>
>Art S. Kagel
>----- Original Message -----
>From: Juan Pablo <ids@iiug.org>
>At: 5/01 12:20:10
>
>Hello to all:
>Dbexport of my BDs does not finish satisfactorily. The error message that
>shows to me is the following one:
>
>No owner present for the table in systables
>
>Also in some ooportunidades the instance falls and it shows the following
>message to me of error:
>
>00:36:05 Assert Failed: read_record: decompress_row, source = 0x151370018,
>target = 0x210bc50a8
>00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
>
>Thread(213, sqlexec, 20434b068, 4)
>
>File: rsread.c Line: 2834
>00:36:05 Results: Record not read
>00:36:05 Action: Please notify IBM Informix Technical Support.
>00:36:05 Stack for thread: 213 sqlexec
>
>I hope that can help me to solve the problem.
>
>Thank you very much
>
>_________________________________________________________________
>Sé uno de los primeros a testar el Windows Live Messenger beta.
>http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
>
>
>*******************************************************************************
>Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
_________________________________________________________________
Sabe más sobre la próxima generación del MSN Messenger.
http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
I have the following architecture:
* Solaris 10
* IBM Informix 10.00 FC5W5 + HDR
The execution of dbexport I make it in the secondary server.
Also it is affected by bug ???
Thanks Joseph
>From: "Joseph_Jurcazak@aotx.uscourts.gov"
><Joseph_Jurcazak@aotx.uscourts.gov>
>Reply-To: ids@iiug.org
>To: ids@iiug.org
>Subject: Re: dbexport DOWN [9049]
>Date: Tue, 1 May 2007 12:28:07 -0400 (EDT)
>
>Your bug might be....
>
>Bug: 119881 ASSERT FAILED: READ_RECORD: DECOMPRESS_ROW, SOURCE = A086018,
>TARGET = A3294A4 WHEN USING DIRTY READ ISOLATION
>
>Description:
>This is caused by a query with isolation level of dirty read. One process
>inserts a row with varchars and a rowsize large enough to cause a
>remainder
>page. A query comes along with dirty read isolation level and happens to
>read the home row buffer in memory, but the SL_INDIR flag has not been set
>
>on the home row data page.
>
>If you are 7.3X. Anyway, if you have informix support, they can give you
>a patch for it or you can upgrade.
>
>"Juan Pablo" <in4mixperu@hotmail.com>
>Sent by: ids-bounces@iiug.org
>05/01/2007 11:19 AM
>Please respond to
>ids@iiug.org
>
>To
>ids@iiug.org
>cc
>
>Subject
>dbexport DOWN [9048]
>
>Hello to all:
>Dbexport of my BDs does not finish satisfactorily. The error message that
>shows to me is the following one:
>
>No owner present for the table in systables
>
>Also in some ooportunidades the instance falls and it shows the following
>message to me of error:
>
>00:36:05 Assert Failed: read_record: decompress_row, source = 0x151370018,
>
>target = 0x210bc50a8
>00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
>
>Thread(213, sqlexec, 20434b068, 4)
>
>File: rsread.c Line: 2834
>00:36:05 Results: Record not read
>00:36:05 Action: Please notify IBM Informix Technical Support.
>00:36:05 Stack for thread: 213 sqlexec
>
>I hope that can help me to solve the problem.
>
>Thank you very much
>
>_________________________________________________________________
>Sé uno de los primeros a testar el Windows Live Messenger beta.
>http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
>
>
>*******************************************************************************
>
>Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
_________________________________________________________________
MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
Joseph-
See below:
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Juan
> Pablo
> Sent: Tuesday, May 01, 2007 2:13 PM
> To: ids@iiug.org
> Subject: Re: dbexport DOWN [9052]
>
> I have the following architecture:
>
> * Solaris 10
> * IBM Informix 10.00 FC5W5 + HDR
>
> The execution of dbexport I make it in the secondary server.
>
I don't believe dbexport works on the secondary of an HDR pair while
replication is happening. I know it doesn't at least through IDS 9.40.FC8. If
you need to do this:
make the secondary a standard engine (onmode -d standard on the secondary)
run your dbexport
restart replication (this may require a restore of the secondary's database
instance)
Otherwise your must run dbexport from the primary, which of course locks the
entire database in exclusive mode until the export completes.
--EEM
> Also it is affected by bug ???
>
> Thanks Joseph
>
> >From: "Joseph_Jurcazak@aotx.uscourts.gov"
> ><Joseph_Jurcazak@aotx.uscourts.gov>
> >Reply-To: ids@iiug.org
> >To: ids@iiug.org
> >Subject: Re: dbexport DOWN [9049]
> >Date: Tue, 1 May 2007 12:28:07 -0400 (EDT)
> >
> >Your bug might be....
> >
> >Bug: 119881 ASSERT FAILED: READ_RECORD: DECOMPRESS_ROW, SOURCE = A086018,
> >TARGET = A3294A4 WHEN USING DIRTY READ ISOLATION
> >
> >Description:
> >This is caused by a query with isolation level of dirty read. One process
> >inserts a row with varchars and a rowsize large enough to cause a
> >remainder
> >page. A query comes along with dirty read isolation level and happens to
> >read the home row buffer in memory, but the SL_INDIR flag has not been
> set
> >
> >on the home row data page.
> >
> >If you are 7.3X. Anyway, if you have informix support, they can give you
> >a patch for it or you can upgrade.
> >
> >"Juan Pablo" <in4mixperu@hotmail.com>
> >Sent by: ids-bounces@iiug.org
> >05/01/2007 11:19 AM
> >Please respond to
> >ids@iiug.org
> >
> >To
> >ids@iiug.org
> >cc
> >
> >Subject
> >dbexport DOWN [9048]
> >
> >Hello to all:
> >Dbexport of my BDs does not finish satisfactorily. The error message that
> >shows to me is the following one:
> >
> >No owner present for the table in systables
> >
> >Also in some ooportunidades the instance falls and it shows the following
> >message to me of error:
> >
> >00:36:05 Assert Failed: read_record: decompress_row, source =
> 0x151370018,
> >
> >target = 0x210bc50a8
> >00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
> >
> >Thread(213, sqlexec, 20434b068, 4)
> >
> >File: rsread.c Line: 2834
> >00:36:05 Results: Record not read
> >00:36:05 Action: Please notify IBM Informix Technical Support.
> >00:36:05 Stack for thread: 213 sqlexec
> >
> >I hope that can help me to solve the problem.
> >
> >Thank you very much
> >
> >_________________________________________________________________
> >Sé uno de los primeros a testar el Windows Live Messenger beta.
> >http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
> >
> >
>
> >*************************************************************************
> ******
> >
> >Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> >*************************************************************************
> ******
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
> _________________________________________________________________
> MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
>
>
> **************************************************************************
> *****
> Forum Note: Use "Reply" to post a response in the discussion forum.
Hi Everett Mills:
I have the following architecture:
* Solaris 10
* IBM Informix 10.00 FC5W5 + HDR
The execution of dbexport I make it in the secondary server.
Also it is affected by bug ???
Thanks Everett
>From: "Everett Mills" <eemills@nationalbeef.com>
>Reply-To: ids@iiug.org
>To: ids@iiug.org
>Subject: RE: dbexport DOWN [9053]
>Date: Tue, 1 May 2007 15:30:20 -0400 (EDT)
>
>Joseph-
>
>See below:
>
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
>Juan
> > Pablo
> > Sent: Tuesday, May 01, 2007 2:13 PM
> > To: ids@iiug.org
> > Subject: Re: dbexport DOWN [9052]
> >
> > I have the following architecture:
> >
> > * Solaris 10
> > * IBM Informix 10.00 FC5W5 + HDR
> >
> > The execution of dbexport I make it in the secondary server.
> >
>
>I don't believe dbexport works on the secondary of an HDR pair while
>replication is happening. I know it doesn't at least through IDS 9.40.FC8.
>If
>you need to do this:
>
>make the secondary a standard engine (onmode -d standard on the secondary)
>
>run your dbexport
>
>restart replication (this may require a restore of the secondary's database
>instance)
>
>Otherwise your must run dbexport from the primary, which of course locks
>the
>entire database in exclusive mode until the export completes.
>
>--EEM
> > Also it is affected by bug ???
> >
> > Thanks Joseph
> >
> > >From: "Joseph_Jurcazak@aotx.uscourts.gov"
> > ><Joseph_Jurcazak@aotx.uscourts.gov>
> > >Reply-To: ids@iiug.org
> > >To: ids@iiug.org
> > >Subject: Re: dbexport DOWN [9049]
> > >Date: Tue, 1 May 2007 12:28:07 -0400 (EDT)
> > >
> > >Your bug might be....
> > >
> > >Bug: 119881 ASSERT FAILED: READ_RECORD: DECOMPRESS_ROW, SOURCE =
>A086018,
> > >TARGET = A3294A4 WHEN USING DIRTY READ ISOLATION
> > >
> > >Description:
> > >This is caused by a query with isolation level of dirty read. One
>process
> > >inserts a row with varchars and a rowsize large enough to cause a
> > >remainder
> > >page. A query comes along with dirty read isolation level and happens
>to
> > >read the home row buffer in memory, but the SL_INDIR flag has not been
> > set
> > >
> > >on the home row data page.
> > >
> > >If you are 7.3X. Anyway, if you have informix support, they can give
>you
> > >a patch for it or you can upgrade.
> > >
> > >"Juan Pablo" <in4mixperu@hotmail.com>
> > >Sent by: ids-bounces@iiug.org
> > >05/01/2007 11:19 AM
> > >Please respond to
> > >ids@iiug.org
> > >
> > >To
> > >ids@iiug.org
> > >cc
> > >
> > >Subject
> > >dbexport DOWN [9048]
> > >
> > >Hello to all:
> > >Dbexport of my BDs does not finish satisfactorily. The error message
>that
> > >shows to me is the following one:
> > >
> > >No owner present for the table in systables
> > >
> > >Also in some ooportunidades the instance falls and it shows the
>following
> > >message to me of error:
> > >
> > >00:36:05 Assert Failed: read_record: decompress_row, source =
> > 0x151370018,
> > >
> > >target = 0x210bc50a8
> > >00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
> > >
> > >Thread(213, sqlexec, 20434b068, 4)
> > >
> > >File: rsread.c Line: 2834
> > >00:36:05 Results: Record not read
> > >00:36:05 Action: Please notify IBM Informix Technical Support.
> > >00:36:05 Stack for thread: 213 sqlexec
> > >
> > >I hope that can help me to solve the problem.
> > >
> > >Thank you very much
> > >
> > >_________________________________________________________________
> > >Sé uno de los primeros a testar el Windows Live Messenger beta.
> > >http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
> > >
> > >
> >
> >
> >*************************************************************************
> > ******
> > >
> > >Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> >
> >*************************************************************************
> > ******
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> >
> > _________________________________________________________________
> > MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
> >
> >
> >
>**************************************************************************
> > *****
> > Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
_________________________________________________________________
MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
Joseph-
As I said: dbexport isn't designed to work from an HDR secondary. It isn't a
bug, it only works from the primary or a standard database engine. That is why
I suggested that if you really needed to dbexport from the secondary, you must
stop replication and make the secondary a standard engine while you do it.
En espanol mas yucky:
Cuando dije: el dbexport no es diseñado para trabajar de un secundario HDR.
Esto no es un bicho, esto sólo trabaja de la primaria o un motor de base de
datos estándar. Por eso sugerí que si usted realmente necesitara a dbexport
del secundario, usted debe parar la réplica y hacer el secundario un motor
estándar mientras usted lo hace.
--EEM
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Juan
> Pablo
> Sent: Tuesday, May 01, 2007 3:51 PM
> To: ids@iiug.org
> Subject: RE: dbexport DOWN [9054]
>
> Hi Everett Mills:
>
> I have the following architecture:
>
> * Solaris 10
> * IBM Informix 10.00 FC5W5 + HDR
>
> The execution of dbexport I make it in the secondary server.
>
> Also it is affected by bug ???
>
> Thanks Everett
>
> >From: "Everett Mills" <eemills@nationalbeef.com>
> >Reply-To: ids@iiug.org
> >To: ids@iiug.org
> >Subject: RE: dbexport DOWN [9053]
> >Date: Tue, 1 May 2007 15:30:20 -0400 (EDT)
> >
> >Joseph-
> >
> >See below:
> >
> > > -----Original Message-----
> > > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> >Juan
> > > Pablo
> > > Sent: Tuesday, May 01, 2007 2:13 PM
> > > To: ids@iiug.org
> > > Subject: Re: dbexport DOWN [9052]
> > >
> > > I have the following architecture:
> > >
> > > * Solaris 10
> > > * IBM Informix 10.00 FC5W5 + HDR
> > >
> > > The execution of dbexport I make it in the secondary server.
> > >
> >
> >I don't believe dbexport works on the secondary of an HDR pair while
> >replication is happening. I know it doesn't at least through IDS
> 9.40.FC8.
> >If
> >you need to do this:
> >
> >make the secondary a standard engine (onmode -d standard on the
> secondary)
> >
> >run your dbexport
> >
> >restart replication (this may require a restore of the secondary's
> database
> >instance)
> >
> >Otherwise your must run dbexport from the primary, which of course locks
> >the
> >entire database in exclusive mode until the export completes.
> >
> >--EEM
> > > Also it is affected by bug ???
> > >
> > > Thanks Joseph
> > >
> > > >From: "Joseph_Jurcazak@aotx.uscourts.gov"
> > > ><Joseph_Jurcazak@aotx.uscourts.gov>
> > > >Reply-To: ids@iiug.org
> > > >To: ids@iiug.org
> > > >Subject: Re: dbexport DOWN [9049]
> > > >Date: Tue, 1 May 2007 12:28:07 -0400 (EDT)
> > > >
> > > >Your bug might be....
> > > >
> > > >Bug: 119881 ASSERT FAILED: READ_RECORD: DECOMPRESS_ROW, SOURCE =
> >A086018,
> > > >TARGET = A3294A4 WHEN USING DIRTY READ ISOLATION
> > > >
> > > >Description:
> > > >This is caused by a query with isolation level of dirty read. One
> >process
> > > >inserts a row with varchars and a rowsize large enough to cause a
> > > >remainder
> > > >page. A query comes along with dirty read isolation level and happens
> >to
> > > >read the home row buffer in memory, but the SL_INDIR flag has not
> been
> > > set
> > > >
> > > >on the home row data page.
> > > >
> > > >If you are 7.3X. Anyway, if you have informix support, they can give
> >you
> > > >a patch for it or you can upgrade.
> > > >
> > > >"Juan Pablo" <in4mixperu@hotmail.com>
> > > >Sent by: ids-bounces@iiug.org
> > > >05/01/2007 11:19 AM
> > > >Please respond to
> > > >ids@iiug.org
> > > >
> > > >To
> > > >ids@iiug.org
> > > >cc
> > > >
> > > >Subject
> > > >dbexport DOWN [9048]
> > > >
> > > >Hello to all:
> > > >Dbexport of my BDs does not finish satisfactorily. The error message
> >that
> > > >shows to me is the following one:
> > > >
> > > >No owner present for the table in systables
> > > >
> > > >Also in some ooportunidades the instance falls and it shows the
> >following
> > > >message to me of error:
> > > >
> > > >00:36:05 Assert Failed: read_record: decompress_row, source =
> > > 0x151370018,
> > > >
> > > >target = 0x210bc50a8
> > > >00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
> > > >
> > > >Thread(213, sqlexec, 20434b068, 4)
> > > >
> > > >File: rsread.c Line: 2834
> > > >00:36:05 Results: Record not read
> > > >00:36:05 Action: Please notify IBM Informix Technical Support.
> > > >00:36:05 Stack for thread: 213 sqlexec
> > > >
> > > >I hope that can help me to solve the problem.
> > > >
> > > >Thank you very much
> > > >
> > > >_________________________________________________________________
> > > >Sé uno de los primeros a testar el Windows Live Messenger beta.
> > > >http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-ar
> > > >
> > > >
> > >
> > >
> >
> >*************************************************************************
> > > ******
> > > >
> > > >Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >
> > > >
> > >
> > >
> >
> >*************************************************************************
> > > ******
> > > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > > >
> > >
> > > _________________________________________________________________
> > > MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
> > >
> > >
> > >
> >*************************************************************************
> *
> > > *****
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> >*************************************************************************
> ******
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
>
> _________________________________________________________________
> MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
>
>
> **************************************************************************
> *****
> Forum Note: Use "Reply" to post a response in the discussion forum.
OK...
I just tried it and it does seem to work. I still don't think it's supposed
to. Call support for info.
--EEM
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Everett Mills
> Sent: Tuesday, May 01, 2007 4:37 PM
> To: ids@iiug.org
> Subject: RE: dbexport DOWN [9057]
>
> Joseph-
>
> As I said: dbexport isn't designed to work from an HDR secondary. It isn't
> a
> bug, it only works from the primary or a standard database engine. That is
> why
> I suggested that if you really needed to dbexport from the secondary, you
> must
> stop replication and make the secondary a standard engine while you do it.
>
> En espanol mas yucky:
>
> Cuando dije: el dbexport no es diseñado para trabajar de un secundario
> HDR.
> Esto no es un bicho, esto sólo trabaja de la primaria o un motor de base
> de
> datos estándar. Por eso sugerí que si usted realmente necesitara a
> dbexport> del secundario, usted debe parar la réplica y hacer el secundario un motor
> estándar mientras usted lo hace.
>
> --EEM
>
> > -----Original Message-----
> > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Juan
> > Pablo
> > Sent: Tuesday, May 01, 2007 3:51 PM
> > To: ids@iiug.org
> > Subject: RE: dbexport DOWN [9054]
> >
> > Hi Everett Mills:
> >
> > I have the following architecture:
> >
> > * Solaris 10
> > * IBM Informix 10.00 FC5W5 + HDR
> >
> > The execution of dbexport I make it in the secondary server.
> >
> > Also it is affected by bug ???
> >
> > Thanks Everett
> >
> > >From: "Everett Mills" <eemills@nationalbeef.com>
> > >Reply-To: ids@iiug.org
> > >To: ids@iiug.org
> > >Subject: RE: dbexport DOWN [9053]
> > >Date: Tue, 1 May 2007 15:30:20 -0400 (EDT)
> > >
> > >Joseph-
> > >
> > >See below:
> > >
> > > > -----Original Message-----
> > > > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf
> Of
> > >Juan
> > > > Pablo
> > > > Sent: Tuesday, May 01, 2007 2:13 PM
> > > > To: ids@iiug.org
> > > > Subject: Re: dbexport DOWN [9052]
> > > >
> > > > I have the following architecture:
> > > >
> > > > * Solaris 10
> > > > * IBM Informix 10.00 FC5W5 + HDR
> > > >
> > > > The execution of dbexport I make it in the secondary server.
> > > >
> > >
> > >I don't believe dbexport works on the secondary of an HDR pair while
> > >replication is happening. I know it doesn't at least through IDS
> > 9.40.FC8.
> > >If
> > >you need to do this:
> > >
> > >make the secondary a standard engine (onmode -d standard on the
> > secondary)
> > >
> > >run your dbexport
> > >
> > >restart replication (this may require a restore of the secondary's
> > database
> > >instance)
> > >
> > >Otherwise your must run dbexport from the primary, which of course
> locks
> > >the
> > >entire database in exclusive mode until the export completes.
> > >
> > >--EEM
> > > > Also it is affected by bug ???
> > > >
> > > > Thanks Joseph
> > > >
> > > > >From: "Joseph_Jurcazak@aotx.uscourts.gov"
> > > > ><Joseph_Jurcazak@aotx.uscourts.gov>
> > > > >Reply-To: ids@iiug.org
> > > > >To: ids@iiug.org
> > > > >Subject: Re: dbexport DOWN [9049]
> > > > >Date: Tue, 1 May 2007 12:28:07 -0400 (EDT)
> > > > >
> > > > >Your bug might be....
> > > > >
> > > > >Bug: 119881 ASSERT FAILED: READ_RECORD: DECOMPRESS_ROW, SOURCE =
> > >A086018,
> > > > >TARGET = A3294A4 WHEN USING DIRTY READ ISOLATION
> > > > >
> > > > >Description:
> > > > >This is caused by a query with isolation level of dirty read. One
> > >process
> > > > >inserts a row with varchars and a rowsize large enough to cause a
> > > > >remainder
> > > > >page. A query comes along with dirty read isolation level and
> happens
> > >to
> > > > >read the home row buffer in memory, but the SL_INDIR flag has not
> > been
> > > > set
> > > > >
> > > > >on the home row data page.
> > > > >
> > > > >If you are 7.3X. Anyway, if you have informix support, they can
> give
> > >you
> > > > >a patch for it or you can upgrade.
> > > > >
> > > > >"Juan Pablo" <in4mixperu@hotmail.com>
> > > > >Sent by: ids-bounces@iiug.org
> > > > >05/01/2007 11:19 AM
> > > > >Please respond to
> > > > >ids@iiug.org
> > > > >
> > > > >To
> > > > >ids@iiug.org
> > > > >cc
> > > > >
> > > > >Subject
> > > > >dbexport DOWN [9048]
> > > > >
> > > > >Hello to all:
> > > > >Dbexport of my BDs does not finish satisfactorily. The error
> message
> > >that
> > > > >shows to me is the following one:
> > > > >
> > > > >No owner present for the table in systables
> > > > >
> > > > >Also in some ooportunidades the instance falls and it shows the
> > >following
> > > > >message to me of error:
> > > > >
> > > > >00:36:05 Assert Failed: read_record: decompress_row, source =
> > > > 0x151370018,
> > > > >
> > > > >target = 0x210bc50a8
> > > > >00:36:05 Who: Session(44, informix@hiperion, 21917, 20437fa68)
> > > > >
> > > > >Thread(213, sqlexec, 20434b068, 4)
> > > > >
> > > > >File: rsread.c Line: 2834
> > > > >00:36:05 Results: Record not read
> > > > >00:36:05 Action: Please notify IBM Informix Technical Support.
> > > > >00:36:05 Stack for thread: 213 sqlexec
> > > > >
> > > > >I hope that can help me to solve the problem.
> > > > >
> > > > >Thank you very much
> > > > >
> > > > >_________________________________________________________________
> > > > >Sé uno de los primeros a testar el Windows Live Messenger beta.
> > > > >http://imagine-msn.com/minisites/messenger/default.aspx?locale=es-
> ar
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >*************************************************************************
> > > > ******
> > > > >
> > > > >Forum Note: Use "Reply" to post a response in the discussion forum.
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >*************************************************************************
> > > > ******
> > > > > Forum Note: Use "Reply" to post a response in the discussion
> forum.
> > > > >
> > > >
> > > > _________________________________________________________________
> > > > MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
> > > >
> > > >
> > > >
> >
> >*************************************************************************
> > *
> > > > *****
> > > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> > >
> >
> >
> >*************************************************************************
> > ******
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> >
> > _________________________________________________________________
> > MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
> >
> >
> >
> **************************************************************************
> > *****
> > Forum Note: