boneimre  any suggestion ?

If you suspect that the SA DB schema was manipulated/modified by mistake then you could review the fields of the TRUTH.WAY_SCRIPTS and TRUTH.WAY_SCRIPT_VERSIONS tables. These tables are the ones being updated when when failure happens.

Taking forward the investigation from the side of the application will be possible only if you upload log files. I suggest that you open a support ticket and provide the /var/log/opsware/waybot/* , /var/log/opsware/spin/* and /var/log/opsware/install_opsware/* logs.

Did this ever get resolved? Ran into the same error in my dev lab. Spin.err shows:

spinerror.DBUniqueConstraintError: <Error(spin.DBUniqueConstraintError): DB unique constraint violated on fields ['way_script_id', 'version'] in table 'way_script_versions' while executing 'INSERT INTO way_script_versions (way_script_version_id, way_script_id, version, status, policy, comments, upload_dt, uploaded_by, script_digest, signature, tran_id, conflicting) VALUES (5520003, :p1, :p2, :p3, :p4, :p5, TO_DATE(:p6, 'DD-MON-YYYY HH24:MI:SS'), :p7, :p8, :p9, :p10, :p11)' with arguments (190001, 'SA.90.0.95037.0', 'APPROVED', 'PTY 0\nUSER root\nEXEMPT\nPERM agentDeployment.scanNetwork\n\n', "Don't toss stderr", '25-SEP-2024 12:50:08', 'opsware', 'SHA256:sa9cRpg3+mXCXUsKUgXEWycRtwTzNOd+j9+MSPXCL/o=', '$$$', None, 'N')>

Hi Sharp_2  , Yes it got resolved for me.

Initially, the database character set was configured to UTF-8. However, due to incompatibility with SA24.1, it was necessary to switch to AL32UTF8. I believe the database team performed a bounce and recreation of the database to implement this change effectively.

Thank-you. Although the upgrade guide states this, I was hoping to avoid it...

Ensure the Oracle character set is supported

If your environment uses Oracle databases you must ensure that NLS_CHARACTERSET is set to AL32UTF8 on all of them.

SA does not support the UTF8 Oracle database character set anymore.