Activity overview
Latest activity by Brian.Lieb
Object reference not set to an instance
Well, after upgrading to Version 3.1.16.2198 Schema Compare gives me this error:
I am unaware of any permission changes on the schema or database for the user that I am using to deploy the changes....
Schema Compare "NO_COMMON_DATA"
Hello, I don't know what happened, but recently someone made a change to a development database that cannot be checked in to source control, or compared against other databases. In fact, the error...
Manual Connection
For some reason, when trying to setup a Manual Connection in Source Control For Oracle v. 3.0.5.1416, one of the users on a VM does not see the drop down to chose a Service Name.
This was fine unti...
Schema Compare and Cross Schema Foreign Key constraints
I have two schemas, and recently I added a foreign key constraint in one schema to a table's primary key in another schema.
For example:
Table 1:
create table schema1.standard_price (
"ID" number(6...
Update:
Thanks for your input. I will definitely keep this in mind for next time. The fix with some background.
As you can probably tell from the above two messages, this database was a development database that I was making changes to before committing to the repository.
As I mentioned, Source Control saw a difference between the source database and the repository. After the initial commit, no matter how many more times I committed that change, I kept getting the error "Nothing to commit" even though the Oracle Source Control kept showing there was something to commit.
So, after reading your message, I realized that I had not used Schema Compare directly, so I checked the repository out to my hard drive using TortoiseSVN.
I then compared the Scripts folder that was made from the checkout to my development database, where it found a difference (again, the diff screen showed no differences).
I deployed that change from schema compare, it dropped and recreated a unique index (with the exact same name and columns).
After the deploy, Schema Compare showed there were no differences between the scripts folder and the database.
I refreshed Oracle Source Control, and it too saw nothing to commit.
Thanks. / comments
Update:
Thanks for your input. I will definitely keep this in mind for next time.The fix with some background.
As you can probably tell from the above two messages, this database was a developmen...
Follow up:
I removed the offending table from the repository using TortoiseSVN.
When I launched Source Control for Oracle, it noticed. I chose the Database Version as the correct version to commit.
I committed it.
===
The Project still shows one difference, but not the diff, and I cannot commit again. / comments
Follow up:
I removed the offending table from the repository using TortoiseSVN.
When I launched Source Control for Oracle, it noticed. I chose the Database Version as the correct version to commit...
Committing issues
So, I have a source control project. I launch Source Control for Oracle and it indicates that the project has 1 chagne to check-in.
When I go to the check-in screen, and look at the item, the 'dif...
Followup:
I removed the project from Oracle Source Control, and re-created it and was able to check the project in without an error.
Unfortunately, this did not fix the problem for all the other users. This is not 'unfixable', but is not very convenient or easy to fix.
I have seen this error before in other SVN clients, and I was able re-checkout the repo to fix it. It seems like something must be out of synch on the local machine. / comments
Followup:
I removed the project from Oracle Source Control, and re-created it and was able to check the project in without an error.
Unfortunately, this did not fix the problem for all the other us...
Hi,
Thanks for the response. I have done this, and things seemed to be working fine for checking out, and then comparing using schema compare.
To be clear the steps I took were
- Checked the repository using Tortoise to two places on my harddrive. (repo1, repo2)
- Used schema compare to 'Update' repo1, which removed the .svn folder and thereby removing the recognition this is an SVN repo from Tortoise
- Copied the contents of repo1 over the top of repo2, making sure to overwrite the files in repo2.
- Checked in repo2.
- Removed all local copies.
- Used Tortoise to checkout again to a folder called repo
- Opened Schema compare and used the repo as the source
VOILA! I don't need to update any more and schema compare works fine.
However, now, when I try to check in changes via Oracle Source Control, I get this error:
Error Some objects were out of date. Review the changes and check in again. Report
When I click the Report link, Source Control crashes with this:
System.NullReferenceException: Object reference not set to an instance of an object.
at
Smartassembly.SmartExceptionsCore.UnhandledExceptionHandler.ReportException(Exception exception, Boolean, continue, Boolean manuallyReported)
I can probably destroy the entire repository and start over from the schema, but that is not a palatable option. Is there any suggestion on how to proceed? / comments
Hi,
Thanks for the response. I have done this, and things seemed to be working fine for checking out, and then comparing using schema compare.
To be clear the steps I took were
- Checked the repos...
Schema Compare/Source Control
I am not totally sure where to post this, but I have a question at the Schema Compare for Oracle (3.0.7.736) and Source Control for Oracle (2.0.7.1037) border.
So, the deployment process that I hav...