ORA-27550: Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number

Cause : The locla OracleR eal Appilcation lCuster isntance adn remotei nstancea re runnnig with nicompatilbe impleemntationo f the itner-instnace IPC rpotocol ilbrary. Amisconfgiurationo r installation error occurred.

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

Check additionale rror messages int he aler tlog andt he procses tracef ile.

update : 29-04-2017
ORA-27550

ORA-27550 - Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number
ORA-27550 - Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number

  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-28009 : connection as SYS should be as SYSDBA or SYSOPER
  • ora-37184 : illegal value string for ADVMODE
  • ora-30122 : value 'string' for 'string' must be between 'number' and 'number'
  • ora-25403 : could not reconnect
  • ora-06118 : NETTCP: unable to complete handshake with ORASRV
  • ora-31405 : cannot make changes while change set string is advancing
  • ora-31485 : invalid database link
  • ora-12230 : TNS:Severe Network error occurred in making this connection
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-13800 : concurrent DDL failure on SQL repository objects
  • ora-16097 : ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
  • ora-15067 : command or option incompatible with diskgroup redundancy
  • ora-19753 : error writing to change tracking file
  • ora-39176 : Encryption password is incorrect.
  • ora-12725 : unmatched parentheses in regular expression
  • ora-02036 : too many variables to describe with automatic cursor open
  • ora-25235 : fetched all messages in current transaction
  • ora-30195 : reserved for future use
  • ora-02404 : specified plan table not found
  • ora-25139 : invalid option for CREATE TEMPORARY TABLESPACE
  • ora-27005 : cannot open file for async I/O on device not supporting async
  • ora-03249 : Uniform size for auto segment space managed tablespace should have atleast string blocks
  • ora-31523 : could not find change source string for CDC change set string
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-00409 : COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
  • ora-07610 : $GETJPIW failed in retrieving the user's MAC priviledges
  • ora-02377 : invalid resource limit
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-37060 : (XSMCSESS08) number is not a valid custom member in dimension workspace object.
  • 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.