Rules with quality area Reliability

Reliability is a measure of how your software is capable of maintaining its level of performance under stated conditions for a stated period of time.

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

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

  Reliability
• G-1240Try to index foreign key columns.

  Reliability
• G-1250Try to define a business key for each table.

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

  Reliability
• G-2110Try to use anchored declarations for variables, constants and types.

  Reliability
• G-2135Avoid assigning values to local variables that are not used by a subsequent statement.

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

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

  Reliability
• G-2190Avoid using ROWID or UROWID.

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

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

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

  Reliability
• G-2310Avoid using CHAR data type.

  Reliability
• 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-3140Try to use anchored records as targets for your cursors.

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

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

  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-3180Always specify column names instead of positional references in ORDER BY clauses.

  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-3210Always use BULK OPERATIONS (BULK COLLECT, FORALL) whenever you have to execute a DML statement for more than 4 times.

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

  Reliability
• 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-4230Always 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-4240Always 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-4350Always use 1 as lower and COUNT() as upper bound when looping through a dense array.

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

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

  Reliability
• G-4390Avoid use of unreferenced FOR loop indexes.

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

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

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

  Reliability
• G-5060Avoid unhandled exceptions.

  Reliability
• G-5070Avoid using Oracle predefined exceptions.

  Reliability
• G-7130Always use parameters or pull in definitions rather than referencing external variables in a local program unit.

  Reliability
• G-7160Always explicitly state parameter mode.

  Reliability
• G-7170Avoid using an IN OUT parameter as IN or OUT only.

  Reliability
• G-7210Try to keep your packages small. Include only few procedures and functions that are used in the same context.

  Reliability
• G-7230Avoid declaring global variables public.

  Reliability
• G-7250Never use RETURN in package initialization block.

  Reliability
• G-7460Try to define your packaged/standalone function deterministic if appropriate.

  Reliability
• G-7730Avoid multiple DML events per trigger.

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

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

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

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

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

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

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

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

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

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

  Reliability
• G-9601Never use unknown hints.

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

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

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

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

  Reliability

67 total