Oracle8 Migration Release 8.0 A58243-01 |
Library | Product | Contents | Index

# A
Migration Utility Messages

The Migration Utility may return error messages and informational messages during migration. This appendix describes errors you may encounter when using the Migration Utility. For each error, a description of its probable cause and instructions for corrective action are provided. Informational messages also are listed, but they require no corrective action.

##### cannot reduce file number bits in DBA during migration

Cause: The Migration Utility attempted to reduce the number of file-number bits used in a datablock address.

Action: Contact your Oracle Customer Support representative.

##### cannot create conversion file, records exceed number bytes

Cause: An internal error occurred. A valid convert file could not be created from the version 7 control file.

Action: Check the version 7 control file for corruption, fix any problems, and rerun the Migration Utility.

##### CHECK_ONLY - estimate V8 catalog space requirement ONLY (default=FALSE)

Cause: This is an informational message about the CHECK_ONLY command line argument.

Action: No user action is required.

##### CHECK_ONLY and NO_SPACE_CHECK are mutually exclusive options

Cause: These 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 (string)

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> (string)

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 informational message displays the command-line arguments.

Action: No user action is required.

##### command name not found (string)

Cause: An internal error has occurred; the MIGRATE.BSQ script may be corrupted.

Action: Check that the version of the Migration Utility, of MIGRATE.BSQ, and of the target version 8 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### command not of form CMD(ARG1, ARG2, ...)

Cause: An internal error has occurred; the MIGRATE.BSQ script may be corrupted.

Action: Check that the version of the Migration Utility, of MIGRATE.BSQ, and of the target version 8 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### copy long command must be of form COPYLONG(U1,T1,C1,U2,T2,C2,K1<,K2>)

Cause: An internal error has occurred; the MIGRATE.BSQ script may be corrupted.

Action: Check that the version of the Migration Utility, MIGRATE.BSQ, and of the target version 7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### could not find single contiguous extent of number bytes 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 rerun the Migration Utility.

##### could not find single contiguous extent of number bytes for c_ts#

Cause: You do not have enough contiguous space in your SYSTEM tablespace.

Action: Add free space to your SYSTEM tablespace, and rerun the Migration Utility.

##### could not find single contiguous extent of number bytes for i_file#_block#

Cause: You do not have enough contiguous space in your SYSTEM tablespace.

Action: Add free space to your SYSTEM tablespace, and rerun the Migration Utility.

##### could not find single contiguous extent of number bytes for i_ts#

Cause: You do not have enough contiguous space in your SYSTEM tablespace.

Action: Add free space to your SYSTEM tablespace, and rerun the Migration Utility.

##### could not translate logical name name

Cause: An internal error has occurred.

Action: Check that the logical name is defined correctly, and rerun the Migration Utility.

##### current version: str -- Database must be version 7.1 or later

Cause: Current database is an earlier version than version 7, release 7.1.

Action: Migrate or upgrade current database to a release supported by the Migration Utility on your platform. Then, rerun the Migration Utility. See your platform-specific Oracle documentation for information about the releases supported by the Migration Utility on your platform.

##### data type must be long for column name

Cause: An internal error has occurred; the MIGRATE.BSQ script may be corrupted.

Action: Check that the version of the Migration Utility, of MIGRATE.BSQ, and of the target version 7 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### datafiles is found in inconsistent states (internal error) -- filename

Cause: An internal error occurred; a datafile was found in inconsistent state.

Action: Contact your Oracle Customer Support representative.

##### datafile is offline while tablespace is online - apply media recovery and bring datafile online before migration -- datafile

Cause: The datafile in a tablespace is offline while the tablespace is online. Migration cannot proceed until the datafile and tablespace are both either online or offline normal.

Action: Apply media recovery and bring the datafile online before rerunning the migration.

##### DBNAME - current database name (db_name in init.ora)

Cause: This is an informational message about the DBNAME command-line argument.

Action: No user action is required.

##### dictionary constant not found - name

Cause: An internal error has occurred; the MIGRATE.BSQ script may be corrupted.

Action: Check that the version of the Migration Utility, of MIGRATE.BSQ, and of the target version 8 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### entries found in system.def$_call, def$_calldest or def$_error - push all deferred transactions before migration

Cause: Entries exist in system.def$_call, def$_calldest, or def$_error.

Action: If entries are in system.def$_call, push all deferred transactions until system.def$_call is empty. If entries are in system.def$_error, resolve and re-execute any errors in the local queue until it is empty. Rerun the Migration Utility.

##### error calling slgtd

Cause: Error in getting current time from slgtd, an internal error. The Migration Utility may be corrupted.

Action: Check that the version of the Migration Utility, of MIGRATE.BSQ, and of the target version 8 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### error closing file name

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 rerun the Migration Utility.

##### estimated space requirement for object is number blocks

Cause: In this informational message, the Migration Utility displays the space required for the object.

Action: No user action is required.

##### file filename is too large for DBA conversion

Cause: An internal error has occurred; filename is too large for DBA conversion.

Action: Contact your Oracle Customer Support representative.

##### file header does not fit in number bytes

Cause: An internal error has occurred.

Action: Check the control file for corruption, fix any problems, and rerun the Migration Utility.

##### fixed portion of control file does not fit in number bytes

Cause: An internal error has occurred.

Action: Check the control file for corruption, fix any problems, and rerun the Migration Utility.

##### found NULL SQL statement

Cause: An internal error has occurred; the MIGRATE.BSQ script may be corrupted.

Action: Check that the version of the Migration Utility, of MIGRATE.BSQ, and of the target version 8 software are compatible, and that no corruption exists in MIGRATE.BSQ. Fix any problems, and rerun the Migration Utility.

##### free space found in system tablespace is number blocks

Cause: This informational message shows the amount of free space in the
SYSTEM tablespace.

Action: No user action is needed.

##### free space found: number

Cause: This informational message shows the amount of free space in the
SYSTEM tablespace.

Action: No user action is needed.

##### 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 rerun the Migration Utility.

##### insufficient space for new dictionaries, number bytes needed, number 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.

##### invalid NLS_NCHAR value specified

Cause: The NLS_NCHAR value specified in the command line is invalid.

Action: Correct the NLS_NCHAR value specified in the command line, and rerun the Migration Utility.

##### migration can't proceed - database blocksize size is less than Oracle8's minimum block size 2k

Cause: The existing database blocksize is less than 2KB.

Action: Make sure the block size of the version 7 database is at least 2KB. You may consider rebuilding the version 7 database. Then, rerun the Migration
Utility.

##### migration can't proceed with datafile online while tablespace offline -- datafile

Cause: The datafile in a tablespace is online while the tablespace is offline. Migration cannot proceed until the datafile and tablespace are both either online or offline normal.

Action: Make sure the online status of the datafile is the same as the online status of the tablespace, and rerun the Migration Utility.

##### migration cannot proceed with active transaction or offline tablespaces with outstanding undo

Cause: One or more tablespaces were offline with outstanding save undo when the Migration Utility attempted to migrate the database.

Action: Go to Step 7 on 3-7 in "Prepare the Version 7 Source Database for Migration" and make sure all offline tablespaces have been taken offline cleanly. Then, rerun the version 8 Migration Utility.

##### mounting database ...

Cause: This is an informational message. The Migration Utility is mounting the version 7 database.

Action: No user action is required.

##### MULTIPLIER - seg$/uet$ cluster index size increase factor (default=15)

Cause: This is an informational message that the Migration Utility displays about the MULTIPLIER command-line setting.

Action: No user action is required.

##### MULTIPLIER value must be at least 2

Cause: The MULTIPLIER value, which specifies the initial size of the version 8 i_file#_block# in the command line, is less than 2.

Action: Change the MULTIPLIER value to be equal to or greater than 2, and rerun the Migration Utility.

##### NEW_DBNAME name too long - maximum length is 8 characters

Cause: The new database name specified is more than 8 characters long.

Action: Change the specified name for the new database to 8 or fewer characters, and rerun the Migration Utility.

##### NEW_DBNAME - new name for the database (max. 8 characters)

Cause: This informational message displays information about the NEW_DBNAME command-line argument.

Action: No user action is required.

##### NLS_NCHAR - specify the nchar characterset value

Cause: This informational message displays information about the NLS_NCHAR command-line argument.

Action: No user action is required.

##### NO_SPACE_CHECK - do not execute the space check (default=FALSE)

Cause: This is an informational message about the NO_SPACE_CHECK command-line argument.

Action: No user action is required, but make sure there is adequate space before you run the Migration Utility with this option.

##### tablespace/datafile number being processed is incorrect during creating
convert file

Cause: An internal error occurred while creating the convert file.

Action: Contact your Oracle Customer Support representative.

##### opening database ...

Cause: This is an informational message. The Migration Utility is opening the version 7 database.

Action: No user action is required.

##### ORA_NLS33 environment variable is not set or incorrectly set

Cause: The ORA_NLS33 environment variable does not point to the NLS datafiles.

Action: Set the ORA_NLS33 environment variable to point to the correct files, and rerun the Migration Utility.

##### ORA-number:

Cause: The Migration Utility has received an ORA error and cannot retrieve the message text for the error.

Action: Take appropriate action based on the Oracle error number (see Oracle8 Error Messages).

##### 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 rerun the Migration Utility.

##### parameter file exceeds number bytes

Cause: The parameter file for your version 7 database exceeds the maximum size.

Action: If possible, reduce the size of your parameter file by removing obsolete parameters. Otherwise, contact your Oracle Customer Support representative.

##### PFILE - use alternate 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 reading file name.

Action: Make sure the file and disk are not corrupted. Fix any corruption before you rerun the Migration Utility.

##### short read, number bytes requested, number bytes read

Cause: There is a problem reading the control file.

Action: Check the control file for corruption, fix any problems, and rerun the Migration Utility.

##### shut down database (abort) ...

Cause: An internal error occurred.

Action: Additional error messages should inform you of the cause of the shutdown. Follow the actions suggested for these additional messages.

##### shutting down database ...

Cause: This is an informational message. The Migration Utility is shutting down the version 7 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 7 instance.

Action: No user action is required.

##### string argument too long, maximum length number

Cause: A string in the command line argument passed to the Migration Utility exceeds the maximum size.

Action: Shorten the string in the command line argument, and rerun the Migration Utility.

##### tablespace of datafile not taken offline normal. Bring tablespace online, offline normal or drop before migration -- tablespace

Cause: Tablespace was taken offline using IMMEDIATE or TEMPORARY.

Action: Bring tablespace online, and then take it offline using NORMAL or drop it. Then, rerun the Migration Utility.

##### too many args in command (number 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 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 Migration Utility, and rerun the Migration Utility.

##### unable to open file name

Cause: An internal error has occurred, or a file was not in the expected location, when you started the version 8 Migration Utility.

Action: Check that the file exists and that its access permissions allow Oracle to open and read the it. If possible, check that the file, and/or the disks on which the file resides, are not corrupt. Fix any problems, and rerun the Migration Utility.

##### unable to read file name

Cause: An internal error occurred or a file was not in the expected location when you started the Migration Utility.

Action: Check that the file exists and that its access permissions allow Oracle to open and read the it. If possible, check that the file, and/or the disks on which the file resides, are not corrupt. Fix any problems, and rerun the Migration Utility.

##### unable to write file name

Cause: An internal error occurred.

Action: Check the access permissions to make sure that Oracle can write to the file. Check that the disks to which the file is being written are not corrupt. Fix any corruption; then, rerun the Migration Utility.

##### V8 catalog space requirement: number

Cause: This is an informational message that shows the amount of additional space required in your SYSTEM tablespace to run the Migration Utility successfully.

Action: Make sure you have the specified amount of additional space before running the Migration Utility.

Prev | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index