Hi all,

Version DB@ U8.2
OS : Linux/Windows

While doing Set Integrity Operation on the table,
SET INTEGRITY FOR COMMON .USER_JOBROLE_MQT IMMEDIATE CHECKED

I got this error like

DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
SQL0964C The transaction log for the database is full. SQLSTATE=57011


For that i Update the LOGSECOND Db parameter to -1.

Even though i got this error like Transaction Log full.

So, please give the solution about this.
Please do let me know.

Regards,

Abdul Rehaman

Did you reactivate the database - ie disconnect all applications and 'restart' ?

Before setting this to -1, did you try to increase you logprimary and logsecondary? The implications of setting logsecond to -1 has to be carefully considered before using this value on production

Sathyaram

Thanks for reply,

I did all the things what u mentioned.

I disconnect all the applications which are connected to the database.

First i increase the logsecondary from 2 to 20. But i got same error.

At last i set the LogSecond to -1, still i am not getting.

After this I stop the instance and start again. DB Paramerter Logsecond is

successfully updated.

Even though i got the Error like previous which i mentioned.

This Database belongs to Development Environment.

Regards,

Abdul Rehaman

But do you have enough disk space? I would monitor disk space utilization while the process is running just to make sure.