Skip to Content
avatar image
Former Member

DB6CONV Stuck in Status "New"

We used DB6CONV 6.36 to enable compression and reclaim back space to disk. Due to a transaction log full error, we have to reset a aborted runs. All other tables were converted and moved to the new tablespace except for table FAGLFLEXA which is now stuck in status "New" after the reset.

We are unable to start it; deleting it prompts this message:

deletion is only possible for - conversions with status RESET, FINISHED or ERROR(RESOLVED) - new conversions with status SCHEDULED, PLANNED or NEW

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    Jul 11, 2017 at 01:30 PM

    Hi Ahmad,

    problem (-> incident 323636 2017) has been solved. status "NEW" was shown incorrectly (due to the log_dir full condition), because the conversion was already started. when deleting such an enty, DB6CONV first checks not only the JOB_STATUS, but also if the conversion was really not started yet. since the latter was not true in your case, the deletion was forbidden. I manually adjusted the JOB_STATUS, so I could successfully RESET the conversion. now everything concerning DB6CONV is fine again.

    best regards, Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you Frank for the quick fix. One last query: in case it happens again, how can we reset the status ourselves? Can I go debug mode and update it?

  • Jul 11, 2017 at 07:34 AM

    Hi

    Check the db2diag to see if anything fishy is reported.

    Use command db2top to check if any session is active for DB6CONV.

    Did you try creating a new session for the mentioned table to see if the report goes ahead with it?

    Regards,

    Prithviraj.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 11, 2017 at 06:53 AM

    the program does not allow to delete this entry in the program:

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 11, 2017 at 08:06 AM

    Hi Ahmad,

    please check SM37 for Job(s) DB6CONV_FAGLFLEXA and check the Job Status - if the Job Status changed, please refresh DB6CONV to see if the Status in DB6CONV changed as well.

    if not, please open an incident (already open the System Connection as well) and let me know the incident number.

    best regards, Frank

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 19, 2017 at 05:46 PM

    Hi,

    I had the same issue in the past.

    use the DB6CONV v6.34 or above

    https://launchpad.support.sap.com/#/notes/1513862/E

    thanks.

    Add comment
    10|10000 characters needed characters exceeded