Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 12 Feb 2008 @ 20:32:21 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: Problem installing VC++ with Demo Version
 
From:   Vinay Bagare

Srinivas,

Jeff Casher (Teradata) with a very good writeup for fixing this. Straight from my archives.

Follow the steps as they are, you should be out of woods soon.

Step 1 : Install Microsoft .NET Framework 1.1 Redistributable (exe, 4/9/03, 24MB) (dotnetfx11.exe)

Step 2: Then install Microsoft .NET Framework 1.1 Software Development Kit (exe, 4/9/03, 109MB) (dotnetsdk11.exe)

Step 3: Then execute Registry Update for V2R5.1 for Windows 2000 (reg, 1/9/04, 1KB)

Or execute Registry Update for V2R5.1 for Windows XP (reg, 9/9/04, 1KB)

Step 4: Also, copy C:\Program Files\Microsoft.NET\SDK\v1.1\Bin\nmake.exe to C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\.

Step 5: Also, enter following in a Teradata Command Prompt window:

     cd \Program Files\NCR\Tdat\LTDBMS\bin
     cufconfig -i
     Cufconfig -o

Here is the content of the Windows Registry fix. It is in a file with type of .reg. Paste it in, save, double-click and it puts the entries in your registry. While it says for 5.1, these entries are needed for 6.1. Look at the registry and see if the .net install made the entries. If not, do the .reg update:

Step 6: Windows Registry Editor Version 5.00

     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1]
     "InstallDir"="C:\Program Files\Microsoft Visual Studio .NET
     2003\Common7\\IDE\"

     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\Setup\VC]
     "ProductDir"="C:\Program Files\Microsoft Visual Studio .NET2003\Vc7\"

Step 7: After the reg update, it is important to do the cufconfig command to get the database to know that you installed the compiler. Ther first cufconfig does the configuration. The second one shows the output. Output might look something like this:

     _______
         |                                |              |
         |    ___     __     ____         |    ____    __|__    ____
         |   /      |/  \    ____|    ____|    ____|     |      ____|
         |   ---    |       /    |   /    |   /    |     |     /    |
         |   \___   |       \____|   \____|   \____|     |__   \____|

         Release V2R.06.02.01.08 Version 06.02.01.11 
         UDF GDO Configuration Utility (Mar 2005)


     Version: 4
     ModTime: 1185566741
     SWDistNodeID: 33
     SourceDirectoryPath: C:\Program
     Files\NCR\TDAT\tdconfig\Teradata\tdbs_udf\usr\
     CompilerTempDirectory: C:\Program Files\NCR\TDAT\TdTemp\UDFTemp\
     UDFLibraryPath: C:\Program Files\NCR\TDAT\tdconfig\udflib\
     CompilerPath: C:\Program Files (x86)\Microsoft Visual Studio
     8\VC\bin\amd64\CL.EXE  (NOTE: This was from a 64bit so )
     LinkerPath: C:\Program Files (x86)\Microsoft Visual Studio
     8\VC\bin\amd64\LINK.EXE  (      names are different     )
     UDFServerMemPath: C:\Program Files\NCR\TDAT\TdTemp\udfsrv\
     MaximumCompilations: 10
     UDFServerTasks: 2
     SecureServerAMPs: 20
     ParallelUserServerAMPs: 2
     SecureServerPEs: 20
     ParallelUserServerPEs: 2
     TDSPLibBase: C:\Program Files\NCR\TDAT\tdconfig\tdsplib\
     SecureGroupMembership: tdatudf

Your names will be different since the above was from a 64bit install. What you are looking for is to see that the compiler path and the linker path are filled in. If they are NOT filled in, then you don't have a compiler.

Step 8: After you have done all of this, SHUTDOWN and RESTART the database. I think it is during the startup that it recognizes things...jpc


Thanks,

Vinay Bagare



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 23 Jun 2019