Toad 9.0 with Oracle 11g

Here are my two cents on connectivity issues between Toad and Oracle 11g...

Everyone knows about Toad and is the most widely used tool for connecting to Oracle databases. We use Toad all the time to connect to Oracle 10g databases. But recently we upgraded one of our environments to Oracle 11g and Toad stopped working. (Dont we have such issues all the time?)

Basically this is the issue:
I tried connecting to Oracle 11g using Toad 9.1 and it popped an error saying invalid username/password. So i used SQL Plus, Native connection of Oracle and tried connecting it to 11g environment and expected i will get the same error, but guess what SQL Plus got connected.

So Toad was unable to connect and SQL Plus got connected. Then i installed SQL Developer and again surprisingly SQL Developer also got connected using the same tnsnames.ora file. So there was something going on with Toad; which i needed to find out.

So basically this was the issue

In Oracle 11g, we have a variable called SEC_CASE_SENSITIVE_LOGON which says whether case sensitivity should be enabled for password or not during the logon

And keep in mind this was introduced only in Oracle 11g and none of the previous versions of Oracle had this parameter for the "password case sensitivity".

Now if sec_case_sensitive_logon = true, Password case sensitivity matters
and if sec_case_sensitive_logon = false, Password case sensitivity does not matters.

Now issue on the Toad side, it converts all the passwords to Uppercase(which is a bug in Toad 9.0). So the workaround is while connecting using Toad, enter username and keep the password field blank and Toad will prompt a dialog box asking for password, and then enter the password...and there you go..You successfully connected to Oracle 11g.

Or the other solution is change the sec_case_sensitive_logon and set it to False, using the following query
alter system set sec_case_sensitive_logon=false


Just sharing my knowledge....as i learn

Nilesh Makhija

Multiple Data Feeds in Kalido 8.5

As we have seen in most of the Data Warehousing projects, we try to run the reference data loads in parallel and increase the number of threads so that we can maximize the resources allocated to the Database Server. With Kalido also we can run the parallel loads but we need to keep a small thing in mind that we cannot run the parallel loads on the same object in Kalido Warehouse. Meaning; if we have a GL Account CBE and this CBE is being seeded from two source Systems SRC1 and SRC 2, we cannot run the loads from the 2 source systems at the same time. For sure these can run back to back but not in parallel with each other. And the reason for this is Kalido locks the object and only one load can update that object(in our example GL Account CBE). So if we try running another load while one load is in progress,the second load will error out. Consider yourself lucky, as Kalido generates a log file which can be decrypted by a human being with an error message "Another Load is in Progress".

So if we have feeds from various source systems loading data into the CBE, they should be executed sequentially. A dependency has to be build saying that when one load is complete, trigger the next load on the same object. For sure we can execute the different feeds for different objects and in that way parallelism can be achieved but not on the same object. We could increase the number of threads while loading the data, but not greater than 4(loads start degrading after 4)

So the thought for the day is "Never Ever run multiple data feeds on the same object in Kalido at the same time"


As usual Enjoy working with this great tool....

Nilesh Makhija