↧
RDBMS error 3813: The positional assignment list has too many values - response (2) by Fred
↧
DECODE Does Not Trap Divide by Zero Error - response (3) by ssi112
Excellent solution Dieter, thanks much for the help!
↧
↧
How to recover from error 3916: Requested information not in dictionary - forum topic by maestrox2
Hello,
I have a probelm that I have been banging my head trying to recover from.
We have an application that replicates data from our own database into Teradata. Tests are run which repeatedly will create sets of tables, load data, perform some tests, then drop the tables.
Problem is somwhere in a recent test run, probably due to a failed mload process (my guess), I am left with one table that will not drop. Anytime I try and drop the table I get an Error 3916: Requested information not in dictionary. The table is viewable through Teradata Manager, but when I try and drop it whether through the manager or using BTEQ I get this error. The table DDL looks like this:
REATE MULTISET TABLE Adabas.SUBALL_EMPLOYEES_ADDRESS_LINE ,FALLBACK ,
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT
(
ISN INTEGER,
ADDRESS_LINE VARCHAR(20) CHARACTER SET UNICODE NOT CASESPECIFIC,
ADDRESS_LINE_IX INTEGER,
FOREIGN KEY ( ISN ) REFERENCES NON-EXISTENT PARENT TABLE)
PRIMARY INDEX ( ISN );
I am concerned abou the "FOREIGN KEY...REFERENCES NON-EXISTENT PARENT TABLE". Is that part of the cause of the issue? Recreating the table does not help, as the table create fails saying it already exists. Trying to drop it says it does not. I have even tried creating a dummy parent table called "NON-EXISTENT PARENT TABLE" and adding the foreign key references, no good. I have even gone so far as to delete all other user tables in the database and tried deleting the database with the intention of recreating it. Can't delete the database because it says I cannot drop a database when tables exist.
Any help in how I can recover from this is much appreciated.
This is Teradata v13 on Windows.
Bob
Tags:
Forums:
↧
issue to install ODBC Driver (64x) -CLIv2 (64x) not recognized - response (1) by perezco
adding comments
both version point 15.10.01.00
↧
Equivalent sentence in Teradata for the Oracle "CONVERT"? - response (5) by david.craig
If I understand correctly, you want the Teradata equivalent of the Oracle CONVERT function. For starters, I was pointing out some of the differences in string literals between the two products. There is plenty of information on the developer exchange on Oracle migations, for example: http://developer.teradata.com/database/training/oracle-to-teradata-101.
As Ulrich noted, TRANSLATE is not the equivalent of CONVERT. I say 'not' because you want to do a best-fit mapping of UTF8 to 7-bit ASCII. TRANSLATE will return a conversion exception if the source character is not in the destination repertoire. It does not do best-fit.
The best-fit mapping of UTF8 to 7-bit ASCII would conceivably need to map 110,000 assigned Unicode characters to 128 ASCII Characters. This is probably why Oracle discourages the use of CONVERT, see https://docs.oracle.com/cd/B28359_01/server.111/b28286/functions027.htm. The Unicode consortium also discourages best-fit conversions, see http://unicode.org/reports/tr22/tr22-3.html#Best-Fit_Mappings.
If you still want to do a best-fit mapping to 7-bit ASCII, you'll need to implement it as a Teradata UDF (User Defined Function). You could also try the TRANSLATE .... using UNICODE_TO_UNICODE_NFD to expose the base characters.
-David
↧
↧
Windows Defender Trojan detected - install for Studio 15.10.01.01 - response (2) by todddube
@fgrimmer thanks - it was wierd -
↧
How to expose Temporal Table to BI tools which doesn't speak Temporal - forum topic by jessielin
Does anyone has experience in exposing Temporal Table to BI tools which doesn't speak Temporal?
For example, I have temporal table below:
CREATE MULTISET TABLE DimModel.Stores_ST_Temp ,NO FALLBACK ,
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT,
DEFAULT MERGEBLOCKRATIO
(
Store_ID INTEGER NOT NULL,
Store_Name VARCHAR(50) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
District_ID INTEGER NULL,
Store_Manager VARCHAR(50) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
Tel_Number CHAR(10) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
District_Name VARCHAR(50) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
District_Manager VARCHAR(50) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,
EffectivePeriod PERIOD(DATE) AS VALIDTIME NOT NULL
)
PRIMARY INDEX (Store_ID)
And I can create the sequenced validtime,
CREATE VIEW DimModel.Stores_ST_TempV AS
SEQUENCED VALIDTIME SELECT * FROM DimModel.Stores_ST_Temp;
And when I select from this view, the column VALIDTIME will be in the result set, if I use EQUENCED VALIDTIME again.
But I wan't able to use BEGIN(VALIDTIME) as Effective_Date, END(VALIDTIME) as Effective_End_Date to expose it as the traditional SCD type 2 columns. So that if a BI tool doesn't speak Temporal would still be able to access it.
Lastly, do the major BI tools such as Microstratgy, Cognos, OBIEE, Qlikview, Tableau etc support Temporal?
Either ISO or Teradata style?
Forums:
↧
MAC ODBC does not handle Unicode - forum topic by Pat GoHabsGo
MAC ODBC doesn't handle UNICODE correctly. It just removed none plain text character. Does anybody have a trick to fix it?
Below are conducted test:
MAC terminal handle . For example, can display the Euro sign:
$ echo -e '\xe2\x82\xac'
€
Moreover, locale reveals that everything is set to en_US.UTF-8 and iterm2 has the character encoding set to Unicode (UTF-8).
One of the Unicode value that creates the problem is U+2011, a non breaking hyphen. Oct/dec/hex
020021
8209
0x2011
‑
This is just one example. Everything that is not plain ASCII appears to be missing.
Window ODBC display correct string that I see in Alation or SQL Assistant is
TI‑84 Plus C Silver Edition Graphing Calculator Color Display Brand New!
When I attempt to validate my ODBC installation with tdxodbc, the hyphen does not display correctly:
dmasterov @ /Library/Application Support/teradata/client/15.10/bin
$
Connecting with SQLDriverConnect("Driver=Teradata; DBCNAME=mozart; UID=dmasterov; PWD=*; CharacterSet=UTF8")...
.....ODBC connection successful.
ODBC version = -03.52.0000-
DBMS name = -Teradata-
DBMS version = -14.10.0603 14.10.06.03-
Driver name = -tdata.dylib-
Driver version = -15.10.01.00-
Driver ODBC version = -03.51-
(type quit to terminate adhoc)
Enter SQL string : SELECT auct_titl FROM access_views.dw_lstg_item_cold WHERE item_id = 301142510864;
Executing SQLExecDirect("SELECT auct_titl FROM access_views.dw_lstg_item_cold WHERE item_id = 301142510864;")...
SQL Statement [1]: 1 rows affected.
AUCT_TITL
TI84 Plus C Silver Edition Graphing Calculator Color Display Brand New!
See Hyphen was removed between TI and 84
Tags:
Forums:
↧
How to recover from error 3916: Requested information not in dictionary - response (1) by Fred
To remove the "orphan" foreign key constraint:
ALTER TABLE xxx DROP INCONSISTENT REFERENCES;
↧
↧
MAC ODBC does not handle Unicode - response (1) by Fred
Have you tried using the driver with your own ODBC application or a full-featured client? This is likely a limitation of the tdxodbc test program rather than the driver.
↧
Windows Defender Trojan detected - install for Studio 15.10.01.01 - response (3) by fgrimmer
@toddube, We agree. We have scanned the files and found nothing. We have had others download the package without reporting any issues. I am not sure where/how the virus could slip in? Just curious, if you are able to install the 32-bit version successfully?
↧
Help on Teradata real time scenario interview questions - response (2) by MDinesh
Dear Chava,
Great and good support.
Please share and spread the same to my email id : dineshcorp27@gmail.com.
Thank you very much and wishing you a immense in all your works.
Best Regards,
Dinesh M
↧
interview help - response (44) by MDinesh
Dear ANANDEKBOTE,
Great initiative in preparation of the same.
Will be helpful to us, if you share the same and spread the power of Teradata via the same.
My email id : dineshcorp27@gmail.com
Thank you very much for your unconditional support! Inspired.
Best Regards,
Dinesh M
↧
↧
Unicode (German) characters are not getting displayed properly in Teradata SQL Assistant - response (2) by sunilsaw
Hi Carlos!
You're correct, actually the column is UTF 8, but my TPT's session character set was "USING CHARACTER SET ASCII" in place of "USING CHARACTER SET UTF8".
I have changed it to UTF8 and now I am getting correct unicode characters in SQL Assistant.
Thanks a lot!
Sunil
↧
Failed 2666: Invalid Date Supplied for Date_Column - forum topic by uchandru85
AND CAST (contact_date AS DATE FORMAT 'dd/mm/yyyy') <=CAST ({?StartDATE} AS DATE FORMAT 'dd/mm/yyyy')
Above code returns error - Failed 2666: Invalid Date Supplied for contact_date
Forums:
↧
issue to install ODBC Driver (64x) -CLIv2 (64x) not recognized - response (2) by perezco
never mind the CLIv2 and ODBC have thier own install apps
↧
My data mover job sometimes work and sometimes hang - forum topic by nick2408
Hi
My requirement is to move a complete databases, along with the tables and data from one server to another. I have a DM job that I am using which normally does the task but most of the times it doesnt do anything. I see that the sessions in the target server, are always in idle state (when seen from viewpoint) Any pointers to what might be causing this?
Below is my xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dmCreate xmlns="http://schemas.teradata.com/dataMover/v2009" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.teradata.com/dataMover/v2009/DataMover.xsd">
<job_name>AMEX1_AMEX2_impac_data</job_name>
<source_tdpid>dev</source_tdpid>
<source_user>abc</source_user>
<source_password>xxxxxx</source_password>
<target_tdpid>test</target_tdpid>
<target_user>abc1</target_user>
<target_password>xxxx</target_password>
<data_streams>4</data_streams>
<source_sessions>32</source_sessions>
<target_sessions>64</target_sessions>
<force_utility>ARC</force_utility>
<log_level>1</log_level>
<database selection="included">
<name>sourcedb</name>
<target_database>
<name>targetdb</name>
</target_database>
</database>
<query_band>xyzzzzzzzzzzzzzzzzzzzzzzz</queryband>
</dmCreate>Any quick help would be greatly appreciated
Thanks
Forums:
↧
↧
Teradata perm space release issue - forum topic by Tdusersam
We have a scenario in our teradata database where perm space is not getting released even when we delete all rows from the tables. Also, under the same condition the current perm of 2 replica tables with same rowcount, same structure and same index are deviating by 300% . when in a manual effort, we dropped and recreated the table, the currentperm was back to expected. Can somebody tell me any potential reason ?
Forums:
↧
After Initial BLC Loading - forum topic by Kishore_1
As space saving initiative, we are applying BLC on certain tables in our Teradata system.
We are using queryband "SET QUERY_BAND='BLOCKCOMPRESSION=YES;' FOR SESSION;" to compress the data and insert into a table.After the initial load, we are dropping the old table and renaming the compressed table as original.My question is after the initial load, do we need to use the querybanding on a daily basis for the incremental loads on that table?Will be data inserted into that table be compressed automatically , or we have to specify compression query band in the job session that loads data on a daily basis?
Tags:
Forums:
↧
Teradata perm space release issue - response (1) by dnoeth
Two possible reasons come to mind:
- It's a Temporal Table, all rows were closed
- ONLINE ARCHIVE was used, but not switched off. Check using dbc.ArchiveLoggingObjsV.
↧
That error specificallly indicates you have too many commas within the INSERT statement. Check that you don't have any lines with both leading and trailing commas, or extra comma before first or after last expression, duplicated lines, etc.