Lab 5 Data Manipulation To perform the following tasks, recreate the tables with JLDB_Build_5.sql script posted in Learning Materials' Module 6 in BB. How to submit the work: Save screen capture for each question that includes query and its output. Your name, question#, lab/assignment name must appear in each screen capture. Name your document as yourname_DB_lab/assignment name. Note: Some questions suppose to raise a valid error. Not enough values is not a valid error. You need to correct 'not enough values' error and try to run the query again. 1. Add a new row in the PUBLISHER table with the following data: PUBID = 6, Name = CENGAGE LEARNING, phone = 800-354-9706.| 2. Add a new row in the BOOKS table with the following data: ISBN = 1439041284, Title = Oracle 11g SQL, and Publish date = May 24, 2010, pubid = 6, category=COMPUTER. 3. Modify the zip code of customer 1008 to 25689 in the CUSTOMERS table. a. Save the changes permanently to the database. b. Add 3 more customers into CUSTOMERS table demonstrating your knowledge to input NULL values in variety of ways. 4. Add a new row in the BOOKS table with the following data: ISBN = 0131483986, Title =JAVA HOW TO PROGRAM, pubid = 7, category= COMPUTER. Describe the error raised and what caused the error. 5. Add a new row in the ORDERS table with the following data: Order# = 1023 and Customer# = 1009. Describe the error raised and what caused the error. 6. Create a script using substitution variables that allows a user to set a new cost amount for a book based on the ISBN. a. Execute the script and set the following values: isbn = 1439041284 and cost = $120.00. b. Execute a command that undoes the change in Step 6a. Confirm the changes. 7. Delete Order# 1012 from ORDERS table. You need to address both the master order record and the related detail records. Confirm if the records are deleted. a. Execute a command that undoes the previous deletion done in Q.7. Confirm the result. 8. Repeat step 7 by making changes at the constraint level by adding ON DELETE CASCADE option while recreating FOREIGN KEY constraint, so deleting ORDER#1012 from parent table does not erase integrity issues. Confirm the changes in respective tables. a. Execute a command that undoes the previous deletion done in Q.8. Confirm the result