Eddie Awad’s Blog - Latest Comments in About The BUILTIN, FIPSFLAG and INTERFACE Pragmas in Oracle

Re: About The BUILTIN, FIPSFLAG and INTERFACE Pragmas in Oracle

Jens — Sat, 03 Jun 2006 12:11:56 -0000

I would also guess that the pragma FIPSFLAG is related with the FIPS compliance.
There is a session parameter FLAGGER which causes an error message to be generated when a SQL statement issued is an extension of ANSI SQL92.
This would somehow explain why SQLERRM is declared with this pragma.

Re: About The BUILTIN, FIPSFLAG and INTERFACE Pragmas in Oracle

Eddie Awad — Sat, 03 Jun 2006 00:57:09 -0000

Pete, thanks for your work on this and the extra clarification.

Re: About The BUILTIN, FIPSFLAG and INTERFACE Pragmas in Oracle

Pete Finnigan — Fri, 02 Jun 2006 15:56:21 -0000

Hi Eddie,

Nice post!!

A couple of comments. Normally FIPS stands for Federal Information Processing Standards, I don't know but maybe its related?

Also on the Pragma interface C, if you read further in my first big Oracle paper (Expoliting and protecting Oracle) you will see that i tried to use the syntax myself but if fails with an ORA-6509 - ICD vector Processing error. I assumed at the time that Oracle implements a function call table. Like a table of structs that includes details for each function implemented as a pragma interface C call. This table or linked list would include function pointers for each C function, hence you cannot simply call your own C directly from PL/SQL unless you can update this table to add the address of the function you add. This is a great interface for calling C directly without the extproc overheads if only we coluld find a way to make it work..:-)

cheers

Pete