ORA-19683: real and backup blocksize of file string are unequal

Cause : block size changed between backup & real file

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

use right backup

update : 23-04-2017

ORA-19683 - real and backup blocksize of file string are unequal
ORA-19683 - real and backup blocksize of file string are unequal

  • ora-23313 : object group "string"."string" is not mastered at string
  • ora-07444 : function address string is not readable
  • ora-26031 : index maintenance error, the load cannot continue
  • ora-24157 : duplicate variable name string
  • ora-00321 : log string of thread string, cannot update log file header
  • ora-12685 : Native service required remotely but disabled locally
  • ora-12707 : error while getting create database NLS parameter string
  • ora-01569 : data file too small for system dictionary tables
  • ora-12674 : Shared server: proxy context not saved
  • ora-12915 : Cannot alter dictionary managed tablespace to read write
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-27431 : chain string.string has a user-managed rule set
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-01409 : NOSORT option may not be used; rows are not in ascending order
  • ora-32106 : array fetch not allowed without setBuffer on all columns
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-38029 : object statistics are locked
  • ora-10281 : maximum time to wait for process creation
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-01280 : Fatal LogMiner Error.
  • ora-25011 : cannot create trigger on internal AQ table
  • ora-00452 : foreground process unexpectedly terminated with error string
  • ora-02833 : Server was unable to close file
  • ora-16745 : unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-39064 : unable to write to the log file
  • ora-09750 : pw_attachPorts: port_rename failed.
  • ora-16510 : messaging error using ksrwait
  • 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.