If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Problem in Trigger

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-01-03, 11:45
rabbit rabbit is offline
Registered User
 
Join Date: Oct 2003
Location: Germany
Posts: 29
Question Problem in Trigger

Hi all,
i have inserted 1 GB images in my table and after comparing the images with each other i want to delete the images from the table. But i get always the error message during the delete:

COM.ibm.db2.jdbc.DBException: [ IBM][CLI Driver][DB2/NT ] SQL0723N An error occurred in a triggered SQL statement in trigger "MMDBSYS.DBIMAGE3FC8BCBBF". Information returned for the error includes SQLCODE "-964", SQLSTATE "57011" and message tokens "". SQLSTATE=09000

Does anybody know what's wrong with the trigger? I didn't program yet for the trigger. Have i anything forgotten? Please help me! I use DB2 V8 image extender no fix pack.



Thank you very much and greeting from germany!


rabbit
Reply With Quote
  #2 (permalink)  
Old 12-02-03, 14:46
GertK GertK is offline
Registered User
 
Join Date: Nov 2003
Location: Netherlands
Posts: 96
Re: Problem in Trigger

Quote:
Originally posted by rabbit
Hi all,
i have inserted 1 GB images in my table and after comparing the images with each other i want to delete the images from the table. But i get always the error message during the delete:

COM.ibm.db2.jdbc.DBException: [ IBM][CLI Driver][DB2/NT ] SQL0723N An error occurred in a triggered SQL statement in trigger "MMDBSYS.DBIMAGE3FC8BCBBF". Information returned for the error includes SQLCODE "-964", SQLSTATE "57011" and message tokens "". SQLSTATE=09000

Does anybody know what's wrong with the trigger? I didn't program yet for the trigger. Have i anything forgotten? Please help me! I use DB2 V8 image extender no fix pack.



Thank you very much and greeting from germany!


rabbit
'db2 ? sql0964' shows what this error means, you don't have enough log space.
If you can't commit more frequently you need to specify additional logs (or define a larger logfilesize).

Hope this helps.
Reply With Quote
  #3 (permalink)  
Old 12-04-03, 08:48
rabbit rabbit is offline
Registered User
 
Join Date: Oct 2003
Location: Germany
Posts: 29
Re: Problem in Trigger (how can i define a larger logfile)

thank you gertk,
I think my logfile is not large enough. But i don't know how can i define a larger logfile. I have no experence for this. Can you give me any suggestions? (new configuration?)

thank you very much and greeting from germany!


rabbit

Quote:
Originally posted by GertK
'db2 ? sql0964' shows what this error means, you don't have enough log space.
If you can't commit more frequently you need to specify additional logs (or define a larger logfilesize).

Hope this helps.
Reply With Quote
  #4 (permalink)  
Old 12-04-03, 14:06
GertK GertK is offline
Registered User
 
Join Date: Nov 2003
Location: Netherlands
Posts: 96
Re: Problem in Trigger (how can i define a larger logfile)

Quote:
Originally posted by rabbit
thank you gertk,
I think my logfile is not large enough. But i don't know how can i define a larger logfile. I have no experence for this. Can you give me any suggestions? (new configuration?)

thank you very much and greeting from germany!


rabbit
You can change the log with the 'db2 update database configuration ' command (or 'db2 update db cfg').

Some examples from my Windows Command prompt:

With 'db2 get db cfg for sample|find "(LOG" ' you can get the current log settings:
Log buffer size (4KB) (LOGBUFSZ) = 8
Log file size (4KB) (LOGFILSIZ) = 250
Number of primary log files (LOGPRIMARY) = 3
Number of secondary log files (LOGSECOND) = 2
Log retain for recovery enabled (LOGRETAIN) = OFF

Things you can change are the LOGFILSIZ (the size of one log file), LOGPRIMARY (the number of primary logs) and LOGSECONDARY you can guess

The log 'behaviour' is fully documented in the information center, check the third option after searching for logprimary.

Hope this helps.

Greetings from the Netherlands.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
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

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On