Hot answers tagged oracle
You created your column with double quotes, so now Oracle requires you to always refer to this column using identifiers and respecting the case. If you remove the double quotes, Oracle always transforms the name to upper case, so without them it is case insensitive. This will work if you created the column without identifiers: where rulE_id where RULE_ID ...
Edition-Based Redefinition is perfect for this. You define schema changes in a new edition, along with procedures that are used to migrate the data between the base and new edition/schema. Switching between the two is seamless and can be done with zero downtime. There's a good demo on the Oracle Base blog.
There are a lot of ways to do this one that go beyond what I listed, but here's a start. 1) You could try the SQL Server Migration Assistant for Oracle. It's free and usually works well for me for smaller or medium sized datasets. http://www.microsoft.com/en-us/download/details.aspx?id=28766 2) Create a SSIS package. 3) You could create a linked server ...
Had the same issue. Turned out to be a firewall issue. Here is how I turned it off: As root in terminal: chkconfig iptables off chkconfig ip6tables off service iptables stop service ip6tables stop Then modify /etc/selinux/config and set SELINUX=enforcing to SELINUX=disabled. A more elegant solution is to open the 1521 port in the firewall. You can do that ...
Only top voted, non community-wiki answers of a minimum length are eligible