Oracle7 Server Migration Guide Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents
Go to Index
Index



Go to previous file in sequence Go to next file in sequence

Migration Utility Errors and Messages


The Migration Utility can return various error messages and informational messages. This appendix describes the errors that can be encountered when using the Migration Utility. For each error, probable cause and corrective action are given. Informational messages are also listed, although no action is necessary.

Cannot create conversion file, records exceed num bytes

Cause:An internal error has occurred. A valid control file could not be created from the Version 6 control file.
Action:Check the Version 6 control file for corruption, fix any problems, and rerun the Migration Utility.
CFILE - use this init.ora file

Cause:This is an informational message that displays information about the CFILE command-line argument.
Action:No user action is required.
CHECK_ONLY - estimate V7 catalog space requirement only

Cause:This is an informational message that displays information about the CHECK_ONLY command-line argument.
Action:No user action is required.
CHECK_ONLY and NO_SPACE_CHECK are mutually exclusive

Cause:Two mutually exclusive command-line options were passed to the Migration Utility.
Action:Rerun the Migration Utility using only one of these options.
Command-line argument value must be TRUE or FALSE (str)

Cause:You entered a command-line argument with a value other than TRUE or FALSE.
Action:Check the syntax of the command-line argument, correct the statement, and retry the operation.
Command-line arguments must be of the form <keyword>=<value> (str)

Cause:You used a command-line argument improperly.
Action:Check the syntax of the command-line argument, correct the statement, and retry the operation.
Command-line arguments:

Cause:This is an informational message that displays the command-line arguments.
Action:No user action is required.
Command name not found (str)

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
Command not of form CMD(ARG1, ARG2, ...)

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
CNVFILE - use this file for convert.ora

Cause:This is an informational message that displays information about the CNVFILE command-line argument.
Action:No user action is required.
Copy long command must be of form

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
Could not find single contiguous extent of numbytes for c_file#_block#

Cause:You do not have enough contiguous space in your SYSTEM tablespace.
Action:Add free space to your SYSTEM tablespace and repeat the migration.
Could not find single contiguous extent of numbytes for c_ts#

Cause:You do not have enough contiguous space in your SYSTEM tablespace.
Action:Add free space to your SYSTEM tablespace and repeat the migration.
Could not translate logical name

Cause:An internal error has occurred.
Action:Check that the logical is defined correctly and rerun the Migration Utility.
Data type must be long for column name

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
DBNAME - database name

Cause:This is an informational message that displays information about the DBNAME command-line argument.
Action:No user action is required.
Dictionary constant not found - name

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
DUMPCF - dump control file symbolically

Cause:This is an informational message that displays information about the DUMPCF command-line argument. You should generally only use this argument when asked to do so by your Customer Support representative.
Action:No user action is required.
ECHO - echo all SQL statements to standard out

Cause:This is an informational message that displays information about the ECHO command-line argument.
Action:No user action is required.
Error calling slgtd

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
Error closing file name

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
File header does not fit in num bytes

Cause:An internal error has occurred.
Action:Check the control file for corruption, fix any problems, and repeat the migration.
Fixed portion of control file does not fit in num bytes

Cause:An internal error has occurred.
Action:Check the control file for corruption, fix any problems, and repeat the migration.
Found NULL SQL statement

Cause:An internal error has occurred; possibly the MIGRATE.SQL script is corrupted.
Action:Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target Oracle7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any such problems and rerun the migration.
Free space found: num

Cause:This is an informational message that informs you how much free space you have in your SYSTEM tablespace.
Action:Be certain that you have enough free space before running the Migration Utility.
Incomplete write

Cause:An internal error has occurred. Data could not be written to disk.
Action:Check that the file access permissions are correct, that you have enough space or quota to write this file, and that the disk is not corrupt. Fix any problems and repeat the migration.
Insufficient space for new dictionaries, num bytes needed, num found

Cause:There is insufficient room in your SYSTEM tablespace for the new data dictionary information.
Action:Allocate the additional space required in the SYSTEM tablespace, and rerun the Migration Utility.
MIGFILE - use this file for MIGRATE.BSQ

Cause:This is an informational message that displays information about the MIGFILE command-line argument.
Action:No user action is required.
Mounting database ...

Cause:This is an informational message. The Migration Utility is mounting the Version 6 database.
Action:No user action is required.
NEW_DBNAME - new name for the database

Cause:This is an informational message that displays information about the NEW_DBNAME command-line argument.
Action:No user action is required.
NO_SPACE_CHECK - do not execute the space check

Cause:This is an informational message that displays information about the NO_SPACE_CHECK command-line argument.
Action:No user action is required. You should be certain that you have adequate space before running the Migration Utility with this option.
Offline tablespaces with outstanding undo, cannot proceed

Cause:One or more tablespaces were offline, with outstanding save undo, when you attempted to use the Migration Utility to migrate.
Action:If you are using Release 6.0.34.3, or later, complete the following steps:

Opening database ...

Cause:This is an informational message. The Migration Utility is opening the Version 6 database.
Action:No user action is required.
ORA-num: ???

Cause:The Migration Utility has received an ORA error and cannot retrieve the message text for the error.
Action:Take appropriate action for Oracle error num.
Parameter file exceeds num bytes

Cause:The parameter file for your Version 6 database exceeds the maximum size given.
Action:If possible, reduce the size of your parameter file by removing obsolete parameters. Otherwise, contact your Customer Support representative.
Parameter buffer overflow

Cause:The initialization parameter file is too large to fit in the buffer.
Action:Reduce the size of the parameter file, possibly by removing any obsolete parameters, and repeat the migration.
PFILE - use this init.ora file

Cause:This is an informational message that displays information about the PFILE command-line argument.
Action:No user action is required.
Seek error in file name

Cause:An internal error has occurred.
Action:An error occurred reading file name. Check that the file and disk are not corrupted. Fix any such corruption before restarting the migration.
Short read, num bytes requested, num bytes read

Cause:There is a problem reading the control file.
Action:Check the CFILE parameter to make certain that the Migration Utility is using the correct control file.
Shutting down database (abort) ...

Cause:An internal error has occurred.
Action:Additional error messages should occur to inform you of the cause of the shutdown. Follow the actions suggested for these messages.
Shutting down database ...

Cause:This is an informational message. The Migration Utility is shutting down the Version 6 database.
Action:No user action is required.
SPOOL - spool output to file

Cause:This is an informational message that displays information about the SPOOL command-line argument.
Action:No user action is required.
Starting up database ...

Cause:This is an informational message. The Migration Utility is starting up a Version 6 instance.
Action:No user action is required.
Too many arguments in command (num max)

Cause:You specified too many arguments on the command-line.
Action:Check the syntax of the command and specify fewer command-line options.
Unable to open file name

Cause:An internal error has occurred, or a database file was offline or not in the expected location when the Migration Utility was started.
Action:Check to see that all database files are online before shutting down your Version 6 database. Check that the file exists and has access permissions that allow Oracle to open and read the file. If possible, check that the file is not corrupt and the disks on which the file resides are not corrupt. Fix any problems and restart the Migration Utility.
Unable to allocate buffer space to copy longs

Cause:The Migration Utility could not allocate memory to serve as a buffer for copying LONG columns in the database.
Action:Make sure enough machine resources are available for the utility and rerun the migration.
Unable to read file name

Cause:An internal error occurred, or a database file was offline or not in the expected location when the Migration Utility was started.
Action:Check to see that all database files are online before shutting down your Version 6 database. Check that the file exists and has access permissions that allow Oracle to open and read the file. If possible, check that the file is not corrupt and the disks on which the file resides are not corrupt. Fix any problems and restart the Migration Utility.
Unable to write file name

Cause:An internal error occurred.
Action:Check that the correct access permissions exist for Oracle to write to the file. Check that the disks to which the file is being written are not corrupt. Fix any such corruption before restarting the migration.
V7 catalog space requirement: num

Cause:This is an informational message that informs you how much additional space you need in your SYSTEM tablespace to run the Migration Utility successfully.
Action:Be certain that you have the specified amount of additional space before running the Migration Utility.




Go to previous file in sequence Go to next file in sequence
Prev Next
Oracle
Copyright © 1996 Oracle Corporation.
All Rights Reserved.
Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents
Go to Index
Index