PCC-00078: FIPS warning: Invalid ANSI SQL Identifier
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the name given to a host variable: o is longer than 18 characters, o does not begin with a letter, or o contains consecutive or trailing underscores. In the following Pro*C example, the host variable name is 19 characters long and therefore non-compliant: EXEC SQL BEGIN DECLARE SECTION; int department_location: --not ANSI or ISO compliant EXEC SQL END DECLARE SECTION; This informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI or ISO compliance, change the host variable name so that it is lamp;lt;lamp;nbsp;= 18 characters long, begins with a letter, and does not contain consecutive or trailing underscores.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the name given to a host variable: o is longer than 18 characters, o does not begin with a letter, or o contains consecutive or trailing underscores. In the following Pro*C example, the host variable name is 19 characters long and therefore non-compliant: EXEC SQL BEGIN DECLARE SECTION; int department_location: --not ANSI or ISO compliant EXEC SQL END DECLARE SECTION; This informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI or ISO compliance, change the host variable name so that it is lamp;lt;lamp;nbsp;= 18 characters long, begins with a letter, and does not contain consecutive or trailing underscores.
No comments:
Post a Comment