CONCURRENCY CONTROL IN DBMS

My Detailed Curriculum Vitae

Shambhu Kumar Jha                     

(Work Exeperience : 17 Years +)

Amity Institute of Information Technology                                        

Amity University, NOIDA, India                                                        

Mobile –919810625752                                                    

E-Mail: shambhukjha@yahoo.com, skjha24081970@gmail.com

1.     ACADEMIC QUALIFICATION

Award/ Qualification                                    Course	Awarding Body (Institute/University)	Year	Degree / Class ( Grade Point / Percentage )	Date of Award
PhD	Mewar  University (Dept of Computer Science and Studies) , India	2013-2016	PhD Course Work (CGPA: 6.67/10) (1st Class)	(Pursuing)
Master of Computer Applications	National Institute of Technology, Jamshedpur, Ranchi University,   India	1994-1997	(CGPA: 7.4/10) (1st Class)	July 1997
Bachelor of Science (B.Sc.)	B.R. Ambedkar  Bihar University, Muzaffarpur, India	1988-1991	67% (1st Class)	Dec-1992
Senior Secondary (10+2)	Bihar University, Muzaffarpur India	1986-1988	58.77% (2nd Class)	July-1988
Higher Secondary  (10th )	Bihar School Examination Board, Patna , India	1984-1986	66.87% (1st Class)	July-1986

2. EMPLOYMENT SUMMARY:

Having more than sixteen years of experience in Classroom teaching / Training / Online teaching, Academic planning and administration in various reputed institutions /University including NIT Jamshedpur , BHU Varanasi  , Amity University  Noida  , IGNOU New Delhi  at PG and UG levels excluding one year of experience in industry as software developer /Trainer.

Employer	Job Title	Period of Appointment
Amity Institute of Information Technology, Amity University,   NOIDA, India	Assistant Professor  (Senior Grade)	Sep 2006 to till date
BLS Institute of Management, Department of IT ,  Ghaziabad Indraprashta University, New Delhi, India	Sr. Lecturer	July 2003 to Aug 2006.
Institute of Technology and Science, Department of IT, Ghaziabad, U P Technical University, Lucknow,  India	Lecturer	July 2002 to June 2003
School of Management Spradeciences, Varanasi, U P Technical University, Lucknow India	Lecturer	August-2000 to June 2002
Institute of science & Information Technology (IISIT), Bhubaneswar, Utkal University,  Bhubaneshwar ,  India	Lecturer	Sept. 1998 to July 2000.

 3. TRAINING CONDUCTED:

·         Working on prestigious e-Learning/ Pan African e-Network Project since 2012 for delivering Live Online Lectures sessions for different PG and UG program.

·         Conducted IT skill training program for Navy and Army personnel.

·         Taught in six month DGR course for junior commanding officer.

·         Conducted two weeks  training  for skill development of   underprivileged Children  on CISCO sponsored project  for Networking with the CISCO IT-Essentials

4. ADMINISTRATIVE SKILLL:

·         Member of Board of Studies, Amity University, NOIDA, play a key role in implementation of Choice Based Credit System in Amity University, NOIDA.

·         As admission coordinator at department level, coordinating with central admission team of the University Formation of admission board and evaluation admission test papers, declaration of result.

·         As a Program Leader and Academic in charge managed various academic activities including Academic planning, Allotment of subjects, scheduling and monitoring for classes of core faculty as well as visiting faculty, Planning and preparation for the internal assessment

5.  COURSES /MODULE TAUGHT:

                                                            1. Database Management System.

                                                            2. Advance Database Concepts          

                                                            3. System Analyses and Design.         

                                                            4. Software Project Management.

                                                            5. Software Engineering.

                                                            6. ORACLE: 

6. BOOK AND STUDY MATERIAL AUTHORED / REVIEWED:

1) Authored a book Titled “Management Information System” for MBA, MCA and BBA students published by S M Publication, Bhubaneswar.

2) Authored a book Titled “Quality Management for Component Based Software System published by LAMBERT ACADMIC PUBLICATION , GERMANY

3)  Authored  an E- book Titled “Database Management System” for PAN African Project. (Amity University)

4) Authored an E-Book Titled “IT Project Management “for PAN African Project. (Amity University)

5) Reviewed a book Titled “Advance Database Concepts” for MCA course published by Directorate of distance and online education. (Amity University)

7. PAPER PUBLISHED IN JOURNAL & CONFERENCE:

Paper Published in Journal

[1] Shambhu  Jha; R K Mishra “Accessing Software Quality for Component –Based Software through Trustworthiness and Dependability Analysis” , International Journal of Development Research(IJDR) of India, ISSN: 2230-9926 [online] , Volume 5 &  Issue 4 , Page: 4259-4261-18, April 2015. 

[2] S K Jha; A  Kapahi  “ Identity Verification In Hybrid Cloud  Computing”  International Journal Of Technology  Enhancement And Emerging Engineering Research (IJTEEER) ISSN 2347-4289 [Online]; VOL 3 & ISSUE 06, Page No: 54-56 ,June 2015 .

[3] S K Jha; Nikita Soni, “Component Based Software Development: A new Paradigm”  ”International Journal of Scientific Research and Education(IJSRE) of India, ISSN (e): 2321-7545, Volume:2& Issue 6. Page No: 969-974  ,July  2015.

[4] Shambhu Jha; Ratnesh Sharma,“Oracle Recovery Manager” has been published in the International Journal Of Technology  Enhancement And Emerging Engineering Research (IJTEEER), VOL 2, ISSUE 7 ISSN: 2347-4289 ,Page No: 50 – 52 , July 2014

[5] Ruby Bhati; Nitika  Bansal; S K Jha, “Distribute Database System: The Current Future and Problems”,  International Journal of Computer Science and Management Research (IJCSMR),ISSN 2278-733X, Volume II & Issue III , March 2013

Paper Published/ Presented     in Conference Proceedings:

[1]  Shambhu Kr  Jha;  Dr. R. K. Mishra , “ Predicting and Accessing Security Feature into Component Based Software Development : A critical survey”  in 50th Golden Jubilee Convention on “ Digital Life” organized by  Computer Society of India ,New Delhi ,India. Dec 2-5 2015.

[2] Shambhu kr.  Jha; Dr R. K. Mishra, “Analyzing Trustworthiness and Dependability for Component Based Software through Reuse”   National Conference at IMS Unison University,  Dehradun, India , June 27-28,  2014.

[3] Shambhu Kr Jha; “Reuse Oriented Requirement Engineering” in National Confluence on The Next Generation Information Technology Summit , Amity University Noida , India ,  Jan 27-28 , 2011.

[4] Shambhu   Jha; Dr. R. K. Mahapatra;, “Retrieving Reusable Software Component: A Critical Survey in a National Conference at Udaipur, India , 6 Mar  2010.

[5] Shambhu Jha , “Software Quality Model for Component Based Software”, National Conference on Factory Automation , Robotics and Soft Computing , NIT Warangal, India , 18-19 Jan 2007.

 [6] Presented a paper on Robotic Application for Childhood Disability in a National Seminar at Jawaharlal Nehru University, New Delhi, India, 4 Dec 2005.

8. PROGRAM COMMITTEE MEMBER OF CONFERENCES / INVITED TALK:

1. Program Committee Member of 2015 IEEE International Conference on Research in Computational Intelligence and Communication Networks (ICRCICN`2015), November 20-22, 2015 will be organized by RCCIIT, Kolkata, India in association with IEEE Computer Society.

2. Reviewer and Program Committee Member of 2015 IEEE 4^th International Conference on Reliability, Infocom Technologies and Optimization (ICRITO`2015), September 02-04, 2015   Amity University, Noida, India in association with Computer Society of India (CSI) and IEEE Computer Society.

3. Program Committee Member of 2014 IEEE 3^rd International Conference on Reliability, Infocom Technologies and Optimization (ICRITO`2014), October 08-10, 2014 organized by Amity University, Noida, India in association with Computer Society of India (CSI) and IEEE Computer Society.

4. Technical program Committee Member of 2nd International Conference on ICT for Competitive Strategies (ICTCS 2016 –SS22) 4–5 March, 2016 organized by Association of Computing Machinery.

5. Technical Pgrogram Committee Member of  50^th Golden Jubilee Convention on “Digital Life”  02^nd to 5^th Dec , 2015 organized by Computer Society of India.

6. Delivered an Invited Talk on “Traffic Management of Disabled Pedestrian through ICT”: in a National Conclave organized by Society for Disability and Rehabilitation Studies,  2014, at Indian Spinal Injuries Centre , New Delhi

9. MEMBERSHIP OF PROFESSIONAL BODIES:

1. Associate Member of Computer Society of India                    (Membership No:  I0175123)

2. Associate   Member of Association for Computing Machinery. (Membership No. 0611441).

3. Member of International Association of Computer Science and Information Technology (IACSIT).                                                                                 (Membership No:  80351188)

4. Member of Society of Digital Information and Wireless Communications (SDIWC).

 (Membership No: 13949)

5. Associate Member of the Computer Science Teachers Association.  (CSTA). 

10.. PERSONAL DETAILS:

Name                                         :        Jha , Shambhu Kumar

Father's Name                          :        Mahanand Jha

Date of Birth                             :        24^th Aug. 1970

Nationality                                :        Indian

Passport Number                     :        K3908732

Sex                                             :        Male

Marital Status                           :        Married

Category                                   :        General

Language Known                    :        Hindi & English

Address                                     :      318 Shantam Khand , Vasundhara ,Sec 19 Ghaziabad   .                                                                 Vasundhara , Ghaziabad (UP) Pin : 201012 ,INDIA

Date:                                                                          

Place:                                                                          (SHAMBHU KUMAR JHA)

Introductory Concept of Database Failures and Recovery

Database operations can not be protected to the system on which it operates (both the hardware and the software, including the operating systems). The system should ensure that any transaction submitted to it is terminated in one of the following ways.

a)      All the operations listed in the transaction are completed, the changes are recorded permanently back to the database and the database is indicated that the operations are complete.

b)      In case the transaction has failed to achieve its desired objective, the system should ensure that no change, whatsoever, is reflected onto the database.  Any intermediate changes made to the database are restored to their original values, before calling off the transaction and intimating the same to the database.

In the second case, we say the system should be able to “Recover” from the failure.

Database failure

Database Failures can occur in a variety of ways.

i)                    A System Crash: A hardware, software or network error can make the completion of the transaction impossibility.

ii)                  A transaction or system error: The transaction submitted may be faulty – like creating a situation of division by zero or creating a negative numbers which cannot be handled (For example, in a reservation system, negative number of seats conveys no meaning).  In such cases, the system simply discontinuous the transaction by reporting an error.

iii)                Some programs provide for the user to interrupt during execution.  If the user changes his mind during execution, (but before the transactions are complete) he may opt out of the operation.

iv)                Local exceptions: Certain conditions during operation may force the system to raise what are known as “exceptions”.  For example, a bank account holder may not have sufficient balance for some transaction to be done or special instructions might have been given in a bank transaction that prevents further continuation of the process.  In all such cases, the transactions are terminated.

v)                  Concurrency control enforcement: In certain cases when concurrency constrains are violated, the enforcement regime simply aborts the process to restart later.

The other reasons can be physical problems like theft, fire etc or system problems like disk failure, viruses etc.  In all such cases of failure, a recovery mechanism is to be in place.

Database Recovery

Recovery most often means bringing the database back to the most recent consistent state, in the case of transaction failures.  This obviously demands that status information about the previous consistent states are made available in the form a “log” (which has been discussed in one of the previous sections in some detail).

            A typical algorithm for recovery should proceed on the following lines.

1. If the database has been physically damaged or there are catastrophic crashes like disk crash etc, the database has to be recovered from the archives.  In many cases, a reconstruction process is to be adopted using various other sources of information.
2. In situations where the database is not damaged but has lost consistency because of transaction failures etc, the method is to retrace the steps from the state of the crash (which has created inconsistency) until the previously encountered state of consistency is reached.  The method normally involves undoing certain operation, restoring previous values using the log etc.

In general two broad categories of these retracing operations can be identified.  As we have seen previously, most often, the transactions do not update the database as and when they complete the operation.  So, if a transaction fails or the system crashes before the commit operation, those values need not be retraced.  So no “undo” operation is needed.  However, if one is still interested in getting the results out of the transactions, then a “Redo” operation will have to be taken up.  Hence, this type of retracing is often called the “no-undo /Redo algorithm”.  The whole concept works only when the system is working on a “deferred update” mode.

However, this may not be the case always.  In certain situations, where the system is working on the “immediate update” mode, the transactions keep updating the database without bothering about the commit operation. In such cases however, the updating will be normally onto the disk also.  Hence, if a system fails when the immediate updating are being made, then it becomes necessary to undo the operations using the disk entries.  This will help us to reach the previous consistent state.  From there onwards, the transactions will have to be redone.  Hence, this method of recovery is often termed as the Undo/Redo algorithm.

Components of the Database System Environment

Components of the Database System Environment

There are five major components in the database system environment and their interrelationship are.

• Hardware

• Software

• Data

• Users

• Procedures

                      

1.Hardware: The hardware is the actual computer system used for keeping and accessing the database. Conventional DBMS hardware consists of secondary storage devices, usually hard disks, on which the database physically resides, together with the associated Input-Output devices, device controllers and· so forth. Databases run on a' range of machines, from Microcomputers to large mainframes. Other hardware issues for a DBMS includes database machines, which is hardware designed specifically to support a database system.

2. Software: The software is the actual DBMS. Between the physical database itself (i.e. the data as actually stored) and the users of the system is a layer of software, usually called the Database Management System or DBMS. All requests from users for access to the database are handled by the DBMS. One general function provided by the DBMS is thus the shielding of database users from complex hardware-level detail.

The DBMS allows the users to communicate with the database. In a sense, it is the mediator between the database and the users. The DBMS controls the access and helps to maintain the consistency of the data. Utilities are usually included as part of the DBMS. Some of the most common utilities are report writers and application development.

                         

3. Data : It is the most important component of DBMS environment from the end users point of view. As shown in observes that data acts as a bridge between the machine components and the user components. The database contains the operational data and the meta-data, the 'data about data'.

The database should contain all the data needed by the organization. One of the major features of databases is that the actual data are separated from the programs that use the data. A database should always be designed, built and populated for a particular audience and for a specific purpose.

4. Users : There are a number of users who can access or retrieve data on demand using the applications and interfaces provided by the DBMS. Each type of user needs different software capabilities. The users of a database system can be classified in the following groups, depending on their degrees of expertise or the mode of their interactions with the DBMS. The users can be:

• Naive Users

• Online Users

• Application Programmers

• Sophisticated Users

• Data Base Administrator (DBA)

Naive Users: Naive Users are those users who need not be aware of the presence of the database system or any other system supporting their usage. Naive users are end users of the database who work through a menu driven application program, where the type and range of response is always indicated to the user.

A user of an Automatic Teller Machine (ATM) falls in this category. The user is instructed through each step of a transaction. He or she then responds by pressing a coded key or entering a numeric value. The operations that can be performed by valve users are very limited and affect only a precise portion of the database. For example, in the case of the user of the Automatic Teller Machine, user's action affects only one or more of his/her own accounts.

Online Users : Online users are those who may communicate with the database directly via an online terminal or indirectly via a user interface and application program. These users are aware of the presence of the database system and may have acquired a certain amount of expertise with in the limited interaction permitted with a database.

Sophisticated Users : Such users interact with the system without ,writing programs.

Instead, they form their requests in database query language. Each such query is submitted to a very processor whose function is to breakdown DML statement into instructions that the storage manager understands.

Specialized Users : Such users are those ,who write specialized database application that do not fit into the fractional data-processing framework. For example: Computer-aided design systems, knowledge base and expert system, systems that store data with complex data types (for example, graphics data and audio data).

Application Programmers : Professional programmers are those who are responsible for developing application programs or user interface. The application programs could be written using general purpose programming language or the commands available to manipulate a database.

Database Administrator: The database administrator (DBA) is the person or group in charge for implementing the database system ,within an organization. The "DBA has all the system privileges allowed by the DBMS and can assign (grant) and remove (revoke) levels of access (privileges) to and from other users. DBA is also responsible for the evaluation, selection and implementation of DBMS package. 

5. Procedures: Procedures refer to the instructions and rules that govern the design and use of the database. The users of the system and the staff that manage the database require documented procedures on how to use or run the system.

These may consist of instructions on how to:

• Log on to the DBMS.

• Use a particular DBMS facility or application program.

• Start and stop the DBMS.

• Make backup copies of the database.

• Handle hardware or software failures.

Change the structure of a table, reorganize the database across multiple disks, improve performance, or archive data to secondary storage.