PL$/$SQL homewerk help needed. I$\text{'}$m using SQL developer. Please use PL$/$SQL and use SQL Developer

Here is the questions below:

$1.$ The Raise Procedure $(40$ points

Create a copy of the EMPLOYEES table by running the following code:

CREATE TABLE MyEmployees AS SELECT $*$ FROM HR$.$Employees;

Now, create a new table that you will use for logging$.$

CREATE TABLE HW$1$Log

$($

Message VARCHAR$2(200),$

TStamp TIMESTAMP DEFAULT SYSTIMESTAMP

$)$;

Notice that the TStamp column was created with a default value. You can add a log message to the table like this:

INSERT INTO HW$1$Log $($Message$)$ VALUES $(\text{'}$Some message'$)$;

If you look at the table now, you$$ll see that the timestamp column has been populated automatically. Later on$,$ you$$ll be asked to use code like this to write messages to your log table.

Now, create a stored procedure called RaiseSalary that accepts two parameters $$ an employee id and an integer raise percentage. The procedure will raise the salary of the specified employee by the specified percentage. It will do this by updating the Salary column in MyEmployees. Calling the procedure with an argument of $101$ for the employee id and $20$ for the raise percentage would raise that employee$$s salary by $20$ percent.

Your procedure should include exception handling. It should have a generic error handler which prints out both the SQLERRM and the phrase $$Encountered while trying to give employee a raise.$$ Of course, instead of $,$ your error message should include the value of the employee id parameter that was passed into the procedure.

Every time your procedure raises the salary of an employee, you should write a message to your HW$1$Log table in the following form:

Employee was raised by percent.

Note that an UPDATE statement that affects zero records won$$t cause an exception. Implicit cursor attributes can help you determine if anybody$$s salary was actually raised.

Do a $$COMMIT;$$ inside your procedure $($after all the other code in the BEGIN section but before EXCEPTION$)$ to make your changes public and permanent. It$$s not always a good idea to have a COMMIT inside your procedures, but for the sake of this exercise, please put one in there.

Show the code for your procedure, as well as the code and output from the following exercises:

$$ Show the initial salary of employee $179($can do this with a standard SQL query$)$

$$ Call your procedure with an employee id of $179$ and a percentage of $10$

$$ Show the salary of employee $179$ after the procedure call $($can do this with a standard SQL query$)$

$$ Show the initial salary of employee $202($can do this with a standard SQL query$)$

$$ Call your procedure with an employee id of $202$ and a percentage of $15$

$$ Show the salary of employee $202$ after the procedure call $($can do this with a standard SQL query$)$

$$ Call your procedure with an employee id of $500$ and a percentage of $20$

$$ Show all of the data from your HW$1$Log table $($can do this with a standard SQL query$)$ order your results by ascending TStamp value.