Results 1 to 13 of 13

Thread: "0xFFFFD121

  1. #1
    Join Date
    Nov 2003
    Posts
    68

    Unanswered: "0xFFFFD121

    hi to all
    pl tell me how to decode this error code."0xFFFFD121"


    y it is comming?
    DIA9999E An internal error occurred. Report the following error code :
    "0xFFFFD121

  2. #2
    Join Date
    Apr 2003
    Posts
    191

    Re: "0xFFFFD121

    Hi,

    errors like these should be reported to DB2 support.

    Johann

    Originally posted by jagan_5378
    hi to all
    pl tell me how to decode this error code."0xFFFFD121"


    y it is comming?
    DIA9999E An internal error occurred. Report the following error code :
    "0xFFFFD121

  3. #3
    Join Date
    Mar 2003
    Posts
    343
    If you look in the troublshooting guide, Appendix A DB2 Internal Return Codes, 0xFFFFD121 means Container full - which means that there is a process out there trying to insert/import/load a tablespace, one of whose containers are full.

  4. #4
    Join Date
    Nov 2003
    Posts
    68

    cchattoraj

    thank u very much cchattoraj.


    Tablespaces for Current Database

    Tablespace ID = 0
    Name = SYSCATSPACE
    Type = System managed space
    Contents = Any data
    State = 0x0000
    hattoraj
    Normal
    Total pages = 23316
    Useable pages = 23316
    Used pages = 23316
    Free pages = Not applicable
    High water mark (pages) = Not applicable
    Page size (bytes) = 4096
    Extent size (pages) = 32
    Prefetch size (pages) = 32
    Number of containers = 1

    Tablespace ID = 1
    Name = DYTAB
    Type = Database managed space
    Name = DYTAB
    Type = Database managed space
    Contents = User Temporary data
    State = 0x0000
    Detailed explanation:
    Normal
    Total pages = 512000
    Useable pages = 511936
    Used pages = 192
    Free pages = 511744
    High water mark (pages) = 224
    Page size (bytes) = 4096
    Extent size (pages) = 32
    Prefetch size (pages) = 32
    Number of containers = 2

    Tablespace ID = 2
    Name = KALTAB
    Type = Database managed space
    Contents = Any data
    State = 0x0000
    Detailed explanation:
    Normal
    Detailed explanation:
    Normal
    Total pages = 1408000
    Useable pages = 1407968
    Used pages = 128896
    Free pages = 1279072
    High water mark (pages) = 128896
    Page size (bytes) = 4096
    Extent size (pages) = 32
    Prefetch size (pages) = 128
    Number of containers = 1
    Minimum recovery time Useable pages = 1023872
    Used pages = 1312
    Free pages = 1022560
    High water mark (pages) = 15296
    Page size (bytes) = 4096
    Extent size (pages) = 32
    Prefetch size (pages) = 32
    Number of containers = 4

    = 2003-12-22-06.42.27.000000

    Tablespace ID = 3
    Name = TEMPSPACE1
    Type = Database managed space
    Contents = System Temporary data
    State = 0x0000
    Detailed explanation:
    Normal
    Total pages = 1024000
    Useable pages = 1023872
    Used pages = 1312



    all table spaces having free pages.

    pl tell how read that error code?

    thank u

  5. #5
    Join Date
    Mar 2003
    Posts
    343
    I said that a container is full. I do not know how you have the tablespace containers setup so I really can't tell you what the issue is. However, here's the manner in which it works and hopefully you can work it out. If you define multiple containers for a tablespace, they should all be the same size. DB2 will place data in the containers somewhat evenly - there will however be some variation in the amount of data in each (by which I mean that they will not be exactly the same). What this also means is that if one container fills up, then DB2 will rollback the transaction which fills it up.

    I have noticed that when this happens, it creates a bunch of trap files in the db2dump directory and writes messages to the db2diag.log indicating which container filled out. That should tell you where the problem is. If you do not know what the containers for each tablespace are, do a
    list tablespace containers for <tbspaceid>

    where tbspaceid is the ID for each tablespace in syscat.tablespaces or from db2 list tablespaces.

    For sms tablespaces, do a df -k . in the directory for each container.

    Hope this helps.

  6. #6
    Join Date
    May 2003
    Posts
    369

    tablespace snapshot

    Also useful:

    db2 get snapshot for tablespace on database;

  7. #7
    Join Date
    Mar 2003
    Posts
    343
    But the snapshots do not give storage related information - they give access information. Or is there an option which gives storage information as well?

  8. #8
    Join Date
    Jul 2002
    Location
    ATL
    Posts
    170
    Your Syscat Tablespace is full.

    If you look at Usable Pages and Used Pages , they are same and it means your tablespace is full

  9. #9
    Join Date
    Nov 2004
    Posts
    15

    Question

    Hi,

    I also got 0xFFFFD121 and DB2 abended while running an IMPORT. I have UDB 7.2 on Solaris 8. Here is the background:

    I have a table T1 using 3 tablespaces:
    data on TS1 , pgsz 8K
    lobs on TS1L, pgsz 4K
    index on TS1X, pgsz 4K

    Due to the pgsz difference, REORG cannot be done on this table.
    So I did the followings:
    1) Export all data from T1
    2) Drop T1 and its TS then a) recreate the TS's with same pgsz 8K, b) recreate T1
    3) Import data into the new table.
    Db2 always crashed with 0xFFFFD121 after inserting the first 5000 rows. I had to restart DB2. If I delete all rows in T1 then run the IMPORT again, it works fine, but if I restart from step 2) above, DB2 crash again after 5000 rows.

    Any idea ?

    Thanks

  10. #10
    Join Date
    Apr 2003
    Posts
    191

    0xFFFFD121 - mvo@work

    Hi mvo@work,

    do you mind passing along the import statement that you use?

    Also, what is DB2 crashes supposed to mean? Instance, database or just your application?

    Johann

    Quote Originally Posted by mvo@work
    Hi,

    I also got and DB2 abended while running an IMPORT. I have UDB 7.2 on Solaris 8. Here is the background:

    I have a table T1 using 3 tablespaces:
    data on TS1 , pgsz 8K
    lobs on TS1L, pgsz 4K
    index on TS1X, pgsz 4K

    Due to the pgsz difference, REORG cannot be done on this table.
    So I did the followings:
    1) Export all data from T1
    2) Drop T1 and its TS then a) recreate the TS's with same pgsz 8K, b) recreate T1
    3) Import data into the new table.
    Db2 always crashed with 0xFFFFD121 after inserting the first 5000 rows. I had to restart DB2. If I delete all rows in T1 then run the IMPORT again, it works fine, but if I restart from step 2) above, DB2 crash again after 5000 rows.

    Any idea ?

    Thanks

  11. #11
    Join Date
    Nov 2004
    Posts
    15
    1) import from tab1.ixf of ixf lobs from 'lobs/' modified by lobsinfile commitcount 5000 insert into T1

    There are ~182000 rows to insert

    2) DB2 crash: db2 stopped, I had to issue db2start.

  12. #12
    Join Date
    Nov 2004
    Posts
    374

    db2 crash

    db2diag.log should indicate the error anyhow
    after the startup :
    db2 connect to xx
    db2 list tablespaces show detail
    db2 list tablespace containers for 1 <-- repeat for each tablespace
    there must be a tablespace full
    syscatspace is NOT full : this is sms : usable pages = used pages
    pages are acquired when needed
    or the filesystem is full keeping the syscatspace
    Best Regards, Guy Przytula
    Best Regards, Guy Przytula
    DB2/ORA/SQL Services
    DB2 DBA & Advanced DBA Certified
    DB2 Dprop Certified
    http://users.skynet.be/przytula/dbss.html

  13. #13
    Join Date
    Apr 2003
    Posts
    191

    import may not bring down an instance

    This looks like a bug.

    I would get IBM support to look into this.

    Johann


    Quote Originally Posted by mvo@work
    1) import from tab1.ixf of ixf lobs from 'lobs/' modified by lobsinfile commitcount 5000 insert into T1

    There are ~182000 rows to insert

    2) DB2 crash: db2 stopped, I had to issue db2start.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •