DB2 driver/connection issue

Hi guys,

I have a kind of weird situation that may be causing this problem. My setup is that I'm remote desktopping into a 64-bit box on a client's network. They installed SSIS there, I use login 1 which has rights to the box, but none of the databases. To do that I run SSIS as login 2, who can hit the databases.

I've got two datasources for this project one is DB2 and the other is SqlServer2k5. I've been focusing on the DB2 (I'm running the Microsoft OLEDB Provider for DB2 that was part of the feature pack from feb 2007). I've registered the dll with "regsvr32.exe /s /c ibmdadb2.dll" and tried to import database settings from a pdb with "db2cfimp db2Settings.pdb". The connection to, we'll call it, DB2A doesn't actually show up in the "Admin Tools\ODBC Data Source Administrator", but seeing as how the connection sort of works I don't think this is the problem.

Using the "IBM OLE DB Provider for DB2 Servers" connection I can connect to the DB2 database in SSIS's Data Flow with a DataReader Source. The correct columns are shown in the column mappings and everything looks good while designing.

Upon executing the package I get the following error:

SSIS package "Package.dtsx" starting.
Information: 0x4004300A at TGMV019, DTS.Pipeline: Validation phase is beginning.
Error: 0xC0047062 at TGMV019, GM19 [31]: System.InvalidOperationException: The 'IBMDADB2.1' provider is not registered on the local machine.
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)
Error: 0xC0047017 at TGMV019, DTS.Pipeline: component "GM19" (31) failed validation and returned error code 0x80131509.
Error: 0xC004700C at TGMV019, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at TGMV019: There were errors during task validation.
SSIS package "Package.dtsx" finished: Failure.

The problem sure looks like it's with the IBMDADB2.1 provider. I have retried the regsvr32 command (is this just a 32bit version?) to no avail. Does this assignment require a reboot (because they installed this on a training database box that really can't be easily rebooted)?

Thanks for any ideas, I'm fresh out

Jeff
Since you are using the Microsoft OLEDB Provider for DB2, why aren't you using the OLE DB Source in the data flow instead of the DataReader source?|||I gave up on using "OLE DB Provider: Microsoft OLE DB Provider for DB2" because I can't seem to get away from the error: "Test connection failed because of an error in initializing provider. The parameter is incorrect.". Also, these forums (I think) said the IBM one was more reliable than the microsoft one.

I'm not sure what to enter under: Data Link Properties. I've tried various combination for 'Initial catalog', 'package collection' and 'default schema' but none of them work. Also, pressing the "Packages" button on the bottom crashes visual studio, so I'm not sure what's supposed to go there.
|||See if this helps any:
http://www.ssistalk.com/db2_configurations.jpg

That is the list of all of the properties for one of my connections that I use on a daily basis to transfer records from DB2 to SQL Server 2005.

db log Timeout errors

Hi,
we've got a situation as below:
Error: database log truncated, db1
Error 9002 : The database log file for "temdb" is full. Backup the
transaction log for the database to free up some space
Any thoughts on these errors?
On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
10% unrestricted. Our Apps developers were getting some timeouts running
queries on DB1. It's possible they may be running some large queries that
cause these errors (or at least the second error). Any ideas on this?
What would be a probable solution?
Or they are harmless and can be ignored?
Many thanks,
SQL NewbieFor some operations, autogrow doesn't grow the file fast enough to keep up with the space usage
requirements. Hence a "full" error message. Reading your error message, this is in the tempdb
database. I suggest you pre-allocate space for tempdb. Use the ALTER DATABASE command for that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hugh" <Hugh@.discussions.microsoft.com> wrote in message
news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> Some guru please help...pretty congeated.
> "Hugh" wrote:
>> Hi,
>> we've got a situation as below:
>> Error: database log truncated, db1
>> Error 9002 : The database log file for "temdb" is full. Backup the
>> transaction log for the database to free up some space
>> Any thoughts on these errors?
>> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
>> 10% unrestricted. Our Apps developers were getting some timeouts running
>> queries on DB1. It's possible they may be running some large queries that
>> cause these errors (or at least the second error). Any ideas on this?
>> What would be a probable solution?
>> Or they are harmless and can be ignored?
>> Many thanks,
>> SQL Newbie|||thanx mate.
can recommend some good materials on the concepts of how SQL server works?
Any samples of what the statement will be like?
Also how to know how much more space is required? Will it require restart?
Is anything loss due this error?
Any means to analyse and prevent similar occurences?
thanx,
An SQL newbie
"Tibor Karaszi" wrote:
> For some operations, autogrow doesn't grow the file fast enough to keep up with the space usage
> requirements. Hence a "full" error message. Reading your error message, this is in the tempdb
> database. I suggest you pre-allocate space for tempdb. Use the ALTER DATABASE command for that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> > Some guru please help...pretty congeated.
> >
> > "Hugh" wrote:
> >
> >> Hi,
> >>
> >> we've got a situation as below:
> >>
> >> Error: database log truncated, db1
> >>
> >> Error 9002 : The database log file for "temdb" is full. Backup the
> >> transaction log for the database to free up some space
> >>
> >> Any thoughts on these errors?
> >>
> >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
> >> 10% unrestricted. Our Apps developers were getting some timeouts running
> >> queries on DB1. It's possible they may be running some large queries that
> >> cause these errors (or at least the second error). Any ideas on this?
> >>
> >> What would be a probable solution?
> >> Or they are harmless and can be ignored?
> >>
> >> Many thanks,
> >> SQL Newbie
>
>|||You might want to get a hold of "Inside SQL Server 2000" by Kalen Delaney.
It is a big book but if you want to know how sql server works that is the
book.
--
Andrew J. Kelly SQL MVP
"Hugh" <Hugh@.discussions.microsoft.com> wrote in message
news:8B067416-65CF-45A6-B899-636CE6AF4CE1@.microsoft.com...
> thanx mate.
> can recommend some good materials on the concepts of how SQL server works?
> Any samples of what the statement will be like?
> Also how to know how much more space is required? Will it require
restart?
> Is anything loss due this error?
> Any means to analyse and prevent similar occurences?
> thanx,
> An SQL newbie
> "Tibor Karaszi" wrote:
> > For some operations, autogrow doesn't grow the file fast enough to keep
up with the space usage
> > requirements. Hence a "full" error message. Reading your error message,
this is in the tempdb
> > database. I suggest you pre-allocate space for tempdb. Use the ALTER
DATABASE command for that.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> > news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> > > Some guru please help...pretty congeated.
> > >
> > > "Hugh" wrote:
> > >
> > >> Hi,
> > >>
> > >> we've got a situation as below:
> > >>
> > >> Error: database log truncated, db1
> > >>
> > >> Error 9002 : The database log file for "temdb" is full. Backup the
> > >> transaction log for the database to free up some space
> > >>
> > >> Any thoughts on these errors?
> > >>
> > >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to
grow by
> > >> 10% unrestricted. Our Apps developers were getting some timeouts
running
> > >> queries on DB1. It's possible they may be running some large queries
that
> > >> cause these errors (or at least the second error). Any ideas on this?
> > >>
> > >> What would be a probable solution?
> > >> Or they are harmless and can be ignored?
> > >>
> > >> Many thanks,
> > >> SQL Newbie
> >
> >
> >|||thanx Andrew,
Pertaining to my problem. can any1 provide some samples of what the
statement will be like?
Also how to know how much more space is required? Will it require restart?
Is anything loss due this error?
Any means to analyse and prevent similar occurences?
thanx,
An SQL newbie
"Andrew J. Kelly" wrote:
> You might want to get a hold of "Inside SQL Server 2000" by Kalen Delaney.
> It is a big book but if you want to know how sql server works that is the
> book.
> --
> Andrew J. Kelly SQL MVP
>
> "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> news:8B067416-65CF-45A6-B899-636CE6AF4CE1@.microsoft.com...
> > thanx mate.
> >
> > can recommend some good materials on the concepts of how SQL server works?
> >
> > Any samples of what the statement will be like?
> > Also how to know how much more space is required? Will it require
> restart?
> > Is anything loss due this error?
> >
> > Any means to analyse and prevent similar occurences?
> >
> > thanx,
> > An SQL newbie
> >
> > "Tibor Karaszi" wrote:
> >
> > > For some operations, autogrow doesn't grow the file fast enough to keep
> up with the space usage
> > > requirements. Hence a "full" error message. Reading your error message,
> this is in the tempdb
> > > database. I suggest you pre-allocate space for tempdb. Use the ALTER
> DATABASE command for that.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
> > > news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
> > > > Some guru please help...pretty congeated.
> > > >
> > > > "Hugh" wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> we've got a situation as below:
> > > >>
> > > >> Error: database log truncated, db1
> > > >>
> > > >> Error 9002 : The database log file for "temdb" is full. Backup the
> > > >> transaction log for the database to free up some space
> > > >>
> > > >> Any thoughts on these errors?
> > > >>
> > > >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to
> grow by
> > > >> 10% unrestricted. Our Apps developers were getting some timeouts
> running
> > > >> queries on DB1. It's possible they may be running some large queries
> that
> > > >> cause these errors (or at least the second error). Any ideas on this?
> > > >>
> > > >> What would be a probable solution?
> > > >> Or they are harmless and can be ignored?
> > > >>
> > > >> Many thanks,
> > > >> SQL Newbie
> > >
> > >
> > >
>
>|||> Pertaining to my problem. can any1 provide some samples of what the
> statement will be like?
There's an example in Books Online, I believe (I'm in a hurry right now).
> Also how to know how much more space is required?
Monitor tempdb size over time to get an idea of the space it needs for your particular applications,
schema, indexes, queries and workload.
> Will it require restart?
Tempdb is re-created every time SQL Server restarts. Applying the "template" size which you set
using ALTER DATABASE requires a re-start. You can also use ALTER DATABASE to change the size of your
running tempdb, but again, it is re-created at restart.
> Is anything loss due this error?
The statements that failed has ... failed.
> Any means to analyze and prevent similar occurences?
Monitor size, and your errorlogs/eventlogs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hugh" <Hugh@.discussions.microsoft.com> wrote in message
news:06CD159E-9ED4-4F20-9788-A40560615699@.microsoft.com...
> thanx Andrew,
> Pertaining to my problem. can any1 provide some samples of what the
> statement will be like?
> Also how to know how much more space is required? Will it require restart?
> Is anything loss due this error?
> Any means to analyse and prevent similar occurences?
> thanx,
> An SQL newbie
>
>
> "Andrew J. Kelly" wrote:
>> You might want to get a hold of "Inside SQL Server 2000" by Kalen Delaney.
>> It is a big book but if you want to know how sql server works that is the
>> book.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
>> news:8B067416-65CF-45A6-B899-636CE6AF4CE1@.microsoft.com...
>> > thanx mate.
>> >
>> > can recommend some good materials on the concepts of how SQL server works?
>> >
>> > Any samples of what the statement will be like?
>> > Also how to know how much more space is required? Will it require
>> restart?
>> > Is anything loss due this error?
>> >
>> > Any means to analyse and prevent similar occurences?
>> >
>> > thanx,
>> > An SQL newbie
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > For some operations, autogrow doesn't grow the file fast enough to keep
>> up with the space usage
>> > > requirements. Hence a "full" error message. Reading your error message,
>> this is in the tempdb
>> > > database. I suggest you pre-allocate space for tempdb. Use the ALTER
>> DATABASE command for that.
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://www.solidqualitylearning.com/
>> > >
>> > >
>> > > "Hugh" <Hugh@.discussions.microsoft.com> wrote in message
>> > > news:80BF48AB-2D21-4DA4-9E47-B860F0859FA6@.microsoft.com...
>> > > > Some guru please help...pretty congeated.
>> > > >
>> > > > "Hugh" wrote:
>> > > >
>> > > >> Hi,
>> > > >>
>> > > >> we've got a situation as below:
>> > > >>
>> > > >> Error: database log truncated, db1
>> > > >>
>> > > >> Error 9002 : The database log file for "temdb" is full. Backup the
>> > > >> transaction log for the database to free up some space
>> > > >>
>> > > >> Any thoughts on these errors?
>> > > >>
>> > > >> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to
>> grow by
>> > > >> 10% unrestricted. Our Apps developers were getting some timeouts
>> running
>> > > >> queries on DB1. It's possible they may be running some large queries
>> that
>> > > >> cause these errors (or at least the second error). Any ideas on this?
>> > > >>
>> > > >> What would be a probable solution?
>> > > >> Or they are harmless and can be ignored?
>> > > >>
>> > > >> Many thanks,
>> > > >> SQL Newbie
>> > >
>> > >
>> > >
>>|||Some guru please help...pretty congeated.
"Hugh" wrote:
> Hi,
> we've got a situation as below:
> Error: database log truncated, db1
> Error 9002 : The database log file for "temdb" is full. Backup the
> transaction log for the database to free up some space
> Any thoughts on these errors?
> On db1, tempdb is 1314Mb with a log size of 28Mb. Both are set to grow by
> 10% unrestricted. Our Apps developers were getting some timeouts running
> queries on DB1. It's possible they may be running some large queries that
> cause these errors (or at least the second error). Any ideas on this?
> What would be a probable solution?
> Or they are harmless and can be ignored?
> Many thanks,
> SQL Newbie

DB in "loading" state - error 22274

We had a situation where we had to restore one of our SQL
databases to the same server the original was running on.
We restored using Arcserve 2000 w/ SQL Agent and it
completed successfully to a different name & directory.
Name of DB was RES_LAW & we had the .mdf & .ldf files
named differently then the originals and in a different
folder.
Arcserve finished the restore successfully with no errors.
When you go into Enterprise Manager the database is there
but shows up GRAY and says "loading" underneath it. When
you double-click to expand properties, you get two errors:
1. error 22274 [SQL-DMO]This Database has been marked
inaccessible (then when you click OK, you get...)
2. Could not get property information for the
database "res_law"
Then it closes.
Does anyone know what is wrong or what we should do?
Computer Associates (maker of Arcserve, said it's not
their problem)
Any help is greatly appreciated.It may just need to be recovered. From Query Analyzer,
execute the following:
RESTORE DATABASE yourDB WITH RECOVERY
>Does anyone know what is wrong or what we should do?
>Computer Associates (maker of Arcserve, said it's not
>their problem)
Sounds familiar and you have my sympathy.
Linchi
>--Original Message--
>We had a situation where we had to restore one of our SQL
>databases to the same server the original was running
on.
>We restored using Arcserve 2000 w/ SQL Agent and it
>completed successfully to a different name & directory.
>Name of DB was RES_LAW & we had the .mdf & .ldf files
>named differently then the originals and in a different
>folder.
>Arcserve finished the restore successfully with no errors.
>When you go into Enterprise Manager the database is there
>but shows up GRAY and says "loading" underneath it. When
>you double-click to expand properties, you get two errors:
>1. error 22274 [SQL-DMO]This Database has been marked
>inaccessible (then when you click OK, you get...)
>2. Could not get property information for the
>database "res_law"
>Then it closes.
>Does anyone know what is wrong or what we should do?
>Computer Associates (maker of Arcserve, said it's not
>their problem)
>Any help is greatly appreciated.
>
>.
>

DB in "loading" state - error 22274

We had a situation where we had to restore one of our SQL
databases to the same server the original was running on.
We restored using Arcserve 2000 w/ SQL Agent and it
completed successfully to a different name & directory.
Name of DB was RES_LAW & we had the .mdf & .ldf files
named differently then the originals and in a different
folder.
Arcserve finished the restore successfully with no errors.
When you go into Enterprise Manager the database is there
but shows up GRAY and says "loading" underneath it. When
you double-click to expand properties, you get two errors:
1. error 22274 [SQL-DMO]This Database has been marked
inaccessible (then when you click OK, you get...)
2. Could not get property information for the
database "res_law"
Then it closes.
Does anyone know what is wrong or what we should do?
Computer Associates (maker of Arcserve, said it's not
their problem)
Any help is greatly appreciated.It may just need to be recovered. From Query Analyzer,
execute the following:
RESTORE DATABASE yourDB WITH RECOVERY

quote:

---

>Does anyone know what is wrong or what we should do?
>Computer Associates (maker of Arcserve, said it's not
>their problem)

---

Sounds familiar and you have my sympathy.
Linchi

quote:

---

>--Original Message--
>We had a situation where we had to restore one of our SQL
>databases to the same server the original was running

---

on.

quote:

---

>We restored using Arcserve 2000 w/ SQL Agent and it
>completed successfully to a different name & directory.
>Name of DB was RES_LAW & we had the .mdf & .ldf files
>named differently then the originals and in a different
>folder.
>Arcserve finished the restore successfully with no errors.
>When you go into Enterprise Manager the database is there
>but shows up GRAY and says "loading" underneath it. When
>you double-click to expand properties, you get two errors:
>1. error 22274 [SQL-DMO]This Database has been marked
>inaccessible (then when you click OK, you get...)
>2. Could not get property information for the
>database "res_law"
>Then it closes.
>Does anyone know what is wrong or what we should do?
>Computer Associates (maker of Arcserve, said it's not
>their problem)
>Any help is greatly appreciated.
>
>.
>

---