How to use UDL file in Powershell script?

Question

Hello Scripting Guys,
I have a VBScript that works great for connecting to an Oracle DB using a .UDL file. Here is the important part of the script:
Set dataconnect = CreateObject("ADODB.Connection")
Path= "File name=C:\UDLs\TEST.udl"
dataconnect.ConnectionString = Path
dataconnect.open
Set oCmd = CreateObject("ADODB.Command")
oCmd.ActiveConnection = dataconnect
oCmd.CommandText = "SYSTEM.JOB.INSERT_JOB"
oCmd.CommandType = 4
set oParam = oCmd.CreateParameter("job_name_val")
oParam.type = 200
oParam.direction = 1
oParam.size = 255
oParam.value = job_name
oCmd.Parameters.Append oParam
set oParam = oCmd.CreateParameter("description")
oParam.type = 200
oParam.direction = 1
oParam.size = 4000
oParam.value = descrip
oCmd.Parameters.Append oParam
set oParam = oCmd.CreateParameter("status_val")
oParam.type = 200
oParam.direction = 1
oParam.size = 50
oParam.value = status
oCmd.Parameters.Append oParam
oCmd.Execute
As you can see, it creates "ADODB.Connection" and "ADODB.Command" objects. Everything works as intended here.
Now, I'm trying to convert this VBScript to a Powershell script.
Here's what I have so far with my PowerShell Script (non-working, but no errors):
$job_name = $args[0]
$status = $args[1]
$descrip = $args[2]
write-host "Job Name = " $job_name
write-host "Status = " $status
write-host "Description = " $descrip
#Create an object of type: ADODB class: Connection
$objConn = New-Object -com "ADODB.Connection"
#Create Connection String
$connString = "File name=C:\UDLs\TEST.udl"
#Open the connection
$objConn.open($connString)
#Command Object
$oCmd = New-Object -com "ADODB.Command"
#Assign DB connection To Command
$oCmd.ActiveConnection = $objConn
#Set Command text
$oCmd.CommandText = "SYSTEM.JOB.INSERT_JOB"
#Set Command Type
$oCmd.CommandType = 4
#Create parameter list For Command
#Job name Parameter
$oParam1 = $oCmd.CreateParameter("job_name_val")
$oParam1.type = 200
$oParam1.direction = 1
$oParam1.size = 255
$oParam1.value = $job_name
#Append parameter list
$oCmd.Parameters.Append($oParam1)
#Description Parameter
$oParam2 = $oCmd.CreateParameter("description")
$oParam2.type = 200
$oParam2.direction = 1
$oParam2.size = 4000
$oParam2.value = $descrip
#Append parameter list
$oCmd.Parameters.Append($oParam2)
#Status Parameter
$oParam3 = $oCmd.CreateParameter("status_val")
$oParam3.type = 200
$oParam3.direction = 1
$oParam3.size = 50
$oParam3.value = $status
#Append parameter list
$oCmd.Parameters.Append($oParam3)
#Command Execution
$oCmdX = $oCmd.Execute
write-host $oCmdX
#Cleanup
#Set parameters = To NULL
$oParam1 = $null
$oParam2 = $null
$oParam3 = $null
#Set Command = To NULL
$oCmd = $null
#Close DB object
$objConn.Close()
So, not too many changes with the syntax, but it doesn't actually send the ADODB Command to the Database. I have also tried hardcoding the connection string, but no luck there either. Am I not using the right syntax with the Command object? I am fairly new
to both of these languages, so I appreciate any help/suggestions you can offer!
Thank you,
Brian

Answer 1

Thanks JRV.
I am now getting this error (at least some feedback from Powershell now):
Exception calling "Open" with "1" argument(s): "[Microsoft][ODBC Driver Manager
] Data source name not found and no default driver specified"
At C:\temp\JobMon.ps1:21 char:14
+ $objConn.open <<<< ($connString)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
The thing is, it shouldn't be using a Microsoft driver. It should be using the Oracle Client driver (which I have installed and tested successfully using TNSPing).
Do I need to declare some sort of "using System.Data.OracleClient namespace" like in C++? How would I do that in Powershell?
Thanks again,
Brian