|
Problem IT42880
|
Status: Closed |
ARCHECKER UNABLE TO LOCATE OBJECT WHILE RESTORING LOGICAL LOGS AND GETTING BSAGETOBJECT FAILED WITH 3 ON AMAZON S3
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
Customer has an issue of restoring Logical logs from S3 bucket
location using archecker table level restore utility
What we have done is listed in below:
1) Setup both 'LOGPOOL' and 'DBSPOOL' devices to CLOUD path
2) Took 2 L0 full backups to S3 bucket Location.
3) Generated some logical logs (512, 513 in our case)
4) Trying to restore a single table using the above backup(s)
with below archecker command
 archecker Command using in it is --> archecker -bdvs -f
/arch.txt
5) Getting the below error:
Path /aws/*/512
Resource L
CRITICAL ERROR: Unable to locate object.
BSAGetObject failed with 3 (System error), pid=2355865
----
We suspect 'archecker internal call to get the logical log
folder path
 --> /aws/*/512' does not recognize by underline CLI call to
get logical logs.
Please see, 'aws_s3_cli_call_test.png' file for more detail.
We can get the S3 backed-up Logical log '512' object using
'/aws/0/512' call but not with '/aws/*/512' call... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* see Error Description *
****************************************************************
* PROBLEM DESCRIPTION: *
* see Error Description *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* see Error Description *
****************************************************************
* PROBLEM DESCRIPTION: *
* see Error Description *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Comment |
see Error Description |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.01.2023
02.10.2023
02.10.2023 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
