ORA-28105: cannot create security relevant column policy in an object view

Cause : Security relevant column argument is not null in policy creation for an object view

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts


update : 29-06-2017

ORA-28105 - cannot create security relevant column policy in an object view
ORA-28105 - cannot create security relevant column policy in an object view

  • ora-01300 : writable database required for specified LogMiner options
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-12629 : TNS:no event test
  • ora-14551 : cannot perform a DML operation inside a query
  • ora-39765 : stream must be reset before used in a column array conversion
  • ora-00025 : failed to allocate string
  • ora-21612 : key is already being used
  • ora-00471 : DBWR process terminated with error
  • ora-19611 : backup piece out of order. Expected string but found string
  • ora-19527 : physical standby redo log must be renamed
  • ora-04054 : database link string does not exist
  • ora-19687 : SPFILE not found in backup set
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-12481 : effective label not within program unit clearance range
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-10244 : make tranids in error msgs print as 0.0.0 (for testing)
  • ora-13142 : invalid PROXIMITY window definition
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-01651 : unable to extend save undo segment by string for tablespace string
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-24079 : invalid name string, names with AQ$_ prefix are not valid for string
  • ora-31510 : name uses reserved prefix CDC$
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-14451 : unsupported feature with temporary table
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-13389 : unable to compute buffers or intersections in analysis function
  • ora-16533 : inconsistent Data Guard broker state
  • ora-39779 : type "string"."string" not found or conversion to latest version is not possible
  • ora-12159 : TNS:trace file not writeable
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.