Release 8.1.5
A67774-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Migration Release 8.1.5 A67774-01 |
|
This appendix describes corrective action for common problems that you may encounter during the migration process when you are using either the Migration utility or the Oracle Data Migration Assistant. If you are using the Migration utility, the migration process is described in Chapter 3, "Migrating Using the Migration Utility"; if you are using the Oracle Data Migration Assistant, the migration process is described in Chapter 4, "Migrating Using the Oracle Data Migration Assistant".
This appendix covers the following topics:
When you run either the Migration utility or the Oracle Data Migration Assistant, you may encounter the following types of problems:
General migration problems may occur when you run either the Migration utility or the Oracle Data Migration Assistant, but they are caused by your database system's configuration. While either the utility or the assistant is performing the necessary actions to migrate the database, an error is generated by your Oracle software. Typically, when such an error occurs, the utility or assistant stops and displays one or more error messages.
If you encounter one of the following problems when you run either the utility or the assistant, perform the suggested actions, and then re-run the utility or assistant.
This problem may return an error message similar to the following:
ORA-01652: unable to extend temp segment by 473 in tablespace SYSTEM
You need to add a new datafile to the SYSTEM tablespace and allocate enough space to the new datafile to successfully complete the migration.
It also is possible to run out of space in the temporary tablespace during migration. If you do, add a new datafile to the temporary tablespace and allocate enough space to the new datafile to successfully complete the migration.
|
See Also:
If you are using the Migration utility, see "Space Requirements" and Step 8. If you are using the Oracle Data Migration Assistant, see "Space Requirements" and Step 9. These sections provide more information about the space requirements for the SYSTEM tablespace, and information about adding a new datafile to increase its available space. |
This problem may return error messages similar to the following:
ORA-00604: error occurred at recursive SQL level num ORA-01552: cannot use system rollback segment for non-system tablespace 'name' ORA-02002: error while writing to audit trail
You will encounter these errors only under the following conditions:
To correct this problem, complete the following steps:
initsid.ora file in the following way:
AUDIT_TRAIL = NONE
This problem may return an error message similar to the following:
ORA-01562: failed to extend rollback segment (id = 0)
Both the Migration utility and the Oracle Data Migration Assistant take all non-SYSTEM rollback segments offline and then freeze the size of the SYSTEM rollback segment by altering MAXEXTENTS to the number of extents currently allocated. This action prevents any space operations, such as an extent allocation, while the utility or assistant handles the space management tables.
If the SYSTEM rollback segment has an OPTIMAL setting, extents are de-allocated dynamically when their data is no longer needed for active transactions. The dynamic de-allocation may cause the number of currently allocated extents to be small when the SYSTEM rollback segment is frozen. Therefore, the SYSTEM rollback segment may not be large enough to handle the transactions involving the space management tables during migration.
This problem may return an error message similar to the following:
ORA-01632: max # extents (%s) reached in index %s.%s
The Migration utility is using the default value of 15 for the MULTIPLIER option, and this value is too low. To correct the problem, increase the value of the MULTIPLIER option.
If you are using the Migration utility, when you run it from the command line, enter the following to raise the MULTIPLIER option to 30:
mig MULTIPLIER=30
If, however, you are running the Migration utility in the background by using the Oracle Data Migration Assistant, restore your Oracle7 backup and then re-run the assistant. Choose the Custom migration option in the assistant. When you are prompted for the MULTIPLIER value, enter a value greater than the default of 15.
|
See Also:
"Review Migration Utility Command-Line Options" for more information about the MULTIPLIER option. |
The Migration utility may return error messages and informational messages during migration. This section 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.
If you are using the Oracle Data Migration Assistant, the Migration utility messages are recorded in a log file. See the online help for the Oracle Data Migration Assistant for information about accessing its log files. Also, if you are using the Oracle Data Migration Assistant and the recommended action for a message includes rerunning the Migration utility, you should rerun the assistant.
The following messages are listed in alphabetical order:
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 Oracle7 control file.
Action: Check the Oracle7 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.
client nls_characterset does not match server nls_characterset - check that NLS_LANG environment variable is set
Cause: The NLS_LANG character set does not match the character set in PROPS$.
Action: Check the database character set in PROPS$ and set the NLS_LANG environment variable to match it.
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 Oracle8i 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 Oracle8i 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, of migrate.bsq, and of the target Oracle7 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 Oracle7.1 or later
Cause: Current database is an earlier version than Oracle7, release 7.1.
Action: Migrate or upgrade current database to a release supported by the Migration utility on your operating system. Then, rerun the Migration utility. See your operating-system specific Oracle documentation for information about the releases supported by the Migration utility on your operating system.
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 Oracle7 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 Oracle8i 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 Oracle8i 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 Oracle8i 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 thanOracle8i's minimum block size 2k
Cause: The existing database blocksize is less than 2KB.
Action: Make sure the block size of the Oracle7 database is at least 2KB. You may consider rebuilding the Oracle7 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: If you are using the Migration utility, go to Step 4 and make sure all offline tablespaces have been taken offline cleanly. If you are using the Oracle Data Migration Assistant, go to Step 4 and make sure all offline tablespaces have been taken offline cleanly. Then, rerun the Oracle8i Migration utility.
mounting database ...
Cause: This is an informational message. The Migration utility is mounting the Oracle7 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 Oracle8i 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 Oracle7 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 Oracle8i 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 Oracle7 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 Oracle7 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 an Oracle7 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 computer 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 Oracle8i Migration utility.
Action: Check that the file exists and that its access permissions allow Oracle to open and read it. If possible, check that the file, and 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 it. If possible, check that the file, and 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.
You may encounter one of the problems described in this section when you issue the ALTER DATABASE CONVERT command during the migration process after you run the Migration utility. Typically, the conversion will stop and one or more error messages will be displayed. If you encounter one of the following problems when you run the ALTER DATABASE CONVERT command, perform the suggested actions to correct the problem.
This problem may return the following error messages:
ORA-00200: cannot create control file name ORA-00202: controlfile: name ORA-27038: skgfrcre: file exists
The old Oracle7 control files must be renamed or removed before you issue the ALTER DATABASE CONVERT command.
This problem may return the following error messages:
ORA-00227: corrupt block detected in controlfile: (block num, # blocks num) ORA-00202: control file: '%s'
The old Oracle7 control files must be renamed or removed before you issue the ALTER DATABASE CONVERT command. Also, the database must be started in NOMOUNT mode when you issue the ALTER DATABASE CONVERT command, but the database was started in a different mode.
This problem may return the following error messages:
ORA-00404: convert file not found: name ORA-27037: unable to obtain file status
The convert file (convsid.dbf on UNIX and convert.ora on Windows NT) generated by the Migration utility was not found in the expected location. On UNIX, the expected location is the $ORACLE_HOME/dbs directory in the Oracle8i environment; on Windows NT, the expected location is the $ORACLE_HOME\database directory in the Oracle8i environment. The convert file must be moved to this location before you issue the ALTER DATABASE CONVERT command.
This problem may return the following error message:
ORA-00600: internal error code, arguments: [kzsrsdn: 1], [32]
You will encounter this error under the following conditions:
$ORACLE_HOME/dbs in the Oracle8i environment; on Windows NT, the correct directory is $ORACLE_HOME\database in the Oracle8i environment
initsid.ora file.
To continue with the migration, complete the following steps:
initsid.ora file:
REMOTE_LOGIN_PASSWORDFILE = NONE
SVRMGR> STARTUP MOUNT
You may need to use the PFILE option to specify the location of your initsid.ora file.
SVRMGR> ALTER DATABASE OPEN RESETLOGS;
You cannot use the existing password file because it is no longer valid. If you want to use a password file with Oracle8i, recreate the password file and repopulate it with users. Remember to set REMOTE_LOGIN_PASSWORDFILE correctly.
This problem may return the following error message:
ORA-01103: database name name in control file is not name
There is a mismatch in the database name. This mismatch is in one or more of the following places:
initsid.ora file does not match the database name in the convsid.dbf filename.
convsid.dbf filename.
To correct the problem, make sure the correct database name is specified in each of the following places:
initsid.ora file
sid part of the convsid.dbf filename
For example, if your ORACLE_SID environment variable and the DB_NAME parameter in the initsid.ora file are both set to DB1, the convsid.dbf filename should be the following:
convDB1.dbf
This problem may return the following error messages:
ORA-01122: datafile name - failed verification check ORA-01110: data file name: str ORA-01202: wrong incarnation of this file - wrong creation time
These errors usually indicate that the ALTER DATABASE CONVERT command was issued previously but failed. If you encounter these errors, you can attempt to move on to the next step in the migration process by issuing the ALTER DATABASE OPEN RESETLOGS command. However, if you encounter problems, restore the backup you created before you started the migration process, and use it to start the migration again from the beginning. Start at the beginning of Chapter 3, but make sure you performed the pre-migration actions described in Chapter 2.
This problem may return the following error messages:
ORA-01122: datafile name - failed verification check ORA-01110: data file name: str ORA-01211: Oracle7 data file is not from migration to Oracle8i
The Migration utility must be the last utility to access the database in the Oracle7 environment. The datafile specified in the error messages is either a backup taken before you ran the Migration utility, or the database was opened by Oracle7 after you ran the Migration utility. Only the datafiles that were current when the Migration utility ran can be accessed by Oracle8i.
To ensure datafile version integrity, the system change numbers (SCNs) in the data dictionary, the convert file, and the file headers must all be consistent when the database is converted to Oracle8i. If the database is opened under Oracle7 after the Migration utility has run, the SCN checking fails when you issue the ALTER DATABASE CONVERT command.
To correct the problem, complete the following steps:
If you do not have the Oracle7 control files saved, restore the backup you made prior to starting the migration process.
