Error Code
ORA-00236
Description
Snapshot operation disallowed, mounted control file is a backup.
Cause
Possible cause of this error is, attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.
Action
To fix this issue, mount a current control file and retry the operation.
reference
Tuesday, April 30, 2013
ORA-00235 Control File Fixed Table Inconsistent due to Concurrent Update
Error Code
ORA-00235
Description
Control file fixed table inconsistent due to concurrent update.
Cause
Possible cause of this error is, concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.
Action
To fix this issue, retry the operation.
reference
ORA-00235
Description
Control file fixed table inconsistent due to concurrent update.
Cause
Possible cause of this error is, concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.
Action
To fix this issue, retry the operation.
reference
ORA-00234 Error in Identifying or Opening Snapshot or Copy Control File
Error Code
ORA-00234
Description
Error in identifying or opening snapshot or copy control file
Cause
Possible cause of this error is, a snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
Action
To fix this issue, re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.
reference
ORA-00234
Description
Error in identifying or opening snapshot or copy control file
Cause
Possible cause of this error is, a snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
Action
To fix this issue, re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.
reference
ORA-00233 Copy Control File is Corrupt or Unreadable
Error Code
ORA-00233
Description
Copy control file is corrupt or unreadable.
Cause
Possible cause of this error is, the specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.
Action
To fix this issue, before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy.
reference
ORA-00233
Description
Copy control file is corrupt or unreadable.
Cause
Possible cause of this error is, the specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.
Action
To fix this issue, before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy.
reference
ORA-00232 Snapshot Control File is Nonexistent Corrupt or Unreadable
Error Code
ORA-00232
Description
Snapshot control file is nonexistent, corrupt, or unreadable.
Cause
Possible cause of this error is, the snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
Action
To fix this issue, call cfileMakeAndUseSnapshot again or for the first time.
reference
ORA-00232
Description
Snapshot control file is nonexistent, corrupt, or unreadable.
Cause
Possible cause of this error is, the snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
Action
To fix this issue, call cfileMakeAndUseSnapshot again or for the first time.
reference
Monday, April 29, 2013
ORA-00231 Snapshot Control File has not been Named
ErrorCode
ORA-00231
Description
Snapshot control file has not been named.
Cause
Possible cause of this error is, during an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
Action
To fix this issue, specify a name for the snapshot control file by calling cfileSetSnapshotName.
reference
ORA-00231
Description
Snapshot control file has not been named.
Cause
Possible cause of this error is, during an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
Action
To fix this issue, specify a name for the snapshot control file by calling cfileSetSnapshotName.
reference
ORA-00230 Operation Disallowed Snapshot Control File Enqueue Unavailable
Error Code
ORA-00230
Description
Operation disallowed, snapshot control file enqueue unavailable.
Cause
Possible cause of this error is, the attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
Action
To fix this issue, retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.
reference
ORA-00230
Description
Operation disallowed, snapshot control file enqueue unavailable.
Cause
Possible cause of this error is, the attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
Action
To fix this issue, retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.
reference
ORA-00229 Operation Disallowed Already Hold Snapshot Control File Enqueue
Error Code
ORA-00229
Description
Operation disallowed already hold snapshot control file enqueue.
Cause
Possible cause of this error is, the attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.
Action
To fix this issue, retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.
reference
ORA-00229
Description
Operation disallowed already hold snapshot control file enqueue.
Cause
Possible cause of this error is, the attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.
Action
To fix this issue, retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.
reference
ORA-00228 Length of Alternate Control File Name Exceeds Maximum of String
Error Code
ORA-00228
Description
Length of alternate control file name exceeds maximum of string.
Cause
Possible cause of this error is, the specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system.
Action
To fix this issue, retry the operation with a shorter filename.
reference
ORA-00228
Description
Length of alternate control file name exceeds maximum of string.
Cause
Possible cause of this error is, the specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system.
Action
To fix this issue, retry the operation with a shorter filename.
reference
ORA-00227 Corrupt Block Detected in Control File
Error Code
ORA-00227
Description
Corrupt block detected in control file: (block string, # blocks string).
Cause
Possible cause of this error is, a block header corruption or checksum error was detected on reading the control file.
Action
To fix this issue, use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.
reference
ORA-00227
Description
Corrupt block detected in control file: (block string, # blocks string).
Cause
Possible cause of this error is, a block header corruption or checksum error was detected on reading the control file.
Action
To fix this issue, use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.
reference
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-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-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-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
Sunday, April 21, 2013
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-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-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-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-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-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-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-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
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
Friday, April 19, 2013
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>
Subscribe to:
Posts (Atom)