Using linked servers in SQL 2000 for some reason changes the commit mode
when doing an INSERT or UPDATE. That means that journaling needs to be
active on the tables that I am access on the 400. The 400 people have
said no. If I do a straight ODBC connection, not through linked
servers, everything works flawlessly.
From SQL server, what is the best means of utilizing ODBC to issue an
INSERT to our 400 WITHOUT using Linked Servers?
DTS works, but doesnt seem to be the answer. Is it possible to open an
ODBC connection in a stored procedure?
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!See "Openrowset" in Books Online.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Will that type of connection support distributed transactions (commit, rollb
ack)?
Showing posts with label as400. Show all posts
Showing posts with label as400. Show all posts
Sunday, March 11, 2012
connecting to AS400
Hi,
I am trying to transfer information from the AS400 to SQL Server tables but I am having problems trying to connect and get information from the AS400. In the data source I select the iseries connection and type in the ip address, username, and password. When I click the test connection button, it connects but under the initial catalog all I get is the computer name. If anyone has any solutions to my problem that would be great
Thnaks
Brian
I have had success connecting to the AS/400 only with an ADO Data Reader (could not use an OLE DB Source) using the IBMDA400 Provider (connections string included below). You must also explicitly specify libraries in your select statements, and not rely on library list.
Sample connection string:
Data Source=server;User ID=uid;Provider=IBMDA400.DataSource.1;Persist Security Info=False;Connect Timeout=300;Catalog Library List=library1, library2;
Connecting to AS 400
Hi,
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
Connecting to AS 400
Hi,
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.
Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
How can I connect to AS400 from SQL Server 2000.
Client prefers NO DSN.
Thanks
Vijay
I will persist till I win.
Install Client Access on the SQL Server box and then
configure the linked server as described in books online
under Linked Servers, configuring.
For data source, use the IP address of the AS400. For
provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Thu, 22 Jul 2004 09:50:56 -0700, "Vijay"
<Vijay@.discussions.microsoft.com> wrote:
>Hi,
> How can I connect to AS400 from SQL Server 2000.
>Client prefers NO DSN.
>Thanks
>Vijay
>I will persist till I win.
Friday, February 17, 2012
connecting AS400
hi all,
we are running a dts that migrates data from an as400 to sql 2K.
the string data is hebrew (code page 1252).
for that, we have been using a hit odbc:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
untill now we were running the dts from sql 7.0 and that worked well.
the porblem started after copying (and then rewriting) the package to sql 2k
:
when running the dts manually (execute package) it's o.k, but when running
the dts via a job the hebrew characters are being mirrored in the sql 2k.
(e.g, written from left to write instead of right to left).
again, in sql 7 it worked well both ways.
some details:
-in both cases (job and manually) we execute the package from the same serve
r.
-the win login account used for manual executing is identical to the log on
accounts of server service and server agent.
we are using a system dsn.
I have found in a newsgroup a tip to solve that: using a user dsn.
but when I tried that another porblem came up:
when running manualy - it was, again, ok
but when running via a job (or with dtsrun) the server couldn't find the odb
c.
here is the error massage:
DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_2DTSRun OnStart: DTSStep_DTSDataPumpTask_1DTSRun
OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Driver Manager] Data source name not found
and no
default driver specified Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0Error Detail Records:Error:
-2147467259 (80004005); Provider Error: 0 (0) Error string: Error
source: Help file: Help context: 0DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
so.. any help will be usefull (regarding the hebrew mirroring or regarding
finding the user dsn)
thanks,
elad.Elad, shalom
I assume you got connected by using Client Access to the AS400.
Look , first of all it depends on lot of things
1) Right click on the server within a package and press "Advance" button.
Under Property name you will find Auto Translate=1 or =0. Try to play with
it.
" " <@.discussions.microsoft.com> wrote in message
news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> hi all,
> we are running a dts that migrates data from an as400 to sql 2K.
> the string data is hebrew (code page 1252).
> for that, we have been using a hit odbc:
> ODBC OPTIMIZED (READ ONLY) 32 BIT
> VERSION 4.00.06.20
> HIT SOFTWARE, INC
> untill now we were running the dts from sql 7.0 and that worked well.
> the porblem started after copying (and then rewriting) the package to sql
> 2k:
> when running the dts manually (execute package) it's o.k, but when running
> the dts via a job the hebrew characters are being mirrored in the sql 2k.
> (e.g, written from left to write instead of right to left).
> again, in sql 7 it worked well both ways.
> some details:
> -in both cases (job and manually) we execute the package from the same
> server.
> -the win login account used for manual executing is identical to the log
> on
> accounts of server service and server agent.
> we are using a system dsn.
> I have found in a newsgroup a tip to solve that: using a user dsn.
> but when I tried that another porblem came up:
> when running manualy - it was, again, ok
> but when running via a job (or with dtsrun) the server couldn't find the
> odbc.
> here is the error massage:
> DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1DTSRun
> OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> Error
> string: [Microsoft][ODBC Driver Manager] Data source name not fou
nd and
> no
> default driver specified Error source: Microsoft OLE DB Provider for
> ODBC
> Drivers Help file: Help context: 0Error Detail Records:Error:
> -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> source: Help file: Help context: 0DTSRun OnFinish:
> DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> so.. any help will be usefull (regarding the hebrew mirroring or regarding
> finding the user dsn)
> thanks,
> elad.
>
>
>
>|||hi Uri,
well, I used the HIT odbc for as400.
here are it's details again:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
and, for that odbc I couldn't find a auto translate property.
I also looked for a download of the client access odbc but couldn't find it.
so... I will thakfull for a link
thanks,
elad.
"Uri Dimant" wrote:
> Elad, shalom
> I assume you got connected by using Client Access to the AS400.
> Look , first of all it depends on lot of things
> 1) Right click on the server within a package and press "Advance" button.
> Under Property name you will find Auto Translate=1 or =0. Try to play with
> it.
>
>
> "_ìò? ùì?_" <@.discussions.microsoft.com> wrote in message
> news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
>
>
we are running a dts that migrates data from an as400 to sql 2K.
the string data is hebrew (code page 1252).
for that, we have been using a hit odbc:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
untill now we were running the dts from sql 7.0 and that worked well.
the porblem started after copying (and then rewriting) the package to sql 2k
:
when running the dts manually (execute package) it's o.k, but when running
the dts via a job the hebrew characters are being mirrored in the sql 2k.
(e.g, written from left to write instead of right to left).
again, in sql 7 it worked well both ways.
some details:
-in both cases (job and manually) we execute the package from the same serve
r.
-the win login account used for manual executing is identical to the log on
accounts of server service and server agent.
we are using a system dsn.
I have found in a newsgroup a tip to solve that: using a user dsn.
but when I tried that another porblem came up:
when running manualy - it was, again, ok
but when running via a job (or with dtsrun) the server couldn't find the odb
c.
here is the error massage:
DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_2DTSRun OnStart: DTSStep_DTSDataPumpTask_1DTSRun
OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Driver Manager] Data source name not found
and no
default driver specified Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0Error Detail Records:Error:
-2147467259 (80004005); Provider Error: 0 (0) Error string: Error
source: Help file: Help context: 0DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
so.. any help will be usefull (regarding the hebrew mirroring or regarding
finding the user dsn)
thanks,
elad.Elad, shalom
I assume you got connected by using Client Access to the AS400.
Look , first of all it depends on lot of things
1) Right click on the server within a package and press "Advance" button.
Under Property name you will find Auto Translate=1 or =0. Try to play with
it.
" " <@.discussions.microsoft.com> wrote in message
news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> hi all,
> we are running a dts that migrates data from an as400 to sql 2K.
> the string data is hebrew (code page 1252).
> for that, we have been using a hit odbc:
> ODBC OPTIMIZED (READ ONLY) 32 BIT
> VERSION 4.00.06.20
> HIT SOFTWARE, INC
> untill now we were running the dts from sql 7.0 and that worked well.
> the porblem started after copying (and then rewriting) the package to sql
> 2k:
> when running the dts manually (execute package) it's o.k, but when running
> the dts via a job the hebrew characters are being mirrored in the sql 2k.
> (e.g, written from left to write instead of right to left).
> again, in sql 7 it worked well both ways.
> some details:
> -in both cases (job and manually) we execute the package from the same
> server.
> -the win login account used for manual executing is identical to the log
> on
> accounts of server service and server agent.
> we are using a system dsn.
> I have found in a newsgroup a tip to solve that: using a user dsn.
> but when I tried that another porblem came up:
> when running manualy - it was, again, ok
> but when running via a job (or with dtsrun) the server couldn't find the
> odbc.
> here is the error massage:
> DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1DTSRun
> OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> Error
> string: [Microsoft][ODBC Driver Manager] Data source name not fou
nd and
> no
> default driver specified Error source: Microsoft OLE DB Provider for
> ODBC
> Drivers Help file: Help context: 0Error Detail Records:Error:
> -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> source: Help file: Help context: 0DTSRun OnFinish:
> DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> so.. any help will be usefull (regarding the hebrew mirroring or regarding
> finding the user dsn)
> thanks,
> elad.
>
>
>
>|||hi Uri,
well, I used the HIT odbc for as400.
here are it's details again:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
and, for that odbc I couldn't find a auto translate property.
I also looked for a download of the client access odbc but couldn't find it.
so... I will thakfull for a link
thanks,
elad.
"Uri Dimant" wrote:
> Elad, shalom
> I assume you got connected by using Client Access to the AS400.
> Look , first of all it depends on lot of things
> 1) Right click on the server within a package and press "Advance" button.
> Under Property name you will find Auto Translate=1 or =0. Try to play with
> it.
>
>
> "_ìò? ùì?_" <@.discussions.microsoft.com> wrote in message
> news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
>
>
connecting AS400
hi all,
we are running a dts that migrates data from an as400 to sql 2K.
the string data is hebrew (code page 1252).
for that, we have been using a hit odbc:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
untill now we were running the dts from sql 7.0 and that worked well.
the porblem started after copying (and then rewriting) the package to sql 2k:
when running the dts manually (execute package) it's o.k, but when running
the dts via a job the hebrew characters are being mirrored in the sql 2k.
(e.g, written from left to write instead of right to left).
again, in sql 7 it worked well both ways.
some details:
-in both cases (job and manually) we execute the package from the same server.
-the win login account used for manual executing is identical to the log on
accounts of server service and server agent.
we are using a system dsn.
I have found in a newsgroup a tip to solve that: using a user dsn.
but when I tried that another porblem came up:
when running manualy - it was, again, ok
but when running via a job (or with dtsrun) the server couldn't find the odbc.
here is the error massage:
DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_2DTSRun OnStart: DTSStep_DTSDataPumpTask_1DTSRun
OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0Error Detail Records:Error:
-2147467259 (80004005); Provider Error: 0 (0) Error string: Error
source: Help file: Help context: 0DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
so.. any help will be usefull (regarding the hebrew mirroring or regarding
finding the user dsn)
thanks,
elad.Elad, shalom
I assume you got connected by using Client Access to the AS400.
Look , first of all it depends on lot of things
1) Right click on the server within a package and press "Advance" button.
Under Property name you will find Auto Translate=1 or =0. Try to play with
it.
"àìòã ùìåí" <@.discussions.microsoft.com> wrote in message
news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> hi all,
> we are running a dts that migrates data from an as400 to sql 2K.
> the string data is hebrew (code page 1252).
> for that, we have been using a hit odbc:
> ODBC OPTIMIZED (READ ONLY) 32 BIT
> VERSION 4.00.06.20
> HIT SOFTWARE, INC
> untill now we were running the dts from sql 7.0 and that worked well.
> the porblem started after copying (and then rewriting) the package to sql
> 2k:
> when running the dts manually (execute package) it's o.k, but when running
> the dts via a job the hebrew characters are being mirrored in the sql 2k.
> (e.g, written from left to write instead of right to left).
> again, in sql 7 it worked well both ways.
> some details:
> -in both cases (job and manually) we execute the package from the same
> server.
> -the win login account used for manual executing is identical to the log
> on
> accounts of server service and server agent.
> we are using a system dsn.
> I have found in a newsgroup a tip to solve that: using a user dsn.
> but when I tried that another porblem came up:
> when running manualy - it was, again, ok
> but when running via a job (or with dtsrun) the server couldn't find the
> odbc.
> here is the error massage:
> DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1DTSRun
> OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> Error
> string: [Microsoft][ODBC Driver Manager] Data source name not found and
> no
> default driver specified Error source: Microsoft OLE DB Provider for
> ODBC
> Drivers Help file: Help context: 0Error Detail Records:Error:
> -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> source: Help file: Help context: 0DTSRun OnFinish:
> DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> so.. any help will be usefull (regarding the hebrew mirroring or regarding
> finding the user dsn)
> thanks,
> elad.
>
>
>
>|||hi Uri,
well, I used the HIT odbc for as400.
here are it's details again:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
and, for that odbc I couldn't find a auto translate property.
I also looked for a download of the client access odbc but couldn't find it.
so... I will thakfull for a link
thanks,
elad.
"Uri Dimant" wrote:
> Elad, shalom
> I assume you got connected by using Client Access to the AS400.
> Look , first of all it depends on lot of things
> 1) Right click on the server within a package and press "Advance" button.
> Under Property name you will find Auto Translate=1 or =0. Try to play with
> it.
>
>
> "à ìòã ùìåÃ" <@.discussions.microsoft.com> wrote in message
> news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> > hi all,
> > we are running a dts that migrates data from an as400 to sql 2K.
> > the string data is hebrew (code page 1252).
> > for that, we have been using a hit odbc:
> > ODBC OPTIMIZED (READ ONLY) 32 BIT
> > VERSION 4.00.06.20
> > HIT SOFTWARE, INC
> >
> > untill now we were running the dts from sql 7.0 and that worked well.
> > the porblem started after copying (and then rewriting) the package to sql
> > 2k:
> > when running the dts manually (execute package) it's o.k, but when running
> > the dts via a job the hebrew characters are being mirrored in the sql 2k.
> > (e.g, written from left to write instead of right to left).
> > again, in sql 7 it worked well both ways.
> >
> > some details:
> > -in both cases (job and manually) we execute the package from the same
> > server.
> > -the win login account used for manual executing is identical to the log
> > on
> > accounts of server service and server agent.
> > we are using a system dsn.
> >
> > I have found in a newsgroup a tip to solve that: using a user dsn.
> > but when I tried that another porblem came up:
> > when running manualy - it was, again, ok
> > but when running via a job (or with dtsrun) the server couldn't find the
> > odbc.
> > here is the error massage:
> >
> > DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> > DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> > DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> > DTSStep_DTSDataPumpTask_1DTSRun
> > OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> > Error
> > string: [Microsoft][ODBC Driver Manager] Data source name not found and
> > no
> > default driver specified Error source: Microsoft OLE DB Provider for
> > ODBC
> > Drivers Help file: Help context: 0Error Detail Records:Error:
> > -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> > source: Help file: Help context: 0DTSRun OnFinish:
> > DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> >
> > so.. any help will be usefull (regarding the hebrew mirroring or regarding
> > finding the user dsn)
> >
> > thanks,
> > elad.
> >
> >
> >
> >
> >
> >
> >
>
>
we are running a dts that migrates data from an as400 to sql 2K.
the string data is hebrew (code page 1252).
for that, we have been using a hit odbc:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
untill now we were running the dts from sql 7.0 and that worked well.
the porblem started after copying (and then rewriting) the package to sql 2k:
when running the dts manually (execute package) it's o.k, but when running
the dts via a job the hebrew characters are being mirrored in the sql 2k.
(e.g, written from left to write instead of right to left).
again, in sql 7 it worked well both ways.
some details:
-in both cases (job and manually) we execute the package from the same server.
-the win login account used for manual executing is identical to the log on
accounts of server service and server agent.
we are using a system dsn.
I have found in a newsgroup a tip to solve that: using a user dsn.
but when I tried that another porblem came up:
when running manualy - it was, again, ok
but when running via a job (or with dtsrun) the server couldn't find the odbc.
here is the error massage:
DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_2DTSRun OnStart: DTSStep_DTSDataPumpTask_1DTSRun
OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0Error Detail Records:Error:
-2147467259 (80004005); Provider Error: 0 (0) Error string: Error
source: Help file: Help context: 0DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
so.. any help will be usefull (regarding the hebrew mirroring or regarding
finding the user dsn)
thanks,
elad.Elad, shalom
I assume you got connected by using Client Access to the AS400.
Look , first of all it depends on lot of things
1) Right click on the server within a package and press "Advance" button.
Under Property name you will find Auto Translate=1 or =0. Try to play with
it.
"àìòã ùìåí" <@.discussions.microsoft.com> wrote in message
news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> hi all,
> we are running a dts that migrates data from an as400 to sql 2K.
> the string data is hebrew (code page 1252).
> for that, we have been using a hit odbc:
> ODBC OPTIMIZED (READ ONLY) 32 BIT
> VERSION 4.00.06.20
> HIT SOFTWARE, INC
> untill now we were running the dts from sql 7.0 and that worked well.
> the porblem started after copying (and then rewriting) the package to sql
> 2k:
> when running the dts manually (execute package) it's o.k, but when running
> the dts via a job the hebrew characters are being mirrored in the sql 2k.
> (e.g, written from left to write instead of right to left).
> again, in sql 7 it worked well both ways.
> some details:
> -in both cases (job and manually) we execute the package from the same
> server.
> -the win login account used for manual executing is identical to the log
> on
> accounts of server service and server agent.
> we are using a system dsn.
> I have found in a newsgroup a tip to solve that: using a user dsn.
> but when I tried that another porblem came up:
> when running manualy - it was, again, ok
> but when running via a job (or with dtsrun) the server couldn't find the
> odbc.
> here is the error massage:
> DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1DTSRun
> OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> Error
> string: [Microsoft][ODBC Driver Manager] Data source name not found and
> no
> default driver specified Error source: Microsoft OLE DB Provider for
> ODBC
> Drivers Help file: Help context: 0Error Detail Records:Error:
> -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> source: Help file: Help context: 0DTSRun OnFinish:
> DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> so.. any help will be usefull (regarding the hebrew mirroring or regarding
> finding the user dsn)
> thanks,
> elad.
>
>
>
>|||hi Uri,
well, I used the HIT odbc for as400.
here are it's details again:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
and, for that odbc I couldn't find a auto translate property.
I also looked for a download of the client access odbc but couldn't find it.
so... I will thakfull for a link
thanks,
elad.
"Uri Dimant" wrote:
> Elad, shalom
> I assume you got connected by using Client Access to the AS400.
> Look , first of all it depends on lot of things
> 1) Right click on the server within a package and press "Advance" button.
> Under Property name you will find Auto Translate=1 or =0. Try to play with
> it.
>
>
> "à ìòã ùìåÃ" <@.discussions.microsoft.com> wrote in message
> news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> > hi all,
> > we are running a dts that migrates data from an as400 to sql 2K.
> > the string data is hebrew (code page 1252).
> > for that, we have been using a hit odbc:
> > ODBC OPTIMIZED (READ ONLY) 32 BIT
> > VERSION 4.00.06.20
> > HIT SOFTWARE, INC
> >
> > untill now we were running the dts from sql 7.0 and that worked well.
> > the porblem started after copying (and then rewriting) the package to sql
> > 2k:
> > when running the dts manually (execute package) it's o.k, but when running
> > the dts via a job the hebrew characters are being mirrored in the sql 2k.
> > (e.g, written from left to write instead of right to left).
> > again, in sql 7 it worked well both ways.
> >
> > some details:
> > -in both cases (job and manually) we execute the package from the same
> > server.
> > -the win login account used for manual executing is identical to the log
> > on
> > accounts of server service and server agent.
> > we are using a system dsn.
> >
> > I have found in a newsgroup a tip to solve that: using a user dsn.
> > but when I tried that another porblem came up:
> > when running manualy - it was, again, ok
> > but when running via a job (or with dtsrun) the server couldn't find the
> > odbc.
> > here is the error massage:
> >
> > DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> > DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> > DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> > DTSStep_DTSDataPumpTask_1DTSRun
> > OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> > Error
> > string: [Microsoft][ODBC Driver Manager] Data source name not found and
> > no
> > default driver specified Error source: Microsoft OLE DB Provider for
> > ODBC
> > Drivers Help file: Help context: 0Error Detail Records:Error:
> > -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> > source: Help file: Help context: 0DTSRun OnFinish:
> > DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> >
> > so.. any help will be usefull (regarding the hebrew mirroring or regarding
> > finding the user dsn)
> >
> > thanks,
> > elad.
> >
> >
> >
> >
> >
> >
> >
>
>
connecting AS400
hi all,
we are running a dts that migrates data from an as400 to sql 2K.
the string data is hebrew (code page 1252).
for that, we have been using a hit odbc:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
untill now we were running the dts from sql 7.0 and that worked well.
the porblem started after copying (and then rewriting) the package to sql 2k:
when running the dts manually (execute package) it's o.k, but when running
the dts via a job the hebrew characters are being mirrored in the sql 2k.
(e.g, written from left to write instead of right to left).
again, in sql 7 it worked well both ways.
some details:
-in both cases (job and manually) we execute the package from the same server.
-the win login account used for manual executing is identical to the log on
accounts of server service and server agent.
we are using a system dsn.
I have found in a newsgroup a tip to solve that: using a user dsn.
but when I tried that another porblem came up:
when running manualy - it was, again, ok
but when running via a job (or with dtsrun) the server couldn't find the odbc.
here is the error massage:
DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_2DTSRun OnStart: DTSStep_DTSDataPumpTask_1DTSRun
OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0Error Detail Records:Error:
-2147467259 (80004005); Provider Error: 0 (0) Error string: Error
source: Help file: Help context: 0DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
so.. any help will be usefull (regarding the hebrew mirroring or regarding
finding the user dsn)
thanks,
elad.
Elad, shalom
I assume you got connected by using Client Access to the AS400.
Look , first of all it depends on lot of things
1) Right click on the server within a package and press "Advance" button.
Under Property name you will find Auto Translate=1 or =0. Try to play with
it.
" " <@.discussions.microsoft.com> wrote in message
news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> hi all,
> we are running a dts that migrates data from an as400 to sql 2K.
> the string data is hebrew (code page 1252).
> for that, we have been using a hit odbc:
> ODBC OPTIMIZED (READ ONLY) 32 BIT
> VERSION 4.00.06.20
> HIT SOFTWARE, INC
> untill now we were running the dts from sql 7.0 and that worked well.
> the porblem started after copying (and then rewriting) the package to sql
> 2k:
> when running the dts manually (execute package) it's o.k, but when running
> the dts via a job the hebrew characters are being mirrored in the sql 2k.
> (e.g, written from left to write instead of right to left).
> again, in sql 7 it worked well both ways.
> some details:
> -in both cases (job and manually) we execute the package from the same
> server.
> -the win login account used for manual executing is identical to the log
> on
> accounts of server service and server agent.
> we are using a system dsn.
> I have found in a newsgroup a tip to solve that: using a user dsn.
> but when I tried that another porblem came up:
> when running manualy - it was, again, ok
> but when running via a job (or with dtsrun) the server couldn't find the
> odbc.
> here is the error massage:
> DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1DTSRun
> OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> Error
> string: [Microsoft][ODBC Driver Manager] Data source name not found and
> no
> default driver specified Error source: Microsoft OLE DB Provider for
> ODBC
> Drivers Help file: Help context: 0Error Detail Records:Error:
> -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> source: Help file: Help context: 0DTSRun OnFinish:
> DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> so.. any help will be usefull (regarding the hebrew mirroring or regarding
> finding the user dsn)
> thanks,
> elad.
>
>
>
>
|||hi Uri,
well, I used the HIT odbc for as400.
here are it's details again:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
and, for that odbc I couldn't find a auto translate property.
I also looked for a download of the client access odbc but couldn't find it.
so... I will thakfull for a link
thanks,
elad.
"Uri Dimant" wrote:
> Elad, shalom
> I assume you got connected by using Client Access to the AS400.
> Look , first of all it depends on lot of things
> 1) Right click on the server within a package and press "Advance" button.
> Under Property name you will find Auto Translate=1 or =0. Try to play with
> it.
>
>
> "Xìò? ùì?X" <@.discussions.microsoft.com> wrote in message
> news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
>
>
we are running a dts that migrates data from an as400 to sql 2K.
the string data is hebrew (code page 1252).
for that, we have been using a hit odbc:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
untill now we were running the dts from sql 7.0 and that worked well.
the porblem started after copying (and then rewriting) the package to sql 2k:
when running the dts manually (execute package) it's o.k, but when running
the dts via a job the hebrew characters are being mirrored in the sql 2k.
(e.g, written from left to write instead of right to left).
again, in sql 7 it worked well both ways.
some details:
-in both cases (job and manually) we execute the package from the same server.
-the win login account used for manual executing is identical to the log on
accounts of server service and server agent.
we are using a system dsn.
I have found in a newsgroup a tip to solve that: using a user dsn.
but when I tried that another porblem came up:
when running manualy - it was, again, ok
but when running via a job (or with dtsrun) the server couldn't find the odbc.
here is the error massage:
DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
DTSStep_DTSExecuteSQLTask_2DTSRun OnStart: DTSStep_DTSDataPumpTask_1DTSRun
OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005) Error
string: [Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified Error source: Microsoft OLE DB Provider for ODBC
Drivers Help file: Help context: 0Error Detail Records:Error:
-2147467259 (80004005); Provider Error: 0 (0) Error string: Error
source: Help file: Help context: 0DTSRun OnFinish:
DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
so.. any help will be usefull (regarding the hebrew mirroring or regarding
finding the user dsn)
thanks,
elad.
Elad, shalom
I assume you got connected by using Client Access to the AS400.
Look , first of all it depends on lot of things
1) Right click on the server within a package and press "Advance" button.
Under Property name you will find Auto Translate=1 or =0. Try to play with
it.
" " <@.discussions.microsoft.com> wrote in message
news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
> hi all,
> we are running a dts that migrates data from an as400 to sql 2K.
> the string data is hebrew (code page 1252).
> for that, we have been using a hit odbc:
> ODBC OPTIMIZED (READ ONLY) 32 BIT
> VERSION 4.00.06.20
> HIT SOFTWARE, INC
> untill now we were running the dts from sql 7.0 and that worked well.
> the porblem started after copying (and then rewriting) the package to sql
> 2k:
> when running the dts manually (execute package) it's o.k, but when running
> the dts via a job the hebrew characters are being mirrored in the sql 2k.
> (e.g, written from left to write instead of right to left).
> again, in sql 7 it worked well both ways.
> some details:
> -in both cases (job and manually) we execute the package from the same
> server.
> -the win login account used for manual executing is identical to the log
> on
> accounts of server service and server agent.
> we are using a system dsn.
> I have found in a newsgroup a tip to solve that: using a user dsn.
> but when I tried that another porblem came up:
> when running manualy - it was, again, ok
> but when running via a job (or with dtsrun) the server couldn't find the
> odbc.
> here is the error massage:
> DTSRun: Loading...DTSRun: Executing...DTSRun OnStart:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnFinish:
> DTSStep_DTSExecuteSQLTask_2DTSRun OnStart:
> DTSStep_DTSDataPumpTask_1DTSRun
> OnError: DTSStep_DTSDataPumpTask_1, Error = -2147467259 (80004005)
> Error
> string: [Microsoft][ODBC Driver Manager] Data source name not found and
> no
> default driver specified Error source: Microsoft OLE DB Provider for
> ODBC
> Drivers Help file: Help context: 0Error Detail Records:Error:
> -2147467259 (80004005); Provider Error: 0 (0) Error string: Error
> source: Help file: Help context: 0DTSRun OnFinish:
> DTSStep_DTSDataPumpTask_1DTSRun: Package execution complete.NULL
> so.. any help will be usefull (regarding the hebrew mirroring or regarding
> finding the user dsn)
> thanks,
> elad.
>
>
>
>
|||hi Uri,
well, I used the HIT odbc for as400.
here are it's details again:
ODBC OPTIMIZED (READ ONLY) 32 BIT
VERSION 4.00.06.20
HIT SOFTWARE, INC
and, for that odbc I couldn't find a auto translate property.
I also looked for a download of the client access odbc but couldn't find it.
so... I will thakfull for a link
thanks,
elad.
"Uri Dimant" wrote:
> Elad, shalom
> I assume you got connected by using Client Access to the AS400.
> Look , first of all it depends on lot of things
> 1) Right click on the server within a package and press "Advance" button.
> Under Property name you will find Auto Translate=1 or =0. Try to play with
> it.
>
>
> "Xìò? ùì?X" <@.discussions.microsoft.com> wrote in message
> news:12A0B201-3D38-4626-9DD1-155623940393@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)