DB2 ODBC Connection Problems

Hello,

I've recently run across a couple of problems trying to connect to DB2 using the .NET ODBC Provider.

1) I can create a DataSource using the DataSource designer, and when I edit the connection, the User Name and Password text boxes are empty. If I fill in the correct information and hit "Test Connection", I am able to connect. However, this information is not saved in the DataSource the next time I open it or try to run a Data Flow task that uses it! Is there some property I can set to fix this?

2) When I open up a solution, the DataSource appears to be trying to connect to the DB2 server, and perhaps there is no valid User Name and Password, the connection is refused and I eventually get locked out of my account. This could be related to the issue above.

Does anyone have any experience connecting to DB2 using either an ODBC driver or the perhaps the IBM DB2 UDB iSeries OLE DB providers?

Thanks in advance,

Mark

Mark,

The same problem occurs with Progress Database using .NET ODBC Provider and a didn′t find a solution. Problably is a .NET ODBC Provider problem but I don′t know how to fix. If you find a solution, please post here.

Question: Do you receive this error message ?

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Thanks.

Rodrigo Chagas

|||

I found this post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93045&SiteID=1

Maybe will be useful for you. It seems ODBC connections are having a lot of problems in SQL 2005.

My hope is getting smaller...

|||This is not a problem with .Net, but rather the way in which the ODBC driver builds the connection string or handles security. Some drivers including the CA ODBC driver do not append the password property to the connection string. So when you attempt to connect it will prompt for a password. Depending on how you invoke the program, you may not even see the prompt.
One way to resolve the issue is to append the password to your connection string in the form of "Password=MyPass;"
I've used the OLEDB provider for DB2 before, but there are some limitations to it. Per IBM, OLEDB does not provide the same level of functionality as their ODBC drivers. One thing that OLEDB does not provide is scrollable cursors.
I haven't used DB2 in almost a year, so IBM may have some updated drivers. Also MS just released their version of an OLEDB provider for DB2, so you could try it. You can get it at the following url.
http://www.microsoft.com/downloads/details.aspx?familyid=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en
Larry

db1.dbo.table to db2.other.table

Hi,
I need help/guidance setting up replication across dbs.
db1 has the same tables as db2. tables have the same fields.
db1 has "dbo.table" schema, db2 has "other.table" schema.
I setup simple replication and db1.dbo.tables are being added to db2 as
db2.dbo.tables instead of just refreshing data on db2.other.tables...
Any help would be greatly appreciated.
http://www.dbazine.com/sql/sql-articles/cotter1
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<Doug M> wrote in message
news:1058678B-8239-423C-B68D-C17EC9E882A5@.microsoft.com...
> Hi,
> I need help/guidance setting up replication across dbs.
> db1 has the same tables as db2. tables have the same fields.
> db1 has "dbo.table" schema, db2 has "other.table" schema.
> I setup simple replication and db1.dbo.tables are being added to db2 as
> db2.dbo.tables instead of just refreshing data on db2.other.tables...
> Any help would be greatly appreciated.
>

DB LOCK

Comming across the [BULK-OP-DB],[BULK-OP-LOG] , locks in the database and there is no database backup job running. Auto stats update is set to off. Auto shrink is also set to off.
Can someone shed more light on this ? and its implications on performance ?
Thanks !!
[BULK-OP-LOG]
Lock acquired on a transaction log to synchronize certain bulk (non-logged)
operations.
* If the BULK-OP-LOG lock is LCK_M_X (exclusive), cause may be
database/file/log backup or incremental db backup
* If the BULK-OP-LOG lock is LCK_M_S (shared), cause may be tran log
truncation, nonlogged bulk insert/bcp/select into, or text modification
operations
* If the BULK-OP-LOG lock is LCK_M_U (update), cause may be add file, drop
file, shrink file/db, or create filegroup
* If the BULK-OP-LOG lock is LCK_M_NL (NULL), cause may be dbcc
checkalloc/dbcc checkdb, create index, grow file, or modify file
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

DB Lock

Comming across the [BULK-OP-DB],[BULK-OP-LOG] , locks in the database and there is no database backup job running. Auto stats update is set to off. Auto shrink is also set to off.
Can someone shed more light on this ? and its implications on performance ?
DB:db_id[BULK-OP-DB], which identifies the database lock taken by the backup database.
DB:db_id[BULK-OP-LOG], which identifies the lock taken by the backup log for that particular database.
Thanks !!
It would depend on the kind of lock.
If the BULK-OP-DB lock is
1. LCK_M_X (exclusive):- cause may be database or file backup, incremental
db backup, or dbcc checkalloc/dbcc checkdb
2. LCK_M_S (shared):- cause may be index creation, text modification
operations, or nonlogged bulk insert/bcp/select into
3. LCK_M_U (update):- cause may be filegroup creation, shrink file/shrink
database, drop file, or add file
4. LCK_M_NL (NULL):- cause may be modify file, auto grow file, or tran log
backup/truncation
Hope that helps!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

DB LOCK

Comming across the [BULK-OP-DB],[BULK-OP-LOG] , locks in the database and there is no database backup job running. Auto stats update is set to off. Auto shrink is also set to off.
Can someone shed more light on this ? and its implications on performance '
Thanks !![BULK-OP-LOG]
Lock acquired on a transaction log to synchronize certain bulk (non-logged)
operations.
* If the BULK-OP-LOG lock is LCK_M_X (exclusive), cause may be
database/file/log backup or incremental db backup
* If the BULK-OP-LOG lock is LCK_M_S (shared), cause may be tran log
truncation, nonlogged bulk insert/bcp/select into, or text modification
operations
* If the BULK-OP-LOG lock is LCK_M_U (update), cause may be add file, drop
file, shrink file/db, or create filegroup
* If the BULK-OP-LOG lock is LCK_M_NL (NULL), cause may be dbcc
checkalloc/dbcc checkdb, create index, grow file, or modify file
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

DB Lock

Comming across the [BULK-OP-DB],[BULK-OP-LOG] , locks in the database and there is no database backup job running. Auto stats update is set to off. Auto shrink is also set to off.
Can someone shed more light on this ? and its implications on performance '
DB:db_id[BULK-OP-DB], which identifies the database lock taken by the backup database.
DB:db_id[BULK-OP-LOG], which identifies the lock taken by the backup log for that particular database.
Thanks !!It would depend on the kind of lock.
If the BULK-OP-DB lock is
1. LCK_M_X (exclusive):- cause may be database or file backup, incremental
db backup, or dbcc checkalloc/dbcc checkdb
2. LCK_M_S (shared):- cause may be index creation, text modification
operations, or nonlogged bulk insert/bcp/select into
3. LCK_M_U (update):- cause may be filegroup creation, shrink file/shrink
database, drop file, or add file
4. LCK_M_NL (NULL):- cause may be modify file, auto grow file, or tran log
backup/truncation
Hope that helps!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

DB Lock

Comming across the [BULK-OP-DB],[BULK-OP-LOG] , locks in the databas
e and there is no database backup job running. Auto stats update is set to o
ff. Auto shrink is also set to off.
Can someone shed more light on this ? and its implications on performance '
DB:db_id[BULK-OP-DB], which identifies the database lock taken by the ba
ckup database.
DB:db_id[BULK-OP-LOG], which identifies the lock taken by the backup log
for that particular database.
Thanks !!It would depend on the kind of lock.
If the BULK-OP-DB lock is
1. LCK_M_X (exclusive):- cause may be database or file backup, incremental
db backup, or dbcc checkalloc/dbcc checkdb
2. LCK_M_S (shared):- cause may be index creation, text modification
operations, or nonlogged bulk insert/bcp/select into
3. LCK_M_U (update):- cause may be filegroup creation, shrink file/shrink
database, drop file, or add file
4. LCK_M_NL (NULL):- cause may be modify file, auto grow file, or tran log
backup/truncation
Hope that helps!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

DB LOCK

Comming across the [BULK-OP-DB],[BULK-OP-LOG] , locks in the databas
e and there is no database backup job running. Auto stats update is set to o
ff. Auto shrink is also set to off.
Can someone shed more light on this ? and its implications on performance '
Thanks !![BULK-OP-LOG]
Lock acquired on a transaction log to synchronize certain bulk (non-logged)
operations.
* If the BULK-OP-LOG lock is LCK_M_X (exclusive), cause may be
database/file/log backup or incremental db backup
* If the BULK-OP-LOG lock is LCK_M_S (shared), cause may be tran log
truncation, nonlogged bulk insert/bcp/select into, or text modification
operations
* If the BULK-OP-LOG lock is LCK_M_U (update), cause may be add file, drop
file, shrink file/db, or create filegroup
* If the BULK-OP-LOG lock is LCK_M_NL (NULL), cause may be dbcc
checkalloc/dbcc checkdb, create index, grow file, or modify file
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.