ORA-00226 Operation Disallowed while Alternate Control File Open

Error Code
ORA-00226

Description
Operation disallowed while alternate control file open.

Cause
Possible cause of this error is, the attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.

Action
To fix this issue, retry the operation after calling cfileUseCurrent.

reference

ORA-00225 Expected Size String of Control File Differs from Actual Size String

Error Code
ORA-00225

Description
Expected size string of control file differs from actual size string

Cause
Possible cause of this error is, the expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted.

Action
To fix this issue, restore a good copy of the control file.

reference

ORA-00224 Control File Resize Attempted with illegal Record Type

Error Code
ORA-00224

Description
Control file resize attempted with illegal record type (string).

Cause
Possible cause of this error is, an attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.

Action
To fix this issue, use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).

reference

ORA-00223 Convert File is Invalid or Incorrect Version

Error Code
ORA-00223

Description
Convert file is invalid or incorrect version

Cause
Possible cause of this error is, an Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued.

Action
To fix this issue, use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.

reference

ORA-00222 Operation would Reuse Name of a Currently Mounted control file

Error Code
ORA-00222

Description
Operation would reuse name of a currently mounted control file

Cause
Possible cause of this error is, the filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file.

Action
To fix this issue, Retry the operation with a different filename.

reference

ORA-00221 Error on Write to Control File

Error Code
ORA-00221

Description
Error on write to control file

Cause
Possible cause of this error is, an error occurred when writing to one or more of the control files.

Action
To fix this issue, see accompanying messages.

reference

ORA-00220 Control File not Mounted by First Instance

Error Code
ORA-00220

Description
Control File not mounted by first instance, check alert log for more info

Cause
Possible cause of this error is, the specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.

Action
To fix this issue, find and install the correct control file.

reference

ORA-00219 Required Control File Size Exceeds Maximum Allowable Size

Error Code
ORA-00219

Description
Required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks).

Cause
Possible cause of this error is, an invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.

Action
To fix this issue, in the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.

reference

ORA-00218 Block Size String of Control File 'string' does not match DB_BLOCK_SIZE

Error Code
ORA-00218

Description
Block size string of control file 'string' does not match DB_BLOCK_SIZE (string)

Cause
Possible cause of this error is, the block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.

Action
To fix this issue, restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.

reference

ORA-00217 Control File could not be Resized for New Record Types

Error Code
ORA-00217

Description
Control file could not be resized for new record types

Cause
Possible cause of this error is, the control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.

Action
To fix this issue, look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.

reference

ORA-00216 Control File could not be Resized for Migration

Error Code
ORA-00216

Description
Control file could not be resized for migration from 8.0.2

Cause
Possible cause of this error is, the control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.

Action
To fix this issue, look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.

reference

How to Enable and Disable ASP.NET TextBox Control on CheckBox Click in Java Script

• Create New Project in Visual Studio 2010 (or in any version).
• Add New Page ( named default.aspx ).
• Add Following aspx Code in default.aspx page.

        <table style="width: 100%;">

            <tr>

                <td align="right" style="width: 50%">

                    <asp:Label ID="LabelClick" runat="server" Text="Click Me !!!"></asp:Label>

                </td>

                <td align="left" style="width: 50%;">

                    <asp:CheckBox ID="CheckBox" onclick="EnableDisableTextBox();" Checked="false" runat="server" />

                </td>

            </tr>

            <tr>

                <td align="right" style="width: 50%">

                    <asp:Label ID="LabelName" runat="server" Text="Name:"></asp:Label>

                </td>

                <td align="left" style="width: 50%">

                    <asp:TextBox ID="TextBoxName" runat="server" Width="70%"></asp:TextBox>

                </td>

            </tr>

            <tr>

                <td align="right" style="width: 50%">

                    <asp:Label ID="LabelAge" runat="server" Text="Age:"></asp:Label>

                </td>

                <td align="left" style="width: 50%">

                    <asp:TextBox ID="TextBoxAge" runat="server" Width="70%"></asp:TextBox>

                </td>

            </tr>

        </table>

• Add Following Java Script Code inside head tag in default.aspx page.

    <script type="text/javascript" language="javascript">

        function EnableDisableTextBox() {

            var CallerCheckBoxID = "<%= CheckBox.ClientID %>";

            var LblName = "<%= LabelName.ClientID %>";

            var TxtName = "<%= TextBoxName.ClientID %>";

            var LblAge = "<%= LabelAge.ClientID %>";

            var TxtAge = "<%= TextBoxAge.ClientID %>";

            if (document.getElementById(CallerCheckBoxID).checked == true) {

                document.getElementById(LblName).disabled = true;

                document.getElementById(TxtName).disabled = true;

                document.getElementById(LblAge).disabled = true;

                document.getElementById(TxtAge).disabled = true;

            }

            else {

                document.getElementById(LblName).disabled = false;

                document.getElementById(TxtName).disabled = false;

                document.getElementById(LblAge).disabled = false;

                document.getElementById(TxtAge).disabled = false;

            }

        }

    </script>

You have all done. View it in browser.
Follow me on Facebook to get more cool tutorials. -:)

ORA-00215 Must be at Least one Control File

Error Code
ORA-00215

Description
Must be at least one control file.

Cause
Possible cause of this error is, no control file is specified or the control file specified does not exist.

Action
To fix this issue, specify at least one valid control file and retry the operation.

reference

ORA-00214 Control file String Version String Inconsistent

Error Code
ORA-00214

Description
Control file 'string' version string inconsistent with file 'string' version string.

Cause
Possible cause of this error is, an inconsistent set of control files, datafiles/logfiles, and redo files was used.

Action
To fix this issue, use a consistant set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.

reference

ORA-00213 Cannot Reuse Control File

Error Code
ORA-00213

Description
Cannot reuse control file; old file size string, string required.

Cause
Possible cause of this error is,to reuse a control file, it must be the same size as the one previously used.

Action
To fix this issue, either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.

reference

ORA-00212 Block Size String below Minimum Required Size of String Bytes

Error Code
ORA-00212

Description
Block size string below minimum required size of string bytes.

Cause
Possible cause of this error is, the block size specified was too small. Space for the system overhead is required.

Action
To fix this issue, specify a larger block size and retry the operation.

reference

ORA-00211 Control File does not Match Previous Control Files

Error Code
ORA-00211

Description
Control file does not match previous control files.

Cause
Possible cause of this error is, a control file was specified that belongs to another database.

Action
To fix this error, find and install the correct control file.

reference

ORA-00210 Cannot Open the Specified Control File

Error Code
ORA-00210

Description
Cannot open the specified control file.

Cause
Possible cause of this error is, cannot open the control file.

Action
To fix this issue, check to make sure the control file exists and is not locked by some other program.

reference

ORA-00209 Control File Blocksize Mismatch

Error Code
ORA-00209

Description
Control file blocksize mismatch, check alert log for more info.

Cause
Possible cause of this error is, the block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.

Action
To fix this issue, look at the alert log for more information.

reference

ORA-00208 Number of Control File Names Exceeds Limit of String

Error Code
ORA-00208

Description
Number of control file names exceeds limit of string.

Cause
Possible cause of this error is, an attempt was made to use more control files than Oracle supports.

Action
To fix this issue, shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files.

reference

ORA-00207 Control Files are not for the Same Database

Error Code
ORA-00207

Description
Control files are not for the same database.

Cause
Possible cause of this error is, the database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name.

Action
To fix this error, check that the control file is for the correct database and is not an old version.

reference

ORA-00206 Error in Writing Block String of Control File

Error Code
ORA-00206

Description
Error in writing (block string, # blocks string) of control file.

Cause
Possible cause of this error is, a disk I/O failure was detected on writing the control file.

Action
To fix this error, check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

reference

ORA-00205 Error in Identifying Control File

Error Code
ORA-00205

Description
Error in identifying control file, check alert log for more info.

Cause
Possible cause of this error is, the system could not find a control file of the specified name and size.

Action
To fix this issue, check that ALL control files are online and that they are the same files that the system created at cold start time.

reference

ORA-00204 Error in Reading Block String of Control File

Error Code
ORA-00204

Description
Error in reading (block string, # blocks string) of control file.

Cause
Possible cause of this error is, a disk I/O failure was detected on reading the control file.

Action
To fix this issue, check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

reference

ORA-00203 Using the Wrong Control Files

Error Code
ORA-00203

Description
Using the wrong control files.

Cause
Possible cause of this error is ,the mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file.

Action
To fix this issue, check that the correct control files were specified.

reference

ORA-00202 Control File String

Error Code
ORA-00202

Description
Control file: 'string'.

Cause
Possible cause of this error is, this message reports the name file involved in other messages.

Action
To fix this error, see associated error messages for a description of the problem.

reference

ORA-00201 Control File Version String Incompatible with ORACLE Version String

Error Code
ORA-00201

Description
Control file version string incompatible with ORACLE version string.

Cause
Possible cause of this error is, the control file was created by incompatible software.

Action
To fix this error, either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.

reference

ORA-00200 Control File could not be Created

Error Code
ORA-00200

Description
Control file could not be created.

Cause
Possible cause of this error is, it was not possible to create the control file.

Action
To fix this issue, check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.

reference

ORA-00166 Remote or Local Nesting Level is too Deep

Error Code
ORA-00166

Description
Remote/local nesting level is too deep.

Cause:
Possible cause of this error is, too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.

Action
To fix this error, rearrange the query or co-locate the functions with the tables.

reference

ORA-00165 Migratable Distributed Autonomous Transaction with Remote Operation is not Allowed

Error Code
ORA-00165

Description
Migratable distributed autonomous transaction with remote operation is not allowed.

Cause
Possible cause of this error is, a request was made by the application to start a migratable distributed autonomous transaction with remote operation.

Action
none

reference

ORA-00164 Distributed Autonomous Transaction Disallowed within Migratable Distributed Transaction

Error Code
ORA-00164

Description
Distributed autonomous transaction disallowed within migratable distributed transaction

Cause
Possible cause of this error is, a request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.

Action
To fix this error, roll back or commit the current distributed transaction first.

reference

ORA-00163: Internal Database Name Length String is Greater than Maximum

Error Code
ORA-00163

Description
Internal database name length string is greater than maximum (string).

Cause
Possible cause of this error is, an internal database name with a too large length field was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

ORA-00162 External dbid Length String is Greater than Maximum

ErrorCode
ORA-00162

Description
External dbid length string is greater than maximum (string).

Cause
Possible cause of this error is, an external database name with too large a length field was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

ORA-00161 Transaction Branch Length String is Illegal

Error Code
ORA-00161

Description
Transaction branch length string is illegal (maximum allowed string).

Cause
Possible cause of this error is, an external transaction branch ID with a length either too large or 0 was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

ORA-00160 Global Transaction Length String is Greater than Maximum

Error Code
ORA-00160

Description
Global transaction length string is greater than maximum (string).

Cause
Possible cause of this error is, an external global transaction ID with a too large length field was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

ORA-00155 Cannot Perform Work Outside of Global Transaction

Error Code
ORA-00155

Description
Cannot perform work outside of global transaction.

Cause
Possible cause of this error is, the application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.

Action
To fix this error, check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.

reference

ORA-00154 Protocol Error in Transaction Monitor

Error Code
ORA-00154

Description
Protocol error in transaction monitor.

Cause
Possible cause of this error is, the transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.

Action
To fix this error, contact the transaction monitor customer support.

reference

ORA-00153 Internal Error in XA Library

Error Code
ORA-00153

Description
Internal error in XA library.

Cause
Possible cause of this error is, the XA library could not access thread-specific pointers.

Action
To fix this error, contact customer support.

reference

ORA-00152 Current Session does not Match Requested Session

Error Code
ORA-00152

Description
Current session does not match requested session.

Cause
Possible cause of this error is, the current session is not the same as the session that was passed into a upixado() call.

Action
To fix this error, check your application.

reference

ORA-00151 Invalid Transaction ID

Error Code
ORA-00151

Description
Invalid transaction ID.

Cause
Possible cause of error is, the specified transaction ID does not correspond to an existing valid transaction.

Action
To fix this error, check your application.

reference

ORA-00150 Duplicate Transaction ID

Error Code
ORA-00150

Description
Duplicate transaction ID.

Cause
Possible cause of this error is, attempted to start a new transaction with an ID already in use by an existing transaction.

Action
To fix this error, check your application.

reference

ORA-00134 Invalid Dispatchers Specification String

Error Code
ORA-00134

Description
Invalid DISPATCHERS specification #string.

Cause
Possible cause of this error is, the syntax for the n-th DISPATCHERS specification was incorrect.

Action
To fix this error, refer to the Oracle Reference Manual for the correct syntax.

reference

ORA-00133 Value of String is too Long

Error Code
ORA-00133

Description
Value of string is too long.

Cause
Possible cause of this error is, the value specified for the attribute was too long.

Action
To fix this error, use shorter names and keywords or remove unneeded blanks.

reference

ORA-00132 Syntax Error or Unresolved Network Name String

Error Code
ORA-00132

Description
Syntax error or unresolved network name 'string'.

Cause
Possible cause of this error is, listener address has syntax error or cannot be resolved.

Action
To fix this error, if a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct.

reference

ORA-00131 Network Protocol does not Support Registration String

Error Code
ORA-00131

Description
Network protocol does not support registration 'string'.

Cause
Possible cause of this error is, the specified protocol does not support async notification.

Action
To fix this error, refer to the manual for information on supported network protocols.

reference

ORA-00130 Invalid Listener Address String

Error Code
ORA-00130

Description
Invalid listener address 'string'

Cause
Possible cause of this error is, the listener address specification is not valid.

Action
To fix this error, make sure that all fields in the listener address (protocol, port, host, key, ...) are correct.

reference

ORA-00129 Listener Address Validation Failed String

Error Code
ORA-00129

Description
Listener address validation failed 'string'.

Cause
Possible cause of this error is, an error was encountered while validating the listener address.

Action
To fix this problem, resolve error or contact your ORACLE representative.

reference

ORA-00128 This Command Requires a Dispatcher Name

Error Code
ORA-00128

Description
This command requires a dispatcher name.

Cause
Possible cause of this error is, wrong syntax for ALTER SYSTEM SHUTDOWN

Action
To fix this error, use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name'.

reference

ORA-00127 Dispatcher string does not exist

Error Code
ORA-00127

Description
Dispatcher string does not exist.

Cause
Possible cause of this error is, there is currently no dispatcher running with the specified name.

Action
To fix this error, retry with a name of the form "D###" denoting an existing dispatcher process.

reference

ORA-00126 Connection Refused Invalid Duplicity

Error Code
ORA-00126

Description
Connection refused, invalid duplicity.

Cause
Possible cause of this error is, the DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

Action
To fix this error, correct the DUPLICITY specified in the TNS address.

reference