No JSON Object Could Be Decoded In Dbsat
(Doc ID 2770057.1)
Last updated on FEBRUARY 23, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 19.1.0.0.0 version, Database Security
ACTUAL BEHAVIOR
---------------
No JSON object could be decoded in dbsat
When generating the report with dbsat “pdb1_output.zip“ for a version 19c container database, it generates the following error:
[oracle @ probd20 dbsat] $ ./dbsat report pdb1_output
Database Security Assessment Tool version 2.2.1 (May 2020)
This tool is intended to assist you in securing your Oracle database
system. You are solely responsible for your system and the effect and
results of the execution of this tool (including, without limitation,
any damage or data loss). Further, the output generated by this tool may
include potentially sensitive system configuration data and information
that could be used by a skilled attacker to penetrate your system. You
are solely responsible for ensuring that the output of this tool,
including any generated reports, is handled in accordance with your
company's policies.
Archive: pdb1_output.zip
[pdb1_output.zip] pdb1_output.json password:
inflating: pdb1_output.json
Unable to process input file: pdb1_output.json
No JSON object could be decoded
Error: Unexpected error occurred while running DBSAT Reporter.
[oracle@probd20 dbsat]$
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |