Error when comparing databases

• 
  Hello,
  
  Thanks for your post.
  
  We've just released a new build that includes a 'direct connection' option that connects via TCP/IP instead of through the Oracle client.
  
  The option is in the Application Options, called "Use direct connection".
  
  Can you give it a try and let us know if it helps with the ORA-03113?
  
  Thanks,
  
  Alice.

  Alice E January 12, 2010 06:21

  - 0 +
• 
  Thanks, I gave that a try and I get a little further but I still get an error
  
  ORA-00904: "P"."OBJECT_TYPE": invalid identifier

  jspibey January 12, 2010 08:19

  - 0 +
• 
  To help us track down what's going on, can you turn on logging and send us the log file?
  
  This help file explains how to turn on logging:
  http://www.red-gate.com/supportcenter/C ... ta_Compare\knowledgebase\logging_and_log_files.htm
  
  If you send the log to me at alice.easey@red-gate.com, that'd be great.
  
  Thanks,
  
  Alice.

  Alice E January 12, 2010 08:34

  - 0 +
• 
  I've sent you the log file via email
  
  Thanks

  jspibey January 12, 2010 08:46

  - 0 +
• 
  1.0.0.475 - I only downloaded it an hour or two ago but it was an upgrade of a previous version

  jspibey January 12, 2010 09:28

  - 0 +
• 
  Thanks for sending the logs across.
  
  We've identified the issue as being a problem with the way we're handling PL/SQL objects in dependent schemas not included for comparison.
  
  We've got a fix for this that will be in the next EAP build (unfortunately we don't have any timescales for that yet).
  
  In the meantime, a workaround would be to make sure your comparison includes all the schemas that are referenced by the objects you want to compare (so, if you're comparing a table in SchemaA that references a procedure in SchemaB, make sure you include SchemaB for comparison).
  
  Hopefully that should fix the problem - please let us know if it doesn't or if you have any other feedback for us.
  
  Thanks,
  
  Alice.

  Alice E January 12, 2010 09:46

  - 0 +
• 
  Thanks for the quick reply. I tried adding in the other schemas which were referenced but couldn't get any further. I'll wait for the next build before I look at it again

  jspibey January 13, 2010 04:54

  - 0 +
• 
  Same problem here with "P"."OBJECT_TYPE". Will also wait for the newest build to see if we can come across. Thanks

  jcossio February 08, 2010 09:02

  - 0 +
• 
  jcossio - is 'P' an actual schema in your database, or a synonym for that schema?

  Michelle T February 09, 2010 06:25

  - 0 +
• 
  We do not have a schema or synonym called P on our database. It would be strange if I had the same stuff as jspibey that also pointed out this same issue ("P"."OBJECT_TYPE") at the beginning of this thread.
  Thanks anyway.

  jcossio February 09, 2010 08:04

  - 0 +
• 
  We've just released our new early access build.
  
  We've made a lot of improvements around dependencies and general stability, and would hugely appreciate it if you could give it a try and let us know if it resolves your issues.
  
  You can download the new build here.
  
  Thanks,
  
  Alice.

  Alice E March 10, 2010 12:03

  - 0 +
• 
  Gave it a try and got an error on the fourth step "Comparing Databases". it says "An item with the same key has already been added." and aborts the process. Logs have been sent to Alice

  jcossio March 10, 2010 15:20

  - 0 +
• 
  We've tracked this down to an error registering the WMSYS schema which we've fixed in the latest build (1.0.0.681).
  
  Can you give this new build a try and let us know if it fixes the problem?
  
  Thanks,
  
  Alice.

  Alice E March 16, 2010 12:49

  - 0 +

Add comment

Please sign in to leave a comment.