Rules

Tenant	Name	Title	Check?	Free?	Quick Fix?	Test?	Severity	Level	Quality Area	Profile	Fixing Time
Core	G-1010	Try to label your sub blocks.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-1020	Always have a matching loop or block label.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Extreme	Local-easy
Core	G-1030	Avoid defining variables that are not used.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Balanced	Local-medium
Core	G-1040	Avoid dead code.	Yes	Yes	No	No	Warning	Minor	Maintainability	Balanced	Local-medium
Core	G-1050	Avoid using literals in your code.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-1060	Avoid storing ROWIDs or UROWIDs in database tables.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Other
Core	G-1070	Avoid nesting comment blocks.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-1080	Avoid using the same expression on both sides of a relational comparison operator or a logical operator.	Yes	Yes	Yes	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-1110	Avoid connect users that own database objects.	No	Yes	No	Yes	Error	Blocker	Security	Aggressive	Other
Core	G-1120	Avoid granting system privileges to connect users.	No	Yes	No	Yes	Error	Blocker	Security	Aggressive	Other
Core	G-1130	Avoid granting table access to API roles.	No	Yes	No	Yes	Warning	Critical	Maintainability	Aggressive	Other
Core	G-1140	Avoid granting object privileges directly to connect users.	No	Yes	No	Yes	Warning	Minor	Maintainability	Aggressive	Other
Core	G-1150	Always limit privileges of schema owners according to principle of least privileges.	No	Yes	No	Yes	Error	Blocker	Security	Aggressive	Other
Core	G-1210	Never create a table without a primary key.	No	Yes	No	Yes	Error	Blocker	Reliability	Balanced	Other
Core	G-1220	Avoid composite primary keys.	No	Yes	No	Yes	Warning	Major	Maintainability	Aggressive	Other
Core	G-1230	Avoid tables without relationships.	No	Yes	No	Yes	Warning	Major	Maintainability	Strict	Other
Core	G-1240	Try to index foreign key columns.	No	Yes	No	Yes	Warning	Major	Reliability	Strict	Other
Core	G-1250	Try to define a business key for each table.	No	Yes	No	Yes	Warning	Major	Reliability	Aggressive	Other
Core	G-1260	Try to define a comment for each table.	No	Yes	No	Yes	Info	Info	Maintainability	Extreme	Other
Core	G-1270	Try to define a comment for each column.	No	Yes	No	Yes	Info	Info	Maintainability	Extreme	Other
Core	G-1280	Try to use domains instead of raw datatypes for table columns.	No	Yes	No	Yes	Warning	Minor	Maintainability	Extreme	Other
Core	G-1310	Never keep database objects in an invalid state.	No	Yes	No	Yes	Error	Blocker	Reliability	Balanced	Other
Core	G-1910	Avoid using the NOSONAR marker.	Yes	Yes	No	No	Info	Info	Maintainability	Extreme	Other
Core	G-1920	Avoid syntax errors.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-high
Core	G-1930	Avoid long parsing times.	Yes	Yes	No	No	Info	Info	Maintainability	Extreme	Local-high
Core	G-1940	Avoid long checking times.	Yes	Yes	No	No	Info	Info	Maintainability	Extreme	Local-high
Core	G-2110	Try to use anchored declarations for variables, constants and types.	Yes	Yes	No	No	Warning	Major	Reliability	Extreme	Local-medium
Core	G-2120	Try to have a single location to define your types.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-2130	Try to use subtypes for constructs used often in your code.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-2135	Avoid assigning values to local variables that are not used by a subsequent statement.	Yes	Yes	No	No	Warning	Major	Reliability	Balanced	Local-medium
Core	G-2140	Never initialize variables with NULL.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Balanced	Local-easy
Core	G-2145	Never self-assign a variable.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-2150	Avoid comparisons with NULL value, consider using IS [NOT] NULL.	Yes	Yes	Yes	No	Error	Blocker	Reliability	Essential	Local-easy
Core	G-2160	Avoid initializing variables using functions in the declaration section.	Yes	Yes	No	No	Warning	Critical	Reliability	Aggressive	Local-easy
Core	G-2170	Never overload variables.	Yes	Yes	No	No	Warning	Major	Maintainability	Balanced	Local-medium
Core	G-2180	Never use quoted identifiers.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Balanced	Local-easy
Core	G-2185	Avoid using overly short names for explicitly or implicitly declared identifiers.	Yes	Yes	No	No	Warning	Major	Maintainability	Extreme	Local-easy
Core	G-2190	Avoid using ROWID or UROWID.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-2210	Avoid declaring NUMBER variables, constants or subtypes with no precision.	Yes	Yes	No	No	Warning	Critical	Reliability	Balanced	Local-medium
Core	G-2220	Try to use PLS_INTEGER instead of NUMBER for arithmetic operations with integer values.	Yes	Yes	Yes	No	Warning	Critical	Reliability	Balanced	Local-medium
Core	G-2230	Try to use SIMPLE_INTEGER datatype when appropriate.	Yes	Yes	Yes	No	Warning	Critical	Reliability	Balanced	Local-medium
Core	G-2310	Avoid using CHAR data type.	Yes	Yes	Yes	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-2320	Never use VARCHAR data type.	Yes	Yes	Yes	No	Error	Blocker	Maintainability	Essential	Local-easy
Core	G-2330	Never use zero-length strings to substitute NULL.	Yes	Yes	Yes	No	Error	Blocker	Maintainability	Essential	Local-easy
Core	G-2340	Always define your VARCHAR2 variables using CHAR SEMANTIC (if not defined anchored).	Yes	Yes	Yes	No	Error	Blocker	Reliability	Essential	Local-easy
Core	G-2410	Try to use boolean data type for values with dual meaning.	Yes	Yes	No	No	Warning	Minor	Maintainability	Aggressive	Local-medium
Core	G-2510	Avoid using the LONG and LONG RAW data types.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Balanced	Local-medium
Core	G-2610	Never use self-defined weak ref cursor types.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Balanced	Local-medium
Core	G-3110	Always specify the target columns when coding an insert statement.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-3115	Avoid self-assigning a column.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-3120	Always use table aliases when your SQL statement involves more than one source.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-high
Core	G-3130	Try to use ANSI SQL-92 join syntax.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Strict	Local-high
Core	G-3140	Try to use anchored records as targets for your cursors.	Yes	Yes	No	No	Warning	Major	Reliability	Aggressive	Local-medium
Core	G-3145	Avoid using SELECT * directly from a table or view.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-high
Core	G-3150	Try to use identity columns for surrogate keys.	Yes	Yes	No	No	Warning	Critical	Reliability	Aggressive	Other
Core	G-3160	Avoid visible virtual columns.	No	Yes	No	Yes	Error	Blocker	Reliability	Essential	Other
Core	G-3170	Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.	Yes	No	Yes	Yes	Error	Blocker	Reliability	Essential	Other
Core	G-3180	Always specify column names instead of positional references in ORDER BY clauses.	Yes	Yes	Yes	No	Warning	Major	Reliability	Balanced	Local-easy
Core	G-3182	Always specify column names/aliases instead of positional references in GROUP BY clauses.	Yes	Yes	Yes	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-3183	Always specify column aliases instead of expressions in GROUP BY clauses.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Strict	Local-medium
Core	G-3185	Never use ROWNUM at the same query level as ORDER BY.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-high
Core	G-3190	Avoid using NATURAL JOIN.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-high
Core	G-3195	Always use wildcards in a LIKE clause.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-3210	Always use BULK OPERATIONS (BULK COLLECT, FORALL) whenever you have to execute a DML statement for more than 4 times.	Yes	Yes	No	No	Warning	Critical	Reliability	Aggressive	Local-high
Core	G-3220	Always process saved exceptions from a FORALL statement.	Yes	Yes	Yes	No	Warning	Critical	Reliability	Essential	Local-high
Core	G-3310	Never commit within a cursor loop.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-3320	Try to move transactions within a non-cursor loop into procedures.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-high
Core	G-3330	Avoid autonomous transactions.	Yes	No	No	No	Error	Blocker	Reliability	Essential	Other
Core	G-4110	Always use %NOTFOUND instead of NOT %FOUND to check whether a cursor returned data.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Aggressive	Local-easy
Core	G-4120	Avoid using %NOTFOUND directly after the FETCH when working with BULK OPERATIONS and LIMIT clause.	Yes	No	Yes	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-4130	Always close locally opened cursors.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-4140	Avoid executing any statements between a SQL operation and the usage of an implicit cursor attribute.	Yes	No	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-4210	Try to use CASE rather than an IF statement with multiple ELSIF paths.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Strict	Local-high
Core	G-4220	Try to use CASE rather than DECODE.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Strict	Local-medium
Core	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.	Yes	Yes	Yes	No	Warning	Critical	Reliability	Essential	Local-easy
Core	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.	Yes	No	Yes	No	Warning	Critical	Reliability	Essential	Local-medium
Core	G-4250	Avoid using identical conditions in different branches of the same IF or CASE statement.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-4260	Avoid inverting boolean conditions with NOT.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-4270	Avoid comparing boolean values to boolean literals.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-4310	Never use GOTO statements in your code.	Yes	Yes	No	No	Warning	Major	Maintainability	Balanced	Local-high
Core	G-4320	Always label your loops.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-4325	Never reuse labels in inner scope.	Yes	Yes	No	No	Warning	Major	Maintainability	Balanced	Local-medium
Core	G-4330	Always use a CURSOR FOR loop to process the complete cursor results unless you are using bulk operations.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Aggressive	Local-high
Core	G-4340	Always use a NUMERIC FOR loop to process a dense array.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-high
Core	G-4350	Always use 1 as lower and COUNT() as upper bound when looping through a dense array.	Yes	No	Yes	No	Error	Blocker	Reliability	Essential	Local-high
Core	G-4360	Always use a WHILE loop to process a loose array.	Yes	Yes	No	No	Warning	Critical	Reliability	Balanced	Local-high
Core	G-4365	Never use unconditional CONTINUE or EXIT in a loop.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-medium
Core	G-4370	Avoid using EXIT to stop loop processing unless you are in a basic loop.	Yes	Yes	No	No	Warning	Major	Maintainability	Strict	Local-medium
Core	G-4375	Always use EXIT WHEN instead of an IF statement to exit from a loop.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-medium
Core	G-4380	Try to label your EXIT WHEN statements.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-4385	Never use a cursor for loop to check whether a cursor returns data.	Yes	No	No	No	Warning	Critical	Maintainability	Balanced	Local-medium
Core	G-4387	Never use a FOR LOOP for a query that should return not more than one row.	Yes	No	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-4390	Avoid use of unreferenced FOR loop indexes.	Yes	Yes	No	No	Warning	Major	Reliability	Strict	Local-medium
Core	G-4395	Avoid hard-coded upper or lower bound values with FOR loops.	Yes	Yes	No	No	Warning	Minor	Maintainability	Aggressive	Local-medium
Core	G-5010	Try to use a error/logging framework for your application.	Yes	Yes	No	No	Warning	Critical	Reliability	Strict	Local-medium
Core	G-5020	Never handle unnamed exceptions using the error number.	Yes	No	No	No	Warning	Critical	Maintainability	Essential	Local-medium
Core	G-5030	Never assign predefined exception names to user defined exceptions.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-high
Core	G-5040	Avoid use of WHEN OTHERS clause in an exception section without any other specific handlers.	Yes	Yes	No	No	Warning	Critical	Reliability	Strict	Local-medium
Core	G-5050	Avoid use of the RAISE_APPLICATION_ERROR built-in procedure with a hard-coded 20nnn error number or hard-coded message.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-high
Core	G-5060	Avoid unhandled exceptions.	Yes	Yes	Yes	No	Warning	Major	Reliability	Aggressive	Local-medium
Core	G-5070	Avoid using Oracle predefined exceptions.	Yes	Yes	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-5080	Always use FORMAT_ERROR_BACKTRACE when using FORMAT_ERROR_STACK or SQLERRM.	Yes	Yes	Yes	No	Warning	Critical	Maintainability	Essential	Local-medium
Core	G-6010	Always use a character variable to execute dynamic SQL.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-medium
Core	G-6020	Try to use output bind arguments in the RETURNING INTO clause of dynamic DML statements rather than the USING clause.	Yes	Yes	No	No	Warning	Minor	Maintainability	Aggressive	Local-medium
Core	G-7110	Try to use named notation when calling program units.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-medium
Core	G-7120	Always add the name of the program unit to its end keyword.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Extreme	Local-easy
Core	G-7125	Always use CREATE OR REPLACE instead of CREATE alone.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Strict	Local-easy
Core	G-7130	Always use parameters or pull in definitions rather than referencing external variables in a local program unit.	Yes	Yes	No	No	Warning	Major	Reliability	Aggressive	Local-high
Core	G-7140	Always ensure that locally defined procedures or functions are referenced.	Yes	Yes	No	No	Warning	Major	Maintainability	Balanced	Local-medium
Core	G-7150	Try to remove unused parameters.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Strict	Local-medium
Core	G-7160	Always explicitly state parameter mode.	Yes	Yes	Yes	No	Warning	Major	Reliability	Strict	Local-medium
Core	G-7170	Avoid using an IN OUT parameter as IN or OUT only.	Yes	Yes	Yes	No	Warning	Major	Reliability	Strict	Local-medium
Core	G-7180	Try to keep the complexity of functions, procedures and triggers simple.	Yes	Yes	No	No	Warning	Critical	Maintainability	Aggressive	Local-high
Core	G-7210	Try to keep your packages small. Include only few procedures and functions that are used in the same context.	Yes	Yes	No	No	Warning	Minor	Reliability	Aggressive	Other
Core	G-7220	Always use forward declaration for private functions and procedures.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-7230	Avoid declaring global variables public.	Yes	Yes	Yes	No	Warning	Major	Reliability	Balanced	Local-high
Core	G-7250	Never use RETURN in package initialization block.	Yes	Yes	No	No	Warning	Major	Reliability	Strict	Local-medium
Core	G-7310	Avoid standalone procedures – put your procedures in packages.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-high
Core	G-7320	Avoid using RETURN statements in a PROCEDURE.	Yes	Yes	No	No	Warning	Major	Maintainability	Strict	Local-medium
Core	G-7330	Always assign values to OUT parameters.	Yes	Yes	No	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-7410	Avoid standalone functions – put your functions in packages.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-high
Core	G-7420	Always make the RETURN statement the last statement of your function.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-high
Core	G-7430	Try to use no more than one RETURN statement within a function.	Yes	Yes	No	No	Warning	Major	Maintainability	Aggressive	Local-high
Core	G-7440	Never use OUT parameters to return values from a function.	Yes	Yes	No	No	Warning	Major	Maintainability	Strict	Local-high
Core	G-7450	Never return a NULL value from a BOOLEAN function.	Yes	No	No	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-7460	Try to define your packaged/standalone function deterministic if appropriate.	Yes	Yes	Yes	No	Warning	Major	Reliability	Extreme	Local-medium
Core	G-7510	Always prefix Oracle supplied packages with owner schema name.	Yes	No	Yes	No	Error	Blocker	Security	Strict	Local-easy
Core	G-7520	Avoid using deprecated units in your own code.	Yes	Yes	No	No	Warning	Major	Maintainability	Strict	Local-high
Core	G-7710	Avoid cascading triggers.	Yes	Yes	No	No	Warning	Major	Maintainability	Strict	Local-high
Core	G-7720	Never use multiple UPDATE OF in trigger event clause.	Yes	Yes	Yes	No	Error	Blocker	Maintainability	Essential	Local-medium
Core	G-7730	Avoid multiple DML events per trigger.	Yes	Yes	No	No	Warning	Minor	Reliability	Aggressive	Local-high
Core	G-7740	Never handle multiple DML events per trigger if primary key is assigned in trigger.	Yes	No	No	No	Warning	Critical	Reliability	Strict	Local-high
Core	G-7810	Never use SQL inside PL/SQL to read sequence numbers (or SYSDATE).	Yes	Yes	Yes	No	Warning	Critical	Reliability	Essential	Local-easy
Core	G-7910	Never use DML within a SQL macro.	Yes	No	No	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-8110	Never use SELECT COUNT(*) if you are only interested in the existence of a row.	Yes	No	No	No	Warning	Critical	Reliability	Balanced	Local-high
Core	G-8120	Never check existence of a row to decide whether to create it or not.	Yes	No	No	No	Warning	Critical	Reliability	Essential	Local-high
Core	G-8210	Always use synonyms when accessing objects of another application schema.	Yes	Yes	Yes	No	Warning	Minor	Maintainability	Extreme	Local-high
Core	G-8310	Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.	Yes	Yes	No	No	Warning	Minor	Maintainability	Extreme	Local-medium
Core	G-8410	Always use application locks to ensure a program unit is only running once at a given time.	Yes	Yes	No	No	Error	Blocker	Reliability	Strict	Local-high
Core	G-8510	Always use dbms_application_info to track program process transiently.	No	Yes	No	Yes	Warning	Critical	Reliability	Strict	Local-medium
Core	G-9010	Always use a format model in string to date/time conversion functions.	Yes	Yes	Yes	No	Error	Blocker	Security	Essential	Local-medium
Core	G-9020	Try to use a format model and NLS_NUMERIC_CHARACTERS in string to number conversion functions.	Yes	Yes	Yes	No	Warning	Critical	Reliability	Extreme	Local-medium
Core	G-9030	Try to define a default value on conversion errors.	Yes	Yes	Yes	No	Warning	Major	Maintainability	Aggressive	Local-medium
Core	G-9040	Try using FX in string to date/time conversion format model to avoid fuzzy conversion.	Yes	No	Yes	No	Error	Blocker	Reliability	Essential	Local-medium
Core	G-9101	Always follow naming conventions for global variables.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9102	Always follow naming conventions for local variables.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9103	Always follow naming conventions for cursor variables.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9104	Always follow naming conventions for record variables.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9105	Always follow naming conventions for collection variables (arrays/tables).	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9106	Always follow naming conventions for object variables.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9107	Always follow naming conventions for cursor parameters.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9108	Always follow naming conventions for IN parameters of functions and procedures.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9109	Always follow naming conventions for OUT parameters of functions and procedures.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9110	Always follow naming conventions for IN/OUT parameters of functions and procedures.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9111	Always follow naming conventions for record type definitions.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9112	Always follow naming conventions for collection type definitions (arrays/tables).	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9113	Always follow naming conventions for exceptions.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9114	Always follow naming conventions for constants.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9115	Always follow naming conventions for subtypes.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9116	Always follow naming conventions for record fields.	Yes	Yes	No	No	Warning	Minor	Maintainability	Strict	Other
Core	G-9201	Always follow naming conventions for tables.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9202	Always follow naming conventions for table/view columns.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9203	Always follow naming conventions for indexes.	No	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-high
Core	G-9204	Always follow naming conventions for primary key constraints.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-high
Core	G-9205	Always follow naming conventions for unique constraints.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-high
Core	G-9206	Always follow naming conventions for foreign key constraints.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-high
Core	G-9207	Always follow naming conventions for check constraints.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-high
Core	G-9208	Always follow naming conventions for assertions.	No	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9209	Always follow naming conventions for global temporary tables.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9210	Always follow naming conventions for views.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9211	Always follow naming conventions for sequences.	No	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9212	Always follow naming conventions for synonyms.	No	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9213	Always follow naming conventions for triggers.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Local-easy
Core	G-9214	Always follow naming conventions for PL/SQL packages.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9215	Always follow naming conventions for functions.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9216	Always follow naming conventions for procedures.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9217	Always follow naming conventions for object types.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9218	Always follow naming conventions for object type attributes.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9219	Always follow naming conventions for collection types.	Yes	Yes	No	Yes	Warning	Minor	Maintainability	Strict	Other
Core	G-9501	Never use parameter in string expression of dynamic SQL. Use asserted local variable instead.	Yes	No	Yes	No	Error	Blocker	Security	Essential	Local-medium
Core	G-9600	Never define more than one comment with hints.	Yes	No	Yes	No	Warning	Critical	Reliability	Essential	Local-medium
Core	G-9601	Never use unknown hints.	Yes	Yes	Yes	No	Warning	Critical	Reliability	Essential	Local-medium
Core	G-9602	Always use the alias name instead of the table name.	Yes	No	Yes	No	Warning	Critical	Reliability	Essential	Local-medium
Core	G-9603	Never reference an unknown table/alias.	Yes	No	Yes	No	Warning	Critical	Reliability	Essential	Local-medium
Core	G-9604	Never use an invalid stats method.	Yes	No	Yes	No	Warning	Critical	Reliability	Essential	Local-medium
Core	G-9605	Never use an invalid stats keyword.	Yes	No	Yes	No	Warning	Critical	Reliability	Essential	Local-medium

row(s) 1 - 186 of 186

Search

Overview