织梦CMS - 轻松建站从此开始!

文档之家-IT技术文档共享平台

当前位置: 文档之家 > 数据库 > Oracle >

Oracle 10g errors message troubleshooting 198

时间:2011-04-17 12:46来源:Oracle 作者:admin 点击:
ORA-32593: database supplemental logging attributes in flux Cause: there is another process actively modifying the database wide supplemental logging attributes. Action: Retry the DDL or the LogMiner dictionary build that raised this erro

 

ORA-32401: materialized view log on "string"."string" does not have new values
Cause: Materialized view log on the indicated table does not have new values information.
Action: Add new values to materialized view log using the ALTER MATERIALIZED VIEW LOG command.
ORA-32403: cannot use new values from mv log on "string"."string"
Cause: The materialized view log either does not have new values logged, or the timestamp associated with the new values columns is more recent than the last refresh time.
Action: Perform a complete refresh is required before the next fast refresh.
ORA-32404: snapshot log uses Change Data Capture which is not enabled for this database
Cause: A snapshot log that utilizes Change Data Capture is being imported to a database where Change Data Capture has not been enabled.
Action: First enable Change Data Capture on the database then retry the import.
ORA-32405: cannot alter tablespace for existing materialized view log
Cause: The tablespace specification for the existing materialized view log cannot be altered or changed.
Action: remove the tablespace clause from the statement.
ORA-32406: cannot alter partitioning for existing materialized view log
Cause: The partitioning specification for the existing materialized view log cannot be altered or changed.
Action: remove the partitioning clause from the statement.
ORA-32407: cannot exclude new values when materialized view log includes new values
Cause: The excluding new values specification for the existing materialized view log cannot be accepted when including new values is the current option.
Action: change excluding new values clause.
ORA-32408: materialized view log on "string"."string" already has new values
Cause: The materialized view log on the indicated table already has new values.
Action: No action required.
ORA-32409: materialized view log on "string"."string" already excludes new values
Cause: The materialized view log on the indicated table already excludes new values.
Action: No action required.
ORA-32500: Dirname 'string' cannot exceed 'number' characters
Cause: Path name too long
Action: Use shorter pathname than maximum specified for dirname.
ORA-32501: Writing SGA to file failed
Cause: Underlying OSDs encountered an error
Action: Check additional information. slercerrno contains errno.
ORA-32502: Cannot execute command. Flash Freeze is not in effect
Cause: This command can only be issued after a flash freeze
Action: Refer to instructions for flash freeze and Oracle diagnostics.
ORA-32503: Mapping SGA from file failed
Cause: Underlying OSDs encountered an error
Action: Check additional information. slercerrno contains errno.
ORA-32504: expecting one of stringstringstring, or string but found string
Cause: illegal value specified for create watchpoint mode
Action: specify one of the expected modes
ORA-32505: too many watchpoints
Cause: too many watchpoints created
Action: increase appropriate initialization parameters
ORA-32506: expecting one of stringstring, or string but found string
Cause: invalid arguments provided
Action: provide one of the expected arguments
ORA-32507: expecting string but found string
Cause: invalid arguments to command
Action: provide one of the expected arguments
ORA-32508: no such watchpoint id
Cause: invalid watchpoint id
Action: use oradebug show to list valid watchpoint ids
ORA-32509: watchpoint was already deleted
Cause: trying to delete an already deleted watchpoint
Action: use oradebug show to list valid watchpoint ids
ORA-32510: cannot create watchpoint on unreadable memory
Cause: trying to create watchpoint on invalid address
Action: provide a different valid address
ORA-32511: cannot create watchpoint in memory needed by watchpointing code
Cause: overlap exists between requested memory range to watch and internal memory structures that watchpointing operations need
Action: provide a different address range
ORA-32550: Replacement occured despite hint to the contrary
Cause: This should never be signalled; it's internal.
Action: Report to Oracle support.
ORA-32575: Explicit column default is not supported for modifying views
Cause: Default keyword was used to modify views.
Action: Use implicit default - omitting column-value pair.
ORA-32576: missing TYPE keyword
Cause: keyword TYPE is missing.
Action: Use TYPE keyword.
ORA-32577: username must be SYS or SYSTEM
Cause: A user name of SYS or SYSTEM was not specified when providing a password in the CREATE DATABASE statement.
Action: Only passwords for the SYS and SYSTEM users can be provided in the CREATE DATABASE statement. Re-issue the statement with passwords for users SYS or SYSTEM.
ORA-32578: password for SYS already specified
Cause: A password for the SYS user was specified twice in the CREATE DATABASE statement.
Action: Re-issue the CREATE DATABASE statement with only one password for the SYS user.
ORA-32579: password for SYSTEM already specified
Cause: A password for the SYSTEM user was specified twice in the CREATE DATABASE statement.
Action: Re-issue the CREATE DATABASE statement with only one password for the SYSTEM user.
ORA-32580: both SYS and SYSTEM passwords must be provided
Cause: Passwords for both the SYS and SYSTEM users were not provided in the CREATE DATABASE statement. If one of the passwords was provided, then both should be provided.
Action: Re-issue the CREATE DATABASE statement with a password for both the SYS and SYSTEM users.
ORA-32581: missing or invalid password
Cause: An incorrect password was provided for the SYS or SYSTEM user in the CREATE DATABASE statement.
Action: Re-issue the CREATE DATABASE statement with a valid password.
ORA-32582: table function with left correlation to a table cannot also be left outer-joined to the table
Cause: A table function T2 contains a reference to a table T1. T2 is also left outer-joined to T1. This is not allowed.
Action: Remove the reference to T1 from T2 or remove the left outer-join specification (+).
ORA-32583: query passed to table function has wrong number of elements in select list
Cause: The query used as an input to a table function which takes a a ref cursor as argument has wrong number of elements in the select list which does not correspond to the elements in ref cursor. The ref cursor mentioned here refers to the one referenced in order by parition clauses. This is not allowed.
Action: Make sure that the select list of the query matches the ref cursor columns as defined in the function.
ORA-32584: missing LOG keyword
Cause: keyword LOG is missing.
Action: Use LOG keyword.
ORA-32585: duplicate specification of a supplemental log attribute
Cause: In a create/alter DDL a supplemental log attribute is specified more than once.
Action: Rewrite the Create/Alter DDL such that it has a single occurence of any supplemental log attribute.
ORA-32586: multiple specification of a supplemental logging attribute
Cause: The primary key, unique index, foreign key or all column supplemental logging attribute can be specified at most once in a create/alter ddl.
Action: Rewrite the Create/Alter DDL with single occurence of the offending supplemental logging attribute.
ORA-32587: Cannot drop nonexistent string supplemental logging
Cause: specified supplemental log attribute does not exist.
Action: None
ORA-32588: supplemental logging attribute string exists
Cause: specified supplemental logging attribute exits.
Action: retry the alter/create ddl after removing this supplemental logging attribute.
ORA-32589: unable to drop minimal supplemental logging
Cause: Minimal supplemental logging could not be dropped as one of primary key, foreign key, unique or all column supplemental logging is enabled at the database level.
Action: Use V$DATABASE to determine the databasewide supplemental logging directives. Minimal supplemental logging could be dropped if and only if no other databasewide supplemental logging directives are enabled.
ORA-32590: log group specification not allowed here
Cause: Supplemental log specification is not allowed in the statement.
Action: Remove the supplemental log specification from the statement.
ORA-32591: connect string too long
Cause: The connect string specified for the database link was more than 2000 characters.
Action: Specify a connect string less than 2000 chracters.
ORA-32592: all columns in log group can not be no log columns
Cause: A supplemental log group must have at least one column of scalar type that is not marked as no log.
Action: Redefine the supplemental log group with at least one column of scalar type that is not marked as no log.
ORA-32593: database supplemental logging attributes in flux
Cause: there is another process actively modifying the database wide supplemental logging attributes.
Action: Retry the DDL or the LogMiner dictionary build that raised this error.
ORA-32600: RETENTION and PCTVERSION cannot be used together
Cause: cannot use both RETENTION and PCTVERSION together.
Action: Use either RETENTION or PCTVERSION.
(责任编辑:eric)
织梦二维码生成器
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
发表评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 验证码:点击我更换图片
栏目列表
推荐内容