Comments
Sort by recent activity
Registry key: Computer\HKEY_CURRENT_USER\Software\Red Gate\Schema Compare for Oracle 5\UI\DefaultOptions2 System upgraded from 5.7.1 (initial install) --> 5.7.2 43 entries including -IgnoreCheckingSchemaExists System upgraded from 5.6.2 --> 5.7.2 (don't see it here either) 42 entries / comments
Registry key:Computer\HKEY_CURRENT_USER\Software\Red Gate\Schema Compare for Oracle 5\UI\DefaultOptions2System upgraded from 5.7.1 (initial install) --> 5.7.243 entries including-IgnoreCheckingSch...
Try a colon (not a space) after the source and target switch /source:FTREC/oracle32?@//172.16.11.250:1521/IRECS{FTREC} /target:FTREC/oracle32?@//172.16.11.247:1521/IRECS{FTREC} / comments
Try a colon (not a space) after the source and target switch/source:FTREC/oracle32?@//172.16.11.250:1521/IRECS{FTREC} /target:FTREC/oracle32?@//172.16.11.247:1521/IRECS{FTREC}
Try a colon (not a space) after the source and target switch /source:FTREC/oracle32?@//172.16.11.250:1521/IRECS{FTREC} /target:FTREC/oracle32?@//172.16.11.247:1521/IRECS{FTREC} / comments
Try a colon (not a space) after the source and target switch/source:FTREC/oracle32?@//172.16.11.250:1521/IRECS{FTREC} /target:FTREC/oracle32?@//172.16.11.247:1521/IRECS{FTREC}
Try a colon : (not a space) after the /source: and /target: switch (May just be the this page rendering) / comments
Try a colon : (not a space) after the /source: and /target: switch(May just be the this page rendering)
If you already have a colon after the source and target switches. You can also try removing the // before the IP address. Is IRECS a Service name or SID? - if a SID try adding the /direct switch (separate switch space delimited) /source:<source connect string> / target:<target connect string> /direct - if a ServiceName try adding the /indirect switch (separate switch space delimited) /source:<source connect string> / target:<target connect string> /indirect / comments
If you already have a colon after the source and target switches.You can also try removing the // before the IP address.Is IRECS a Service name or SID?- if a SID try adding the /direct switch (sep...
See the command line documentation: https://documentation.red-gate.com/sco5/using-the-command-line/command-line-switches#Commandlineswitches-/source:%3Cvalue%3E You're current problem is that you're specifying the server's physical IP address which isn't in you TNSNames.ora file (i.e. it thinks the IP is a TNS names entry). Docs for the direct connection (using host's IP) appear to indicate that you need to specify the service name (DB instance name) after the server host name or IP and before the schema name(s) in the braces {}. (user/pass|/)@host[:port]/service{SchemaA, SchemaB} Alternately if you have an entry (DB instance name) that is in your TNSNames.ora file use that instead of the host IP address with your current syntax and that should work just fine: (user/pass|/)@tns{SchemaA, SchemaB} / comments
See the command line documentation:https://documentation.red-gate.com/sco5/using-the-command-line/command-line-switches#Commandlineswitches-/source:%3Cvalue%3EYou're current problem is that you're ...
See the command line documentation: https://documentation.red-gate.com/sco5/using-the-command-line/command-line-switches#Commandlineswitches-/source:%3Cvalue%3E You're current problem is that you're specifying the server's physical IP address which isn't in you TNSNames.ora file (i.e. it thinks the IP is a TNS names entry). Docs for the direct connection (using host's IP) appear to indicate that you need to specify the service name (DB instance name) after the server host name or IP and before the schema name(s) in the braces {}. (user/pass|/)@host[:port]/service{SchemaA, SchemaB} Alternately if you have an entry (DB instance name) that is in your TNSNames.ora file use that instead of the host IP address with your current syntax and that should work just fine: (user/pass|/)@tns{SchemaA, SchemaB} / comments
See the command line documentation:https://documentation.red-gate.com/sco5/using-the-command-line/command-line-switches#Commandlineswitches-/source:%3Cvalue%3EYou're current problem is that you're ...
Some things to try w/o any guarantee for success: 1) try setting the Behavior option to Use forward Slash 2) try setting the Behavior option to Exclude Schema Names 3) are you executing the drop statement from within the schema that owns the object or are you running as a user w/ a DROP any PRIV?) 4) check your encoding settings: Tools / Application Options -- default is UTF-16 (I haven't had issues w/ that). Oracle SQL developer is a JAVA implementation so UTF16 would likely be most appropriate -- but you can try switching to ASCII (Sorry I use a different SQL IDE, but a SQL script is a SQL script and should behave similarly whether code generated or written from scratch -- check for any subtle syntax differences) / comments
Some things to try w/o any guarantee for success:1) try setting the Behavior option to Use forward Slash 2) try setting the Behavior option to Exclude Schema Names 3) are you executing the drop sta...
Hi Alex, I tested w/ version 5.3.1 and the abortonwarnings behavior appears to be resolved. / comments
Hi Alex, I tested w/ version 5.3.1 and the abortonwarnings behavior appears to be resolved.
The FORCE appears to persist once the object has been modified w/ a FORCE command. That, however, doesn't impact the behavior of the abort on warnings. Even more so, if SCO isn't using FORCE then it follows a drop and re-create pattern for dependent collections.
Since an object is being dropped, the ABORT on WARNINGS should probably be HIGH-- and the commadline exit code identifies it as such, but it doesn't abort before the drop as expected. Version: Schema Compare for Oracle version:5.2.5.1424: activated Command line: "C:\Program Files\Red Gate\Schema Compare for Oracle 5"\sco /source:mbruegel_parameter_Pair2.onp{MBRUEGEL} /target:mbruegel/<PWD>@<DB_INSTANCE>{MBRUEGEL} /excludedependencies /exclude:additional /loglevel:verbose /report:ObjectDiff.html /reporttype:Simple /scriptfile:SCOUpdate.sql /verbose /abortonwarnings:high Echo w/ /abortonwarnings:high echo %errorlevel% 63 Echo w/o /abortonwarnings echo %errorlevel% 61
Source: is Snapshot or Scripts folder (no difference in behavior)
Target Oracle DB: 11.2.0.4.0 / comments
The FORCE appears to persist once the object has been modified w/ a FORCE command.That, however, doesn't impact the behavior of the abort on warnings.Even more so, if SCO isn't using FORCE then it ...