ECS:Oracle RMAN 应用程序在升级到 ECS 3.8.0.1 - 3.8.0.4 后遇到 HTTP 501 错误

Summary: 由于 ECS 回归,在升级到 ECS 3.8.0.1 - 3.8.0.4 后,Oracle Recovery Manager (RMAN) 备份应用程序可能会遇到 HTTP 错误 501“Not Implemented”。

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

升级到 ECS 3.8.0.1 - 3.8.0.4 后,如果请求中使用的所有参数不在 ECS 内部支持列表中,则应用程序请求可能会失败并显示 HTTP 错误“501 Not Implemented”。
  • Oracle Recovery Manager (RMAN) 备份应用程序已确认受此问题的影响。 
  • 如果直接写入 ECS,此问题会影响 Oracle RMAN。如果 Oracle RMAN 通过另一个应用程序写入 ECS,则它不会受到影响。 
  • 如果其他应用程序使用类似的配置(其中请求中的所有参数不属于受支持列表的一部分),则可能会受到影响。 
 
RMAN 上出现错误:
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 11/20/2023 15:15:13 ORA-19506: failed to create sequential file,
name="DB_FIP_20231120_mj2bv7g0_503507_1_1", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: non RMAN, but media manager or vendor specific failure, 
error text: KBHS-01404: See trace file /soft/oracle19/diag/rdbms/fip/fip/trace/sbtio_25047_140117933847552.log for details KBHS-00700: HTTP response error 'Not Implemented'

验证 ECS 上的问题:

命令:
svc_log -f "does not support operation with signature B" -start '<Timeline errors received in ECS> -sr dataheadsvc -n all -sf

示例:
# svc_log -f "does not support operation with signature B" -start '1 hours ago' -sr dataheadsvc -n all -sf
svc_log v1.0.31 (svc_tools v2.14.0)                 Started 2023-11-22 15:34:17

Running on nodes:              <All nodes>
Time range:                    2023-11-21 03:34:17 - 2023-11-22 15:34:17
Filter string(s):              'does not support operation with signature B'
Show filename(s):              True
Show nodename(s):              True
Search reclaim logs (if any):  False

169.254.1.5 dataheadsvc.log.20231121-134402.gz 2023-11-21T12:01:51,006 [qtp379782668-6225-88a5e8cf:18bedd2e9f0:d5e:4-s3-136.165.238.100] 
ERROR  S3Service.java (line 638) does not support operation with signature B?not-implemented, request Id 88a5e8cf:18bedd2e9f0:d5e:4

以requestID为例,进一步跟踪错误如下:

Command:
# svc_log -f "request ID highlighted from previous step" -sr dataheadsvc dataheadsvc-access -start <Timeline of requestID> -sf
示例:
#svc_log -f "88a5e8cf:18bedd2e9f0:d5e:4" -sr dataheadsvc dataheadsvc-access -start 1h -sf
svc_log v1.0.31 (svc_tools v2.14.0)                 Started 2023-11-22 15:45:40

Running on nodes:              <All nodes>
Time range:                    2023-11-21 03:45:40 - 2023-11-22 15:45:40
Filter string(s):              '88a5e8cf:18bedd2e9f0:d5e:4'
Show filename(s):              True
Show nodename(s):              True
Search reclaim logs (if any):  False

<output truncated>
.
.
169.254.1.5 dataheadsvc.log.20231121-134402.gz 2023-11-21T12:01:51,006 [qtp379782668-6225-88a5e8cf:18bedd2e9f0:d5e:4-s3-136.165.238.100] 
ERROR  S3Service.java (line 638) does not support operation with signature B?not-implemented, request Id 88a5e8cf:18bedd2e9f0:d5e:4

169.254.1.5 dataheadsvc-access.log 2023-11-21 12:01:51,007 88a5e8cf:18bedd2e9f0:d5e:4 136.165.232.207:9020 136.165.238.100:4249 dba-rman-prod - HEAD ul-rman-prod ul-rman-prod-01 
ul-rman-prod-01 format=xml&x-BlockSize=262144&x-CopyNumber=0&x-Dbid=808640723&x-Dbname=RCAT&x-FileName=DB_RCAT_20231121_1i2c0uuu_63538_1_1&x-Incarnation=fpC63dLILKPb&x-NetTest=FALSE&x-Node=node1.hostname&x-OpenTime=2023-11-21%2012%3A01%3A51
&x-ReqCnt=34&x-ReqTime=2023-11-21%2012%3A01%3A51&x-SbtApi=sbtbackup&x-SbtOp=BeginUpload&x-SbtVersion=19.0.0.1&x-SessionId=0AA9580D05342089E063F7EDA5880453&x-System=Linux%20x86%2064-bit&x-
SystemId=13&x-User=oracle HTTP/1.1 501 2 - - 1 - - - - 'x-amz-date: 20231121T120151Z' 'Connection: close' 'X-Amz-Content-SHA256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
.
.
<output truncated>

Cause

此问题是由于 ECS STORAGE-28517 中引入的回归所致。
  1. 如果应用程序未使用任何参数,则不会遇到 HTTP 501 错误。 
  2. 如果应用程序使用参数:
    1. 如果您使用的是受支持参数列表(如下所示)中的至少一个参数,则不会报告 HTTP 501 错误。 
    2. 如果查询中使用的所有参数不在支持的参数列表中,则会报告 HTTP 501 错误。 
下面是支持的参数列表。如果您的应用程序在向 ECS 查询时未使用这些参数中的任何一个,则会报告 501 错误。
 
“acl”,
“lifecycle”,
“object-lock”,
“enable-object-lock”,
“location”,
“logging”,
“notification”,
“policy”,
“requestPayment”,
“torrent”,
“delete”,
“uploadId”,
“uploads”,
“versioning”,
“versions”,
“website”,
“tagging”,
“cors”,
“accessmode”,
“fileaccess”,
“ping”,
“cors”,
“endpoint”,
“isstaleallowed”,
“query”,
“replication”,
“replicationInfo”,
“legal-hold”,
“retention”,
“retentionUpdate”,
“searchmetadata”,
“snapshot”,
“snapshots”,
“snapshotId”,
“empty-bucket-status”,
“select”,
“detailedReplicationStatus”

Resolution

从 ECS 3.8.0.5 开始,此问题已得到修复。
  • 如果在升级到 ECS 3.8.0.1 - 3.8.0.4 后受到此问题的影响,请向技术支持部门创建案例以获取修复。
  • 如果使用 Oracle RMAN 并计划升级到 ECS 3.8.0.1 - 3.8.0.4,请在规划升级时通知 Services,以便他们请求用于升级的特殊修补程序。此特殊修补程序将修复此问题。 
    提醒:由于此问题已在较新的代码中得到修复,因此建议升级到具有修复的版本。 

Affected Products

ECS, ECS Appliance, ECS Appliance Gen 1, ECS Appliance Gen 2, ECS Appliance Gen 3, ECS Appliance Hardware Series, ECS Appliance Software with Encryption, ECS Appliance Software without Encryption, ECS Software, Elastic Cloud Storage
Article Properties
Article Number: 000219799
Article Type: Solution
Last Modified: 11 Mar 2024
Version:  8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.