Difference between revisions of "ARS0016E"
m (Promoted heading.) |
m (IBM CMOD Upgrades are the best way to prevent this error.) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
Message Number: 16 | Message Number: 16 | ||
Message Severity: Error | Message Severity: Error (Corrective action is required to continue) | ||
Message Name: ARS0016E | Message Name: ARS0016E | ||
| Line 23: | Line 23: | ||
If you are still using DMS, have your administrator provide a new raw logical volume (AIX), slice (Solaris), or partition (Linux), and add the new storage to the database. | If you are still using DMS, have your administrator provide a new raw logical volume (AIX), slice (Solaris), or partition (Linux), and add the new storage to the database. | ||
Consider [https://Tenacious.Consulting Upgrading IBM CMOD] and DB2 to a newer version. | |||
Latest revision as of 02:29, 24 March 2018
What was the error?
Message Number: 16
Message Severity: Error (Corrective action is required to continue)
Message Name: ARS0016E
Message Text: Unable to allocate enough DMS filesystem space for table. Need(integer),Available(integer), Extent(size)
What were you doing?
Probably loading new data into an existing Application Group.
What happened?
CMOD decided it was time to create a new table, as the current table had reached it's maximum size limit (usually 2.5 or 10 million rows). When CMOD attempted to allocate space for the new table, DB2 reported that there was not enough space available to create the table.
Troubleshooting
This message should be very rare. Database Managed Space is an older method for allocating storage to a database manager, and has been replaced with the more robust 'System Managed Space' ('SMS').
If you are still using DMS, have your administrator provide a new raw logical volume (AIX), slice (Solaris), or partition (Linux), and add the new storage to the database.
Consider Upgrading IBM CMOD and DB2 to a newer version.