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 : 25-06-2017
ORA-12324

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-32618 : incorrect use of MODEL PREVIOUS function
  • ora-30747 : cannot create substitutable tables or columns of non final type string.string
  • ora-07416 : slpath: pathname construction failed; lack of output buffer space.
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-00077 : dump string is not valid
  • ora-30653 : reject limit reached
  • ora-13408 : invalid blockSize storage parameter
  • ora-24413 : Invalid number of sessions specified
  • ora-16811 : apply instance not recorded by the Data Guard broker
  • ora-30963 : The indexed column is not of XMLType.
  • ora-02164 : DATAFILE clause specified more than once
  • ora-13250 : insufficient privileges to modify metadata table entries
  • ora-04931 : unable to set initial sequence number value
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-15090 : handle string is not a valid descriptor
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-22928 : invalid privilege on directories
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-09979 : skxfqhsnd: Error Sending a message to another endpoint
  • ora-27156 : request for process information failed
  • ora-13402 : the rasterType is null or not supported
  • ora-31626 : job does not exist
  • ora-06547 : RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
  • ora-38440 : attribute set string does not exist
  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-09927 : Unable to set label of server
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-29521 : referenced name string could not be found
  • ora-14152 : invalid number of partitions specified in PARTITIONS clause
  • 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.