Rules with severity level Critical

Will have a high/direct impact on the maintenance cost. May have an impact on runtime behavior; for example, incomplete audit data or slower runtime performance.

• G-1130 Avoid granting table access to API roles.

  Maintainability
• G-2160 Avoid initializing variables using functions in the declaration section.

  Reliability
• G-2210 Avoid declaring NUMBER variables, constants or subtypes with no precision.

  Reliability
• G-2220 Try to use PLS_INTEGER instead of NUMBER for arithmetic operations with integer values.

  Reliability
• G-2230 Try to use SIMPLE_INTEGER datatype when appropriate.

  Reliability
• G-3150 Try to use identity columns for surrogate keys.

  Reliability
• G-3210 Always use BULK OPERATIONS (BULK COLLECT, FORALL) whenever you have to execute a DML statement for more than 4 times.

  Reliability
• G-3220 Always process saved exceptions from a FORALL statement.

  Reliability
• G-4230 Always use a COALESCE instead of a NVL command, if parameter 2 of the NVL function is a function call or a SELECT statement.

  Reliability
• G-4240 Always use a CASE instead of a NVL2 command if parameter 2 or 3 of NVL2 is either a function call or a SELECT statement.

  Reliability
• G-4360 Always use a WHILE loop to process a loose array.

  Reliability
• G-4385 Never use a cursor for loop to check whether a cursor returns data.

  Maintainability
• G-5010 Try to use a error/logging framework for your application.

  Reliability
• G-5020 Never handle unnamed exceptions using the error number.

  Maintainability
• G-5040 Avoid use of WHEN OTHERS clause in an exception section without any other specific handlers.

  Reliability
• G-5080 Always use FORMAT_ERROR_BACKTRACE when using FORMAT_ERROR_STACK or SQLERRM.

  Maintainability
• G-7740 Never handle multiple DML events per trigger if primary key is assigned in trigger.

  Reliability
• G-7810 Never use SQL inside PL/SQL to read sequence numbers (or SYSDATE).

  Reliability
• G-8110 Never use SELECT COUNT(*) if you are only interested in the existence of a row.

  Reliability
• G-8120 Never check existence of a row to decide whether to create it or not.

  Reliability
• G-8510 Always use dbms_application_info to track program process transiently.

  Reliability
• G-9020 Try to use a format model and NLS_NUMERIC_CHARACTERS in string to number conversion functions.

  Reliability
• G-9600 Never define more than one comment with hints.

  Reliability
• G-9601 Never use unknown hints.

  Reliability
• G-9602 Always use the alias name instead of the table name.

  Reliability
• G-9603 Never reference an unknown table/alias.

  Reliability
• G-9604 Never use an invalid stats method.

  Reliability
• G-9605 Never use an invalid stats keyword.

  Reliability

28 total