SRM 5.0: A tarefa de otimizar tabelas não é concluída nos servidores back-end do SRM após a atualização para o SRM 5.0
Summary: As tarefas optimize-tables-apgX falham com o estado 15 após a atualização do SRM para a versão 5.0.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Taskrun Os logs da tarefa Tabelas otimizadas mostraram os seguintes erros:
yymmdd 09:51:38 : Starting task optimize-tables-apg2. yymmdd 09:51:38 : Starting execution of subtask number 1. yymmdd 09:51:38 : Terminate method (terminate) could not be found within the class. Task execution won't be notified if destroyed. yymmdd 09:51:38 : yymmdd 09:51:39 : May 01, 2024 9:51:39 AM com.watch4net.apg.v2.mysql.utils.MySqlCommandRunner main yymmdd 09:51:39 : INFO: Executing 'query' ... yymmdd 09:51:39 : May 01, 2024 9:51:39 AM com.watch4net.apg.v2.mysql.utils.MySqlCommandRunner main yymmdd 09:51:39 : INFO: MysqlcommandRunner:: main -connection obj- <<mysql8>>:com.watch4net.apg.v2.mysql.utils.data.MySqlConfiguration@19e1023e yymmdd 09:51:40 : Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary. yymmdd 09:51:40 : May 01, 2024 9:51:40 AM com.watch4net.apg.v2.mysql.utils.runner.LogQueryRunner update yymmdd 09:51:40 : INFO: LogQueryRunner::update conn <<mysql8>>: com.mysql.cj.jdbc.ConnectionImpl@29176cc1 yymmdd 09:51:40 : May 01, 2024 9:51:40 AM com.watch4net.apg.v2.mysql.utils.runner.LogQueryRunner update yymmdd 09:51:40 : INFO: LogQueryRunner::update sql <<mysql8>>: OPTIMIZE TABLE data_variable yymmdd 09:51:40 : May 01, 2024 9:51:40 AM com.watch4net.apg.v2.mysql.utils.runner.LogQueryRunner update yymmdd 09:51:40 : INFO: LogQueryRunner::update params <<mysql8>>: null yymmdd 09:51:40 : May 01, 2024 9:51:40 AM com.watch4net.apg.v2.mysql.utils.runner.LogQueryRunner update yymmdd 09:51:40 : INFO: OPTIMIZE TABLE data_variable -> 0.012 (0.012) yymmdd 09:51:40 : May 01, 2024 9:51:40 AM com.watch4net.apg.v2.mysql.utils.command.SqlQuery execute yymmdd 09:51:40 : SEVERE: error executing query: OPTIMIZE TABLE data_variable yymmdd 09:51:40 : java.sql.SQLException: Can not issue executeUpdate() or executeLargeUpdate() with statements that produce result sets Query: OPTIMIZE TABLE data_variable Parameters: [] yymmdd 09:51:40 : at org.apache.commons.dbutils.QueryRunner.rethrow(QueryRunner.java:359) yymmdd 09:51:40 : at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:428) yymmdd 09:51:40 : at com.watch4net.apg.v2.mysql.utils.runner.LogQueryRunner.update(LogQueryRunner.java:68) yymmdd 09:51:40 : at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:484) yymmdd 09:51:40 : at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:449) yymmdd 09:51:40 : at com.watch4net.apg.v2.mysql.utils.command.SqlQuery.execute(SqlQuery.java:49) yymmdd 09:51:40 : at com.watch4net.apg.v2.mysql.utils.MySqlCommandRunner.main(MySqlCommandRunner.java:236) yymmdd 09:51:40 : at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) yymmdd 09:51:40 : at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) yymmdd 09:51:40 : at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) yymmdd 09:51:40 : at java.lang.reflect.Method.invoke(Method.java:498) yymmdd 09:51:40 : at com.watch4net.component.loader.util.ComponentLauncher.invoke(ComponentLauncher.java:108) yymmdd 09:51:40 : at com.watch4net.component.loader.util.ComponentLauncher.main(ComponentLauncher.java:49) yymmdd 09:51:40 : at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) yymmdd 09:51:40 : at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) yymmdd 09:51:40 : at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) yymmdd 09:51:40 : at java.lang.reflect.Method.invoke(Method.java:498) yymmdd 09:51:40 : at com.watch4net.apg.scheduler.executor.JavaTaskProcessMain.callExecuteMethod(JavaTaskProcessMain.java:538) yymmdd 09:51:40 : at com.watch4net.apg.scheduler.executor.JavaTaskProcessMain.main(JavaTaskProcessMain.java:130) yymmdd 09:51:40 : yymmdd 09:51:40 : Execute method (main) exited with a failure error code of -1 yymmdd 09:51:40 : Execution of subtask number 1 failed with status 15. yymmdd 09:51:40 : Execution of task sequence with name optimize-tables-apg2 did not complete. Only 1 subtasks out of 2 were executed. yymmdd 09:51:40 : Task optimize-tables-apg2 failed with status 15.
Cause
O processo de atualização do SRM 5.0 requer uma atualização do mecanismo MySQL do myISAM para o InnoDB. Para esse efeito, esta tarefa já não é necessária e pode ser desativada. A tarefa não está desativada de imediato e tem de ser desativada manualmente. A pasta
A situação está documentada na Página do Produto SRM de Suporte da Dell, nas Notas de Versão M&R 8.0.0.0; HTLM ou formato PDF.
optimize-tables.task não é mais necessário para tabelas InnoDB.
A situação está documentada na Página do Produto SRM de Suporte da Dell, nas Notas de Versão M&R 8.0.0.0; HTLM ou formato PDF.
Resolution
Para desativar a tarefa de tabelas otimizadas, aceda à IU do SRM e siga os passos abaixo:
- Inicie sessão na IU de Frontend do SRM e aceda à página Admin
- Em Visão geral físicadoméstica>, clique no host de back-end principal
- Clique em Tasks > mysql-maintenance-tool/Default/optimize-tables.task
- Clique em Desativar para desativar a tarefa
- Clique em Página Inicial novamente e clique em cada back-end adicional
- Clique em Tarefas>Desativar as tarefas para cada back-end
- mysql-maintenance-tool/apg1/optimize-tables.task
- mysql-maintenance-tool/apg2/optimize-tables.task
- mysql-maintenance-tool/apg3/optimize-tables.task
- mysql-maintenance-tool/apg4/optimize-tables.task
Article Properties
Article Number: 000225706
Article Type: Solution
Last Modified: 05 Jun 2024
Version: 1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.