unable to delete rows on ph_alert and ph_alerts
Posted in 2015
Topics: Error Codes & Troubleshooting
Hello I'm trying to delete rows in ph_alert table doing this sql command:
delete from ph_alerts; (I know this delete every row in the table)
In this table there is just 6 rows belonging to 2014, but when i do this i
get the next mesage
"Could no delete a row, ISAM error not found"
But when I Do a select, there is 6 rows.
However doing a select in ph_alerts I get the next error
" 750: Invalid distribution format found for tk_id"
Dropping distributions with update statistics and add a new one dosn't
solve the issue. Any clue how to sort this out?
Regards.
--94eb2c06f0aafa99580526d71ced
Hi Juan. Try "truncate ph_alert". In fact, you should always do this when clearing out a table as it is far quicker and won't ever result in "Long transaction aborted". See also: http://www.oninitgroup.com/ids-11-sysadminalertcleanup-function-bug-fix Regards, Doug Lawry
I would also recommend onchecking the table. It may have corrupt indexes that need to be rebuilt. Art On Dec 14, 2015 06:18, "DOUG LAWRY" <douglawry@hotmail.com> wrote: > Hi Juan. > > Try "truncate ph_alert". In fact, you should always do this when clearing > out > a table as it is far quicker and won't ever result in "Long transaction > aborted". See also: > > http://www.oninitgroup.com/ids-11-sysadminalertcleanup-function-bug-fix > > Regards, > Doug Lawry > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e013c68d66772250526dac0fa
Thank you every one. Truncating table works!!!!
Regards
2015-12-14 8:04 GMT+00:00 Juan Francisco González Navarro <
jfrancisco.navarro@gmail.com>:
> Hello I'm trying to delete rows in ph_alert table doing this sql command:
>
> delete from ph_alerts; (I know this delete every row in the table)>
> In this table there is just 6 rows belonging to 2014, but when i do this i
> get the next mesage
>
> "Could no delete a row, ISAM error not found"
>
> But when I Do a select, there is 6 rows.
>
> However doing a select in ph_alerts I get the next error
>
> " 750: Invalid distribution format found for tk_id"
>
> Dropping distributions with update statistics and add a new one dosn't
> solve the issue. Any clue how to sort this out?
>
> Regards.
>
> --94eb2c06f0aafa99580526d71ced
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--089e0122ab7444f7480526ebe155
Just a FYI you can get LTX when truncating large tables that contain
TimeSeries data as the truncate will need to release container space and that
is a relatively expensive task
Cheers
Paul
Paul Watson
Oninit www.oninit.com
+1 913 387 7529
Oninit® is a Registered Trademark of Oninit LLC
> On Dec 15, 2015, at 02:50, Juan Francisco González Navarro
<jfrancisco.navarro@gmail.com> wrote:
>
> Thank you every one. Truncating table works!!!!
>
> Regards
>
> 2015-12-14 8:04 GMT+00:00 Juan Francisco González Navarro <
> jfrancisco.navarro@gmail.com>:
>
>> Hello I'm trying to delete rows in ph_alert table doing this sql command:
>>
>> delete from ph_alerts; (I know this delete every row in the table)>>
>> In this table there is just 6 rows belonging to 2014, but when i do this i
>> get the next mesage
>>
>> "Could no delete a row, ISAM error not found"
>>
>> But when I Do a select, there is 6 rows.
>>
>> However doing a select in ph_alerts I get the next error
>>
>> " 750: Invalid distribution format found for tk_id"
>>
>> Dropping distributions with update statistics and add a new one dosn't
>> solve the issue. Any clue how to sort this out?
>>
>> Regards.
>>
>> --94eb2c06f0aafa99580526d71ced
>
*******************************************************************************
>> Forum Note: Use "Reply" to post a response in the discussion forum.
>
> --089e0122ab7444f7480526ebe155
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.