ORA-00983: cannot audit or noaudit SYS user actions
Cause : An attempt was made to AUDIT or NOAUDIT SYS user actions.
Action : Execute the statement again with a valid user.
Popularity: 4% [?]
Complete Source for Oracle Error Code Ora-, Pl/Sql Tips and Tricks and Oracle Error Message Description
Cause : An attempt was made to AUDIT or NOAUDIT SYS user actions.
Action : Execute the statement again with a valid user.
Popularity: 4% [?]
Cause : A left parenthesis appeared in a join condition, but a plus sign (+) did not follow. A left parenthesis in a join condition usually signals an outer-join specification and so a plus sign is expected to follow. To specify an outer join on a column in a join operation, follow the column reference in the join condition with a plus sign (+) enclosed in parentheses.
Action : Correct the SQL syntax and retry the statement.
Popularity: 3% [?]
Cause : Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement.
Action : You must issue table and system options in separate statements.
Popularity: 2% [?]
Cause : A synonym did not translate to a legal target object. This could happen for one of the following reasons:
1. The target schema does not exist.
2. The target object does not exist.
3. The synonym specifies an incorrect database link.
4. The synonym is not versioned but specifies a versioned target object.
Action : Change the synonym definition so that the synonym points at a legal target object.
Popularity: 4% [?]
Cause : The GROUP BY clause does not contain all the expressions in the SELECT clause. SELECT expressions that are not included in a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, must be listed in the GROUP BY clause.
Action : Include in the GROUP BY clause all SELECT expressions that are not group function arguments.
Popularity: 3% [?]
Cause : A group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used within another group function, as in MAX(COUNT(*)), without a corresponding GROUP BY clause.
Action : Either add a GROUP BY clause or remove the extra level of nesting.
Popularity: 3% [?]
Cause : An AUDIT or NOAUDIT statement specified the same option more than once.
Action : Either specify ALL without other auditing options or remove the duplicate auditing specifications.
Popularity: 2% [?]
Cause : The use of the PRIOR clause, the pseudo-column LEVEL, or ROWNUM is incorrect in this context.
Action : Check the syntax for the SQL statement. Then remove or relocate the keyword PRIOR, LEVEL, or ROWNUM.
Popularity: 4% [?]
Cause : An attempt was made to add two date fields together. Dates may be added only to numeric fields, not to other dates.
Action: Use the Oracle function TO_NUMBER to convert one of the date fields to a numeric field before adding it to the other date field.
Popularity: 7% [?]
Cause : The percentage of free space specified in a CREATE INDEX statement is not between 0 and 100. A PCTFREE value of 0 means the entire block is available. The value 100 is not useful because it means that no data may be inserted. The default is 10.
Action : Specify a PCTFREE value between 0 and 100. Then retry the statement.
Popularity: 2% [?]