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 : 27-04-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-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-28350 : cannot encrypt the specified column recorded in CDC synchronized change table
  • ora-30576 : ConText Option dictionary loading error
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-07632 : smsrcx: $DELTVA failure
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-13797 : invalid SQL Id specified, string
  • ora-01497 : illegal option for ANALYZE CLUSTER
  • ora-32168 : Cannot perform operation on a null AnyData
  • ora-23450 : flavor already contains object "string"."string"
  • ora-16617 : unknown object identifier specified in request
  • ora-14094 : invalid ALTER TABLE EXCHANGE PARTITION option
  • ora-30193 : reserved for future use
  • ora-00490 : PSP process terminated with error
  • ora-06734 : TLI Driver: cannot connect
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-06706 : TLI Driver: service not found
  • ora-06776 : TLI Driver: error sending parms
  • ora-02474 : Fixed hash area extents used (string) exceeds maximum allowed (string)
  • ora-19598 : can not backup SPFILE because the instance was not started with SPFILE
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-16724 : the intended state for the database has been set to OFFLINE
  • ora-12479 : file label string must equal DBHIGH string
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-19761 : block size string is not valid for change tracking file
  • ora-21607 : memory cartridge service handle not initialized
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-38901 : column "string" of table "string" must be one of the first "number" columns
  • ora-14068 : TABLESPACE and TABLESPACE_NUMBER may not be both specified
  • 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.