mceoni -- how many wallet entries were you able to add for this user? You can get the info on the limits by executing "tdwallet help limits", as mentioned a few times in the comments above.
The only way to get that exception should be if the user's wallet file (or disk) was full, just like the message says. The wallet file should be capable of containing a very high number of entries, so filling the file is not trivial. Perhaps there's some kind of other disk space quota you've ran into, or the free space you checked is not on the same disk as where the wallet file is located. If you can't figure it out, please open an incident with GSC so we can take a closer look.
I have the same scenario that "mceoni" posted before. I'm getting the message below from TPT:
Lizarb -- I found your incident (it didn't make its way to me yet, so I asked to have it escalated).
Could you please check if your temporary directory or partition is full or nearly full? That may also trigger the exception. Please use the incident to provide the answer -- I will communicate with you through our support team.
I just realized that in an earlier comment I provided a bad example for hiding a username in the wallet:
This is wrong, because the item name would have to include the contents of $tdwallet(usr1), thus exposing the username. If the intention is to hide the username, the correct answer would be something like the following:
which does not require the use of nested keywords.
Hello - Thanks for the wonderful article. I am getting the error "The logmech string exceeds the length limit. The maximum length is 8" when I try to run a fast export job. Below are the login info and the TD Wallet entry.
.logon tdpid/bakthro,$tdwallet # fast Export login
com.teradata.TD2 -> $td_wallet(testpw).
testpw -> P@$sw0rd
I don't get this error, when I do the same in a bteq script.
Also, when I use the below.
.logon tdpid/$tdwallet(user),$tdwallet(password) # Fastexport logon
I get the below error. This too works well in bteq.
**** 15:17:26 UTY1006 CLI error: 303, CLI2: BADLOGON(303): Invalid logon
I figured out the reason for the second issue- CLI2: BADLOGON(303): Invalid logon
string . I just missed a semi colon. Could I get the reason and work around for the first error - "The logmech string exceeds the length limit". It works in bteq and not in fast export.
Roopalini -- there is an invalid underscore in one of your keywords -- "$td_wallet(testpw)". But that would not cause the logmech string error. The logmech string error doesn't have anything to to with Teradata Wallet -- it is reporting that your .logmech command is invalid. If you can't resolve this, please open an incident.
I'm new to tdwallets. Was wondering if tdwallets work on linux odbc? R14.00.
Using $tdwallet(mydev1) at the password prompt. Same tdwallet works with bteq. And same password works with ODBC when not using tdwallets.
Enter Data Source Name: devpridsn
Enter UserID: myid1
Connecting with SQLConnect(DSN=devpridsn,UID=rssabdev1,PWD=*)...
adhoc: (SQL Diagnostics) STATE=28000, CODE=4294959279, MSG=[Teradata][ODBC Teradata Driver][Teradata Database] The UserId, Password or Account is invalid.
ODBC connection closed.
Regarding Portability? How feasibile would it be to populate the wallet on one linux server and then copy the config and wallet files to other servers? What are all of the files that must be copied?