Rules with severity level Blocker

Will or may result in a bug; for example, an incorrect result or a runtime exception or a security vulnerability.

• A-1010Never allow application pages within an HTML frame.

  Security
• G-1060Avoid storing ROWIDs or UROWIDs in database tables.

  Reliability
• G-1080Avoid using the same expression on both sides of a relational comparison operator or a logical operator.

  Maintainability
• G-1110Avoid connect users that own database objects.

  Security
• G-1120Avoid granting system privileges to connect users.

  Security
• G-1150Always limit privileges of schema owners according to principle of least privileges.

  Security
• G-1210Never create a table without a primary key.

  Reliability
• G-1310Never keep database objects in an invalid state.

  Reliability
• G-1920Avoid syntax errors.

  Maintainability
• G-2145Never self-assign a variable.

  Maintainability
• G-2150Avoid comparisons with NULL value, consider using IS [NOT] NULL.

  Reliability
• G-2190Avoid using ROWID or UROWID.

  Reliability
• G-2310Avoid using CHAR data type.

  Reliability
• G-2320Never use VARCHAR data type.

  Maintainability
• G-2330Never use zero-length strings to substitute NULL.

  Maintainability
• G-2340Always define your VARCHAR2 variables using CHAR SEMANTIC (if not defined anchored).

  Reliability
• G-3110Always specify the target columns when coding an insert statement.

  Reliability
• G-3115Avoid self-assigning a column.

  Maintainability
• G-3120Always use table aliases when your SQL statement involves more than one source.

  Maintainability
• G-3145Avoid using SELECT * directly from a table or view.

  Reliability
• G-3160Avoid visible virtual columns.

  Reliability
• G-3170Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.

  Reliability
• G-3182Always specify column names/aliases instead of positional references in GROUP BY clauses.

  Reliability
• G-3185Never use ROWNUM at the same query level as ORDER BY.

  Reliability
• G-3190Avoid using NATURAL JOIN.

  Reliability
• G-3192Avoid joining tables with the USING clause.

  Reliability
• G-3195Always use wildcards in a LIKE clause.

  Maintainability
• G-3310Never commit within a cursor loop.

  Reliability
• G-3330Avoid autonomous transactions.

  Reliability
• G-4120Avoid using %NOTFOUND directly after the FETCH when working with BULK OPERATIONS and LIMIT clause.

  Reliability
• G-4130Always close locally opened cursors.

  Reliability
• G-4140Avoid executing any statements between a SQL operation and the usage of an implicit cursor attribute.

  Reliability
• G-4250Avoid using identical conditions in different branches of the same IF or CASE statement.

  Maintainability
• G-4350Always use 1 as lower and COUNT() as upper bound when looping through a dense array.

  Reliability
• G-4387Never use a FOR LOOP for a query that should return not more than one row.

  Reliability
• G-5030Never assign predefined exception names to user defined exceptions.

  Reliability
• G-5070Avoid using Oracle predefined exceptions.

  Reliability
• G-7330Always assign values to OUT parameters.

  Maintainability
• G-7450Never return a NULL value from a BOOLEAN function.

  Maintainability
• G-7510Always prefix Oracle supplied packages with owner schema name.

  Security
• G-7515Always prefix Oracle supplied object types with owner schema name.

  Security
• G-7720Never use multiple UPDATE OF in trigger event clause.

  Maintainability
• G-7910Never use DML within a SQL macro.

  Reliability
• G-8410Always use application locks to ensure a program unit is only running once at a given time.

  Reliability
• G-9010Always use a format model in string to date/time conversion functions.

  Security
• G-9040Try using FX in string to date/time conversion format model to avoid fuzzy conversion.

  Reliability
• G-9501Never use parameter in string expression of dynamic SQL. Use asserted local variable instead.

  Security

47 total