Author: Dev

ORA-00999: invalid view name Oracle SQL Error: ORA-00999: invalid view name Cause: In a CREATE VIEW statement, the view name was missing or invalid. Solution: Enter a valid view name following CREATE VIEW. Example: CREATE VIEW AS SELECT * FROM BOOKS; Output: SQL Error: ORA-00999: invalid view name Correct CREATE VIEW BOOKS_VIEW AS SELECT *…(Continue Reading)

ORA-01432: public synonym to be dropped does not exist ORA-01432: public synonym to be dropped does not exist Cause: The synonym specified in DROP PUBLIC SYNONYM is not a valid public synonym. It may be a private synonym. Solution: Correct the synonym name or use DROP SYNONYM if the synonym is not public. Example: DROP…(Continue Reading)

ORA-01434: private synonym to be dropped does not exist ORA-01434: private synonym to be dropped does not exist Cause: A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names may be listed by querying the data dictionary. Solution: Specify the name of an existing synonym in the DROP SYNONYM statement. Example:…(Continue Reading)

ORA-01422: exact fetch returns more than requested number of rows ORA-01422: exact fetch returns more than requested number of rows Cause: The number specified in exact fetch is less than the rows returned. Solution: Rewrite the query or change number of rows requested. Example: declare v_name varchar2(255); begin select name into v_name from books where…(Continue Reading)

ORA-01403: no data found ORA-01403: no data found Cause: A SELECT INTO statement was executed and no rows were returned. Solution: Set the no_data_found exception or correct the SELECT statement. Example: declare v_name varchar2(255); begin select name into v_name from books where id=00011872; dbms_output.put_line(‘The name is: ‘||v_name); end; Output: ORA-01403: no data found Correct declare…(Continue Reading)