Okay, I've made some progress. Apparently the reason the first step was failing was that the very first statement in initDB.bteq didn't allow for versions past V2R6:
SELECT * FROM dbc.dbcinfo WHERE infokey = 'VERSION' AND
(index (infodata,'06.01.00' ) > 0
OR index (infodata,'06.01.01' ) > 0
OR index (infodata,'06.02') > 0
);
So I changed it to this:
SELECT * FROM dbc.dbcinfo WHERE infokey = 'VERSION' AND
(index (infodata,'06.01.00' ) > 0
OR index (infodata,'06.01.01' ) > 0
OR index (infodata,'06.02') > 0
OR index (infodata,'14.00') > 0
);
[Or, possibly better: ... OR substr(infodata, 1,2) >= '12']
A few steps later, I had to copy the code libraries by hand from the Windows host to the TD Express machine (not sure why). Then the script started creating the procedures and functions. All was well, another day saved, until this happened (selected lines from command window):
Install register succeed.
Install register_u succeed.
Install normal XML supported UDFs succeed.
Install publish XML supported UDFs succeed.
Install shred XML supported UDFs succeed.
2012-12-6 15:31:32 install XML Services UDFs without Unicode support finished succeed.
Construction ,Processing Verify succeed.
Publish Verify failed. Please check the log at <C:/Users/Geoffrey/Documents/VM_Shared/TeradataXML_LINUX_v13.10.00.01/TeradataXML_LINUX_v13.10.00.01/log/verify_publish.out> for details.
Error.out now contains this cryptic message:
S E L ' F U N C T I O N R E P L A C E D S U C C E S S F U L L Y # # X M L N O R M A L I Z E _ V C _ U ' ;
$
* * * F a i l u r e 3 7 0 6 S y n t a x e r r o r : e x p e c t e d s o m e t h i n g b e t w e e n t h e b e g i n n i n g o f
t h e r e q u e s t a n d ' . ' .
S t a t e m e n t # 2 , I n f o = 3
S E L ' F U N C T I O N R E P L A C E D F A I L U R E # # X M L N O R M A L I Z E _ V C _ U ' ;
$
* * * F a i l u r e 3 7 0 6 S y n t a x e r r o r : e x p e c t e d s o m e t h i n g b e t w e e n t h e b e g i n n i n g o f
t h e r e q u e s t a n d ' . ' .
S t a t e m e n t # 2 , I n f o = 3
S E L ' F U N C T I O N R E P L A C E D S U C C E S S F U L L Y # # X M L N O R M A L I Z E _ L O B _ U ' ;
$
* * * F a i l u r e 3 7 0 6 S y n t a x e r r o r : e x p e c t e d s o m e t h i n g b e t w e e n t h e b e g i n n i n g o f
t h e r e q u e s t a n d ' . ' .
S t a t e m e n t # 2 , I n f o = 3
S E L ' F U N C T I O N R E P L A C E D F A I L U R E # # X M L N O R M A L I Z E _ L O B _ U ' ;
$
* * * F a i l u r e 3 7 0 6 S y n t a x e r r o r : e x p e c t e d s o m e t h i n g b e t w e e n t h e b e g i n n i n g o f
t h e r e q u e s t a n d ' . ' .
S t a t e m e n t # 2 , I n f o = 3
*** Failure 7504 in UDF/XSP/UDM SYSXML.PUBLISH: SQLSTATE U0035: cli init error!errorcode: 224, errorstring:Logon failed!
Statement# 1, Info =0
"Logon failed"?? What is going on here?
Since I'm really interested only in shredding, maybe I can just give up at this point and use the shredding functions, but if anyone can diagnose or, better yet, fix the problem, it would be appreciated.
Sorry to complain, but the installation procedure seems awfully touchy.
↧