The transaction log for the database is full

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
jack_125
Participant
Posts: 15
Joined: Fri Jul 30, 2010 9:46 am

The transaction log for the database is full

Post by jack_125 »

Hi All,
I've datastage 8.5. My datastage director is showing me error i.e.
transaction log for the database is full.

So how should I increase the size? Delete the log file as well?

Thnks
JackSh
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What database would that be? Have you involved your DBA?
-craig

"You can never have too many knives" -- Logan Nine Fingers
jack_125
Participant
Posts: 15
Joined: Fri Jul 30, 2010 9:46 am

Post by jack_125 »

Its DB2 database and I dont have a DBA support but I have admin privelages
On my id.
JackSh
MT
Premium Member
Premium Member
Posts: 198
Joined: Fri Mar 09, 2007 3:51 am

Post by MT »

jack_125 wrote:Its DB2 database and I dont have a DBA support but I have admin privelages
On my id.
Hi Jack

this means the DB2 log ran full because your Transaction was too long (too many rows where changed).
Several solutions for that - here is one:
1. Increase your number of secondary logs (logsecond parameter in the db cfg)
2. Ensure your transactions commits more oftern (see "Transactions size" in the DB2 stage in DataStage)

By the way it is worth having a DBA!

best regards
Michael
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Is this the XMETA database (or IADB or QSDB) or a database containing your organization's data?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply