We can see Redo generation by using below query
select b.inst_id,
lpad((b.SID || ',' || lpad(b.serial#,5)),11) sid_serial,
b.username,
machine,
b.osuser,
b.status,
a.redo_mb
from (select n.inst_id, sid,
round(value/1024/1024) redo_mb
from gv$statname n, gv$sesstat s
where n.inst_id=s.inst_id
and n.name = 'redo size'
and s.statistic# = n.statistic#
order by value desc
) a,
gv$session b
where b.inst_id=a.inst_id
and a.sid = b.sid
and rownum <= 30
;
Cheers
Friday, December 16, 2011
Thursday, December 1, 2011
Export and Import Error Messages
EXPORT ERROR MESSAGES
-------------------------------------------
EXP-00000 Export terminated unsuccessfully
Cause: Export encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.
EXP-00001 data field truncation - column length=number, buffer size=number actual size=number
Cause: Export could not fit a column in the data buffer.
Action: Record the given size parameters and the accompanying messages and report this as an Export internal error to Oracle Support Services. (Part of the table has been exported. Export will continue with the next table.)
EXP-00002 error in writing to export file
Cause: Export could not write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
EXP-00003 no storage definition found for segment(number, number)
Cause: Export could not find the storage definitions for a cluster, index, or table.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00004 invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
EXP-00005 all allowable logon attempts failed
Cause: Attempts were repeatedly made to log on with an invalid username or password.
Action: Shut down the utility, then restart and retry with a valid username and password.
EXP-00006 internal inconsistency error
Cause: Export's data structure was corrupted.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00007 dictionary shows no columns for string.string
Cause: Export failed to gather column information from the data dictionary. The table may have been dropped.
Action: Retry the export and, if this error recurs, report it as an Export internal error to Oracle Support Services.
EXP-00008 ORACLE error number encountered
Cause: Export encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00009 no privilege to export string's table string
Cause: An attempt was made to export another user's table. Only a database administrator can export another user's tables.
Action: Ask your database administrator to do the export.
EXP-00010 string is not a valid username
Cause: An invalid username was specified.
Action: Shut down the utility, then restart and retry with a valid username.
EXP-00011 string.string does not exist
Cause: Export could not find the specified table.
Action: Retry with the correct table name.
EXP-00012 string is not a valid export mode
Cause: An invalid export mode was specified.
Action: Retry with a valid export mode.
EXP-00013 respond with either 'Y', 'N', RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
EXP-00014 error on row number of table string
Cause: Export encountered an Oracle error while fetching rows.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00015 error on row number of table string, column string, datatype number
Cause: Export encountered an error while fetching or writing the column. An accompanying message gives more information.
Action: Correct the error and try again.
EXP-00016 ORACLE error encountered while reading default auditing options
Cause: Export encountered an Oracle error while reading the default auditing options (those for updates, deletes, and so on).
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00017 feature 'string' is needed, but not present in database"
Cause: The command entered requires the specified feature. Either that feature is not installed, or the row describing the feature is missing from table V$OPTION.
Action: Re-install Oracle with the feature specified in the message.
EXP-00018 datatype (number) for column string, table string.string is not supported
Cause: Export does not support the referenced datatype.
Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or RAW).
EXP-00019 failed to process parameters, type 'EXP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
EXP-00020 failed to allocate memory of size number
Cause: Export failed to allocate the necessary memory.
Action: Decrease the export buffer size so that less memory is required, or increase the runtime memory size for Export.
EXP-00021 can only perform incremental export in Full Database mode
Cause: USER or TABLE mode was specified when doing an incremental export.
Action: Specify FULL database mode (FULL=Y) and retry.
EXP-00022 must be SYS or SYSTEM to do incremental export
Cause: The privileges needed to do an incremental export do not exist. Only a data base administrator can do incremental exports.
Action: Ask the database administrator to do the incremental export.
EXP-00023 must be a DBA to do Full Database or Tablespace export
Cause: The privileges needed to do a FULL database export do not exist. Only a database administrator can do a FULL database export.
Action: Ask the database administrator to do the FULL database export.
EXP-00024 Export views not installed, please notify your DBA
Cause: The necessary Export views were not installed.
Action: Ask the database administrator to install the required Export views.
EXP-00025 dictionary shows no column for constraint string.number
Cause: Export failed to gather column information about the referenced constraint from the data dictionary. The constraint may have been altered.
Action: Retry the export and, if this error recurs, report it as an Export internal error to Oracle Support Services.
EXP-00026 conflicting modes specified
Cause: Conflicting export modes were specified.
Action: Specify only one parameter and retry.
EXP-00027 failed to calculate ORACLE block size
Cause: Export failed to calculate the Oracle block size.
Action: Report this as an Export internal error to Oracle Support Services.
EXP-00028 failed to open string for write
Cause: Export failed to open the export file for writing. This message is usually followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
EXP-00029 Incremental export mode and consistent mode are not compatible
Cause: Both consistent and incremental exports were specified.
Action: No action is required. Consistent mode is turned off.
EXP-00030 Unexpected End-Of-File encountered while reading input
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
EXP-00031 Arraysize not in valid range. Using arraysize=number
Cause: The array size value specified is not in the valid range.
Action: No action required.
EXP-00032 Non-DBAs may not export other users
Cause: Only database administrators can export to other users. A non-database administrator attempted to specify OWNER=USER where exporter is not the user.
Action: Request that this operation be performed by the database administrator.
EXP-00033 Could not find environment character set
Cause: The environment character set is missing or incorrectly specified.
Action: Ensure that the environment character set is correctly specified and is present.
EXP-00034 error on rowid: file# number block# number slot# number
Cause: Identifies the ROWID on which an error occurred.
Action: This is an information message. No action is required.
EXP-00035 QUERY parameter valid only for table mode exports
Cause: You specified the QUERY parameter in an export command, but you are not performing a table mode export. The QUERY parameter cannot be used for a user mode export, a full export, nor a point in time recovery export.
Action: If you want to select a subset of rows for a table, you must export the table independently with a table mode export. Issue a table mode export command that specifies the table name and the query you want to execute during export.
EXP-00036 Object number non-existent in dictionary
Cause: The specified object could not be found in the dictionary. The object might have been dropped during the export
Action: The object no longer exists; no action is needed.
EXP-00037 Export views not compatible with database version
Cause: The Export utility is at a higher version than the database version and is thereby incompatible.
Action: Use the same version of Export utility as the database.
EXP-00038 Bad Hash cluster id in clu$
Cause: The function ID in CLU$ is not a legal number. CLU$ has become corrupted.
Action: Contact Oracle Support Services.
EXP-00039 export file string must be on a disk
Cause: On some platforms, export can read files from tape. This message is displayed if the first file in an export file set was on disk and you specified a tape device for a second or subsequent file.
Action: Verify that you have specified the correct file name for the export file. Remember that all export files can be either on disk or all files can be on tape, but not mixed both tape and disk.
EXP-00040 Dump file and log file must be different
Cause: The dump file and log file cannot be the same file.
Action: Specify different file names for the dump file and the log file, then retry the operation.
EXP-00041 INCTYPE parameter is obsolete
Cause: Export encountered the INCTYPE parameter when parsing Export options. Incremental Exports are no longer supported.
Action: Consult the Oracle9i User-Managed Backup and Recovery Guide. Export will attempt to continue.
EXP-00042 Missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in props$
Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not entered in the props$ table. This is an internal error.
Action: Contact Oracle Support Services.
EXP-00043 Invalid data dictionary information in the row where column "string" is "string" in table string
Cause: The export utility retrieved invalid data from the data dictionary.
Action: Contact Oracle Support Services.
EXP-00044 must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.
EXP-00045 Cannot export SYSTEM Tablespace for Point-in-time Recovery or Transportable Tablespace
Cause: SYSTEM tablespace cannot be part of recovery set or transportable tablespace set.
Action: Contact Oracle Support Services.
EXP-00046 Tablespace named string does not exist
Cause: The specified tablespace does not exist in dictionary.
Action: Contact Oracle Support Services.
EXP-00047 Missing tablespace name(s)
Cause: Tablespace name(s) were not supplied.
Action: Provide tablespace name(s).
EXP-00049 string option is not compatible with Point-in-time Recovery or Transportable Tablespace export
Cause: An option was specified that is incompatible with Point-in-time Recovery or Transportable Tablespace Export.
Action: Retry the export without the displayed option.
EXP-00050 Cannot perform Partition Export "string" on non-partitioned table "string"
Cause: The table specified in this Partition Export is not a partitioned table.
Action: Use Table mode, or specify a non-partitioned table.
EXP-00051 "string" - given partition or subpartition name is not part of "string" table
Cause: The specified partition or subpartition name is not in the specified table.
Action: Check if the correct table, partition or subpartition name was specified.
EXP-00052 error on row number of partition string
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00053 unable to execute QUERY on table string because the table has inner nested tables
Cause: You specified the QUERY parameter on a table that has one or more inner nested tables. The QUERY parameter cannot be specified on tables that have inner nested tables.
Action: Export the entire table by omitting the QUERY parameter.
EXP-00054 error on row number of subpartition string
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00055 string.string is marked not exportable
Cause: An object was marked as non-exportable in the NOEXP$ table.
Action: Consult your database administrator.
EXP-00057 Failure to initialize parameter manager
Cause: The parameter manager failed in intialization.
Action: Record the messages that follow and report this to Oracle Support Services as an Export internal bug.
EXP-00058 Password Verify Function for string profile does not exist
Cause: Cannot find the function for the profile.
Action: Check if the profile was created properly.
EXP-00059 error converting an object type's identifier to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Support Services.
EXP-00060 an object type had multiple TYPE BODYs
Cause: More than one TYPE BODY was found for an object type.
Action: Try dropping the TYPE BODY, if that is not successful, contact Oracle Support Services.
EXP-00061 unable to find the outer table name of a nested table
Cause: While exporting a bitmap index or postable action on an inner nested table, the name of the outer table could not be located, using the NTAB$ table.
Action: Verify the table is properly defined.
EXP-00062 invalid source statements for an object type
Cause: TYPE was not found in the statements in SOURCE$ for an Object Type.
Action: Contact Oracle Support Services.
EXP-00063 error in changing language handle
Cause: Unable to change language handle.
Action: Contact Oracle Support Services.
EXP-00064 string is an inner nested table and connot be exported.
Cause: An attempt was made to export an inner nested table without its parent table.
Action: Export the parent of the inner nested table.
EXP-00065 Error writing lob to the dump file.
Cause: The current LOB could not be written to the dump file.
Action: Identify the cause of the write failure and fix it.
EXP-00066 Object table string is missing its object identifier index
Cause: All object tables must have an object identifier index, but the specified table was missing an index on its object identifier column.
Action: Re-create the type table and retry the operation.
EXP-00068 tablespace string is offline
Cause: Export failed to export tablespace (tablespace being offline).
Action: Make tablespace online and re-export.
EXP-00070 attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Support Services.
EXP-00071 QUERY parameter not compatible with Direct Path export
Cause: You specified a value for the QUERY parameter for a direct path export. The QUERY parameter cannot be used with a direct path export.
Action: Re-issue the export command with DIRECT=N or omit the DIRECT parameter from the command line.
EXP-00072 error closing export file string
Cause: An error occurred while trying to close the export file.
Action: Contact Oracle Support Services.
EXP-00073 dump file size too small
Cause: You specified either the FILESIZE parameter or the VOLSIZE parameter (if your platform supports it), and the value of the parameter is too small to hold the header information for the export file, plus any data.
Action: Increase the value of the FILESIZE or VOLSIZE parameter.
EXP-00074 rounding VOLSIZE down, new value is string
Cause: The VOLSIZE parameter must be a multiple of the RECORDLENGTH, but the value you specified for VOLSIZE does not meet this requirement. The value of VOLSIZE has been rounded down to be a multiple of the RECORDLENGTH used for the dump file.
Action: No action is required. You can adjust the VOLSIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the VOLSIZE value reported by this message.
EXP-00075 rounding FILESIZE down, new value is string
Cause: The FILESIZE parameter must be a multiple of the RECORDLENGTH, but the value you specified for FILESIZE does not meet this requirement. The value of FILESIZE has been rounded down to be a multiple of the RECORDLENGTH used for the dump file.
Action: No action is required. You can adjust the FILESIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the FILESIZE value reported by this message.
EXP-00076 multiple devices specified for tape output
Cause: You specified multiple file names when doing an export to a tape device. EXPORT uses the same device for writing all files, of the number of tape volumes required. For this reason, export will accept only one value for the FILE parameter when writing to tape.
Action: Re-enter the EXPORT command, but specify only one tape device in the FILE parameter.
EXP-00077 multiple output files specified for unbounded export file
Cause: You specified multiple file names when doing an export and you also specified a value of 0 for the FILESIZE parameter. Note that 0 is the value used if FILESIZE is not specified on the command line. Since a value of 0 for FILESIZE means that only one file will be written and there is no size limit for that file, the other files you specified in the FILE parameter can never be used.
Action: If you intended to write multiple files, respecify the command but use the FILESIZE to specify the maximum number of bytes that EXPORT should write to each file. If you intended to write only one file with no limits on it's size, reissue the EXPORT command but specify only one file name for the FILE parameter.
EXP-00078 Error exporting metadata for index string. Index creation will be skipped
Cause: Domain indexes export private metadata via anonymous PL/SQL blocks prior to the CREATE INDEX statement. Export does this by calling the ODCIIndexGetMetadata method on the implementation type associated with the index. A problem occurred inside this routine. Because the metadata is considered an integral part of the index, the CREATE INDEX statement was not written to the dump file.
Action: Contact the developer of the index's implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Support Services.
EXP-00079 Data in table "string" is protected. Conventional path may only be exporting partial table.
Cause: User without the execute privilege on DBMS_RLS, the access control package, tries to export a table that has access control. Since table owner is also subjected to access control, the owner may not be able to export all rows in the table, but only the ones he can see. Also, to preserve integrity of the table, user exporting the table should have enough privilege to re-create the table with the security policies at import time. Therefore, it is strongly recommended the database administrator should be handling exporting of this table. Granting the table owner execute privilege would also satisfy this security check, though it might have other security implications. If the table does not have objects, can use direct mode.
Action: Ask the database administrator to export/import this table/view.
EXP-00080 Data in table "string" is protected. Using conventional mode.
Cause: User without the execute privilege on DBMS_RLS, the access control package, tries to direct export a table that has access control enabled. Using conventional export mode instead. Note that because of access control, only a partial table may be exported.
Action: Ask the database administrator to export/import this table/view.
EXP-00081 Exporting access control for table/view "string" as non-DBA.
Cause: A non-DBA user tries to export table/view and the associated fine grain access control policies. The user may not have enough privilege to re-create the access control policies when importing the table/view. And such an event may cause inconsistency in the security model of the table/view.
Action: Ask the database administrator to export/import this table/view.
EXP-00082 Invalid function name passed to procedural object support: string
Cause: Internal inconsistency error: The listed function is not a method on export's procedural object interface specification.
Action: Contact Oracle Support Services.
EXP-00083 The previous problem occurred when calling string.string.string
Cause: The listed package provides export/import support for procedural actions. The previously listed error occurred while calling the specified function.
Action: Contact Oracle Support Services. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Oracle Support Services determine the correct owner of the problem.
EXP-00084 Unexpected DbmsJava error number at step number
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00085 The previous problem occurred when calling string.string.string for object number
Cause: The listed package provides export/import support for procedural objects, i.e., those whose DDL is supplied by stored procedures. The previously listed error occurred while calling the specified function.
Action: Contact Oracle Support Services. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Oracle Support Services determine the correct owner of the problem.
EXP-00086 Primary key REFs in table "string"may not be valid on import
Cause: The specified table contains primary key REFs which may not be valid in the import database.
Action: Do not use Export/Import to move Primary key REFs between databases having differing character sets.
EXP-00087 Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Support Services.
EXP-00089 invalid FILE_FORMAT specification
Cause: The FILE_FORMAT specification did not contain an instance of "string". This wildcard string must be present.
Action: Correct the error and re-enter the EXPORT command.
EXP-00090 cannot pin type "string"."string"
Cause: Export was unable to pin the specified type in the object cache. This is typically caused because a type could not be made valid (for example because of authorization violations in accessing subtypes).
Action: Fix the problem with the offending type until the type can be successfully compiled.
EXP-00091 Exporting questionable statistics
Cause: Export was able to export statistics, but the statistics may not be useable. The statistics are questionable because one or more of the following happened during export: a row error occurred, client character set or NCHARSET does not match with the server, a query clause was specified on export, only certain partitions or subpartitions were exported, or a fatal error occurred while processing a table.
Action: To export non-questionable statistics, change the client character set or NCHARSET to match the server, export with no query clause, or export complete tables. If desired, import parameters can be supplied so that only non-questionable statistics will be imported, and all questionable statistics will be recalculated.
EXP-00092 unable to set NLS_NUMERIC_CHARACTERS to required defaults
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00093 could not convert to server character set's handle
Cause: Internal error.
Action: Contact Oracle Support Services.
EXP-00094 could not convert to server national character set's handle
Cause: Internal error.
Action: Contact Oracle Support Services.
EXP-00095 Flashback_time and Flashback_scn are not compatible
Cause: Both flashback_time and flashback_scn parameters were specified.
Action: Reissue the command with only one flashback parameter.
EXP-00096 The template name specified can not be found.
Cause: The specified template name does not exist.
Action: Verify the template name by looking up view %_ias_template.
EXP-00097 Object type "string"."string" is not in a valid state, type will not be exported.
Cause: The object type's status is invalid which may be caused by a dependant type's modification (or removal) without cascading the change.
Action: The type must be recompiled using ALTER TYPE COMPILE.
EXP-00098 Data in table has not been upgraded, table will not be exported.
Cause: Export is attempting to process a table containing references to a type which has evolved. In order for Export to process the table successfully, all data within each table must be upgraded to the latest revision of each referenced type.
Action: The table must be updated using ALTER TABLE UPGRADE DATA.
EXP-00099 Table "string"."string" is not in a valid state, table will not be exported.
Cause: A table or one of its dependant types has modified without cascading the change. This left the table in an INVALID state.
Action: The table must be updated using ALTER TABLE UPDATE.
EXP-00100 error converting an object type's hashcode to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Support Services.
EXP-00101 Version 1 extensible index "string"."string" can not be included in Transportable Tablespace Export.
Cause: Transportable Tablespace extensible indexes must be at least version 2.
Action: Upgrade the extensible index implementation to version 2 specifications.
EXP-00102 Resumable parameters ignored -- current session not resumable
Cause: The current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable sessions in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMPORT ERROR MESSAGES
----------------------------------------------
This chapter lists messages generated by the Import utility. For more information about this utility, refer to Oracle9i Database Utilities.
IMP-00000 Import terminated unsuccessfully
Cause: Import encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.
IMP-00001 respond with either string, string, RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
IMP-00002 failed to open string for read
Cause: Import failed to open the export file for reading. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
IMP-00003 ORACLE error number encountered
Cause: Import encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual, and take appropriate action.
IMP-00004 invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
IMP-00005 all allowable logon attempts failed
Cause: An attempt was repeatedly made to log on with an invalid username or password.
Action: Retry with valid username and password.
IMP-00006 failed to allocate memory of size number
Cause: Import failed to allocate the necessary memory.
Action: Decrease the import buffer size so that less memory is required, or increase the runtime memory size for Import.
IMP-00007 must be a DBA to import objects to another user's account
Cause: The privileges needed to import into another user's account do not exist. Only a database administrator can import into another user's account.
Action: Ask the database administrator to do the import.
IMP-00008 unrecognized statement in the export file: string
Cause: Import did not recognize a statement in the export file. Either the export file was corrupted, or an Import internal error has occurred.
Action: If the export file was corrupted, retry with a new export file. Otherwise, report this as an Import internal error and submit the export file to Oracle Support Services.
IMP-00009 abnormal end of export file
Cause: The export file is probably from an aborted Export session.
Action: If so, retry the export and import. Otherwise, report this as an Import bug and submit the export file that caused this error to Oracle Support Services.
IMP-00010 not a valid export file, header failed verification
Cause: Either the file was not generated by Export or it was corrupted.
Action: If the file was indeed generated by Export, report this an Import bug and submit the export file to Oracle Support Services.
IMP-00011 formatted table data not currently supported
Cause: An attempt was made to import an export file that contains formatted table data. Import only supports export files containing binary table data.
Action: Retry using an export file that contains only binary table data.
IMP-00012 invalid export mode (character) in header
Cause: The Export mode specified in the export file header is invalid.
Action: Check the export file to see if it was corrupted. If it was not, report this as an Import bug and submit the export file to Oracle Support Services.
IMP-00013 only a DBA can import a file exported by another DBA
Cause: The privileges needed to Import an export file generated by a database administrator do not exist. Only a database administrator can import such files.
Action: Ask the database administrator to do the import.
IMP-00014 option "string" is needed, but not present in database
Cause: The command entered requires the specified option. Either that option is not installed, or the row describing the option is missing from table V$OPTION.
Action: Reinstall Oracle with the option specified by the message.
IMP-00015 following statement failed because the object already exists:
Cause: Import failed to create an object because it already exists.
Action: Specify IGNORE=Y to ignore such errors and import rows even when tables are not created because they already exist.
IMP-00016 required character set conversion (type number to number) not supported
Cause: Import could not convert the character format of the export file into the native character format.
Action: Change the user character set by setting the NLS_LANG environment variable to match the character set of the export file.
IMP-00017 following statement failed with ORACLE error number:
Cause: Import failed to execute the statement from the export file because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00018 partial import of previous table completed: number rows imported
Cause: A table was only partially imported because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00019 row rejected due to ORACLE error number
Cause: Import encountered the referenced Oracle error while trying to import a row.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00020 long column too large for column buffer size (number)
Cause: The column buffer is too small. This usually occurs when importing LONG data.
Action: Increase the insert buffer size 10,000 bytes at a time (for example). Use this step-by-step approach because a buffer size that is too large may cause a similar problem.
IMP-00021 INCTYPE parameter is obsolete
Cause: Import encountered the INCTYPE parameter when parsing Import options. Incremental Imports are no longer supported.
Action: Consult the Oracle9i User-Managed Backup and Recovery Guide. Import will attempt to continue.
IMP-00022 failed to process parameters, type 'IMP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
IMP-00023 Import views not installed, please notify your DBA
Cause: The necessary Import views were not installed.
Action: Ask your database administrator to install the required Import views.
IMP-00024 Only one mode (TABLES, FROMUSER, or FULL) can be specified
Cause: Parameters were specified that conflict with the import specification FULL=Y.
Action: Retry, making sure not to specify FULL=Y.
IMP-00025 for DBA export files, FROMUSER must be specified with TOUSER option
Cause: When importing a database administrator export file, you specified the TOUSER parameter but not the FROMUSER parameter.
Action: Specify the FROMUSER parameter so that Import knows which user's objects to import.
IMP-00027 failed to rollback partial import of previous table
Cause: Import encountered an Oracle error while trying to roll back a partial import.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action. Then, log on to Oracle and check that the partial import was not committed.
IMP-00028 partial import of previous table rolled back: number rows rolled back
Cause: Import encountered an Oracle error while trying to import a table.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action. Then, if necessary, re-import the table.
IMP-00029 cannot qualify table name by owner (string), use FROMUSER parameter
Cause: A table name was qualified with the name of its owner, as shown in the following example:
IMP SYSTEM/MANAGER TABLES=(SCOTT.EMP)
This is not allowed.
Action: Use the FROMUSER parameter to specify the table's owner, as shown in the following example:
IMP SYSTEM/MANAGER FROMUSER=SCOTT TABLES=(EMP, DEPT)
IMP-00030 failed to create file string for write
Cause: Import was unable to create the specified file with write enabled.
Action: Check the file name and file system for the source of the error.
IMP-00031 Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES arguments
Cause: The database administrator did not specify full or partial import.
Action: The database administrator must specify FROMUSER/TOUSER or table arguments if not a full import.
IMP-00032 SQL statement exceeded buffer length
Cause: The buffer was too small for the SQL statement being read.
Action: Rerun with a larger buffer. This can also be an indication of a corruption in the import datafile.
IMP-00033 Warning: Table "string" not found in export file
Cause: A table name was specified that does not exist in export file.
Action: Correct the table specification.
IMP-00034 Warning: FromUser "string" not found in export file
Cause: The user specified a FROMUSER name that does not exist in export file.
Action: Correct the FROMUSER specification.
IMP-00035 input file string must be on a disk
Cause: On some platforms, import can read files from tape. This message is displayed if the first file in an export file set was on disk and you specified a tape device for a second or subsequent file.
Action: Verify that you have specified the correct file name for the import file. Remember that all input files can be either on disk or all files can be on tape, but not mixed both tape and disk.
IMP-00036 Could not find environment character set
Cause: An environment character set was specified that was not recognized by the Import utility.
Action: Ensure that the spelling of the character set specified in the command line parameter CHARSET (for Release 6 only) or the environment variable NLS_LANG is correct.
IMP-00037 Character set marker unknown
Cause: The export file is corrupted.
Action: Try to obtain an uncorrupted version of the export file. If the export file is not corrupted, report this as an Import internal error and submit the export file to Oracle Support Services.
IMP-00038 Could not convert to environment character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00039 VOLSIZE does not match the value used for export: string
Cause: The value specified for VOLSIZE does not match the value specified during the creation of the export file.
Action: If you believe that the specified VOLSIZE value is correct, verify that you specified the correct file for import. If you specified the correct file but are unsure about the correct value, re-execute the import command but specify VOLSIZE=0.
IMP-00040 FILESIZE does not match the value used for export: string
Cause: The value specified for FILESIZE does not match the value specified during the creation of the export file.
Action: If you believe the specified FILESIZE value is correct, verify that you specified the correct file for import. If you specified the correct file but are unsure about the correct value, re-execute the import command but specify FILESIZE=0.
IMP-00041 Warning: object created with compilation warnings
Cause: The object in the SQL statement following this error was created with compilation errors. If this error occurred for a view, it is possible that the base table of the view was missing.
Action: This is a warning. The object may have to be recompiled before being used.
IMP-00042 CHARSET used, but the export file has specific character set
Cause: The user requested that a specific character set be used to process an export file that has a specific embedded character set ID. The ID in the export file is accurate and should be used.
Action: Remove the CHARSET keyword from the command line.
IMP-00043 export file character set inconsistent
Cause: The character set of the export file and the environment character set (or the character set specified with the CHARSET keyword) are inconsistent. One character set is ASCII-based while the other is EBCDIC based.
Action: Specify the correct character set with the CHARSET keyword.
IMP-00044 unable to allocate enough memory for statement
Cause: Import was unable to allocate sufficient memory to read in the specified statement and execute it.
Action: Run the Import command again with a larger value for the buffer option.
IMP-00045 using VOLSIZE value from export file of string
Cause: Either you did not specify the VOLSIZE parameter in your IMPORT command, or you specified VOLSIZE=0 and the export was created with a non-zero value for VOLSIZE. Import will use the value specified in the export file.
Action: No action required.
IMP-00046 using FILESIZE value from export file of string
Cause: Either you did not specify the FILESIZE parameter in your IMPORT command, or you specified FILESIZE=0 and the export file was created with a non-zero value for FILESIZE. Import will use the value specified in the export file.
Action: No action required.
IMP-00047 unexpected file sequence number; expected number but found number
Cause: The header in the export file contains a sequence number that is used to track the order in which multiple export files are written. The first export file is assigned sequence number one, the second file is assigned sequence number two and so on. This message is displayed when a number other than the expected sequence number is found in the file header
Action: Execute the import command again, but specify the files in the order in which Export wrote them.
IMP-00048 mismatched file header
Cause: During verification of the 2nd or subsequent file in a multi-file export, Import found header fields in the file that did not match values in the first file.
Action: Check the names of the files created by Export and verify that you specified them correctly for the import operation.
IMP-00049 Unknown language specified in CHARSET
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.
IMP-00050 Dump file and log file cannot be identical
Cause: Identical names were given to the dump file and log file.
Action: Specify different names for the dump file and log file and retry the operation.
IMP-00051 Direct path exported dump file contains illegal column length
Cause: An invalid column length was encountered while processing column pieces.
Action: Check to make sure the export file is not corrupted, or else report this to Oracle Support Services as an Import/Export internal bug and submit the export file.
IMP-00052 Warning: Unable to set event for freelist communication with server
Cause: An event could not be set for current the session.
Action: If Import fails, give the Import user ALTER SESSION PRIV and retry the operation.
IMP-00053 Import mode incompatible with Export dump file
Cause: The specified import option is incompatible with point-in-time- recovery dump file.
Action: Generate a proper dump file or use point-in-time-recovery import mode.
IMP- 00054 must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.
Action: Ask your database administrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.
IMP-00055 Warning: partition or subpartition "string":"string" not found in export file
Cause: A partition or subpartition name was specified that does not exist in export file.
Action: Check to make sure the partition or subpartition name belongs to the table.
IMP-00056 multiple devices specified for tape input
Cause: You specified multiple file names when doing an import from a tape device. Import uses the same device for reading all tapes, regardless of the number of tape volumes required. For this reason, export will accept only one value for the FILE parameter when writing to tape.
Action: Re-enter the IMPORT command, but specify only one tape device in the FILE parameter.
IMP-00057 Warning: Dump file may not contain data of all partitions of this table
Cause: The dump file used for this Table Import might not contain all of the data belonging to the exported table.
Action: Check to see if the export was done as intended, or try performing a Partition Import.
IMP-00059 Failure to initialize parameter manager
Cause: Parameter manager failed in initialization.
Action: Report this to Oracle Support Services as an Import internal bug.
IMP-00060 Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
Cause: An object type needed by the table, either does not exist on the target system or, if it does exist, it has a different object identifier.
Action: Create the object type on the target system with a valid identifier.
IMP-00061 Warning: Object type "string"."string" already exists with a different identifier
Cause: An object type cannot be created because it already exists on the target system, but with a different identifier.
Action: Drop the object type from the target system and retry the operation.
IMP-00062 Warning: The identifier on the dump file for object type "string"."string" is invalid
Cause: The character string representing the object type's identifier could not be converted to an object identifier. This is an internal error.
Action: Contact Oracle Support Services.
IMP-00063 Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
Cause: An error occurred creating an object type that is used by the table.
Action: Examine the import log to determine why the object type could not be created. If the object type already existed, with a different object identifier, then drop the object type and retry the import.
IMP-00064 Definition of LOB was truncated by export
Cause: While producing the dump file, Export was unable to write the entire contents of a LOB. Import is therefore unable to reconstruct the contents of the LOB. The remainder of the import of the current table will be skipped.
Action: Delete the offending row in the exported database and retry the export.
IMP-00065 Import is unable to recreate lobs within objects.
Cause: An error occurred while re-creating a LOB within an imported object.
Action: Report this to Oracle Support Services as an Import internal error.
IMP-00066 Missing NLS_CHARACTERSET in props$
Cause: No value for NLS_CHARACTERSET in props$.
Action: Contact Oracle Support Services.
IMP-00067 Could not convert to server character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00068 Could not find environment national character set
Cause: An environment national character set was specified that was not recognized by the Import utility.
Action: Ensure that the spelling of the national character set specified in the environment variable NLS_NCHAR is correct.
IMP-00069 Could not convert to environment national character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00070 Lob definitions in dump file are inconsistent with database.
Cause: The number of LOBS per row in the dump file is different than the number of LOBS per row in the table being populated.
Action: Modify the table being imported so that it matches the column attribute layout of the table that was exported.
IMP-00071 Object identifier of imported table mismatches object identifier of existing table
Cause: An attempt was made to import data into a table that was re-created under a different object identifier than the object identifier used for the exported object table. Under this situation, REF's to this table that are contained within the dump file will also be invalid.
Action: Drop the offending object table prior to import.
IMP-00072 Warning: The object table's object identifier is invalid.
Cause: The character string representing the table's object identifier could not be converted to an internal object identifier. This is an internal error.
Action: Contact Oracle Support Services.
IMP-00073 FILE locator "string" "string" is truncated to "string" "string" in server character set
Cause: The conversion of the specified directory and name strings for a file attribute or column from the export server's character set into the import server's character set exceeded the maximum string lengths allowed within FILE descriptors. The strings will be truncated to the maximum supported lengths.
Action: Rename the directory aliases and external file names to match the truncated names in the specified FILE column or attribute.
IMP-00074 The constraints flagged by ALL_CONSTRAINTS.BAD will break in 2000 A.D.
Cause: Constraints exist in the data base that specify date values without fully specifying the year. These constraints could break in the year 2000 A.D.
Action: Query ALL_CONSTRAINTS and correct those constraints marked as bad.
IMP-00075 Warning: The nested table may contain partial rows or duplicate rows
Cause: An error occurred inserting data into an outer or inner nested table. If the error occurred in the outer table, rows are still inserted into the inner tables. If the error occurred in an inner table, data is still inserted into the outer table and other inner tables. This can result in duplicate inner table rows or partial logical rows.
Action: Examine the data in the tables. Delete the incorrect rows or drop the entire table and perform the import again.
IMP-00076 Missing NLS_NCHAR_CHARACTERSET in props$
Cause: No value for NLS_NCHAR_CHARACTERSET in props$.
Action: Contact Oracle Support Services.
IMP-00077 Could not convert to server national character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00078 Cannot translate FILE locator to "string" "string" in server character set
Cause:
The current export dump file was generated using Beta-2 of Oracle8.0 and
there was a File that appeared as an attribute of an ADT within a table's column and
the character set of the export server's database was different than the character set of the import server's database and
when the file name or the aliasing of the File increased in size when it was translated to the character set of the import server.
When all of these conditions are true, translation of the strings could yield corruption of the data in the column. Rather than proceeding with the translation, import will leave the character strings in the File in the old character set.
Action: After import completes, rename the directory aliases and external file names to match the real names used for the target database.
IMP-00079 Warning: National character set data in this table may be incorrect
Cause: Due to a problem in 8.0.2 Export, national character data in NCHAR and NVARCHAR2 columns was incorrectly assumed to be in the export server's data base character set and was converted to the export client's data base character set. This conversion would only be correct if the export server's data base character set was the same as the export server's national character set and the export client's data base character set was the same as the export client's national character set. All other combinations would likely be incorrect. This export dump file was generated by 8.0.2 Export and the export client and server character sets did not fit that criteria.
Action: Examine the national character data. If incorrect, update the data with correct data.
IMP-00080 Error during character conversion of long column or long command
Cause: During piecewise character conversion of the data in a long column or of a long command, a fatal conversion error occurred. Either character truncation occurred or an invalid character set handle was used.
Action: Retry the import with a different character set.
IMP-00081 attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Support Services.
IMP-00082 Error during conversion ROWID from string format to internal
Cause: An error occurred while attempting to convert a ROWID from an export dump file into an internal format.
Action: Report this to Oracle Support Services as an Import internal error.
IMP-00083 dump file does not contain an incremental export
Cause: An incremental import was requested and the dump file specified for the import command is either a user or table export.
Action: Reissue the command import command but specify the name of a dump file containing an incremental export.
IMP-00084 attempt to mix incremental import with user or table import
Cause: An incremental import was requested along with the FROMUSER, TOUSER, or TABLE qualifier. An incremental import cannot be done if any of these other qualifiers are also specified.
Action: Determine whether you want to do an incremental import, full import, user import or table import and reissue the import command with the appropriate qualifiers.
IMP-00085 multiple input files specified for unbounded export file
Cause: You specified multiple file names for the FILE parameter when doing an import, but the header in the export file indicates that the export operation could create only one file. Specifying multiple file names is valid for an import operation only if the export files were created by an export operation in which the user specified a non-zero value for the FILESIZE parameter.
Action: If you believe the export contains multiple files, verify that you have specified the correct files. If you believe the export should be in only one file then try the import operation again, but specify only one value for the FILE parameter.
IMP-00086 TOID "string" not found in export file
Cause: Import did not find the type identification specified in the TOID_NOVALIDATE parameter. The specified type identification does not exist in export file.
Action: Correct or omit the TOID_NOVALIDATE parameter.
IMP-00087 Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Support Services.
IMP-00088 Problem importing metadata for index string. Index creation will be skipped
Cause: Domain indexes import private metadata via anonymous PL/SQL blocks prior to the CREATE INDEX statement. The execution of one of these PL/SQL blocks failed. Because the metadata is considered an integral part of the index, the subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index's implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Support Services.
IMP-00089 Fine grain policy "string" not recreated on table/view "string"
Cause: Import user fails to recreate fine grained policies of the table/view being imported. To recreate the policy, the user doing the import needs execute privilege on the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export/import of this table/view.
IMP-00090 Unexpected DbmsJava error number at step number while creating string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal error to Oracle Support Services.
IMP-00091 Above error occurred on the following function and object: string. Remaining PL/SQL blocks for this object will be skipped.
Cause: An error occurred while executing a PL/SQL block that implements the DDL for the named function and procedural object. A procedural object is one whose DDL is implemented as stored procedures rather than as standard SQL statements.
Action: Contact Oracle Support Services so they may determine the development group responsible for the package that failed.
IMP-00092 Java object "string"."string" already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it already exists.
Action: Drop the object type from the target system and retry the operation.
IMP-00093 Inconsistency between dumpfile constraint definition for table string with columns (string)
Cause: Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.
IMP-00094 Warning: The identifier on the dump file for object type "string"."string" is invalid.
Cause: The character string representing the object type's identifier could not be converted.
Action: Contact Oracle Support Services.
IMP-00095 Resumable parameters ignored -- current session not resumable
Cause: The current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable sessions in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMP-00096 Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
Cause: An error occurred creating a synonym for a type that is used by the table.
Action: Examine the import log to determine why the type synonym could not be created. If the synonym already existed, but is not needed, then drop the synonym and retry the import. If the synonym is PUBLIC but the importer does not have the CREATE PUBLIC SYNONYM system privilege, then the import must be done by someone possessing that privilege, or the importer must be granted the privilege.
IMP-00097 STREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
Cause: STREAMS_CONFIGURATION=Y can only be used when FULL=Y is present on the command line.
Action: Remove conflicting command arguments.
IMP-00098 INTERNAL ERROR: string
Cause: An INTERNAL error has occurred.
Action: Contact Oracle Support Services.
Thanks
Cheers!!!
-------------------------------------------
EXP-00000 Export terminated unsuccessfully
Cause: Export encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.
EXP-00001 data field truncation - column length=number, buffer size=number actual size=number
Cause: Export could not fit a column in the data buffer.
Action: Record the given size parameters and the accompanying messages and report this as an Export internal error to Oracle Support Services. (Part of the table has been exported. Export will continue with the next table.)
EXP-00002 error in writing to export file
Cause: Export could not write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
EXP-00003 no storage definition found for segment(number, number)
Cause: Export could not find the storage definitions for a cluster, index, or table.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00004 invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
EXP-00005 all allowable logon attempts failed
Cause: Attempts were repeatedly made to log on with an invalid username or password.
Action: Shut down the utility, then restart and retry with a valid username and password.
EXP-00006 internal inconsistency error
Cause: Export's data structure was corrupted.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00007 dictionary shows no columns for string.string
Cause: Export failed to gather column information from the data dictionary. The table may have been dropped.
Action: Retry the export and, if this error recurs, report it as an Export internal error to Oracle Support Services.
EXP-00008 ORACLE error number encountered
Cause: Export encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00009 no privilege to export string's table string
Cause: An attempt was made to export another user's table. Only a database administrator can export another user's tables.
Action: Ask your database administrator to do the export.
EXP-00010 string is not a valid username
Cause: An invalid username was specified.
Action: Shut down the utility, then restart and retry with a valid username.
EXP-00011 string.string does not exist
Cause: Export could not find the specified table.
Action: Retry with the correct table name.
EXP-00012 string is not a valid export mode
Cause: An invalid export mode was specified.
Action: Retry with a valid export mode.
EXP-00013 respond with either 'Y', 'N', RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
EXP-00014 error on row number of table string
Cause: Export encountered an Oracle error while fetching rows.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00015 error on row number of table string, column string, datatype number
Cause: Export encountered an error while fetching or writing the column. An accompanying message gives more information.
Action: Correct the error and try again.
EXP-00016 ORACLE error encountered while reading default auditing options
Cause: Export encountered an Oracle error while reading the default auditing options (those for updates, deletes, and so on).
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00017 feature 'string' is needed, but not present in database"
Cause: The command entered requires the specified feature. Either that feature is not installed, or the row describing the feature is missing from table V$OPTION.
Action: Re-install Oracle with the feature specified in the message.
EXP-00018 datatype (number) for column string, table string.string is not supported
Cause: Export does not support the referenced datatype.
Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or RAW).
EXP-00019 failed to process parameters, type 'EXP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
EXP-00020 failed to allocate memory of size number
Cause: Export failed to allocate the necessary memory.
Action: Decrease the export buffer size so that less memory is required, or increase the runtime memory size for Export.
EXP-00021 can only perform incremental export in Full Database mode
Cause: USER or TABLE mode was specified when doing an incremental export.
Action: Specify FULL database mode (FULL=Y) and retry.
EXP-00022 must be SYS or SYSTEM to do incremental export
Cause: The privileges needed to do an incremental export do not exist. Only a data base administrator can do incremental exports.
Action: Ask the database administrator to do the incremental export.
EXP-00023 must be a DBA to do Full Database or Tablespace export
Cause: The privileges needed to do a FULL database export do not exist. Only a database administrator can do a FULL database export.
Action: Ask the database administrator to do the FULL database export.
EXP-00024 Export views not installed, please notify your DBA
Cause: The necessary Export views were not installed.
Action: Ask the database administrator to install the required Export views.
EXP-00025 dictionary shows no column for constraint string.number
Cause: Export failed to gather column information about the referenced constraint from the data dictionary. The constraint may have been altered.
Action: Retry the export and, if this error recurs, report it as an Export internal error to Oracle Support Services.
EXP-00026 conflicting modes specified
Cause: Conflicting export modes were specified.
Action: Specify only one parameter and retry.
EXP-00027 failed to calculate ORACLE block size
Cause: Export failed to calculate the Oracle block size.
Action: Report this as an Export internal error to Oracle Support Services.
EXP-00028 failed to open string for write
Cause: Export failed to open the export file for writing. This message is usually followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
EXP-00029 Incremental export mode and consistent mode are not compatible
Cause: Both consistent and incremental exports were specified.
Action: No action is required. Consistent mode is turned off.
EXP-00030 Unexpected End-Of-File encountered while reading input
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
EXP-00031 Arraysize not in valid range. Using arraysize=number
Cause: The array size value specified is not in the valid range.
Action: No action required.
EXP-00032 Non-DBAs may not export other users
Cause: Only database administrators can export to other users. A non-database administrator attempted to specify OWNER=USER where exporter is not the user.
Action: Request that this operation be performed by the database administrator.
EXP-00033 Could not find environment character set
Cause: The environment character set is missing or incorrectly specified.
Action: Ensure that the environment character set is correctly specified and is present.
EXP-00034 error on rowid: file# number block# number slot# number
Cause: Identifies the ROWID on which an error occurred.
Action: This is an information message. No action is required.
EXP-00035 QUERY parameter valid only for table mode exports
Cause: You specified the QUERY parameter in an export command, but you are not performing a table mode export. The QUERY parameter cannot be used for a user mode export, a full export, nor a point in time recovery export.
Action: If you want to select a subset of rows for a table, you must export the table independently with a table mode export. Issue a table mode export command that specifies the table name and the query you want to execute during export.
EXP-00036 Object number non-existent in dictionary
Cause: The specified object could not be found in the dictionary. The object might have been dropped during the export
Action: The object no longer exists; no action is needed.
EXP-00037 Export views not compatible with database version
Cause: The Export utility is at a higher version than the database version and is thereby incompatible.
Action: Use the same version of Export utility as the database.
EXP-00038 Bad Hash cluster id in clu$
Cause: The function ID in CLU$ is not a legal number. CLU$ has become corrupted.
Action: Contact Oracle Support Services.
EXP-00039 export file string must be on a disk
Cause: On some platforms, export can read files from tape. This message is displayed if the first file in an export file set was on disk and you specified a tape device for a second or subsequent file.
Action: Verify that you have specified the correct file name for the export file. Remember that all export files can be either on disk or all files can be on tape, but not mixed both tape and disk.
EXP-00040 Dump file and log file must be different
Cause: The dump file and log file cannot be the same file.
Action: Specify different file names for the dump file and the log file, then retry the operation.
EXP-00041 INCTYPE parameter is obsolete
Cause: Export encountered the INCTYPE parameter when parsing Export options. Incremental Exports are no longer supported.
Action: Consult the Oracle9i User-Managed Backup and Recovery Guide. Export will attempt to continue.
EXP-00042 Missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in props$
Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not entered in the props$ table. This is an internal error.
Action: Contact Oracle Support Services.
EXP-00043 Invalid data dictionary information in the row where column "string" is "string" in table string
Cause: The export utility retrieved invalid data from the data dictionary.
Action: Contact Oracle Support Services.
EXP-00044 must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.
EXP-00045 Cannot export SYSTEM Tablespace for Point-in-time Recovery or Transportable Tablespace
Cause: SYSTEM tablespace cannot be part of recovery set or transportable tablespace set.
Action: Contact Oracle Support Services.
EXP-00046 Tablespace named string does not exist
Cause: The specified tablespace does not exist in dictionary.
Action: Contact Oracle Support Services.
EXP-00047 Missing tablespace name(s)
Cause: Tablespace name(s) were not supplied.
Action: Provide tablespace name(s).
EXP-00049 string option is not compatible with Point-in-time Recovery or Transportable Tablespace export
Cause: An option was specified that is incompatible with Point-in-time Recovery or Transportable Tablespace Export.
Action: Retry the export without the displayed option.
EXP-00050 Cannot perform Partition Export "string" on non-partitioned table "string"
Cause: The table specified in this Partition Export is not a partitioned table.
Action: Use Table mode, or specify a non-partitioned table.
EXP-00051 "string" - given partition or subpartition name is not part of "string" table
Cause: The specified partition or subpartition name is not in the specified table.
Action: Check if the correct table, partition or subpartition name was specified.
EXP-00052 error on row number of partition string
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00053 unable to execute QUERY on table string because the table has inner nested tables
Cause: You specified the QUERY parameter on a table that has one or more inner nested tables. The QUERY parameter cannot be specified on tables that have inner nested tables.
Action: Export the entire table by omitting the QUERY parameter.
EXP-00054 error on row number of subpartition string
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
EXP-00055 string.string is marked not exportable
Cause: An object was marked as non-exportable in the NOEXP$ table.
Action: Consult your database administrator.
EXP-00057 Failure to initialize parameter manager
Cause: The parameter manager failed in intialization.
Action: Record the messages that follow and report this to Oracle Support Services as an Export internal bug.
EXP-00058 Password Verify Function for string profile does not exist
Cause: Cannot find the function for the profile.
Action: Check if the profile was created properly.
EXP-00059 error converting an object type's identifier to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Support Services.
EXP-00060 an object type had multiple TYPE BODYs
Cause: More than one TYPE BODY was found for an object type.
Action: Try dropping the TYPE BODY, if that is not successful, contact Oracle Support Services.
EXP-00061 unable to find the outer table name of a nested table
Cause: While exporting a bitmap index or postable action on an inner nested table, the name of the outer table could not be located, using the NTAB$ table.
Action: Verify the table is properly defined.
EXP-00062 invalid source statements for an object type
Cause: TYPE was not found in the statements in SOURCE$ for an Object Type.
Action: Contact Oracle Support Services.
EXP-00063 error in changing language handle
Cause: Unable to change language handle.
Action: Contact Oracle Support Services.
EXP-00064 string is an inner nested table and connot be exported.
Cause: An attempt was made to export an inner nested table without its parent table.
Action: Export the parent of the inner nested table.
EXP-00065 Error writing lob to the dump file.
Cause: The current LOB could not be written to the dump file.
Action: Identify the cause of the write failure and fix it.
EXP-00066 Object table string is missing its object identifier index
Cause: All object tables must have an object identifier index, but the specified table was missing an index on its object identifier column.
Action: Re-create the type table and retry the operation.
EXP-00068 tablespace string is offline
Cause: Export failed to export tablespace (tablespace being offline).
Action: Make tablespace online and re-export.
EXP-00070 attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Support Services.
EXP-00071 QUERY parameter not compatible with Direct Path export
Cause: You specified a value for the QUERY parameter for a direct path export. The QUERY parameter cannot be used with a direct path export.
Action: Re-issue the export command with DIRECT=N or omit the DIRECT parameter from the command line.
EXP-00072 error closing export file string
Cause: An error occurred while trying to close the export file.
Action: Contact Oracle Support Services.
EXP-00073 dump file size too small
Cause: You specified either the FILESIZE parameter or the VOLSIZE parameter (if your platform supports it), and the value of the parameter is too small to hold the header information for the export file, plus any data.
Action: Increase the value of the FILESIZE or VOLSIZE parameter.
EXP-00074 rounding VOLSIZE down, new value is string
Cause: The VOLSIZE parameter must be a multiple of the RECORDLENGTH, but the value you specified for VOLSIZE does not meet this requirement. The value of VOLSIZE has been rounded down to be a multiple of the RECORDLENGTH used for the dump file.
Action: No action is required. You can adjust the VOLSIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the VOLSIZE value reported by this message.
EXP-00075 rounding FILESIZE down, new value is string
Cause: The FILESIZE parameter must be a multiple of the RECORDLENGTH, but the value you specified for FILESIZE does not meet this requirement. The value of FILESIZE has been rounded down to be a multiple of the RECORDLENGTH used for the dump file.
Action: No action is required. You can adjust the FILESIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the FILESIZE value reported by this message.
EXP-00076 multiple devices specified for tape output
Cause: You specified multiple file names when doing an export to a tape device. EXPORT uses the same device for writing all files, of the number of tape volumes required. For this reason, export will accept only one value for the FILE parameter when writing to tape.
Action: Re-enter the EXPORT command, but specify only one tape device in the FILE parameter.
EXP-00077 multiple output files specified for unbounded export file
Cause: You specified multiple file names when doing an export and you also specified a value of 0 for the FILESIZE parameter. Note that 0 is the value used if FILESIZE is not specified on the command line. Since a value of 0 for FILESIZE means that only one file will be written and there is no size limit for that file, the other files you specified in the FILE parameter can never be used.
Action: If you intended to write multiple files, respecify the command but use the FILESIZE to specify the maximum number of bytes that EXPORT should write to each file. If you intended to write only one file with no limits on it's size, reissue the EXPORT command but specify only one file name for the FILE parameter.
EXP-00078 Error exporting metadata for index string. Index creation will be skipped
Cause: Domain indexes export private metadata via anonymous PL/SQL blocks prior to the CREATE INDEX statement. Export does this by calling the ODCIIndexGetMetadata method on the implementation type associated with the index. A problem occurred inside this routine. Because the metadata is considered an integral part of the index, the CREATE INDEX statement was not written to the dump file.
Action: Contact the developer of the index's implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Support Services.
EXP-00079 Data in table "string" is protected. Conventional path may only be exporting partial table.
Cause: User without the execute privilege on DBMS_RLS, the access control package, tries to export a table that has access control. Since table owner is also subjected to access control, the owner may not be able to export all rows in the table, but only the ones he can see. Also, to preserve integrity of the table, user exporting the table should have enough privilege to re-create the table with the security policies at import time. Therefore, it is strongly recommended the database administrator should be handling exporting of this table. Granting the table owner execute privilege would also satisfy this security check, though it might have other security implications. If the table does not have objects, can use direct mode.
Action: Ask the database administrator to export/import this table/view.
EXP-00080 Data in table "string" is protected. Using conventional mode.
Cause: User without the execute privilege on DBMS_RLS, the access control package, tries to direct export a table that has access control enabled. Using conventional export mode instead. Note that because of access control, only a partial table may be exported.
Action: Ask the database administrator to export/import this table/view.
EXP-00081 Exporting access control for table/view "string" as non-DBA.
Cause: A non-DBA user tries to export table/view and the associated fine grain access control policies. The user may not have enough privilege to re-create the access control policies when importing the table/view. And such an event may cause inconsistency in the security model of the table/view.
Action: Ask the database administrator to export/import this table/view.
EXP-00082 Invalid function name passed to procedural object support: string
Cause: Internal inconsistency error: The listed function is not a method on export's procedural object interface specification.
Action: Contact Oracle Support Services.
EXP-00083 The previous problem occurred when calling string.string.string
Cause: The listed package provides export/import support for procedural actions. The previously listed error occurred while calling the specified function.
Action: Contact Oracle Support Services. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Oracle Support Services determine the correct owner of the problem.
EXP-00084 Unexpected DbmsJava error number at step number
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00085 The previous problem occurred when calling string.string.string for object number
Cause: The listed package provides export/import support for procedural objects, i.e., those whose DDL is supplied by stored procedures. The previously listed error occurred while calling the specified function.
Action: Contact Oracle Support Services. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Oracle Support Services determine the correct owner of the problem.
EXP-00086 Primary key REFs in table "string"may not be valid on import
Cause: The specified table contains primary key REFs which may not be valid in the import database.
Action: Do not use Export/Import to move Primary key REFs between databases having differing character sets.
EXP-00087 Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Support Services.
EXP-00089 invalid FILE_FORMAT specification
Cause: The FILE_FORMAT specification did not contain an instance of "string". This wildcard string must be present.
Action: Correct the error and re-enter the EXPORT command.
EXP-00090 cannot pin type "string"."string"
Cause: Export was unable to pin the specified type in the object cache. This is typically caused because a type could not be made valid (for example because of authorization violations in accessing subtypes).
Action: Fix the problem with the offending type until the type can be successfully compiled.
EXP-00091 Exporting questionable statistics
Cause: Export was able to export statistics, but the statistics may not be useable. The statistics are questionable because one or more of the following happened during export: a row error occurred, client character set or NCHARSET does not match with the server, a query clause was specified on export, only certain partitions or subpartitions were exported, or a fatal error occurred while processing a table.
Action: To export non-questionable statistics, change the client character set or NCHARSET to match the server, export with no query clause, or export complete tables. If desired, import parameters can be supplied so that only non-questionable statistics will be imported, and all questionable statistics will be recalculated.
EXP-00092 unable to set NLS_NUMERIC_CHARACTERS to required defaults
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
EXP-00093 could not convert to server character set's handle
Cause: Internal error.
Action: Contact Oracle Support Services.
EXP-00094 could not convert to server national character set's handle
Cause: Internal error.
Action: Contact Oracle Support Services.
EXP-00095 Flashback_time and Flashback_scn are not compatible
Cause: Both flashback_time and flashback_scn parameters were specified.
Action: Reissue the command with only one flashback parameter.
EXP-00096 The template name specified can not be found.
Cause: The specified template name does not exist.
Action: Verify the template name by looking up view %_ias_template.
EXP-00097 Object type "string"."string" is not in a valid state, type will not be exported.
Cause: The object type's status is invalid which may be caused by a dependant type's modification (or removal) without cascading the change.
Action: The type must be recompiled using ALTER TYPE COMPILE.
EXP-00098 Data in table has not been upgraded, table will not be exported.
Cause: Export is attempting to process a table containing references to a type which has evolved. In order for Export to process the table successfully, all data within each table must be upgraded to the latest revision of each referenced type.
Action: The table must be updated using ALTER TABLE UPGRADE DATA.
EXP-00099 Table "string"."string" is not in a valid state, table will not be exported.
Cause: A table or one of its dependant types has modified without cascading the change. This left the table in an INVALID state.
Action: The table must be updated using ALTER TABLE UPDATE.
EXP-00100 error converting an object type's hashcode to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Support Services.
EXP-00101 Version 1 extensible index "string"."string" can not be included in Transportable Tablespace Export.
Cause: Transportable Tablespace extensible indexes must be at least version 2.
Action: Upgrade the extensible index implementation to version 2 specifications.
EXP-00102 Resumable parameters ignored -- current session not resumable
Cause: The current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable sessions in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMPORT ERROR MESSAGES
----------------------------------------------
This chapter lists messages generated by the Import utility. For more information about this utility, refer to Oracle9i Database Utilities.
IMP-00000 Import terminated unsuccessfully
Cause: Import encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.
IMP-00001 respond with either string, string, RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
IMP-00002 failed to open string for read
Cause: Import failed to open the export file for reading. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
IMP-00003 ORACLE error number encountered
Cause: Import encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual, and take appropriate action.
IMP-00004 invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
IMP-00005 all allowable logon attempts failed
Cause: An attempt was repeatedly made to log on with an invalid username or password.
Action: Retry with valid username and password.
IMP-00006 failed to allocate memory of size number
Cause: Import failed to allocate the necessary memory.
Action: Decrease the import buffer size so that less memory is required, or increase the runtime memory size for Import.
IMP-00007 must be a DBA to import objects to another user's account
Cause: The privileges needed to import into another user's account do not exist. Only a database administrator can import into another user's account.
Action: Ask the database administrator to do the import.
IMP-00008 unrecognized statement in the export file: string
Cause: Import did not recognize a statement in the export file. Either the export file was corrupted, or an Import internal error has occurred.
Action: If the export file was corrupted, retry with a new export file. Otherwise, report this as an Import internal error and submit the export file to Oracle Support Services.
IMP-00009 abnormal end of export file
Cause: The export file is probably from an aborted Export session.
Action: If so, retry the export and import. Otherwise, report this as an Import bug and submit the export file that caused this error to Oracle Support Services.
IMP-00010 not a valid export file, header failed verification
Cause: Either the file was not generated by Export or it was corrupted.
Action: If the file was indeed generated by Export, report this an Import bug and submit the export file to Oracle Support Services.
IMP-00011 formatted table data not currently supported
Cause: An attempt was made to import an export file that contains formatted table data. Import only supports export files containing binary table data.
Action: Retry using an export file that contains only binary table data.
IMP-00012 invalid export mode (character) in header
Cause: The Export mode specified in the export file header is invalid.
Action: Check the export file to see if it was corrupted. If it was not, report this as an Import bug and submit the export file to Oracle Support Services.
IMP-00013 only a DBA can import a file exported by another DBA
Cause: The privileges needed to Import an export file generated by a database administrator do not exist. Only a database administrator can import such files.
Action: Ask the database administrator to do the import.
IMP-00014 option "string" is needed, but not present in database
Cause: The command entered requires the specified option. Either that option is not installed, or the row describing the option is missing from table V$OPTION.
Action: Reinstall Oracle with the option specified by the message.
IMP-00015 following statement failed because the object already exists:
Cause: Import failed to create an object because it already exists.
Action: Specify IGNORE=Y to ignore such errors and import rows even when tables are not created because they already exist.
IMP-00016 required character set conversion (type number to number) not supported
Cause: Import could not convert the character format of the export file into the native character format.
Action: Change the user character set by setting the NLS_LANG environment variable to match the character set of the export file.
IMP-00017 following statement failed with ORACLE error number:
Cause: Import failed to execute the statement from the export file because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00018 partial import of previous table completed: number rows imported
Cause: A table was only partially imported because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00019 row rejected due to ORACLE error number
Cause: Import encountered the referenced Oracle error while trying to import a row.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00020 long column too large for column buffer size (number)
Cause: The column buffer is too small. This usually occurs when importing LONG data.
Action: Increase the insert buffer size 10,000 bytes at a time (for example). Use this step-by-step approach because a buffer size that is too large may cause a similar problem.
IMP-00021 INCTYPE parameter is obsolete
Cause: Import encountered the INCTYPE parameter when parsing Import options. Incremental Imports are no longer supported.
Action: Consult the Oracle9i User-Managed Backup and Recovery Guide. Import will attempt to continue.
IMP-00022 failed to process parameters, type 'IMP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
IMP-00023 Import views not installed, please notify your DBA
Cause: The necessary Import views were not installed.
Action: Ask your database administrator to install the required Import views.
IMP-00024 Only one mode (TABLES, FROMUSER, or FULL) can be specified
Cause: Parameters were specified that conflict with the import specification FULL=Y.
Action: Retry, making sure not to specify FULL=Y.
IMP-00025 for DBA export files, FROMUSER must be specified with TOUSER option
Cause: When importing a database administrator export file, you specified the TOUSER parameter but not the FROMUSER parameter.
Action: Specify the FROMUSER parameter so that Import knows which user's objects to import.
IMP-00027 failed to rollback partial import of previous table
Cause: Import encountered an Oracle error while trying to roll back a partial import.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action. Then, log on to Oracle and check that the partial import was not committed.
IMP-00028 partial import of previous table rolled back: number rows rolled back
Cause: Import encountered an Oracle error while trying to import a table.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action. Then, if necessary, re-import the table.
IMP-00029 cannot qualify table name by owner (string), use FROMUSER parameter
Cause: A table name was qualified with the name of its owner, as shown in the following example:
IMP SYSTEM/MANAGER TABLES=(SCOTT.EMP)
This is not allowed.
Action: Use the FROMUSER parameter to specify the table's owner, as shown in the following example:
IMP SYSTEM/MANAGER FROMUSER=SCOTT TABLES=(EMP, DEPT)
IMP-00030 failed to create file string for write
Cause: Import was unable to create the specified file with write enabled.
Action: Check the file name and file system for the source of the error.
IMP-00031 Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES arguments
Cause: The database administrator did not specify full or partial import.
Action: The database administrator must specify FROMUSER/TOUSER or table arguments if not a full import.
IMP-00032 SQL statement exceeded buffer length
Cause: The buffer was too small for the SQL statement being read.
Action: Rerun with a larger buffer. This can also be an indication of a corruption in the import datafile.
IMP-00033 Warning: Table "string" not found in export file
Cause: A table name was specified that does not exist in export file.
Action: Correct the table specification.
IMP-00034 Warning: FromUser "string" not found in export file
Cause: The user specified a FROMUSER name that does not exist in export file.
Action: Correct the FROMUSER specification.
IMP-00035 input file string must be on a disk
Cause: On some platforms, import can read files from tape. This message is displayed if the first file in an export file set was on disk and you specified a tape device for a second or subsequent file.
Action: Verify that you have specified the correct file name for the import file. Remember that all input files can be either on disk or all files can be on tape, but not mixed both tape and disk.
IMP-00036 Could not find environment character set
Cause: An environment character set was specified that was not recognized by the Import utility.
Action: Ensure that the spelling of the character set specified in the command line parameter CHARSET (for Release 6 only) or the environment variable NLS_LANG is correct.
IMP-00037 Character set marker unknown
Cause: The export file is corrupted.
Action: Try to obtain an uncorrupted version of the export file. If the export file is not corrupted, report this as an Import internal error and submit the export file to Oracle Support Services.
IMP-00038 Could not convert to environment character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00039 VOLSIZE does not match the value used for export: string
Cause: The value specified for VOLSIZE does not match the value specified during the creation of the export file.
Action: If you believe that the specified VOLSIZE value is correct, verify that you specified the correct file for import. If you specified the correct file but are unsure about the correct value, re-execute the import command but specify VOLSIZE=0.
IMP-00040 FILESIZE does not match the value used for export: string
Cause: The value specified for FILESIZE does not match the value specified during the creation of the export file.
Action: If you believe the specified FILESIZE value is correct, verify that you specified the correct file for import. If you specified the correct file but are unsure about the correct value, re-execute the import command but specify FILESIZE=0.
IMP-00041 Warning: object created with compilation warnings
Cause: The object in the SQL statement following this error was created with compilation errors. If this error occurred for a view, it is possible that the base table of the view was missing.
Action: This is a warning. The object may have to be recompiled before being used.
IMP-00042 CHARSET used, but the export file has specific character set
Cause: The user requested that a specific character set be used to process an export file that has a specific embedded character set ID. The ID in the export file is accurate and should be used.
Action: Remove the CHARSET keyword from the command line.
IMP-00043 export file character set inconsistent
Cause: The character set of the export file and the environment character set (or the character set specified with the CHARSET keyword) are inconsistent. One character set is ASCII-based while the other is EBCDIC based.
Action: Specify the correct character set with the CHARSET keyword.
IMP-00044 unable to allocate enough memory for statement
Cause: Import was unable to allocate sufficient memory to read in the specified statement and execute it.
Action: Run the Import command again with a larger value for the buffer option.
IMP-00045 using VOLSIZE value from export file of string
Cause: Either you did not specify the VOLSIZE parameter in your IMPORT command, or you specified VOLSIZE=0 and the export was created with a non-zero value for VOLSIZE. Import will use the value specified in the export file.
Action: No action required.
IMP-00046 using FILESIZE value from export file of string
Cause: Either you did not specify the FILESIZE parameter in your IMPORT command, or you specified FILESIZE=0 and the export file was created with a non-zero value for FILESIZE. Import will use the value specified in the export file.
Action: No action required.
IMP-00047 unexpected file sequence number; expected number but found number
Cause: The header in the export file contains a sequence number that is used to track the order in which multiple export files are written. The first export file is assigned sequence number one, the second file is assigned sequence number two and so on. This message is displayed when a number other than the expected sequence number is found in the file header
Action: Execute the import command again, but specify the files in the order in which Export wrote them.
IMP-00048 mismatched file header
Cause: During verification of the 2nd or subsequent file in a multi-file export, Import found header fields in the file that did not match values in the first file.
Action: Check the names of the files created by Export and verify that you specified them correctly for the import operation.
IMP-00049 Unknown language specified in CHARSET
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.
IMP-00050 Dump file and log file cannot be identical
Cause: Identical names were given to the dump file and log file.
Action: Specify different names for the dump file and log file and retry the operation.
IMP-00051 Direct path exported dump file contains illegal column length
Cause: An invalid column length was encountered while processing column pieces.
Action: Check to make sure the export file is not corrupted, or else report this to Oracle Support Services as an Import/Export internal bug and submit the export file.
IMP-00052 Warning: Unable to set event for freelist communication with server
Cause: An event could not be set for current the session.
Action: If Import fails, give the Import user ALTER SESSION PRIV and retry the operation.
IMP-00053 Import mode incompatible with Export dump file
Cause: The specified import option is incompatible with point-in-time- recovery dump file.
Action: Generate a proper dump file or use point-in-time-recovery import mode.
IMP- 00054 must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.
Action: Ask your database administrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.
IMP-00055 Warning: partition or subpartition "string":"string" not found in export file
Cause: A partition or subpartition name was specified that does not exist in export file.
Action: Check to make sure the partition or subpartition name belongs to the table.
IMP-00056 multiple devices specified for tape input
Cause: You specified multiple file names when doing an import from a tape device. Import uses the same device for reading all tapes, regardless of the number of tape volumes required. For this reason, export will accept only one value for the FILE parameter when writing to tape.
Action: Re-enter the IMPORT command, but specify only one tape device in the FILE parameter.
IMP-00057 Warning: Dump file may not contain data of all partitions of this table
Cause: The dump file used for this Table Import might not contain all of the data belonging to the exported table.
Action: Check to see if the export was done as intended, or try performing a Partition Import.
IMP-00059 Failure to initialize parameter manager
Cause: Parameter manager failed in initialization.
Action: Report this to Oracle Support Services as an Import internal bug.
IMP-00060 Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
Cause: An object type needed by the table, either does not exist on the target system or, if it does exist, it has a different object identifier.
Action: Create the object type on the target system with a valid identifier.
IMP-00061 Warning: Object type "string"."string" already exists with a different identifier
Cause: An object type cannot be created because it already exists on the target system, but with a different identifier.
Action: Drop the object type from the target system and retry the operation.
IMP-00062 Warning: The identifier on the dump file for object type "string"."string" is invalid
Cause: The character string representing the object type's identifier could not be converted to an object identifier. This is an internal error.
Action: Contact Oracle Support Services.
IMP-00063 Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
Cause: An error occurred creating an object type that is used by the table.
Action: Examine the import log to determine why the object type could not be created. If the object type already existed, with a different object identifier, then drop the object type and retry the import.
IMP-00064 Definition of LOB was truncated by export
Cause: While producing the dump file, Export was unable to write the entire contents of a LOB. Import is therefore unable to reconstruct the contents of the LOB. The remainder of the import of the current table will be skipped.
Action: Delete the offending row in the exported database and retry the export.
IMP-00065 Import is unable to recreate lobs within objects.
Cause: An error occurred while re-creating a LOB within an imported object.
Action: Report this to Oracle Support Services as an Import internal error.
IMP-00066 Missing NLS_CHARACTERSET in props$
Cause: No value for NLS_CHARACTERSET in props$.
Action: Contact Oracle Support Services.
IMP-00067 Could not convert to server character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00068 Could not find environment national character set
Cause: An environment national character set was specified that was not recognized by the Import utility.
Action: Ensure that the spelling of the national character set specified in the environment variable NLS_NCHAR is correct.
IMP-00069 Could not convert to environment national character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00070 Lob definitions in dump file are inconsistent with database.
Cause: The number of LOBS per row in the dump file is different than the number of LOBS per row in the table being populated.
Action: Modify the table being imported so that it matches the column attribute layout of the table that was exported.
IMP-00071 Object identifier of imported table mismatches object identifier of existing table
Cause: An attempt was made to import data into a table that was re-created under a different object identifier than the object identifier used for the exported object table. Under this situation, REF's to this table that are contained within the dump file will also be invalid.
Action: Drop the offending object table prior to import.
IMP-00072 Warning: The object table's object identifier is invalid.
Cause: The character string representing the table's object identifier could not be converted to an internal object identifier. This is an internal error.
Action: Contact Oracle Support Services.
IMP-00073 FILE locator "string" "string" is truncated to "string" "string" in server character set
Cause: The conversion of the specified directory and name strings for a file attribute or column from the export server's character set into the import server's character set exceeded the maximum string lengths allowed within FILE descriptors. The strings will be truncated to the maximum supported lengths.
Action: Rename the directory aliases and external file names to match the truncated names in the specified FILE column or attribute.
IMP-00074 The constraints flagged by ALL_CONSTRAINTS.BAD will break in 2000 A.D.
Cause: Constraints exist in the data base that specify date values without fully specifying the year. These constraints could break in the year 2000 A.D.
Action: Query ALL_CONSTRAINTS and correct those constraints marked as bad.
IMP-00075 Warning: The nested table may contain partial rows or duplicate rows
Cause: An error occurred inserting data into an outer or inner nested table. If the error occurred in the outer table, rows are still inserted into the inner tables. If the error occurred in an inner table, data is still inserted into the outer table and other inner tables. This can result in duplicate inner table rows or partial logical rows.
Action: Examine the data in the tables. Delete the incorrect rows or drop the entire table and perform the import again.
IMP-00076 Missing NLS_NCHAR_CHARACTERSET in props$
Cause: No value for NLS_NCHAR_CHARACTERSET in props$.
Action: Contact Oracle Support Services.
IMP-00077 Could not convert to server national character set's handle
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMP-00078 Cannot translate FILE locator to "string" "string" in server character set
Cause:
The current export dump file was generated using Beta-2 of Oracle8.0 and
there was a File that appeared as an attribute of an ADT within a table's column and
the character set of the export server's database was different than the character set of the import server's database and
when the file name or the aliasing of the File increased in size when it was translated to the character set of the import server.
When all of these conditions are true, translation of the strings could yield corruption of the data in the column. Rather than proceeding with the translation, import will leave the character strings in the File in the old character set.
Action: After import completes, rename the directory aliases and external file names to match the real names used for the target database.
IMP-00079 Warning: National character set data in this table may be incorrect
Cause: Due to a problem in 8.0.2 Export, national character data in NCHAR and NVARCHAR2 columns was incorrectly assumed to be in the export server's data base character set and was converted to the export client's data base character set. This conversion would only be correct if the export server's data base character set was the same as the export server's national character set and the export client's data base character set was the same as the export client's national character set. All other combinations would likely be incorrect. This export dump file was generated by 8.0.2 Export and the export client and server character sets did not fit that criteria.
Action: Examine the national character data. If incorrect, update the data with correct data.
IMP-00080 Error during character conversion of long column or long command
Cause: During piecewise character conversion of the data in a long column or of a long command, a fatal conversion error occurred. Either character truncation occurred or an invalid character set handle was used.
Action: Retry the import with a different character set.
IMP-00081 attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Support Services.
IMP-00082 Error during conversion ROWID from string format to internal
Cause: An error occurred while attempting to convert a ROWID from an export dump file into an internal format.
Action: Report this to Oracle Support Services as an Import internal error.
IMP-00083 dump file does not contain an incremental export
Cause: An incremental import was requested and the dump file specified for the import command is either a user or table export.
Action: Reissue the command import command but specify the name of a dump file containing an incremental export.
IMP-00084 attempt to mix incremental import with user or table import
Cause: An incremental import was requested along with the FROMUSER, TOUSER, or TABLE qualifier. An incremental import cannot be done if any of these other qualifiers are also specified.
Action: Determine whether you want to do an incremental import, full import, user import or table import and reissue the import command with the appropriate qualifiers.
IMP-00085 multiple input files specified for unbounded export file
Cause: You specified multiple file names for the FILE parameter when doing an import, but the header in the export file indicates that the export operation could create only one file. Specifying multiple file names is valid for an import operation only if the export files were created by an export operation in which the user specified a non-zero value for the FILESIZE parameter.
Action: If you believe the export contains multiple files, verify that you have specified the correct files. If you believe the export should be in only one file then try the import operation again, but specify only one value for the FILE parameter.
IMP-00086 TOID "string" not found in export file
Cause: Import did not find the type identification specified in the TOID_NOVALIDATE parameter. The specified type identification does not exist in export file.
Action: Correct or omit the TOID_NOVALIDATE parameter.
IMP-00087 Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Support Services.
IMP-00088 Problem importing metadata for index string. Index creation will be skipped
Cause: Domain indexes import private metadata via anonymous PL/SQL blocks prior to the CREATE INDEX statement. The execution of one of these PL/SQL blocks failed. Because the metadata is considered an integral part of the index, the subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index's implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Support Services.
IMP-00089 Fine grain policy "string" not recreated on table/view "string"
Cause: Import user fails to recreate fine grained policies of the table/view being imported. To recreate the policy, the user doing the import needs execute privilege on the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export/import of this table/view.
IMP-00090 Unexpected DbmsJava error number at step number while creating string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal error to Oracle Support Services.
IMP-00091 Above error occurred on the following function and object: string. Remaining PL/SQL blocks for this object will be skipped.
Cause: An error occurred while executing a PL/SQL block that implements the DDL for the named function and procedural object. A procedural object is one whose DDL is implemented as stored procedures rather than as standard SQL statements.
Action: Contact Oracle Support Services so they may determine the development group responsible for the package that failed.
IMP-00092 Java object "string"."string" already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it already exists.
Action: Drop the object type from the target system and retry the operation.
IMP-00093 Inconsistency between dumpfile constraint definition for table string with columns (string)
Cause: Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.
IMP-00094 Warning: The identifier on the dump file for object type "string"."string" is invalid.
Cause: The character string representing the object type's identifier could not be converted.
Action: Contact Oracle Support Services.
IMP-00095 Resumable parameters ignored -- current session not resumable
Cause: The current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable sessions in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMP-00096 Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
Cause: An error occurred creating a synonym for a type that is used by the table.
Action: Examine the import log to determine why the type synonym could not be created. If the synonym already existed, but is not needed, then drop the synonym and retry the import. If the synonym is PUBLIC but the importer does not have the CREATE PUBLIC SYNONYM system privilege, then the import must be done by someone possessing that privilege, or the importer must be granted the privilege.
IMP-00097 STREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
Cause: STREAMS_CONFIGURATION=Y can only be used when FULL=Y is present on the command line.
Action: Remove conflicting command arguments.
IMP-00098 INTERNAL ERROR: string
Cause: An INTERNAL error has occurred.
Action: Contact Oracle Support Services.
Thanks
Cheers!!!
Tuesday, October 11, 2011
Optimal Size Of SHMMAX and SHMALL.
Optimal Size Of SHMMAX and SHMALL.
SHMMAX =Physical RAM/2.
SHMALL=SHMMAX /Pagefile_size
Cheers!!!
SHMMAX =Physical RAM/2.
SHMALL=SHMMAX /Pagefile_size
Cheers!!!
Thursday, September 22, 2011
ORA-02069: global_names parameter must be set to TRUE for this operation
ORA-02069: global_names parameter must be set to TRUE for this operation
IF you are using DBLINK,you may get this error.
Check the status of global_names parameter and you can change the value of the parameter.
Alter system set global_names=true scope=both;
You must give global database name of the remote db as datalink name.
Cheers!!!
IF you are using DBLINK,you may get this error.
Check the status of global_names parameter and you can change the value of the parameter.
Alter system set global_names=true scope=both;
You must give global database name of the remote db as datalink name.
Cheers!!!
Friday, September 16, 2011
Private_strands at log switch in alert log
Private_strands at log switch in alert log:
You can see above message in alert log with log switch information.
A "strand" is new terminology for 10g and it deals with latches for redo .
Strands are a mechanism to allow multiple allocation latches for processes to write redo more efficiently in the redo buffer and is related to the log_parallelism parameter present in 9i.
The concept of a strand is to ensure that the redo generation rate for an instance is optimal and that when there is some kind of redo contention then the number of strands is dynamically adjusted to compensate.
The initial allocation for the number of strands depends on the number of CPU’s and is started with 2 strands with one strand for active redo generation.
You Can see more about on metalink.
Cheers!!!
You can see above message in alert log with log switch information.
A "strand" is new terminology for 10g and it deals with latches for redo .
Strands are a mechanism to allow multiple allocation latches for processes to write redo more efficiently in the redo buffer and is related to the log_parallelism parameter present in 9i.
The concept of a strand is to ensure that the redo generation rate for an instance is optimal and that when there is some kind of redo contention then the number of strands is dynamically adjusted to compensate.
The initial allocation for the number of strands depends on the number of CPU’s and is started with 2 strands with one strand for active redo generation.
You Can see more about on metalink.
Cheers!!!
Wednesday, July 20, 2011
Exclude and Include Option in both EXPDP and IMPDP
EXCLUDE and INCLUDE options are really use full in DATAPUMP.
expdp scott/tiger@testdb directory=test dumpfile=isptool_scott.dmp logfile=isptool_scott.log exclude=TABLE:\"='BONUS'\"
impdp scott/tiger@testdb directory=test dumpfile=isptool_scott.dmp logfile=isptool_test_impdp.log include=TABLE:\"='DEPT'\"
Cheers!!!
expdp scott/tiger@testdb directory=test dumpfile=isptool_scott.dmp logfile=isptool_scott.log exclude=TABLE:\"='BONUS'\"
impdp scott/tiger@testdb directory=test dumpfile=isptool_scott.dmp logfile=isptool_test_impdp.log include=TABLE:\"='DEPT'\"
Cheers!!!
Monday, July 11, 2011
ora-12528: TNS:Listener: All Appropriate instances are blocking new connections
ora-12528: TNS:Listener: All Appropriate instances are blocking new connections
Got this Error.
This error means Database instance are not started or Starting.You need to start database server.If your database server is already starting.You have to wait till the database open.
Connect directly to Oracle
command:-
export oracle_sid=testdb
sqlplus sys as sysdba
password:XXXXX
SQL>select status from v$instance;
we can see the current status from Database from above query.
Cheers!!!!
Got this Error.
This error means Database instance are not started or Starting.You need to start database server.If your database server is already starting.You have to wait till the database open.
Connect directly to Oracle
command:-
export oracle_sid=testdb
sqlplus sys as sysdba
password:XXXXX
SQL>select status from v$instance;
we can see the current status from Database from above query.
Cheers!!!!
Wednesday, July 6, 2011
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [0x7C81BD02]
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [0x7C81BD02] [] [] [] []
Current SQL information unavailable - no SGA.
It`s a OS dependent error.You can contact oracle support for more details and patches.
Also
Also check these memory parameters.
1) Increase SGA_MAX_SIZE and SGA_TARGET so that you can accommodate following pools.
2) Restart the instance.
3) Increase INIT.ORA memory parameters and make sure following pools are set to recommended value i.e. 200M.
a) SHARED_POOL_SIZE
b) JAVA_POOL_SIZE
c) STREAMS_POOL_SIZE
Cheers!!!
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [0x7C81BD02] [] [] [] []
Current SQL information unavailable - no SGA.
It`s a OS dependent error.You can contact oracle support for more details and patches.
Also
Also check these memory parameters.
1) Increase SGA_MAX_SIZE and SGA_TARGET so that you can accommodate following pools.
2) Restart the instance.
3) Increase INIT.ORA memory parameters and make sure following pools are set to recommended value i.e. 200M.
a) SHARED_POOL_SIZE
b) JAVA_POOL_SIZE
c) STREAMS_POOL_SIZE
Cheers!!!
ORA-01123: cannot start online backup; media recovery not enabled.
alter tablespace users begin backup;
ORA-01123: cannot start online backup; media recovery not enabled.
Check whether the database in archive log by SYS user
SQL> ARCHIVE LOG LIST;
Database is in non archive mode
We need to change archive mode
SQL>shutdown immediate;
SQL>startup mount;
SQL>alter database archivelog;
SQL>Alter database open;
then you can BEGIN BACKUP command
Cheers!!!
ORA-01123: cannot start online backup; media recovery not enabled.
Check whether the database in archive log by SYS user
SQL> ARCHIVE LOG LIST;
Database is in non archive mode
We need to change archive mode
SQL>shutdown immediate;
SQL>startup mount;
SQL>alter database archivelog;
SQL>Alter database open;
then you can BEGIN BACKUP command
Cheers!!!
Sunday, July 3, 2011
ORA-19809: limit exceeded for recovery files
RMAN-03002: failure of backup plus archivelog command at 07/04/2011 10:58:39
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 1530219520 bytes disk space from 4039114752 limit
Got this error.
You need to increase your flashback recovery area by
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE=4G scope=both;
Also you can delete old backup from recovery area.
Cheers!!!
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 1530219520 bytes disk space from 4039114752 limit
Got this error.
You need to increase your flashback recovery area by
SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE=4G scope=both;
Also you can delete old backup from recovery area.
Cheers!!!
Friday, July 1, 2011
KILL UNNECESSARY SESSION
You want to kill unnecessary session in oracle.
check this
SQL> ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;
You will get sid,serial# from v$session view.
Cheers!!!
check this
SQL> ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;
You will get sid,serial# from v$session view.
Cheers!!!
ora-12638 credential retrieval failed
ora-12638 credential retrieval failed
got this error?
sometimes you will get that error from oracle client
at that time you need to change SQLNET AUTHENTICATION service on SQLNET.ORA file
SQLNET.AUTHENTICATION_SERVICES = (NTS)
TO
SQLNET.AUTHENTICATION_SERVICES = (NONE)
Cheers!!!
got this error?
sometimes you will get that error from oracle client
at that time you need to change SQLNET AUTHENTICATION service on SQLNET.ORA file
SQLNET.AUTHENTICATION_SERVICES = (NTS)
TO
SQLNET.AUTHENTICATION_SERVICES = (NONE)
Cheers!!!
Tuesday, June 28, 2011
INDEX creation on versioned tables.
In the below example table name is "TEST"
EXEC DBMS_WM.enableVersioning('TEST');
exec dbms_wm.beginddl('TEST');
create index index_name on test_lts(ID);
you can drop index on same condition.
drop index index_name;
exec dbms_wm.commitddl('TEST');
Cheers!!!
EXEC DBMS_WM.enableVersioning('TEST');
exec dbms_wm.beginddl('TEST');
create index index_name on test_lts(ID);
you can drop index on same condition.
drop index index_name;
exec dbms_wm.commitddl('TEST');
Cheers!!!
Tuesday, June 21, 2011
ORACLE WORKSPACE INTEGRATION-IMPORTANT DBMS PACKAGES
ORACLE WORKSPACE INTEGRATION
We can create a workspace simply
SQL>exec dbms_wm.createworkspace('WORKSPACE_NAME');
grant workspace privileges to a particular user:
SQL>exec dbms_wm.grantworkspacepriv('ACCESS_WORKSPACE','WORKSPACE_NAME','username');
We can find out current workspaces associated with users
wmsys.wm$workspace_sessions_view
We can resolve conflit of a particular workspace
SQL>exec dbms_wm.SetConflictWorkspace('WORKSPACE_NAME');
After that conflit we need to commit
by
SQL>exec dbms_wm.commitresolve('WORKSPACE_NAME');
We can find out Current workspace
SQL>SELECT DBMS_WM.getworkspace FROM DUAL;
We can connect to a particular workspace
SQL>EXEC dbms_wm.gotoworkspace('WORKSPACE_NAME');
We can merge that particular workspace to parent
SQL>EXEC dbms_wm.mergeworkspace('WORKSPACE_NAME');
We can freeze a workspace to disallow changes to rows in the version-enabled tables
SQL>dbms_wm.freezeworkspace('WORKSPACE_NAME');
reverse this process
by
SQL>exec dbms_wm.unfreezeworkspace('WORKSPACE_NAME');
we can refresh workspace..if we have any conflint,we can find out after refreshing workspace:
SQL> exec dbms_wm.refreshworkspace(' WORKSPACE_NAME');
We can remove a workspace
by
SQL> exec dbms_wm.removeworkspace(' WORKSPACE_NAME');
We can create a workspace simply
SQL>exec dbms_wm.createworkspace('WORKSPACE_NAME');
grant workspace privileges to a particular user:
SQL>exec dbms_wm.grantworkspacepriv('ACCESS_WORKSPACE','WORKSPACE_NAME','username');
We can find out current workspaces associated with users
wmsys.wm$workspace_sessions_view
We can resolve conflit of a particular workspace
SQL>exec dbms_wm.SetConflictWorkspace('WORKSPACE_NAME');
After that conflit we need to commit
by
SQL>exec dbms_wm.commitresolve('WORKSPACE_NAME');
We can find out Current workspace
SQL>SELECT DBMS_WM.getworkspace FROM DUAL;
We can connect to a particular workspace
SQL>EXEC dbms_wm.gotoworkspace('WORKSPACE_NAME');
We can merge that particular workspace to parent
SQL>EXEC dbms_wm.mergeworkspace('WORKSPACE_NAME');
We can freeze a workspace to disallow changes to rows in the version-enabled tables
SQL>dbms_wm.freezeworkspace('WORKSPACE_NAME');
reverse this process
by
SQL>exec dbms_wm.unfreezeworkspace('WORKSPACE_NAME');
we can refresh workspace..if we have any conflint,we can find out after refreshing workspace:
SQL> exec dbms_wm.refreshworkspace(' WORKSPACE_NAME');
We can remove a workspace
by
SQL> exec dbms_wm.removeworkspace(' WORKSPACE_NAME');
Sunday, June 19, 2011
enable_ddl_logging in oracle 11g
enables or disables the writing of DDL statements to the alert log
alter system set enable_ddl_logging=true scope=both;
alter system set enable_ddl_logging=true scope=both;
Enable version & Disable Version
Enable version:
Table name is test
EXEC DBMS_WM.EnableVersioning('TEST');
Disable version:
EXEC DBMS_WM.DisableVersioning('TEST');
We can see versioned tables from
WM$VERSIONED_TABLES in WMSYS user.
We can see version errors in WM$VT_ERRORS_TABLE in WMSYS user.
Table name is test
EXEC DBMS_WM.EnableVersioning('TEST');
Disable version:
EXEC DBMS_WM.DisableVersioning('TEST');
We can see versioned tables from
WM$VERSIONED_TABLES in WMSYS user.
We can see version errors in WM$VT_ERRORS_TABLE in WMSYS user.
Saturday, June 18, 2011
DB LINK CREATION.
Creating database link is an easy task.
create public database link link_name
connect to
username
identified by
password
using 'service_name';
DB LINK VIEWS:
DBA_DB_LINKS
ALL_DB_LINKS
USER_DB_LINKS
create public database link link_name
connect to
username
identified by
password
using 'service_name';
DB LINK VIEWS:
DBA_DB_LINKS
ALL_DB_LINKS
USER_DB_LINKS
Thursday, June 16, 2011
Creating spatial index.
First of all , We need to insert a value in MDSYS.USER_SDO_GEOM_METADATA
Creating spatial index syntax.
CREATE INDEX ADDRESSES_SIDX ON ADDRESS
(OGC_GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS('layer_gtype=point')
NOPARALLEL;
give gtype as your spatial value
In the above example gtype is point.Means 2001 in table.
Creating spatial index syntax.
CREATE INDEX ADDRESSES_SIDX ON ADDRESS
(OGC_GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS('layer_gtype=point')
NOPARALLEL;
give gtype as your spatial value
In the above example gtype is point.Means 2001 in table.
Tuesday, June 7, 2011
Installaing ORACLE 11G R2 in Centos 5 (Minimum requirement)
*****************************
Pre-Instalation Tasks
1. Create oracle User Account
Login as root and create te user oracle which belongs to dba group.
su -
# groupadd dba
# useradd -g dba oracle
# passwd oracle - give password
2. Setting System parameters -for 4+ GB RAM
********************************************
Edit the /etc/sysctl.conf and add following lines:
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 6553600
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
fs.aio-max-nr = 1048576
2. Setting System parameters -for 2 GB RAM
********************************************
kernel.shmall = 2097152
kernel.shmmax = 1258291200
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 8388608
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max =4194304
net.core.wmem_default = 262144
net.core.wmem_max = 2097152
fs.aio-max-nr = 1048576
Note: You need reboot system or execute "sysctl -p" command to apply above settings.
For RedHat (OEL, Centos) 5 version: Edit the /etc/pam.d/login file and add following line:
session required pam_limits.so
Edit the /etc/security/limits.conf file and add following lines:
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
3. Creating oracle directories
# mkdir /opt/oracle
# mkdir /opt/oracle/db_1
# chown -R oracle:dba /opt/oracle
Must Log in as oracle user
*************************
4. Setting Oracle Enviroment
Edit the /home/oracle/.bash_profile file and add following lines:
ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/db_1
ORACLE_SID=ORCL
LD_LIBRARY_PATH=$ORACLE_HOME/lib
PATH=$PATH:$ORACLE_HOME/bin
export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH PATH
Save the .bash_profile and execute following commands for load new enviroment:
cd /home/oracle
. .bash_profile
1. Download and install required .rpm packages
Login as Root user in terminal
******************************
Some additional packages are required for succesful instalation of Oracle software. To check wheter required packages are installed on your operating system use following command:
rpm -q binutils elfutils elfutils-libelf gcc gcc-c++ glibc glibc-common glibc-devel compat-libstdc++-33 cpp make compat-db sysstat libaio libaio-devel unixODBC unixODBC-devel|sort
We get the list of not installed packages
*****************************************
package compat-db is not installed
package compat-libstdc++-33 is not installed
package elfutils is not installed
package gcc-c++ is not installed
package gcc is not installed
package glibc-devel is not installed
package libaio-devel is not installed
package sysstat is not installed
package unixODBC-devel is not installed
package unixODBC is not installed
Give the following command to install each of them
# yum install compat-db
# yum install elfutils
giving permission to oracle installation folder and the home folder at time of installation.
# chmod -R 777 /opt/oracle11g/
# chmod -R 777 /opt/
Logout and Login in GUI as Oracle User
*************************************
Go to the Instalation setup file path and execute the following command
./runInstaller
Post-Instalation Tasks
1. (Optional) Auto Startup and Shutdown of Database and Listener
Login as root and modify /etc/oratab file and change last character to Y for apropriate database.
ORCL:/opt/oracle/db_1:Y
As root user create new file "oracle" (init script for startup and shutdown the database) in /etc/init.d/ directory with following content:
#!/bin/bash
#
# oracle Init file for starting and stopping
# Oracle Database. Script is valid for 10g and 11g versions.
#
# chkconfig: 35 80 30
# description: Oracle Database startup script
# Source function library.
. /etc/rc.d/init.d/functions
ORACLE_OWNER="oracle"
ORACLE_HOME="/opt/oracle/db_1"
case "$1" in
start)
echo -n $"Starting Oracle DB:"
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbstart $ORACLE_HOME"
echo "OK"
;;
stop)
echo -n $"Stopping Oracle DB:"
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbshut $ORACLE_HOME"
echo "OK"
;;
*)
echo $"Usage: $0 {start|stop}"
esac
Execute (as root) following commands (First script change the permissions, second script is configuring execution for specific runlevels):
chmod 750 /etc/init.d/oracle
chkconfig --add oracle --level 0356
Pre-Instalation Tasks
1. Create oracle User Account
Login as root and create te user oracle which belongs to dba group.
su -
# groupadd dba
# useradd -g dba oracle
# passwd oracle - give password
2. Setting System parameters -for 4+ GB RAM
********************************************
Edit the /etc/sysctl.conf and add following lines:
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 6553600
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
fs.aio-max-nr = 1048576
2. Setting System parameters -for 2 GB RAM
********************************************
kernel.shmall = 2097152
kernel.shmmax = 1258291200
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 8388608
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max =4194304
net.core.wmem_default = 262144
net.core.wmem_max = 2097152
fs.aio-max-nr = 1048576
Note: You need reboot system or execute "sysctl -p" command to apply above settings.
For RedHat (OEL, Centos) 5 version: Edit the /etc/pam.d/login file and add following line:
session required pam_limits.so
Edit the /etc/security/limits.conf file and add following lines:
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
3. Creating oracle directories
# mkdir /opt/oracle
# mkdir /opt/oracle/db_1
# chown -R oracle:dba /opt/oracle
Must Log in as oracle user
*************************
4. Setting Oracle Enviroment
Edit the /home/oracle/.bash_profile file and add following lines:
ORACLE_BASE=/opt/oracle
ORACLE_HOME=$ORACLE_BASE/db_1
ORACLE_SID=ORCL
LD_LIBRARY_PATH=$ORACLE_HOME/lib
PATH=$PATH:$ORACLE_HOME/bin
export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH PATH
Save the .bash_profile and execute following commands for load new enviroment:
cd /home/oracle
. .bash_profile
1. Download and install required .rpm packages
Login as Root user in terminal
******************************
Some additional packages are required for succesful instalation of Oracle software. To check wheter required packages are installed on your operating system use following command:
rpm -q binutils elfutils elfutils-libelf gcc gcc-c++ glibc glibc-common glibc-devel compat-libstdc++-33 cpp make compat-db sysstat libaio libaio-devel unixODBC unixODBC-devel|sort
We get the list of not installed packages
*****************************************
package compat-db is not installed
package compat-libstdc++-33 is not installed
package elfutils is not installed
package gcc-c++ is not installed
package gcc is not installed
package glibc-devel is not installed
package libaio-devel is not installed
package sysstat is not installed
package unixODBC-devel is not installed
package unixODBC is not installed
Give the following command to install each of them
# yum install compat-db
# yum install elfutils
giving permission to oracle installation folder and the home folder at time of installation.
# chmod -R 777 /opt/oracle11g/
# chmod -R 777 /opt/
Logout and Login in GUI as Oracle User
*************************************
Go to the Instalation setup file path and execute the following command
./runInstaller
Post-Instalation Tasks
1. (Optional) Auto Startup and Shutdown of Database and Listener
Login as root and modify /etc/oratab file and change last character to Y for apropriate database.
ORCL:/opt/oracle/db_1:Y
As root user create new file "oracle" (init script for startup and shutdown the database) in /etc/init.d/ directory with following content:
#!/bin/bash
#
# oracle Init file for starting and stopping
# Oracle Database. Script is valid for 10g and 11g versions.
#
# chkconfig: 35 80 30
# description: Oracle Database startup script
# Source function library.
. /etc/rc.d/init.d/functions
ORACLE_OWNER="oracle"
ORACLE_HOME="/opt/oracle/db_1"
case "$1" in
start)
echo -n $"Starting Oracle DB:"
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbstart $ORACLE_HOME"
echo "OK"
;;
stop)
echo -n $"Stopping Oracle DB:"
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbshut $ORACLE_HOME"
echo "OK"
;;
*)
echo $"Usage: $0 {start|stop}"
esac
Execute (as root) following commands (First script change the permissions, second script is configuring execution for specific runlevels):
chmod 750 /etc/init.d/oracle
chkconfig --add oracle --level 0356
Monday, June 6, 2011
ORA-12520: TNS:listener could not find available handler for requested type of server
Got this error.
Try to connect your database server directly.Definitely you will get this error.
Enter user-name: sys as sysdba
Enter password:
ERROR:
ORA-00020: maximum number of processes (250) exceeded
you need to down your listener
Try to login directly using sqlplus
If that not possible
Then ... shutdown your db service
After that increase your number of processes
by
SQL>ALTER SYSTEM SET PROCESSES=350 SCOPE=SPFILE;
you must shutdown after this commands for changing this parameter.
Try to connect your database server directly.Definitely you will get this error.
Enter user-name: sys as sysdba
Enter password:
ERROR:
ORA-00020: maximum number of processes (250) exceeded
you need to down your listener
Try to login directly using sqlplus
If that not possible
Then ... shutdown your db service
After that increase your number of processes
by
SQL>ALTER SYSTEM SET PROCESSES=350 SCOPE=SPFILE;
you must shutdown after this commands for changing this parameter.
Wednesday, June 1, 2011
kewastUnPackStats(): bad magic 1 (0x2b2b8f4652ad, 0)
Found the error in rdbms alert log...?
It generates thousands of lines per day which will expand the alert log size.
We can override this error by
ALTER SYSTEM SET control_management_pack_access='NONE' SCOPE=MEMORY;
Otherwise we can download new patches from Metalink.
Cheers...!!!
It generates thousands of lines per day which will expand the alert log size.
We can override this error by
ALTER SYSTEM SET control_management_pack_access='NONE' SCOPE=MEMORY;
Otherwise we can download new patches from Metalink.
Cheers...!!!
Friday, May 27, 2011
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00119: invalid specification for system parameter LOCAL_LISTENER
ORA-00132: syntax error or unresolved network name 'LISTENER_ORA11G'
you need to check your tnsnames.ora file.In this above example.You can see "LISTENER_ORA11G" that is actually a service name from tnsnames.ora file.Check that service name configuration in tnsnames.ora.
Cheers.!!!
ORA-00132: syntax error or unresolved network name 'LISTENER_ORA11G'
you need to check your tnsnames.ora file.In this above example.You can see "LISTENER_ORA11G" that is actually a service name from tnsnames.ora file.Check that service name configuration in tnsnames.ora.
Cheers.!!!
Friday, May 20, 2011
ORA-00845: MEMORY_TARGET not supported on this system
Got this error...?
This type of error depends on your server memory allocated to your database.You need to change your memory_target.
Alter system set memory_target= 2000M scope=both;
cheers!!!
This type of error depends on your server memory allocated to your database.You need to change your memory_target.
Alter system set memory_target= 2000M scope=both;
cheers!!!
Monday, May 9, 2011
The OracleDBConsolev8it3 service terminated with service-specific error 1 (0x1).
Got this error?
The OracleDBConsolev8it3 service terminated with service-specific error 1 (0x1).
emca -config dbcontrol db
SEVERE: Failed to unlock all EM-related accounts
Could not complete the configuration. Refer to the log file for more details
It`s a common error. you need to drop dbconsole first.after that you can recreate the same
1)DROP DBCONSOLE first
emca -deconfig dbcontrol db -repos drop
then
2)CREATE NEW REPOSITORY
emca -repos create
emca -config dbcontrol db
It will take sometime to create new repository.Also you can see the path of EM at end of the execution.
Restart EM Console
emctl stop dbconsole db
emctl start dbconsole db
Cheers!!!
The OracleDBConsolev8it3 service terminated with service-specific error 1 (0x1).
emca -config dbcontrol db
SEVERE: Failed to unlock all EM-related accounts
Could not complete the configuration. Refer to the log file for more details
It`s a common error. you need to drop dbconsole first.after that you can recreate the same
1)DROP DBCONSOLE first
emca -deconfig dbcontrol db -repos drop
then
2)CREATE NEW REPOSITORY
emca -repos create
emca -config dbcontrol db
It will take sometime to create new repository.Also you can see the path of EM at end of the execution.
Restart EM Console
emctl stop dbconsole db
emctl start dbconsole db
Cheers!!!
Thursday, April 21, 2011
Unable to open Log File-EXPDP & IMPDP error
ORA-39002
ORA-39070
ORA-29283
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283
Check out expdp with default directory.If this ok.Then check out drive security.There is no SYSTEM user in SECURITY Tab.Add system user to SECURITY.Then try.
Cheers!!!
ORA-39070
ORA-29283
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283
Check out expdp with default directory.If this ok.Then check out drive security.There is no SYSTEM user in SECURITY Tab.Add system user to SECURITY.Then try.
Cheers!!!
Tuesday, April 5, 2011
ORA-01000 maximum open cursors exceeded
Cause: A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
ALTER SYSTEM SET open_cursors = 400 SCOPE=BOTH;
Try to find out application to see why cursors are staying open.
Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
ALTER SYSTEM SET open_cursors = 400 SCOPE=BOTH;
Try to find out application to see why cursors are staying open.
Subscribe to:
Posts (Atom)