Action Check the statement for a typing mistake in the filename and check for the existence of all files...

Linki


» Dzieci to nie książeczki do kolorowania. Nie da się wypełnić ich naszymi ulubionymi kolorami.
» If both a table EMP in schema PAYROLL and a package PAYROLL with function/ procedure EMP in the current schema exist, the statement DESCRIBE FUNCTION payroll...
» In another mechanism, the action yyclearin clears the current symbol after an error which follows the error entity...
» Simple Frame Actions lub Simple Buttons w menu Control nie spowoduje wykonanianowych akcji w skryptach...
» Action Rewrite the trigger or function so it does not read the table...
» ActionEvent Scrollbar AdjustmentEvent, FocusEvent, KeyEvent, MouseEvent, ComponentEvent ScrollPane ContainerEvent,...
» Action This thread is not required for the operation of the database...
» NOTE: PL/SQL script files can be executed using the START command or the character @...
» any inference from the appearance of one to the existence of another...
» cannot modify files that were installed during setup...
» Once you are happy with the various statements that you want to use, you need to associate each of these statements with the method that will use it...

Dzieci to nie książeczki do kolorowania. Nie da się wypełnić ich naszymi ulubionymi kolorami.

Then issue the statement again after correcting the filenames.
ORA–01171
datafile str is going offline due to error advancing checkpoint Cause
The checkpoint in the file header could not be advanced. See accompanying messages for the reason. The datafile will be taken offline the same as for a write error of a data block.
Action
See accompanying messages for details. Restore access to the file, do media recovery, and bring it back online.
2 – 96
Oracle7 Server Messages
01100–01250: Oracle Files
ORA–01172
recovery of thread num stuck at block num of file name
Cause
Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.
Action
Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, then restore the file from a backup and recover it again.
ORA–01173
data dictionary indicates missing datafile from system tablespace Cause
Either
• The database is recovered to a point in time in the future of the control file.
• A datafile from the system tablespace is omitted from the issued CREATE
CONTROLFILE statement.
Action
Either
• Recover the database from a more recent control file.
• Re–create the control file, ensuring all datafiles are included for the system tablespace in the command line.
ORA–01174
DB_FILES is num but needs to be num to be compatible Cause
The maximum number of datafiles supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
Action
Change the value of the DB_FILES initialization parameter to be compatible.
ORA–01175
data dictionary has more than the num files allowed by the instance Cause
The data dictionary has more files than the instance can support.
Action
Increase the value of the initialization parameter DB_FILES, then shut down and restart the instance.
ORA–01176
data dictionary has more than the num files allowed by the control file Cause
After a CREATE CONTROLFILE statement, the data dictionary has more datafiles than supported by the control file.
Action
Re–create the control file with a larger value for MAXDATAFILES.
Oracle7 Server Messages
2 – 97
01100–01250: Oracle Files
ORA–01177
datafile does not match dictionary – probably old incarnation
Cause
When comparing the control file with the data dictionary after a CREATE
CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.
Action
Do a CREATE CONTROLFILE with the correct file or none at all.
ORA–01178
file name created before last CREATE CONTROLFILE, cannot be recreated Cause
An attempt was made to use the ALTER DATABASE CREATE datafile to
re–create a datafile that existed at the last CREATE CONTROLFILE command.
The information needed to re–create the file was lost with the control file that existed when the file was added to the database.
Action
Find a backup of the file and recover it. Perform incomplete recovery to the time before the file was originally created.
ORA–01179
file name does not exist
Cause
During datafile recovery, a file was listed that was not part of the database.
Action
Recheck the filename. Remember to use single quotation marks at the SQL*DBA command line. Remember also that the filename is translated in the operating environment of SQL*DBA.
ORA–01180
cannot create datafile 1
Cause
datafile 1 cannot be created with the ALTERDATABASECREATEDATA
FILE command.
Action
Either recover the file from a backup or re–create the database.
ORA–01181
file name created before last RESETLOGS, cannot be recreated Cause
An attempt was made to use the ALTER DATABASE CREATE datafile

Powered by MyScript