Type 30 descriptor, table is full.

[vcannadevula]

We are having both the server and prallel extender in the same box. When the parallel jobs are running the server jobs are getting the following message and abortings!!!!

Unable to allocate Type 30 descriptor, table is full.
DataStage Job 3096 Phantom 24343
DataStage Phantom Finished



Do any of you encountered this error. Is it running out of RAM????

[I_Server_Whale]

Hi,

Please USE the SEARCH facility. Here is what I found:

LINK1

LINK2

Thanks!
Naveen.

[vcannadevula]

We are having both the server and prallel extender in the same box. When the parallel jobs are running the server jobs are getting the following message and abortings!!!!

Unable to allocate Type 30 descriptor, table is full.
DataStage Job 3096 Phantom 24343
DataStage Phantom Finished



Do any of you encountered this error. Is it running out of RAM????

Please ignore this message. I got the answer

[ArndW]

You will need to modify your DataStage engine configuration, specifically the T30FILES parameters to allocate enough internal table space to handle all of these concurrent open dynamic files. You can use the search facility to locate threads on this topic, including (i think) some recommendations on sizing.

[vcannadevula]

You will need to modify your DataStage engine configuration, specifically the T30FILES parameters to allocate enough internal table space to handle all of these concurrent open dynamic files. You can use the search facility to locate threads on this topic, including (i think) some recommendations on sizing.

Does any one have any help file how to read the output of this

"analyze.shm -d"

I would like to know how much should i increase the T30 limit by doing this command

[ArndW]

The command tells you what you have, not what you need.

The original configuration parameters were designed on machines with a lot less physical memory. I used uvconfig settings identical to the current defaults in the 80's on machines with only 16Mb of physical memory - so increasing a non-pagable resident table by a couple of Kb could have a significant impact on system swapping!

Without knowing much about your environment, it should be safe to take your current T30FILES value and add 50% to it.

[ray.wurlod]

The T30FILE configuration parameter sets the number of slots ("rows") in a table in shared memory in which the current settings for each open dynamic (Type 30) hashed file resides.

The table contains the following columns displayed by ANALYZE.SHM -d

Code: Select all

Slot #     Slot number in table, beginning at 0      
Inode      File's inode number
Device     File's device number 
Ref Count  Number of processes with this file open 
Htype      Hashing algorithm (20 = GENERAL, 21 = SEQ.NUM) 
Split      SPLIT.LOAD value (default 80)
Merge      MERGE.LOAD value (default 50)
Curmod     Current modulus (number of groups)
Basemod    Largest power of 2 less than or equal to Currmod
Largerec   LARGE.RECORD value (default 80% of group size)
Filesp     Physical size of file (bytes)
Selects    Number of currently active SELECT operations on file
Nextsplit  Number of next group to split

[anu123]

We are having both the server and prallel extender in the same box. When the parallel jobs are running the server jobs are getting the following message and abortings!!!!

Unable to allocate Type 30 descriptor, table is full.
DataStage Job 3096 Phantom 24343
DataStage Phantom Finished



Do any of you encountered this error. Is it running out of RAM????

Please ignore this message. I got the answer

Hi,

Could you please post your findings/solution for the above problem.Even we are getting same error.

thanks in advance,

[vcannadevula]

Our problem was with the Unix OS level limitations.
We cannot create more than 32767 directories with in a directory.
After this , the link limit for the unix will be consumed and it will not allow you to create any directory. as Type 30 hash file is a directory, it did not allow us to create any directory.

Simple test we did was use mkdir command in the directory you are creating the hash file. If it is successful, then u might be facing the T30 limit
If it is not successful , you need to re-create the directory, to which you are creating the hash file.

[anu123]

Our problem was with the Unix OS level limitations.
We cannot create more than 32767 directories with in a directory.
After this , the link limit for the unix will be consumed and it will not allow you to create any directory. as Type 30 hash file is a directory, it did not allow us to create any directory.

Simple test we did was use mkdir command in the directory you are creating the hash file. If it is successful, then u might be facing the T30 limit
If it is not successful , you need to re-create the directory, to which you are creating the hash file.

thanks for the info VC. I will work on it and let you update.

[ray.wurlod]

The error message indicates that it is the T30FILE setting that needs to be fixed. You are not hitting the "sub-directories in a directory" limit - that would generate a rather different error message.

The problem is not being caused by running both parallel and server jobs; it's just the total number of jobs. Every job has to open a number of hashed files in the Repository (such as RT_STATUS, RT_LOG, RT_CONFIG) and the total of these, plus hashed files opened by server jobs, is what's led to the T30FILE table becoming full.

As you can see from my earlier post, each row in the T30FILE table is quite small, so increasing T30FILE by 50% or even 100% is quite feasible.

[vcannadevula]

[quote="ray.wurlod"]The error message indicates that it is the T30FILE setting that needs to be fixed. You are not hitting the "sub-directories in a directory" limit - that would generate a rather different error message.

Ray,
This might be a bug in Datastage 751. It gives the Type 30 descriptor full message even in the scenario i have specified.