SRM 5.0: SRM 5.0으로 업그레이드한 후 SRM 백엔드 서버에서 테이블 최적화 작업이 완료되지 않음

Summary: SRM을 버전 5.0으로 업그레이드한 후 optimize-tables-apgX 작업이 실패하고 상태 15가 표시됩니다.

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.
Check out other resources

Symptoms

Taskrun 최적화된 테이블 작업에 대한 로그에 다음과 같은 오류가 표시되었습니다. 
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

SRM 5.0 업그레이드 프로세스를 수행하려면 MySQL 엔진을 myISAM에서 InnoDB로 업데이트해야 합니다. 이를 위해 이 작업은 더 이상 필요하지 않으며 사용하지 않도록 설정할 수 있습니다. 작업은 기본적으로 비활성화되지 않으며 수동으로 비활성화해야 합니다. 비디오 optimize-tables.task InnoDB 테이블에는 더 이상 필요하지 않습니다.

상황은 Dell 지원 SRM 제품 페이지의 M&R 8.0.0.0 릴리스 노트에 설명되어 있습니다. HTLM 또는 PDF 형식으로 저장합니다.

Resolution

최적화된 테이블 작업을 비활성화하려면 SRM UI로 이동하여 아래 단계를 따릅니다.
  1. SRM Frontend UI에 로그인하고 Admin 페이지로 이동합니다.
  2. HomePhysical >Overview에서 운영 백엔드 호스트를 클릭합니다
  3. Tasksmysql-maintenance-tool>/Default/optimize-tables.task를 클릭합니다. 
  4. Disable을 클릭하여 작업을 비활성화합니다.
  5. Home을 다시 클릭하고 각 추가 백엔드를 클릭합니다
  6. TasksDisable> 작업을 클릭합니다. 각 백엔드에 대한 작업
    • mysql-유지 관리 도구 / apg1 / optimize-tables.task
    • mysql-유지 관리 도구 / apg2 / optimize-tables.task
    • mysql-유지 관리 도구 / apg3 / optimize-tables.task
    • mysql-유지 관리 도구 / 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.