Good morning, my first post here.  In attempting to use OPTIM 11.3 against a SQL Server 2012 database for Archive purposes, an error is being received.
I have checked the ODBC connection and I get a successful connection.  The DBAlias creates without any issues.  The archive job and the access definition create without issues.  The access definition is able to find the database and the tables needed for archiving.

The issue comes up when attempting to execute the archive.
The error is:
The Connect String was not found.
Message: ODBC SQL State: IM002 Data Source name not found and no default driver specified.

The ODBC connection was reverified, the DBAlias was recreated successfully.  
The names of the ODBC connection and the DBAlias are equivalent.

Thank you for any assistance you can provide.

Doug.

------------------------------
Douglas Platz
------------------------------

Jimmy, thank you for your reply.

Here are answers to your questions.
1.  The process is being executed from OPTIM on Windows ver 11.3.  This is the same tool as used to develop the AD and service.  It is the same server where the ODBC was created.

2. The DBAlias has been defined and appears to be working correctly.  When creating the AD and even now reviewing the AD, the tables are shown as "known" in the AD.

3. At your suggestion, I did look at the temp directory, however, I'm not sure exactly what to look for, or how to read the file as I am quite new to the midrange world of OPTIM.

as stated in my original post, the ODBC and DBAlias were verified and rebuilt without success of the process.

Thank you for your assistance.

------------------------------
Douglas Platz
------------------------------

Original Message:
Sent: Wed April 05, 2023 09:56 AM
From: Jimmy Wilson
Subject: ODBC connection issue

Doug,

I don't have an answer to your issue but I'll try to ask questions that may help find it.

1.  How are you executing the archive process?  Is it using the same tool used to develop the AD and service?  If not, does the ODBC connection exist where it is executed?

2.  Are you executing as an Optim Server process?  Does that have the appropriate DBAlias defined?

3.  Have you looked in the temp directory at the log file associated with the execution?  That could lead to more information.

I hope that helps.

--

Jimmy Wilson

1999 S. Bascom Ste 700

Campbell, CA 95008

Phone +1(972) 567-5558

jwilson@abmartin.com

 

Unstructured Data Masking

Data Privacy/Test data Management - fabrication, optimization, obfuscation

Original Message:
Sent: 4/14/2023 7:13:00 AM
From: Douglas Platz
Subject: RE: ODBC connection issue

Jimmy, thank you for your reply.

Here are answers to your questions.
1.  The process is being executed from OPTIM on Windows ver 11.3.  This is the same tool as used to develop the AD and service.  It is the same server where the ODBC was created.

2. The DBAlias has been defined and appears to be working correctly.  When creating the AD and even now reviewing the AD, the tables are shown as "known" in the AD.

3. At your suggestion, I did look at the temp directory, however, I'm not sure exactly what to look for, or how to read the file as I am quite new to the midrange world of OPTIM.

as stated in my original post, the ODBC and DBAlias were verified and rebuilt without success of the process.

Thank you for your assistance.

------------------------------
Douglas Platz
------------------------------

We have that issue every time we create a new DBALIAS and forget to include that logon info on the server

Sent from my iPhone


Original Message:
Sent: 4/14/2023 7:13:00 AM
From: Douglas Platz
Subject: RE: ODBC connection issue

Jimmy, thank you for your reply.

Here are answers to your questions.
1.  The process is being executed from OPTIM on Windows ver 11.3.  This is the same tool as used to develop the AD and service.  It is the same server where the ODBC was created.

2. The DBAlias has been defined and appears to be working correctly.  When creating the AD and even now reviewing the AD, the tables are shown as "known" in the AD.

3. At your suggestion, I did look at the temp directory, however, I'm not sure exactly what to look for, or how to read the file as I am quite new to the midrange world of OPTIM.

as stated in my original post, the ODBC and DBAlias were verified and rebuilt without success of the process.

Thank you for your assistance.

------------------------------
Douglas Platz
------------------------------