SEO

#1 (**permalink**) 04-10-2008, 12:09 AM

Hello,

on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
2 Gb ddram
4 73Gb scsi hdd in raid-5
Progress V8.3C 11

multi-volume database
15 512mb vol + 1 free vol.

I made a online probkup of this database from our actual server (bi P3
xeon, SCO Unix OSR5.06a, Progress V8.3C11).
I created the multi-volume database on the new server using the prostrct
utility and restore it.
When trying to rebuild indexes using "proutil database_name -TM 31 -TB
31 -G 0 -C idxbuild all" (same error in all indexes or some), during
phase 1 block 3799040 of 4672721 it fails

"SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
2147481600 (290)"

What's this 1536 error code ?
How could I resolv it ?
Thank's.

F. STOCK

#2 (**permalink**) 04-10-2008, 12:09 AM

Huh ... why so difficult?
1. Stop your databases.
2. Truncate bi-files.
3. Copy complete databasefiles (*.db, *.bi, *.ai) to your new server.
4. Start your servers.

I migrated from SCO to linux this way.
2x Xeon and Raid5
No problem at all.

Frédéric STOCK schreef:
> Hello,
>
> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
> 2 Gb ddram
> 4 73Gb scsi hdd in raid-5
> Progress V8.3C 11
>
> multi-volume database
> 15 512mb vol + 1 free vol.
>
> I made a online probkup of this database from our actual server (bi P3
> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
> I created the multi-volume database on the new server using the prostrct
> utility and restore it.
> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during
> phase 1 block 3799040 of 4672721 it fails
>
> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
> 2147481600 (290)"
>
> What's this 1536 error code ?
> How could I resolv it ?
> Thank's.
>
> F. STOCK

#3 (**permalink**) 04-10-2008, 12:09 AM

"Frédéric STOCK" <f.stock@jmontblanc.fr> wrote in message
news:4680d9a4$0$21149$7a628cd7@news.club-internet.fr...
> Hello,
>
> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
> 2 Gb ddram
> 4 73Gb scsi hdd in raid-5
> Progress V8.3C 11
>
> multi-volume database
> 15 512mb vol + 1 free vol.
>
> I made a online probkup of this database from our actual server (bi P3
> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
> I created the multi-volume database on the new server using the prostrct
> utility and restore it.
> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during phase
> 1 block 3799040 of 4672721 it fails
>
> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
> 2147481600 (290)"
>
> What's this 1536 error code ?
> How could I resolv it ?
> Thank's.
>
> F. STOCK

The 2147481600 makes me think you hit a 2GB limit somewhere.

Post on the peg and you'll have an answer by morning. (www.peg.com)

#4 (**permalink**) 04-10-2008, 12:09 AM

On Wed, 27 Jun 2007 01:56:14 GMT, "El Maximo" <nobody@nowhere.org>
wrote:

>"Frédéric STOCK" <f.stock@jmontblanc.fr> wrote in message
>news:4680d9a4$0$21149$7a628cd7@news.club-internet.fr...
>> Hello,
>>
>> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
>> 2 Gb ddram
>> 4 73Gb scsi hdd in raid-5
>> Progress V8.3C 11
>>
>> multi-volume database
>> 15 512mb vol + 1 free vol.
>>
>> I made a online probkup of this database from our actual server (bi P3
>> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
>> I created the multi-volume database on the new server using the prostrct
>> utility and restore it.
>> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
>> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during phase
>> 1 block 3799040 of 4672721 it fails
>>
>> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
>> 2147481600 (290)"
>>
>> What's this 1536 error code ?
>> How could I resolv it ?
>> Thank's.
>>
>> F. STOCK
>
>The 2147481600 makes me think you hit a 2GB limit somewhere.
>
>Post on the peg and you'll have an answer by morning. (www.peg.com)
>

and you have not or a incorrect srt file ..

#5 (**permalink**) 04-10-2008, 12:09 AM

Stefan M. a écrit :
> On Wed, 27 Jun 2007 01:56:14 GMT, "El Maximo" <nobody@nowhere.org>
> wrote:
>
>> "Frédéric STOCK" <f.stock@jmontblanc.fr> wrote in message
>> news:4680d9a4$0$21149$7a628cd7@news.club-internet.fr...
>>> Hello,
>>>
>>> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
>>> 2 Gb ddram
>>> 4 73Gb scsi hdd in raid-5
>>> Progress V8.3C 11
>>>
>>> multi-volume database
>>> 15 512mb vol + 1 free vol.
>>>
>>> I made a online probkup of this database from our actual server (bi P3
>>> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
>>> I created the multi-volume database on the new server using the prostrct
>>> utility and restore it.
>>> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
>>> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during phase
>>> 1 block 3799040 of 4672721 it fails
>>>
>>> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
>>> 2147481600 (290)"
>>>
>>> What's this 1536 error code ?
>>> How could I resolv it ?
>>> Thank's.
>>>
>>> F. STOCK
>> The 2147481600 makes me think you hit a 2GB limit somewhere.
>>
>> Post on the peg and you'll have an answer by morning. (www.peg.com)
>>
>
> and you have not or a incorrect srt file ..

could it be a >2Gb temporary file ?

So today I made a dump data (one of the .d table file is near the 2Gb
file size limit (2049244868 bytes)
create multi-vol database
load data by bulkload
rebuild all indexes and I got the same error with the same addr 2147481600.

Where are then temporary srt files, so I could have a look of size
during indexes rebuild ?

Thank's.
F. STOCK

#6 (**permalink**) 04-10-2008, 12:09 AM

On Jun 27, 2:56 pm, Frédéric STOCK <f.st...@jmontblanc.fr> wrote:
> Stefan M. a écrit :
>
>
>
> > On Wed, 27 Jun 2007 01:56:14 GMT, "El Maximo" <nob...@nowhere.org>
> > wrote:
>
> >> "Frédéric STOCK" <f.st...@jmontblanc.fr> wrote in message
> >>news:4680d9a4$0$21149$7a628cd7@news.club-internet.fr...
> >>> Hello,
>
> >>> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
> >>> 2 Gb ddram
> >>> 4 73Gb scsi hdd in raid-5
> >>> Progress V8.3C 11
>
> >>> multi-volume database
> >>> 15 512mb vol + 1 free vol.
>
> >>> I made a online probkup of this database from our actual server (bi P3
> >>> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
> >>> I created the multi-volume database on the new server using the prostrct
> >>> utility and restore it.
> >>> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
> >>> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during phase
> >>> 1 block 3799040 of 4672721 it fails
>
> >>> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
> >>> 2147481600 (290)"
>
> >>> What's this 1536 error code ?
> >>> How could I resolv it ?
> >>> Thank's.
>
> >>> F. STOCK
> >> The 2147481600 makes me think you hit a 2GB limit somewhere.
>
> >> Post on the peg and you'll have an answer by morning. (www.peg.com)
>
> > and you have not or a incorrect srt file ..
>
> could it be a >2Gb temporary file ?
>
> So today I made a dump data (one of the .d table file is near the 2Gb
> file size limit (2049244868 bytes)
> create multi-vol database
> load data by bulkload
> rebuild all indexes and I got the same error with the same addr 2147481600.
>
> Where are then temporary srt files, so I could have a look of size
> during indexes rebuild ?
>
> Thank's.
> F. STOCK

The temp file can be set via -T

#7 (**permalink**) 04-10-2008, 12:09 AM

On Jun 27, 2:56 pm, Frédéric STOCK <f.st...@jmontblanc.fr> wrote:
> Stefan M. a écrit :
>
>
>
> > On Wed, 27 Jun 2007 01:56:14 GMT, "El Maximo" <nob...@nowhere.org>
> > wrote:
>
> >> "Frédéric STOCK" <f.st...@jmontblanc.fr> wrote in message
> >>news:4680d9a4$0$21149$7a628cd7@news.club-internet.fr...
> >>> Hello,
>
> >>> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
> >>> 2 Gb ddram
> >>> 4 73Gb scsi hdd in raid-5
> >>> Progress V8.3C 11
>
> >>> multi-volume database
> >>> 15 512mb vol + 1 free vol.
>
> >>> I made a online probkup of this database from our actual server (bi P3
> >>> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
> >>> I created the multi-volume database on the new server using the prostrct
> >>> utility and restore it.
> >>> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
> >>> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during phase
> >>> 1 block 3799040 of 4672721 it fails
>
> >>> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
> >>> 2147481600 (290)"
>
> >>> What's this 1536 error code ?
> >>> How could I resolv it ?
> >>> Thank's.
>
> >>> F. STOCK
> >> The 2147481600 makes me think you hit a 2GB limit somewhere.
>
> >> Post on the peg and you'll have an answer by morning. (www.peg.com)
>
> > and you have not or a incorrect srt file ..
>
> could it be a >2Gb temporary file ?
>
> So today I made a dump data (one of the .d table file is near the 2Gb
> file size limit (2049244868 bytes)
> create multi-vol database
> load data by bulkload
> rebuild all indexes and I got the same error with the same addr 2147481600.
>
> Where are then temporary srt files, so I could have a look of size
> during indexes rebuild ?
>
> Thank's.
> F. STOCK

The Temp directory for idxrebuild can be set with -T parameter.
Look in Progress data management:database administration how to create
a .srt file and what are the implication of creating one.
If u supply the -T parameter the sort will use that directory and all
available space on that partition. If u do not supply this parameter
the sort will use the working directory and all available space from
the partition where working directory is. The rebuild of all indexes
can take up to 75% of database size .

#8 (**permalink**) 04-10-2008, 12:09 AM

Claus a écrit :
> On Jun 27, 2:56 pm, Frédéric STOCK <f.st...@jmontblanc.fr> wrote:
>> Stefan M. a écrit :
>>
>>
>>
>>> On Wed, 27 Jun 2007 01:56:14 GMT, "El Maximo" <nob...@nowhere.org>
>>> wrote:
>>>> "Frédéric STOCK" <f.st...@jmontblanc.fr> wrote in message
>>>> news:4680d9a4$0$21149$7a628cd7@news.club-internet.fr...
>>>>> Hello,
>>>>> on new server: running SCO Unix OSR 5.06a, P4 xeon dual-core
>>>>> 2 Gb ddram
>>>>> 4 73Gb scsi hdd in raid-5
>>>>> Progress V8.3C 11
>>>>> multi-volume database
>>>>> 15 512mb vol + 1 free vol.
>>>>> I made a online probkup of this database from our actual server (bi P3
>>>>> xeon, SCO Unix OSR5.06a, Progress V8.3C11).
>>>>> I created the multi-volume database on the new server using the prostrct
>>>>> utility and restore it.
>>>>> When trying to rebuild indexes using "proutil database_name -TM 31 -TB
>>>>> 31 -G 0 -C idxbuild all" (same error in all indexes or some), during phase
>>>>> 1 block 3799040 of 4672721 it fails
>>>>> "SYSTEM ERROR: erreur E/S 0 sur writeto,ret 1536,fich. 6(srt),addr
>>>>> 2147481600 (290)"
>>>>> What's this 1536 error code ?
>>>>> How could I resolv it ?
>>>>> Thank's.
>>>>> F. STOCK
>>>> The 2147481600 makes me think you hit a 2GB limit somewhere.
>>>> Post on the peg and you'll have an answer by morning. (www.peg.com)
>>> and you have not or a incorrect srt file ..
>> could it be a >2Gb temporary file ?
>>
>> So today I made a dump data (one of the .d table file is near the 2Gb
>> file size limit (2049244868 bytes)
>> create multi-vol database
>> load data by bulkload
>> rebuild all indexes and I got the same error with the same addr 2147481600.
>>
>> Where are then temporary srt files, so I could have a look of size
>> during indexes rebuild ?
>>
>> Thank's.
>> F. STOCK
>
> The Temp directory for idxrebuild can be set with -T parameter.
> Look in Progress data management:database administration how to create
> a .srt file and what are the implication of creating one.
> If u supply the -T parameter the sort will use that directory and all
> available space on that partition. If u do not supply this parameter
> the sort will use the working directory and all available space from
> the partition where working directory is. The rebuild of all indexes
> can take up to 75% of database size .
>
Hi all, thank's for your usefull answers.
So I created a database_name.srt file like this:

512000 dir/srt_name_file
512000 dir/srt_name_file1
512000 dir/srt_name_file2
512000 dir/srt_name_file3...
0 dir/srt_name_filen

rebuild the indexes and this time the phase1 ended with no error.

F. STOCK

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

What is this error ?