Output to Teradata Database Errors: No more room In Database
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello,
I have few workflows scheduled in Gallery to update the tables in ODBC Teradata Driver. However, I recently got some errors randomly, saying that DataWrap2ODBC::SendBatch:[Teradata][ODBC Teradata Driver]]Teradata Database]No more room in Database....
But after checked with the database admin, we only used 25% of the space so we should have plenty room for new data.
Have anyone had this issue before?
Thanks
- Labels:
- Database Connection
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The errors are not related to Alteryx, but to Teradata database. I have done a google search and found this post that explains the cause and resolution: https://www.docs.teradata.com/r/8MhLDQBmL52OycrEKPuGqg/RL3qcSHqgxQ1~gKmZWL9dg
It says:
"2644 No more room in database %DBID.
Explanation:
This error occurs only when an attempt is made to increase the amount of space used by a database, and there is no space left to accommodate the increase. Note: The numeric database id may be displayed in place of the database name when the name is not available. This would be the case, for example, when a CREATE DATABASE or CREATE USER statement fails because there is insufficient space in the new database for a default journal table.
Generated By:
AMP Step Processing Software.
For Whom:
End User.
Remedy:
Either drop some of the tables currently contained in the database, or have the permanent space limit for the database increased. Then resubmit the request."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thank you so much for your replies. I did check with my data admin and we found that we only had used 25% of total space so we should have space to load the data.
Not sure if it would still trigger this issue.
Thanks
Sammi
