ORA-12324: cannot use the ROM: link type on a private database link

Cause : You can only specify the ROM: link type on a public, not a private, database link.

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

Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command.

update : 22-08-2017

ORA-12324 - cannot use the ROM: link type on a private database link
ORA-12324 - cannot use the ROM: link type on a private database link

  • ora-13439 : GeoRaster metadata pyramid maxLevel error
  • ora-09793 : szguns: length of user name is greater than buffer.
  • ora-31452 : invalid value string for parameter, expecting: Y or N
  • ora-26576 : cannot acquire SR enqueue
  • ora-24235 : bad value for object type: string
  • ora-30967 : operation directly on the Path Table is disallowed
  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-23343 : no match for specified conflict resolution information
  • ora-29395 : cannot set the initial consumer group to string
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-13466 : format not appropriate for specified compression method
  • ora-26079 : file "string" is not part of table string.string
  • ora-01517 : log member: 'string'
  • ora-30941 : Cannot specify empty URI for non-default namespace 'string'
  • ora-24164 : invalid rule engine system privilege: string
  • ora-14082 : new partition name must differ from that of any other partition of the object
  • ora-14062 : one or more of table's partitions reside in a read-only tablespace
  • ora-06010 : NETASY: dialogue file too long
  • ora-30389 : the source statement is not compatible with the destination statement
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-06422 : NETCMN: Error in sending data
  • ora-27044 : unable to write the header block of file
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-02195 : Attempt to create string object in a string tablespace
  • ora-26033 : column string.string encryption properties differ for source or target table
  • ora-25337 : Cannot propagate in queue-to-queue mode to a database with version lower than 10.2
  • ora-24165 : invalid rule engine object privilege: string
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-01195 : online backup of file string needs more recovery to be consistent
  • 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.