ORA-01703: missing SYNONYM keyword Cause: The keyword SYNONYM is required in this context. Action: Check the statement syntax and insert the keyword SYNONYM. ORA-01704: string literal too long Cause: A quoted string specified as a constant was too long. Action: Quoted strings may not contain more than 2000 characters. ORA-01705: an outer join cannot be specified on a correlation column Cause: A correlation column, that is, a column in a subquery from a table referenced in the outer querys FROM clause, was followed by an outer-join indicator (+). This is not allowed. Action: Revise the query. Refer to the syntax for subqueries. The outer-join indicator may follow only columns in the same query block in which their table is included in the FROM clause. ORA-01706: user function result value was too large Cause: The user-written SQL function has generated a result that is larger than the maximum defined in the function table. Action: Change the maximum in the function table or correct the user-written function. ORA-01707: missing LIST keyword Cause: The keyword LIST is required in this context, for example, when using the ARCHIVE LOG statement to display the set of redo log files. Action: Check the statement syntax, insert the keyword LIST where required, and retry the statement. ORA-01708: ACCESS or SESSION expected Cause: An AUDIT or NOAUDIT statement contained the keyword BY followed by something other than ACCESS or SESSION. Action: Check the statement syntax and make sure to follow the keyword BY with ACCESS or SESSION. ORA-01709: program does not exist Cause: This feature is not currently implemented. Action: No user action is required. ORA-01710: missing OF keyword Cause: The keyword OF was not specified in a SELECT FOR UPDATE statement. Action: Check and correct the statement syntax. To specify SELECT FOR UPDATE, add the following clause to the end of the SELECT statement: FOR UPDATE OF column-list ORA-01711: duplicate privilege listed Cause: A privilege was listed twice in a GRANT or REVOKE statement. A privilege may be specified only once in these statements. Action: Remove the duplicate privilege from the list and retry the statement. ORA-01712: cannot grant a privilege grantor does not have Cause: The grantor could not grant a privilege to another user because the grantor does not have the privilege. A grantor can grant only privileges that the grantor has or is authorized to grant. Action: Either Specify only authorized privileges in the GRANT statement. Ask the database administrator to grant the user the required privileges. Ask the database administrator for the required privileges and then grant the other user the privileges. ORA-01713: GRANT OPTION does not exist for that privilege Cause: A GRANT statement specified a privilege that the granting user has but is not authorized to grant to other users. When the user was granted the privilege, the user was not given the GRANT OPTION needed to grant those privileges to others. Action: Change the GRANT statement to specify only authorized privileges or ask the user who granted the privileges to grant the GRANT OPTION also. ORA-01714: error in execution of user function Cause: The user-written SQL function indicated that an error occurred during its execution. The meaning of the message is function-dependent. Action: Ensure proper usage of the function or correct the function. ORA-01715: UNIQUE may not be used with a cluster index Cause: An attempt was made to create a cluster index with the UNIQUE attribute. This is not permitted. Action: Remove the keyword UNIQUE from the CREATE INDEX statement and retry the statement. ORA-01716: NOSORT may not be used with a cluster index