"Invalid bytes count" popup on previously working saved project (Manual Connection)

edkiern

I have a saved .ocp file that specifies a comparison setup in Schema Compare for Oracle.  opening it and running it has previously worked.  I have tried several projects from RedGate Schema Compare 6 (I also updated to 6.3 this morning) - all attempts to all databases (3 Oracle DBs, 4 envs each, I tried 8 different projects ) are all failing with the popup "Invalid bytes count".  This occurs when clicking test to validate the credentials.

Searching Google and the forums failed me - Obviously, from the popup, there is something wrong with the number of bytes here, but I couldn't find any details in logs to determine if this is a RedGate problem or Oracle DB driven issue.  Since I can connect to each of the DBs without issue from the same machine where running RedGate softare, my current assumption is RedGate is where the solve will occur.

Looking for any thoughts on what could drive this or information on where I should be able to find logs tied to this failure.

I tried using the "standard" installation as well as the 32 bit (on 64 bit arch)

I could not find any logs that align within the timing of the experience in \users\<USERNAME>\AppData\RedGate or EventViewer for Windows (you never know). 

Oracle 19c DBs all of them.

Jon_Kirkwood

Hi @edkiern

 

Thank you for reaching out on the Redgate forums regarding your Oracle Schema Compare concern.

 

We have received a few reports of this bug coming through due to an issue in Oracle V19.24. A bug report is submitted with our developers, who are working on a fix.  

 As a possible workaround in the interim, we have a client who has found the following worked for their environment. This may be useful for you to try whilst a formal fix is implemented into Schema Compare:

 We were able to replicate this error on Schema Compare for Oracle 6 (desktop version) on the PC which had no Oracle client and your app was configured to connect to our server via Manual Connection tab. When we have Oracle Client installed and configured, using Manual Connection tab or TNS Connection tab connections were successful. After researching the network we found that other companies had faced the same issue. Here is a link to this problem:
Oracle 19.24 + ASO + DirectMode (devart.com)
 
We have solved it by disabling this parameter on our database server in sqlnet.ora file:
#SQLNET.ENCRYPTION_SERVER = requested
#SQLNET.ENCRYPTION_TYPES_SERVER = (AES128)
#SQLNET.CRYPTO_CHECKSUM_SERVER = requested
#SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (SHA256,SHA1)

 

Please note this workaround is made within your environment and not within any Redgate product, we suggest appropriate backups in the event the fix needs to be reverted.

If you are using an earlier version of Oracle please advise as this may not be connected to this bug, and we will need to investigate further.

edkiern

We tried this, and it sadly didn't work.  Most of those settings were already in place as well.

I guess I can try working with TNS connections, but that will require installing the Oracle Tools.  I'll work with my DBA group to figure this out next I suppose.

Any other advice out there?

edkiern

Well that's interesting.  I installed all the client tools for Oracle 19 in order to start setting up TNS route, and now the Manual Connection method is working.  I cannot say for sure why it is working now, but it is.

aliajmal

It sounds frustrating! The "Invalid bytes count" error could stem from character set mismatches or configuration issues in RedGate. Have you checked for updates on Oracle client libraries or examined the environment variables for inconsistencies? Logs might also be hidden deeper in the RedGate folder.

Jon_Kirkwood

Hi there, our developers have announced that the root cause of this issue was patched recently by Oracle and has been implemented into our recent release of Source Control for Oracle.

We recommend patching into V6.3.13 and verify if this issue is now resolved for you

Download link for this version:
https://download.red-gate.com/checkforupdates/SchemaCompareforOracle/SchemaCompareforOracle_6.3.13.2952.exe

Patch notes:
https://forum.red-gate.com/discussion/91082/additional-object-dependency-information

Schema Compare for Oracle 6.3 release notes
Version 6.3.13 - November 13th, 2024
Features

• ZD-319118: Resolved an issue with connecting to Oracle 19 and higher in Direct mode when using Oracle Encryption or Oracle Data Integrity

henery6547

The "Invalid bytes count" error in a previously working saved project, particularly in the context of a manual connection, typically suggests an issue with how data is being read, written, or interpreted by the application you're working with. It could be related to corrupted project files, changes in the underlying data format, or network-related problems if the manual connection involves communication with a remote system.

To troubleshoot the issue, try the following steps:

1. Check for Data Corruption

• Corrupted File: If the project file itself is corrupted, the application might struggle to interpret the data correctly, resulting in an "Invalid bytes count" error. Try restoring an older version of the project, if possible.
• Re-save the Project: Open the project, make a small change, and save it again. This can sometimes clear up discrepancies in data formatting.

Anay365

The "Invalid bytes count" error in a previously working saved project, particularly in the context of a manual connection, typically suggests an issue with how data is being read, written, or interpreted by the application you're working with. It could be related to corrupted project files, changes in the underlying data format, or network-related problems if the manual connection involves communication with a remote system.

To troubleshoot the issue, try the following steps:

1. Check for Data Corruption

• Corrupted File: If the project file itself is corrupted, the application might struggle to interpret the data correctly, resulting in an "Invalid bytes count" error. If possible, try restoring an older version of the project.
• Re-save the Project: Open the project, make a small change, and save it again. This can sometimes clear up discrepancies in data formatting.