ORA-31086: insufficient privileges to register schema "string"

Cause : An attempt was made to register a schema without sufficient privileges.

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

Make sure that the user has sufficient privileges to register the schema.

update : 18-08-2017
ORA-31086

ORA-31086 - insufficient privileges to register schema "string"
ORA-31086 - insufficient privileges to register schema "string"

  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-14513 : partitioning column may not be of object datatype
  • ora-39114 : Dump files are not supported for network jobs.
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-30432 : summary 'string.string' is in INVALID state
  • ora-30969 : invalid syntax for PARAMETERS
  • ora-26050 : Direct path load of domain index is not supported for this column type.
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-14264 : table is not partitioned by Composite Range method
  • ora-24072 : cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
  • ora-12151 : TNS:received bad packet type from network layer
  • ora-37113 : OLAP API initialization error: (string)
  • ora-24756 : transaction does not exist
  • ora-23504 : columns added to table do not match list of columns to be added
  • ora-15017 : diskgroup "string" cannot be mounted
  • ora-07645 : sszfsl: $CHANGE_CLASS failure
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-00368 : checksum error in redo log block
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-04051 : user string cannot use database link string.string
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-09875 : TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-02039 : bind by value is not allowed for array type
  • ora-39029 : worker string with process name "string" prematurely terminated
  • ora-36634 : (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
  • ora-02241 : must of form EXTENTS (FILE BLOCK SIZE , ...)
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-12433 : create trigger failed, policy not applied
  • 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.