Troubleshooting FGA
Like any other complex and low-level feature in Oracle, FGA might at times produce unexpected results. In this section, I’ll go over some of the common FGA-related errors and how to handle them. Please note that I am not going to talk about FGA bugs—published or unpublished—that might affect its behavior. Bugs are often platform-specific and transient. I will instead focus on errors that can occur with typical use of FGA.
Any time there is a problem with FGA, a trace file is produced in the directory specified by the database initialization parameter USER_DUMP_DEST. This trace file shows important information about the exact error condition and offers clues for diagnosing it further. Here is an except from one such trace file:
/opt/app/oracle/admin/gridr/udump/gridr_ora_14424.trc Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - 64bit Production With the Partitioning, Oracle Label Security, OLAP and Data Mining options ORACLE_HOME = /opt/app/oracle/product/10g_gridr System name: SunOS Node name: smiley2.proligence.com Release: 5.9 Version: Generic_117171-12 Machine: sun4u Instance name: gridr Redo thread mounted by this instance: 1 Oracle process number: 54 Unix process pid: 14424, image: oraclegridr@smiley2.proligence.com *** 2005-07-12 19:01:44.337 *** ACTION NAME:( ) 2005-07-12 19:01:44.288 *** MODULE NAME:(SQL*Plus) 2005-07-12 19:01:44.288 *** SERVICE NAME:(SYS$USERS) 2005-07-12 19:01:44.288 *** SESSION ID:(165.51503) 2005-07-12 19:01:44.288 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access