1.

Getting error as Updated one row and inserted one row in collect statistics we
need to add the following line in front of collect statistics query
/*PTE IGNORE ALL TEXT BEGIN*/
month
Mar

dr
1724
50

Apr

1812
69

desc
temporal
related
Plan directive
setup

used NONTEMPORAL tag in front

for each insert query to prevent too many
arguments error
in order to reproduce the problem in PTE
site run
single test case, then select plan directive
setup

DR Test Tag
************
REGRTESTNEEDED - DR unit test is related to SQL but test case is not available
in PTE (Regression Test Needed).
TEST-NOTE
******************************************************
TEST-TAG: REGRTESTADDED
Test Area: DR2015Q3
Test Abbrev/Prefix: DR2015Q3
Tests: Same as DR Number - drxxxxx
Tool: PTE
Directory: /ptehome/pte_dev/td151000/dr2015q3/network
2. When you get Failure 9843 Query resulting in mixing of ANSI
temporal syntax and Tera data temporal syntax is not allowed.
Do the following in dbscontrol
Enter a command, HELP, or QUIT:
m g 88=0
The TemporalBehavior field has been modified from 1 to 0.
NOTE: This change will become effective after the DBS Control Record
has been written.

Plan
directive
setup
need to be
run in pte

Enter a command, HELP, or QUIT:

wr
3. In any select query current_date should be changed with some static date like
DATE 2016-05-27.
4. LDAP user related dr not collectable

While developing test-cases please follow the below steps for creation of Users/Databases.

Steps to follow for modification:

If the test-case contains only one user modify the user perm space as 3e7 ;
If the test-case contains only one user & < 4 DBs then modify user perm space as 5e7 &
database permspace as 1e7
If the test-case contains only one user & > 4 DBs then modify user perm space as 1e8 &
database permspace as 1e7

5.
6.
7.
8.
9.

vi /var/log/messages ( to see the log messages after executing any test case)
tail -f /var/log/messages ( to see last lines of the var log messages)
grep -Ril "_qcd" . (to search for a key word in entire directory)
upgrade_td_efix -sysinit force (to run sysinit
Sysinit dip command
a. upgrade_td_linux -build 16t.00.00.108 -sysinit force
command
build
command comnand
10./ptehome/linux_client/ttu160/bteq < temp.bteq > temp.out 2>&1
11.
Run Plan directive in PTE with machine ip or machine name
without cleanup for plan directive drs
12.dbscontrol -i | grep -i 'EnableXMLContextCaching' ( to find the label number of
a particular tag in dbs)
13.create table t3 as t1 with data or with no data; copying table with data
14.search for a string in a directory in linux
grep -Ril "text-to-find-here" /

i stands for ignore case (optional in your case).

R stands for recursive.

l stands for "show the file name, not the result itself".

/ stands for starting at the root of your machine.

15.To ignore expected mis matches add the following statement before the
query

a. /*PTE IGNORE RESPONSE*/

b. /*PTE IGNORE COLUMN SamplePct*/
c. /*PTE IGNORE COLUMN 1,2,3*/
16.TLE related drs must be added under TLEON statement in FILELIST.
17.Temporal related DRs must be promoted to temporal test suite only
18.m i =t to enable display of internal flags
19.h i for help of internal flags

ALTER INDEX
20. We generally come across a need to change/alter the index to address storage in AMPs/data
fecth(SQL Performance) issues in any database.
In teradata, we cannot alter a primary index once it is created and the data is loaded into that
table. So, to alter primary index, we would need another copy of the original table and then drop
the actual table and recreate with required primary index.
OR
Delete the data in the original table (If needed take the back up first). And use below statement to
alter the index.
In general the syntax for altering an index is:
alter table <Table_Name> modify
primary index Index_Name(Inde_Col1, ..Index_columnn);

21.upgrade_td_efix -cibt 15.10.03i.79 td15.10.3 -sysinit force

a. to upgrade or downgrade a build on TD15.10 or TD15.00 machines
b. command efix buildnumber build_source-sysinit --force