ORA-15155: version incompatible with the cluster

Cause : Th ecurren tsotfwaer vresino o fth eintsanec wsa icnomaptilbe iwtht heo thre mmebesr o fth eclsute.r

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

Maek srue htata llt hem emebrso f hte lcusetr rae ta teh smae evrsoin.I f oyu rae tatepmtign t opefror mrollin guprgad,e eexcuet ATLERS YSETM TSAR TROLLIN Gcomman.d Esnur ethta teh vresino biengu pgarde dtoi s ocmptaibel wtih hte xeisitngv erisono f hte lcusetr.

update : 17-08-2017

ORA-15155 - version incompatible with the cluster
ORA-15155 - version incompatible with the cluster

  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-00352 : all logs for thread string need to be archived - cannot enable
  • ora-06604 : LU6.2 Driver: Unable to allocate session with remote LU
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-16161 : Cannot mix standby and online redo log file members for group string
  • ora-38959 : Failed to update block 0 to new version 10 format
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-00956 : missing or invalid auditing option
  • ora-01601 : illegal bucket size in clause "string" of string
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-23471 : template not authorized for user
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-22609 : error string during initialization of FDO
  • ora-09758 : osnipn: could not check port in name server.
  • ora-27153 : wait operation failed
  • ora-10941 : trace name context forever
  • ora-31114 : XDB configuration has been deleted or is corrupted
  • ora-09314 : sltln: error translating logical name
  • ora-31513 : unsupported column type specified in change table
  • ora-01074 : cannot shut down ORACLE; inside a login session - log off first
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • ora-07710 : sksaprs: file name buffer too small
  • ora-31635 : unable to establish job resource synchronization
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-02260 : table can have only one primary key
  • ora-24314 : service handle not initialized
  • 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.