Topic
  • 5 replies
  • Latest Post - ‏2005-09-06T14:47:13Z by SystemAdmin
SystemAdmin
SystemAdmin
1731 Posts

Pinned topic Errors loading raster data into SDE 8.3

‏2005-09-02T17:13:38Z |
I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog 8.3.
The
desktop message popup dialog is titled "ArcToolbox Warning", and the message
itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".

My configuration is:
Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000 Server
5.00.2195 SP4
Desktop: ArcInfo 8.3

Selected output from Db2diag.log shows:
<SNIP>
2005-08-30-13.59.02.703001 Instance:DB2 Node:000
PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
DIA3847C An error occurred in a database page header.
ZRC=0xFFFFF136

2005-08-30-13.59.02.765000 Instance:DB2 Node:000
PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
</SNIP>
And further down:
<SNIP>
2005-08-30-13.59.05.921000 Instance:DB2 Node:000
PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
buffer_pool_services sqlbReadPage Probe:74 Database:SDE

  • Page off disk *****0000 0000
</SNIP>
And:
<SNIP>
Data Title:section stmt PID:2440 TID:3488 Node:000
7365 6c65 6374 2020 2a20 2066 726f 6d20 select * from
2053 4445 2e44 4232 4144 4d49 4e2e 4348 SDE.DB2ADMIN.CH
4150 5445 524e 554d 4245 52 APTERNUMBER
</SNIP>

Why the table CHAPTERNUMBER (obj:2328) is being queried I don't know except
perhaps because it is in the same tablespace where I am attempting to load
the rasters.
Running db2dart sde /T on pool:3;obj:2328 reveals:

<SNIP>
Table space: 3
Traversing extent map for object type: 0
Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
Traversing extent map for object type: 1
Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
Extent Map traversal complete.
Table inspection start: DB2ADMIN.CHAPTERNUMBER
Data inspection phase start. Data obj: 2328 In pool: 3
Error: Unable to determine pool relative page number for obj rel page 0 (Obj
ID:2328, Pool ID:3)
Error: Unable to read pool page 4722978, object page 0, from pool 3,
Error: parent pool 3, object ID 2328, object type Data.
Error: extent map anchor page of object is 9281910.
Error: This object page does not exist.
Error: reading page: 0 from object: 2328
Data inspection phase end.
Error: Unable to determine pool relative page number for obj rel page 0 (Obj
ID:2328, Pool ID:3)
Error: Unable to read pool page 1413563508, object page 0, from pool 3,
Error: parent pool 3, object ID 2328, object type Data.
Error: extent map anchor page of object is 9281910.
Error: The tablespace object-table and the data disagree on the existance of
inx data!
Warning: Table descriptor record indicates index exist: 0
Warning: DMS Object table indicates index exist: 1
Index inspection phase start. Index obj: 2328 In pool: 3
Error: Unable to determine pool relative page number for obj rel page 0 (Obj
ID:2328, Pool ID:3)
Error: Unable to read pool page 0, object page 0, from pool 3,
Error: parent pool 3, object ID 2328, object type Index.
Error: extent map anchor page of object is 9281914.
Error detected in index.
Index inspection phase end.
Error: Unable to determine pool relative page number for obj rel page 0 (Obj
ID:2328, Pool ID:3)
Error: Unable to read pool page 4400336, object page 0, from pool 3,
Error: parent pool 3, object ID 2328, object type Data.
Error: extent map anchor page of object is 9281910.
Error: Unable to get table descriptor record.
Error: Unable to determine pool relative page number for obj rel page 0 (Obj
ID:2328, Pool ID:3)
Error: Unable to read pool page 4400336, object page 0, from pool 3,
Error: parent pool 3, object ID 2328, object type Data.
Error: extent map anchor page of object is 9281910.
Error: Unable to get table descriptor record.
Table inspection end.
______________________________________

DB2DART Processing completed with error!
WARNING:
The inspection phase did not complete!
ERROR:
Some tables indexes may be corrupt; errors will be cleared for index
objectswith invalid state after they have been succesfully rebuilt.
ERROR:
One or more tablespaces is corrupt.
Table data in such tablespaces may be orphaned.
</SNIP>

I have attempted to import raster data of differing types and sizes, using
different user IDs each with sufficient privileges, and even created new
tablespaces exclusively for the raster data, but none of these have helped.
Each time the process fails and db2diag.log reveals a reference to the same
CHAPTERNUMBER table as listed above. Does anyone have any suggestions as to
what I should try next? Can I isolate and avoid those portions of
tablespace 3 that seem to be corrupt? Should I not be able to import raster
data into a new tablespace using an updated dbtune.sde table and bypass the
corrupt one?

Thanks in advance,

Gord Mathews
Ducks Unlimited Canada

Updated on 2005-09-06T14:47:13Z at 2005-09-06T14:47:13Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    1731 Posts

    Re: Errors loading raster data into SDE 8.3

    ‏2005-09-02T18:32:22Z  
    Hi,

    Sorry, I didn't set up my newsgroup properties. Previous message is from me
    not John Smith : )

    Gord Mathews
    Ducks Unlimited Canada

    "John Smith" <jsmith@nowhere.com> wrote in message
    news:dfa1ae$123c$1@news.boulder.ibm.com...
    >I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    >8.3. The
    > desktop message popup dialog is titled "ArcToolbox Warning", and the
    > message
    > itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >
    > My configuration is:
    > Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    > Server 5.00.2195 SP4
    > Desktop: ArcInfo 8.3
    >
    > Selected output from Db2diag.log shows:
    > <SNIP>
    > 2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > DIA3847C An error occurred in a database page header.
    > ZRC=0xFFFFF136
    >
    > 2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    > PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    > </SNIP>
    > And further down:
    > <SNIP>
    > 2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >
    > ** Page off disk *****0000 0000
    > </SNIP>
    > And:
    > <SNIP>
    > Data Title:section stmt PID:2440 TID:3488 Node:000
    > 7365 6c65 6374 2020 2a20 2066 726f 6d20 select * from
    > 2053 4445 2e44 4232 4144 4d49 4e2e 4348 SDE.DB2ADMIN.CH
    > 4150 5445 524e 554d 4245 52 APTERNUMBER
    > </SNIP>
    >
    > Why the table CHAPTERNUMBER (obj:2328) is being queried I don't know
    > except perhaps because it is in the same tablespace where I am attempting
    > to load the rasters.
    > Running db2dart sde /T on pool:3;obj:2328 reveals:
    >
    > <SNIP>
    > Table space: 3
    > Traversing extent map for object type: 0
    > Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    > Traversing extent map for object type: 1
    > Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    > Extent Map traversal complete.
    > Table inspection start: DB2ADMIN.CHAPTERNUMBER
    > Data inspection phase start. Data obj: 2328 In pool: 3
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 4722978, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: This object page does not exist.
    > Error: reading page: 0 from object: 2328
    > Data inspection phase end.
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 1413563508, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: The tablespace object-table and the data disagree on the existance
    > of inx data!
    > Warning: Table descriptor record indicates index exist: 0
    > Warning: DMS Object table indicates index exist: 1
    > Index inspection phase start. Index obj: 2328 In pool: 3
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 0, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Index.
    > Error: extent map anchor page of object is 9281914.
    > Error detected in index.
    > Index inspection phase end.
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 4400336, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: Unable to get table descriptor record.
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 4400336, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: Unable to get table descriptor record.
    > Table inspection end.
    > ______________________________________
    >
    > DB2DART Processing completed with error!
    > WARNING:
    > The inspection phase did not complete!
    > ERROR:
    > Some tables indexes may be corrupt; errors will be cleared for index
    > objectswith invalid state after they have been succesfully rebuilt.
    > ERROR:
    > One or more tablespaces is corrupt.
    > Table data in such tablespaces may be orphaned.
    > </SNIP>
    >
    > I have attempted to import raster data of differing types and sizes, using
    > different user IDs each with sufficient privileges, and even created new
    > tablespaces exclusively for the raster data, but none of these have
    > helped. Each time the process fails and db2diag.log reveals a reference to
    > the same CHAPTERNUMBER table as listed above. Does anyone have any
    > suggestions as to what I should try next? Can I isolate and avoid those
    > portions of tablespace 3 that seem to be corrupt? Should I not be able to
    > import raster data into a new tablespace using an updated dbtune.sde table
    > and bypass the corrupt one?
    >
    > Thanks in advance,
    >
    > Gord Mathews
    > Ducks Unlimited Canada
    >
    >
    >
    >

  • SystemAdmin
    SystemAdmin
    1731 Posts

    Re: Errors loading raster data into SDE 8.3

    ‏2005-09-05T10:13:43Z  
    John Smith wrote:

    > I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    > 8.3. The
    > desktop message popup dialog is titled "ArcToolbox Warning", and the
    > message itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >
    > My configuration is:
    > Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    > Server 5.00.2195 SP4
    > Desktop: ArcInfo 8.3
    >
    > Selected output from Db2diag.log shows:
    > <SNIP>
    > 2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > DIA3847C An error occurred in a database page header.
    > ZRC=0xFFFFF136
    >
    > 2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    > PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    > </SNIP>
    > And further down:
    > <SNIP>
    > 2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >
    > ** Page off disk *****0000 0000
    > </SNIP>
    >
    > DB2DART Processing completed with error!
    > WARNING:
    > The inspection phase did not complete!
    > ERROR:
    > Some tables indexes may be corrupt; errors will be cleared for index
    > objectswith invalid state after they have been succesfully rebuilt.
    > ERROR:
    > One or more tablespaces is corrupt.
    > Table data in such tablespaces may be orphaned.
    > </SNIP>
    >
    > I have attempted to import raster data of differing types and sizes, using
    > different user IDs each with sufficient privileges, and even created new
    > tablespaces exclusively for the raster data, but none of these have
    > helped. Each time the process fails and db2diag.log reveals a reference to
    > the same
    > CHAPTERNUMBER table as listed above. Does anyone have any suggestions as
    > to
    > what I should try next? Can I isolate and avoid those portions of
    > tablespace 3 that seem to be corrupt? Should I not be able to import
    > raster data into a new tablespace using an updated dbtune.sde table and
    > bypass the corrupt one?

    You could indeed try to import the data into another tablespace by adjusting
    the dbtune.sde file. However, you should call IBM support to open a PMR
    and get the "bad page" problem investigated and resolved. Such a problem
    is rather troublesome - maybe you just have a HD failure, maybe something
    worse happened.

    Knut Stolze
    Information Integration Development
    IBM Germany / University of Jena
  • SystemAdmin
    SystemAdmin
    1731 Posts

    Re: Errors loading raster data into SDE 8.3

    ‏2005-09-05T11:08:10Z  
    Hi,

    Sorry, I didn't set up my newsgroup properties. Previous message is from me
    not John Smith : )

    Gord Mathews
    Ducks Unlimited Canada

    "John Smith" <jsmith@nowhere.com> wrote in message
    news:dfa1ae$123c$1@news.boulder.ibm.com...
    >I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    >8.3. The
    > desktop message popup dialog is titled "ArcToolbox Warning", and the
    > message
    > itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >
    > My configuration is:
    > Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    > Server 5.00.2195 SP4
    > Desktop: ArcInfo 8.3
    >
    > Selected output from Db2diag.log shows:
    > <SNIP>
    > 2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > DIA3847C An error occurred in a database page header.
    > ZRC=0xFFFFF136
    >
    > 2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    > PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    > </SNIP>
    > And further down:
    > <SNIP>
    > 2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >
    > ** Page off disk *****0000 0000
    > </SNIP>
    > And:
    > <SNIP>
    > Data Title:section stmt PID:2440 TID:3488 Node:000
    > 7365 6c65 6374 2020 2a20 2066 726f 6d20 select * from
    > 2053 4445 2e44 4232 4144 4d49 4e2e 4348 SDE.DB2ADMIN.CH
    > 4150 5445 524e 554d 4245 52 APTERNUMBER
    > </SNIP>
    >
    > Why the table CHAPTERNUMBER (obj:2328) is being queried I don't know
    > except perhaps because it is in the same tablespace where I am attempting
    > to load the rasters.
    > Running db2dart sde /T on pool:3;obj:2328 reveals:
    >
    > <SNIP>
    > Table space: 3
    > Traversing extent map for object type: 0
    > Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    > Traversing extent map for object type: 1
    > Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    > Extent Map traversal complete.
    > Table inspection start: DB2ADMIN.CHAPTERNUMBER
    > Data inspection phase start. Data obj: 2328 In pool: 3
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 4722978, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: This object page does not exist.
    > Error: reading page: 0 from object: 2328
    > Data inspection phase end.
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 1413563508, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: The tablespace object-table and the data disagree on the existance
    > of inx data!
    > Warning: Table descriptor record indicates index exist: 0
    > Warning: DMS Object table indicates index exist: 1
    > Index inspection phase start. Index obj: 2328 In pool: 3
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 0, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Index.
    > Error: extent map anchor page of object is 9281914.
    > Error detected in index.
    > Index inspection phase end.
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 4400336, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: Unable to get table descriptor record.
    > Error: Unable to determine pool relative page number for obj rel page 0
    > (Obj ID:2328, Pool ID:3)
    > Error: Unable to read pool page 4400336, object page 0, from pool 3,
    > Error: parent pool 3, object ID 2328, object type Data.
    > Error: extent map anchor page of object is 9281910.
    > Error: Unable to get table descriptor record.
    > Table inspection end.
    > ______________________________________
    >
    > DB2DART Processing completed with error!
    > WARNING:
    > The inspection phase did not complete!
    > ERROR:
    > Some tables indexes may be corrupt; errors will be cleared for index
    > objectswith invalid state after they have been succesfully rebuilt.
    > ERROR:
    > One or more tablespaces is corrupt.
    > Table data in such tablespaces may be orphaned.
    > </SNIP>
    >
    > I have attempted to import raster data of differing types and sizes, using
    > different user IDs each with sufficient privileges, and even created new
    > tablespaces exclusively for the raster data, but none of these have
    > helped. Each time the process fails and db2diag.log reveals a reference to
    > the same CHAPTERNUMBER table as listed above. Does anyone have any
    > suggestions as to what I should try next? Can I isolate and avoid those
    > portions of tablespace 3 that seem to be corrupt? Should I not be able to
    > import raster data into a new tablespace using an updated dbtune.sde table
    > and bypass the corrupt one?
    >
    > Thanks in advance,
    >
    > Gord Mathews
    > Ducks Unlimited Canada
    >
    >
    >
    >

    It certainly sounds like something is seriously wrong with one of your
    tablespaces and IBM support should be contacted, as Knut suggested.

    Are you able to start up ArcCatalog and display the list of layers in
    the database without error prior to this failure occurring? Do map draw
    operations complete successfully?

    My guess is that the 'SELECT * FROM SDE.DB2ADMIN.CHAPTERNUM' is just
    ArcCatalog doing a DESCRIBE to get information about layers in your
    ArcSDE database. You could take a DB2 CLI trace to get more detail
    about what ArcSDE is doing under the covers but I doubt it will help
    resolve the problem.

    Gord Mathews wrote:
    > Hi,
    >
    > Sorry, I didn't set up my newsgroup properties. Previous message is from me
    > not John Smith : )
    >
    > Gord Mathews
    > Ducks Unlimited Canada
    >
    > "John Smith" <jsmith@nowhere.com> wrote in message
    > news:dfa1ae$123c$1@news.boulder.ibm.com...
    >
    >>I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    >>8.3. The
    >>desktop message popup dialog is titled "ArcToolbox Warning", and the
    >>message
    >>itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >>
    >>My configuration is:
    >>Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    >>Server 5.00.2195 SP4
    >>Desktop: ArcInfo 8.3
    >>
    >>Selected output from Db2diag.log shows:
    >><SNIP>
    >>2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    >>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >>DIA3847C An error occurred in a database page header.
    >>ZRC=0xFFFFF136
    >>
    >>2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    >>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >>Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    >>PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    >></SNIP>
    >>And further down:
    >><SNIP>
    >>2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    >>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >>
    >>** Page off disk *****0000 0000
    >></SNIP>
    >>And:
    >><SNIP>
    >>Data Title:section stmt PID:2440 TID:3488 Node:000
    >>7365 6c65 6374 2020 2a20 2066 726f 6d20 select * from
    >>2053 4445 2e44 4232 4144 4d49 4e2e 4348 SDE.DB2ADMIN.CH
    >>4150 5445 524e 554d 4245 52 APTERNUMBER
    >></SNIP>
    >>
    >>Why the table CHAPTERNUMBER (obj:2328) is being queried I don't know
    >>except perhaps because it is in the same tablespace where I am attempting
    >>to load the rasters.
    >>Running db2dart sde /T on pool:3;obj:2328 reveals:
    >>
    >><SNIP>
    >>Table space: 3
    >>Traversing extent map for object type: 0
    >>Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    >>Traversing extent map for object type: 1
    >>Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    >>Extent Map traversal complete.
    >>Table inspection start: DB2ADMIN.CHAPTERNUMBER
    >>Data inspection phase start. Data obj: 2328 In pool: 3
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 4722978, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: This object page does not exist.
    >>Error: reading page: 0 from object: 2328
    >>Data inspection phase end.
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 1413563508, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: The tablespace object-table and the data disagree on the existance
    >>of inx data!
    >>Warning: Table descriptor record indicates index exist: 0
    >>Warning: DMS Object table indicates index exist: 1
    >>Index inspection phase start. Index obj: 2328 In pool: 3
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 0, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Index.
    >>Error: extent map anchor page of object is 9281914.
    >>Error detected in index.
    >>Index inspection phase end.
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 4400336, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: Unable to get table descriptor record.
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 4400336, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: Unable to get table descriptor record.
    >>Table inspection end.
    >>______________________________________
    >>
    >>DB2DART Processing completed with error!
    >>WARNING:
    >>The inspection phase did not complete!
    >>ERROR:
    >>Some tables indexes may be corrupt; errors will be cleared for index
    >>objectswith invalid state after they have been succesfully rebuilt.
    >>ERROR:
    >>One or more tablespaces is corrupt.
    >>Table data in such tablespaces may be orphaned.
    >></SNIP>
    >>
    >>I have attempted to import raster data of differing types and sizes, using
    >>different user IDs each with sufficient privileges, and even created new
    >>tablespaces exclusively for the raster data, but none of these have
    >>helped. Each time the process fails and db2diag.log reveals a reference to
    >>the same CHAPTERNUMBER table as listed above. Does anyone have any
    >>suggestions as to what I should try next? Can I isolate and avoid those
    >>portions of tablespace 3 that seem to be corrupt? Should I not be able to
    >>import raster data into a new tablespace using an updated dbtune.sde table
    >>and bypass the corrupt one?
    >>
    >>Thanks in advance,
    >>
    >>Gord Mathews
    >>Ducks Unlimited Canada
    >>
    >>
    >>
    >>
    >
    >
    >
  • SystemAdmin
    SystemAdmin
    1731 Posts

    Re: Errors loading raster data into SDE 8.3

    ‏2005-09-06T14:39:41Z  
    John Smith wrote:

    > I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    > 8.3. The
    > desktop message popup dialog is titled "ArcToolbox Warning", and the
    > message itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >
    > My configuration is:
    > Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    > Server 5.00.2195 SP4
    > Desktop: ArcInfo 8.3
    >
    > Selected output from Db2diag.log shows:
    > <SNIP>
    > 2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > DIA3847C An error occurred in a database page header.
    > ZRC=0xFFFFF136
    >
    > 2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    > Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    > PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    > </SNIP>
    > And further down:
    > <SNIP>
    > 2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    > PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    > buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >
    > ** Page off disk *****0000 0000
    > </SNIP>
    >
    > DB2DART Processing completed with error!
    > WARNING:
    > The inspection phase did not complete!
    > ERROR:
    > Some tables indexes may be corrupt; errors will be cleared for index
    > objectswith invalid state after they have been succesfully rebuilt.
    > ERROR:
    > One or more tablespaces is corrupt.
    > Table data in such tablespaces may be orphaned.
    > </SNIP>
    >
    > I have attempted to import raster data of differing types and sizes, using
    > different user IDs each with sufficient privileges, and even created new
    > tablespaces exclusively for the raster data, but none of these have
    > helped. Each time the process fails and db2diag.log reveals a reference to
    > the same
    > CHAPTERNUMBER table as listed above. Does anyone have any suggestions as
    > to
    > what I should try next? Can I isolate and avoid those portions of
    > tablespace 3 that seem to be corrupt? Should I not be able to import
    > raster data into a new tablespace using an updated dbtune.sde table and
    > bypass the corrupt one?

    You could indeed try to import the data into another tablespace by adjusting
    the dbtune.sde file. However, you should call IBM support to open a PMR
    and get the "bad page" problem investigated and resolved. Such a problem
    is rather troublesome - maybe you just have a HD failure, maybe something
    worse happened.

    Knut Stolze
    Information Integration Development
    IBM Germany / University of Jena
    Knut,

    Thanks for your reply. About four months we did indeed have some hard drive
    issues that at the time seemed to get resolved. There may have been some
    damage to the tablespace that is only surfacing now. I will open a PMR and
    see if we can salvage our data as we are about to upgrade the server, DB2,
    SDE, and the OS in the next month or so.

    Gord Mathews
    Ducks Unlimited Canada
    "Knut Stolze" <stolze@de.ibm.com> wrote in message
    news:dfh5on$3rpc$1@news.boulder.ibm.com...
    > John Smith wrote:
    >
    >> I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    >> 8.3. The
    >> desktop message popup dialog is titled "ArcToolbox Warning", and the
    >> message itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >>
    >> My configuration is:
    >> Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    >> Server 5.00.2195 SP4
    >> Desktop: ArcInfo 8.3
    >>
    >> Selected output from Db2diag.log shows:
    >> <SNIP>
    >> 2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    >> PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >> buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >> DIA3847C An error occurred in a database page header.
    >> ZRC=0xFFFFF136
    >>
    >> 2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    >> PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >> buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >> Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    >> PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    >> </SNIP>
    >> And further down:
    >> <SNIP>
    >> 2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    >> PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >> buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >>
    >> ** Page off disk *****0000 0000
    >> </SNIP>
    >>
    >> DB2DART Processing completed with error!
    >> WARNING:
    >> The inspection phase did not complete!
    >> ERROR:
    >> Some tables indexes may be corrupt; errors will be cleared for index
    >> objectswith invalid state after they have been succesfully rebuilt.
    >> ERROR:
    >> One or more tablespaces is corrupt.
    >> Table data in such tablespaces may be orphaned.
    >> </SNIP>
    >>
    >> I have attempted to import raster data of differing types and sizes,
    >> using
    >> different user IDs each with sufficient privileges, and even created new
    >> tablespaces exclusively for the raster data, but none of these have
    >> helped. Each time the process fails and db2diag.log reveals a reference
    >> to
    >> the same
    >> CHAPTERNUMBER table as listed above. Does anyone have any suggestions as
    >> to
    >> what I should try next? Can I isolate and avoid those portions of
    >> tablespace 3 that seem to be corrupt? Should I not be able to import
    >> raster data into a new tablespace using an updated dbtune.sde table and
    >> bypass the corrupt one?
    >
    > You could indeed try to import the data into another tablespace by
    > adjusting
    > the dbtune.sde file. However, you should call IBM support to open a PMR
    > and get the "bad page" problem investigated and resolved. Such a problem
    > is rather troublesome - maybe you just have a HD failure, maybe something
    > worse happened.
    >
    > --
    > Knut Stolze
    > Information Integration Development
    > IBM Germany / University of Jena

  • SystemAdmin
    SystemAdmin
    1731 Posts

    Re: Errors loading raster data into SDE 8.3

    ‏2005-09-06T14:47:13Z  
    It certainly sounds like something is seriously wrong with one of your
    tablespaces and IBM support should be contacted, as Knut suggested.

    Are you able to start up ArcCatalog and display the list of layers in
    the database without error prior to this failure occurring? Do map draw
    operations complete successfully?

    My guess is that the 'SELECT * FROM SDE.DB2ADMIN.CHAPTERNUM' is just
    ArcCatalog doing a DESCRIBE to get information about layers in your
    ArcSDE database. You could take a DB2 CLI trace to get more detail
    about what ArcSDE is doing under the covers but I doubt it will help
    resolve the problem.

    Gord Mathews wrote:
    > Hi,
    >
    > Sorry, I didn't set up my newsgroup properties. Previous message is from me
    > not John Smith : )
    >
    > Gord Mathews
    > Ducks Unlimited Canada
    >
    > "John Smith" <jsmith@nowhere.com> wrote in message
    > news:dfa1ae$123c$1@news.boulder.ibm.com...
    >
    >>I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    >>8.3. The
    >>desktop message popup dialog is titled "ArcToolbox Warning", and the
    >>message
    >>itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >>
    >>My configuration is:
    >>Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    >>Server 5.00.2195 SP4
    >>Desktop: ArcInfo 8.3
    >>
    >>Selected output from Db2diag.log shows:
    >><SNIP>
    >>2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    >>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >>DIA3847C An error occurred in a database page header.
    >>ZRC=0xFFFFF136
    >>
    >>2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    >>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >>Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    >>PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    >></SNIP>
    >>And further down:
    >><SNIP>
    >>2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    >>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >>
    >>** Page off disk *****0000 0000
    >></SNIP>
    >>And:
    >><SNIP>
    >>Data Title:section stmt PID:2440 TID:3488 Node:000
    >>7365 6c65 6374 2020 2a20 2066 726f 6d20 select * from
    >>2053 4445 2e44 4232 4144 4d49 4e2e 4348 SDE.DB2ADMIN.CH
    >>4150 5445 524e 554d 4245 52 APTERNUMBER
    >></SNIP>
    >>
    >>Why the table CHAPTERNUMBER (obj:2328) is being queried I don't know
    >>except perhaps because it is in the same tablespace where I am attempting
    >>to load the rasters.
    >>Running db2dart sde /T on pool:3;obj:2328 reveals:
    >>
    >><SNIP>
    >>Table space: 3
    >>Traversing extent map for object type: 0
    >>Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    >>Traversing extent map for object type: 1
    >>Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    >>Extent Map traversal complete.
    >>Table inspection start: DB2ADMIN.CHAPTERNUMBER
    >>Data inspection phase start. Data obj: 2328 In pool: 3
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 4722978, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: This object page does not exist.
    >>Error: reading page: 0 from object: 2328
    >>Data inspection phase end.
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 1413563508, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: The tablespace object-table and the data disagree on the existance
    >>of inx data!
    >>Warning: Table descriptor record indicates index exist: 0
    >>Warning: DMS Object table indicates index exist: 1
    >>Index inspection phase start. Index obj: 2328 In pool: 3
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 0, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Index.
    >>Error: extent map anchor page of object is 9281914.
    >>Error detected in index.
    >>Index inspection phase end.
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 4400336, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: Unable to get table descriptor record.
    >>Error: Unable to determine pool relative page number for obj rel page 0
    >>(Obj ID:2328, Pool ID:3)
    >>Error: Unable to read pool page 4400336, object page 0, from pool 3,
    >>Error: parent pool 3, object ID 2328, object type Data.
    >>Error: extent map anchor page of object is 9281910.
    >>Error: Unable to get table descriptor record.
    >>Table inspection end.
    >>______________________________________
    >>
    >>DB2DART Processing completed with error!
    >>WARNING:
    >>The inspection phase did not complete!
    >>ERROR:
    >>Some tables indexes may be corrupt; errors will be cleared for index
    >>objectswith invalid state after they have been succesfully rebuilt.
    >>ERROR:
    >>One or more tablespaces is corrupt.
    >>Table data in such tablespaces may be orphaned.
    >></SNIP>
    >>
    >>I have attempted to import raster data of differing types and sizes, using
    >>different user IDs each with sufficient privileges, and even created new
    >>tablespaces exclusively for the raster data, but none of these have
    >>helped. Each time the process fails and db2diag.log reveals a reference to
    >>the same CHAPTERNUMBER table as listed above. Does anyone have any
    >>suggestions as to what I should try next? Can I isolate and avoid those
    >>portions of tablespace 3 that seem to be corrupt? Should I not be able to
    >>import raster data into a new tablespace using an updated dbtune.sde table
    >>and bypass the corrupt one?
    >>
    >>Thanks in advance,
    >>
    >>Gord Mathews
    >>Ducks Unlimited Canada
    >>
    >>
    >>
    >>
    >
    >
    >
    David,

    Thanks for replying. Yes, I am able to display the list of SDE layers, and
    all mapping and querying operations complete successfully. The problem
    first came to our attention when the CHAPTERNUMBER data was added to and
    queried via one of our ArcIMS sites. This caused SDE to become unresponsive
    until I RESTARTed the database. I will contact IBM support. Thanks again.

    Gord Mathews
    Ducks Unlimited Canada
    "David Adler" <dadler@us.ibm.com> wrote in message
    news:dfh8us$45nq$1@news.boulder.ibm.com...
    > It certainly sounds like something is seriously wrong with one of your
    > tablespaces and IBM support should be contacted, as Knut suggested.
    >
    > Are you able to start up ArcCatalog and display the list of layers in the
    > database without error prior to this failure occurring? Do map draw
    > operations complete successfully?
    >
    > My guess is that the 'SELECT * FROM SDE.DB2ADMIN.CHAPTERNUM' is just
    > ArcCatalog doing a DESCRIBE to get information about layers in your ArcSDE
    > database. You could take a DB2 CLI trace to get more detail about what
    > ArcSDE is doing under the covers but I doubt it will help resolve the
    > problem.
    >
    > Gord Mathews wrote:
    >> Hi,
    >>
    >> Sorry, I didn't set up my newsgroup properties. Previous message is from
    >> me not John Smith : )
    >>
    >> Gord Mathews
    >> Ducks Unlimited Canada
    >>
    >> "John Smith" <jsmith@nowhere.com> wrote in message
    >> news:dfa1ae$123c$1@news.boulder.ibm.com...
    >>
    >>>I have become unable to load raster data into ArcSDE 8.3 via ArcCatalog
    >>>8.3. The
    >>>desktop message popup dialog is titled "ArcToolbox Warning", and the
    >>>message
    >>>itself is "Underlying DBMS errorhttp://SDE.DB2ADMIN.(raster name)".
    >>>
    >>>My configuration is:
    >>>Server: DB2 v7.1.0.51 FP4; ArcSDE v8.3 build 750 SP1; Windows 2000
    >>>Server 5.00.2195 SP4
    >>>Desktop: ArcInfo 8.3
    >>>
    >>>Selected output from Db2diag.log shows:
    >>><SNIP>
    >>>2005-08-30-13.59.02.703001 Instance:DB2 Node:000
    >>>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>>buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >>>DIA3847C An error occurred in a database page header.
    >>>ZRC=0xFFFFF136
    >>>
    >>>2005-08-30-13.59.02.765000 Instance:DB2 Node:000
    >>>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>>buffer_pool_services sqlbrdpg Probe:1146 Database:SDE
    >>>Obj={pool:3;obj:2328;type:0} State=x25 Parent={3;2328}, EM=9281910,
    >>>PP0=9281912 Page=9281912 Cont=6 Offset=1680481 BlkSize=12 BadPage
    >>></SNIP>
    >>>And further down:
    >>><SNIP>
    >>>2005-08-30-13.59.05.921000 Instance:DB2 Node:000
    >>>PID:2440(db2syscs.exe) TID:3488 Appid:*LOCAL.DB2.050830185853
    >>>buffer_pool_services sqlbReadPage Probe:74 Database:SDE
    >>>
    >>>** Page off disk *****0000 0000
    >>></SNIP>
    >>>And:
    >>><SNIP>
    >>>Data Title:section stmt PID:2440 TID:3488 Node:000
    >>>7365 6c65 6374 2020 2a20 2066 726f 6d20 select * from
    >>>2053 4445 2e44 4232 4144 4d49 4e2e 4348 SDE.DB2ADMIN.CH
    >>>4150 5445 524e 554d 4245 52 APTERNUMBER
    >>></SNIP>
    >>>
    >>>Why the table CHAPTERNUMBER (obj:2328) is being queried I don't know
    >>>except perhaps because it is in the same tablespace where I am attempting
    >>>to load the rasters.
    >>>Running db2dart sde /T on pool:3;obj:2328 reveals:
    >>>
    >>><SNIP>
    >>>Table space: 3
    >>>Traversing extent map for object type: 0
    >>>Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    >>>Traversing extent map for object type: 1
    >>>Error: Max (512) SMP buffer exceeded in touch_extent! ix= 580
    >>>Extent Map traversal complete.
    >>>Table inspection start: DB2ADMIN.CHAPTERNUMBER
    >>>Data inspection phase start. Data obj: 2328 In pool: 3
    >>>Error: Unable to determine pool relative page number for obj rel page 0
    >>>(Obj ID:2328, Pool ID:3)
    >>>Error: Unable to read pool page 4722978, object page 0, from pool 3,
    >>>Error: parent pool 3, object ID 2328, object type Data.
    >>>Error: extent map anchor page of object is 9281910.
    >>>Error: This object page does not exist.
    >>>Error: reading page: 0 from object: 2328
    >>>Data inspection phase end.
    >>>Error: Unable to determine pool relative page number for obj rel page 0
    >>>(Obj ID:2328, Pool ID:3)
    >>>Error: Unable to read pool page 1413563508, object page 0, from pool 3,
    >>>Error: parent pool 3, object ID 2328, object type Data.
    >>>Error: extent map anchor page of object is 9281910.
    >>>Error: The tablespace object-table and the data disagree on the existance
    >>>of inx data!
    >>>Warning: Table descriptor record indicates index exist: 0
    >>>Warning: DMS Object table indicates index exist: 1
    >>>Index inspection phase start. Index obj: 2328 In pool: 3
    >>>Error: Unable to determine pool relative page number for obj rel page 0
    >>>(Obj ID:2328, Pool ID:3)
    >>>Error: Unable to read pool page 0, object page 0, from pool 3,
    >>>Error: parent pool 3, object ID 2328, object type Index.
    >>>Error: extent map anchor page of object is 9281914.
    >>>Error detected in index.
    >>>Index inspection phase end.
    >>>Error: Unable to determine pool relative page number for obj rel page 0
    >>>(Obj ID:2328, Pool ID:3)
    >>>Error: Unable to read pool page 4400336, object page 0, from pool 3,
    >>>Error: parent pool 3, object ID 2328, object type Data.
    >>>Error: extent map anchor page of object is 9281910.
    >>>Error: Unable to get table descriptor record.
    >>>Error: Unable to determine pool relative page number for obj rel page 0
    >>>(Obj ID:2328, Pool ID:3)
    >>>Error: Unable to read pool page 4400336, object page 0, from pool 3,
    >>>Error: parent pool 3, object ID 2328, object type Data.
    >>>Error: extent map anchor page of object is 9281910.
    >>>Error: Unable to get table descriptor record.
    >>>Table inspection end.
    >>>______________________________________
    >>>
    >>>DB2DART Processing completed with error!
    >>>WARNING:
    >>>The inspection phase did not complete!
    >>>ERROR:
    >>>Some tables indexes may be corrupt; errors will be cleared for index
    >>>objectswith invalid state after they have been succesfully rebuilt.
    >>>ERROR:
    >>>One or more tablespaces is corrupt.
    >>>Table data in such tablespaces may be orphaned.
    >>></SNIP>
    >>>
    >>>I have attempted to import raster data of differing types and sizes,
    >>>using different user IDs each with sufficient privileges, and even
    >>>created new tablespaces exclusively for the raster data, but none of
    >>>these have helped. Each time the process fails and db2diag.log reveals a
    >>>reference to the same CHAPTERNUMBER table as listed above. Does anyone
    >>>have any suggestions as to what I should try next? Can I isolate and
    >>>avoid those portions of tablespace 3 that seem to be corrupt? Should I
    >>>not be able to import raster data into a new tablespace using an updated
    >>>dbtune.sde table and bypass the corrupt one?
    >>>
    >>>Thanks in advance,
    >>>
    >>>Gord Mathews
    >>>Ducks Unlimited Canada
    >>>
    >>>
    >>>
    >>>
    >>
    >>