I was very concerned about exceptions, how they are thrown and handled. I define a proper error code before throwing some error. I never been to a production site, but this time I got a chance to be a implementation team. The way I handled my exceptions seems to be incomplete. Though, my error messages in exception was good, but it still missing a feature, which could help production people. Many of you might not aware of the very fact that, the logging level is severe in production. Then way you log the data in the codes is always helpful, but try to handle your error message for exceptions efficiently that you need not to enable logging to finer levels to analyze the issue. The errors must be self explanatory. Analyze the code snippet mentioned below: public void fetchCurrencyOffset(String bankCode, String branchCode, String currencyCode1, String currencyCode2) { try { ...
Posts
I was testing some piece of code for calculation of new date on the basis of a given pattern and the specified date. I wrote a method to automate the test cases to generates those patterns and calculate the new date for each date of the specified date of the range of years. Since there were around 1 million pattern test cases are possible, so I want to insert this data in database for any future reference. After creating a pattern I was inserting data of the pattern and the calculation date along with the calculated date. It was working fine. I was prepare to hit the start button now, after testing different patterns individually. I hit the run button and it started its executions, but in the middle, I got this error. java.sql.SQLException: Listener refused the connection with the following error:ORA-12516, TNS:listener could not find available handler with matching protocol stack at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:4...
In development environment we have access to the database in the read and write mode, where we can play with tables. Instead of writing simple queries to update any tuple, we use for update functionality of the PL/SQL. But it is a bad idea, since we are blocking other users who are operating on the same table, since for update table the lock on the full table, and noone is allowed to perform any operation untill the lock is released. select * from table_name for update; Instead of the above query write a simple update query. update table_name set column_to_set = value_to_set where column_where_condition = value_where_condition; This is better idea to practice, or you can simple create a query as mentioned below : update &table_name set &to_set_column_name = &value_to_set_column_name where &where_column_name = &value_where_column_name; This will help the user to input all the details at runtime. But still in the testing environment, when the developers don...
As mentioned in the earlier tips, outer join can be done by 3 different techniques. But, from Oracle 10g onwards, Oracle has started to provide the fourth technique to handle the outer join. · Nested loop outer join · Hash outer join · Hash outer right join (from Oracle 10g onwards) · Merge outer join Hash outer right join has been provided by Oracle from 10g version onwards. This technique has been introduced in order to overcome the design flaw of hash outer join. As per the definition of hash outer right join, the smallest of the two tables (where-in outer join is used) will be used to build the hash table, and the other table will be used as the probe table unlike hash outer join, wherein the size of the tables doesn’t play any role and the parent & child table must be used as hash ...