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.

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

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

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

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

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

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

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

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

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

  Reliability
• G-2190 Avoid using ROWID or UROWID.

  Reliability
• G-2310 Avoid using CHAR data type.

  Reliability
• G-2320 Never use VARCHAR data type.

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

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

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

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

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

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

  Reliability
• G-3160 Avoid visible virtual columns.

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

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

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

  Reliability
• G-3190 Avoid using NATURAL JOIN.

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

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

  Reliability
• G-3330 Avoid autonomous transactions.

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

  Reliability
• G-4130 Always close locally opened cursors.

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

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

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

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

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

  Reliability
• G-5070 Avoid using Oracle predefined exceptions.

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

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

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

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

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

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

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

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

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

  Security

43 total