dbTalk Databases Forums  

SSIS Bug?

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss SSIS Bug? in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
MarkFrank
 
Posts: n/a

Default SSIS Bug? - 06-02-2006 , 04:41 PM






Hi all,

I've had a package which ran cleanly for some time. I've since been getting
the following error:

Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code:
0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80004005 Description: "The transaction log for database 'CCG_ODS'
is full. To find out why space in the log cannot be reused, see the
log_reuse_wait_desc column in sys.databases".

The database has simple transaction logging and plenty of space. Not sure
what is going on.

The log reuse from the following query was Nothing when I started the
process and sits at Active Transaction subsequently.

SELECT * FROM sys.databases

Any help would be appreciated.

Thanks in advance,
Mark

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS Bug? - 06-04-2006 , 05:23 PM






Hello MarkFrank,

are you seeing this?

http://support.microsoft.com/?id=317375

Allan



Quote:
Hi all,

I've had a package which ran cleanly for some time. I've since been
getting the following error:

Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error
code:
0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80004005 Description: "The transaction log for database
'CCG_ODS'
is full. To find out why space in the log cannot be reused, see the
log_reuse_wait_desc column in sys.databases".
The database has simple transaction logging and plenty of space. Not
sure what is going on.

The log reuse from the following query was Nothing when I started the
process and sits at Active Transaction subsequently.

SELECT * FROM sys.databases

Any help would be appreciated.

Thanks in advance,
Mark



Reply With Quote
  #3  
Old   
MarkFrank
 
Posts: n/a

Default Re: SSIS Bug? - 06-05-2006 , 11:09 AM



Hi Alan,

That is the error I'm seeing. I re-created a new database with simple
logging that seems to be working ok. However, switching the original to
simple did not alleviate the issue.

Thanks,

Mark

"Allan Mitchell" wrote:

Quote:
Hello MarkFrank,

are you seeing this?

http://support.microsoft.com/?id=317375

Allan



Hi all,

I've had a package which ran cleanly for some time. I've since been
getting the following error:

Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error
code:
0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80004005 Description: "The transaction log for database
'CCG_ODS'
is full. To find out why space in the log cannot be reused, see the
log_reuse_wait_desc column in sys.databases".
The database has simple transaction logging and plenty of space. Not
sure what is going on.

The log reuse from the following query was Nothing when I started the
process and sits at Active Transaction subsequently.

SELECT * FROM sys.databases

Any help would be appreciated.

Thanks in advance,
Mark




Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: SSIS Bug? - 07-25-2006 , 01:28 PM



One of the reasons is that just because the DB T log is set to simple it
still cannot be cleared until active transactions have finished using it.
This still means that large transactions can blow the log because the log
manager cannot breathe yet. ALSO if the log has to expand then this can
also cause this message because the query has to wait and all it knows is
that the log is full.

Allan


"MarkFrank" <MarkFrank (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi all,

I've had a package which ran cleanly for some time. I've since been
getting
the following error:

Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error
code:
0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80004005 Description: "The transaction log for database
'CCG_ODS'
is full. To find out why space in the log cannot be reused, see the
log_reuse_wait_desc column in sys.databases".

The database has simple transaction logging and plenty of space. Not sure
what is going on.

The log reuse from the following query was Nothing when I started the
process and sits at Active Transaction subsequently.

SELECT * FROM sys.databases

Any help would be appreciated.

Thanks in advance,
Mark



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.