ORA-28221 REPLACE not specified
Cause: User is changing password but password verification function is turned on, the original password is not specified, and the user does not have the alter user system privilege.
Action: Supply the original password.
ORA-28231 no data passed to obfuscation toolkit
Cause: A NULL value was passed to a function or procedure.
Action: Make sure that the data passed is not empty.
ORA-28232 invalid input length for obfuscation toolkit
Cause: Length of data submitted for encryption or decryption is not a multiple of 8 bytes.
Action: Make sure that the length of the data to be encrypted or decrypted is a multiple of 8 bytes.
ORA-28233 double encryption not supported
Cause: The obfuscation toolkit does not support the encryption of already-encrypted data.
Action: Do not attempt to encrypt already-encrypted data.
ORA-28234 key length too short
Cause: The key specified is too short for the algorithm. DES requires a key of at least 8 bytes. Triple DES requires a key of at least 16 bytes in two-key mode and 24 bytes in three-key mode.
Action: Specify a longer key.
ORA-28235 algorithm not available
Cause: The desired encryption algorithm is not available.
Action: Run the installer to install the needed algorithm in Oracle Advanced Security.
ORA-28236 invalid Triple DES mode
Cause: An unknown value was specified for the mode in which triple DES encryption is to run.
Action: Specify a valid value. See the package declaration for a list of valid values.
ORA-28237 seed length too short
Cause: The seed specified for the key generation routine must be at least 80 characters.
Action: Specify a longer seed.
ORA-28238 no seed provided
Cause: A NULL value was passed in as the seed to be used in generating a key.
Action: Provide a non-NULL value for the seed.
ORA-28239 no key provided
Cause: A NULL value was passed in as an encryption or decryption key.
Action: Provide a non-NULL value for the key.
ORA-28261 CURRENT_USER can not be used in PLSQL Definer's Right procedure.
Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL interface.
Action: Use a SQL statement to query CURRENT_USER inside a DR procedure.
ORA-28262 global_context_pool_size has invalid value.
Cause: Initialization parameter GLOBAL_CONTEXT_POOL_SIZE has a value less than the minimum required value (10K).
Action: Specify a value for the initialization parameter GLOBAL_CONTEXT_POOL_SIZE that is atleast 10k.
ORA-28263 Insufficient memory in global context pool
Cause: Allocations for the global context heap exceeded the value set in the initialization parameter file.
Action: Increase the value of the GLOBAL_CONTEXT_POOL_SIZE initialization parameter or clear unused global context.
ORA-28264 Client identifier is too long
Cause: The length of the client identifier is longer than 64.
Action: Set a client identifier whose length is less than 64.
ORA-28265 NameSpace beginning with 'sys_' is not allowed
Cause: Namespace beginning with 'sys_' is not allowed.
Action: Use a namespace that does not begin with 'sys_'.
ORA-28270 Malformed user nickname for password authenticated global user
Cause: An attempt to login as password-auuthenticated global user with a malformed user nickname.
Action: Make sure the nickname is valid and re-login.
ORA-28271 No permission to read user entry in LDAP directory service
Cause: ORACLE server does not have read permission on user nickname's X.500 user entry.
Action: Make sure ORACLE server is using the correct SSL credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are correct.
ORA-28272 Domain policy restricts password based GLOBAL user authentication
Cause: Domain policy does not allow password-authenticated GLOBAL users.
Action: Make sure ORACLE server is using the correct SSL credentials to connect to LDAP directory services. Make sure orclDBAuthTypes attributes within Oracle enterprise domain object is either set to PWD or ALL.
ORA-28273 No mapping for user nickname to LDAP distinguished name exists
Cause: ORACLE server cannot map the given user nickname to LDAP distinguished name.
Action: Make sure user entries in LDAP are correctly provisioned with correct user nickname attribute values.
ORA-28274 No ORACLE password attribute corresponding to user nickname exists
Cause: LDAP user entry corresponding to user nickname does not have a ORACLE password attribute or the attribute is not initialized.
Action: Make sure user entries in LDAP are correctly provisioned with correct ORACLE password attribute values.
ORA-28275 Multiple mappings for user nickname to LDAP distinguished name exist
Cause: The given user nickname maps to more than one LDAP distinguished name.
Action: Make sure user nickname is unique within the enterprise.
ORA-28276 Invalid ORACLE password attribute
Cause: The ORACLE password attribute of a user entry has an invalid format.
Action: Make sure ORACLE password attribute value is RFC-2307 compliant.
ORA-28277 LDAP search, while authenticating global user with passwords, failed
Cause: The LDAP search for finding the appropriate user entry and ORACLE password failed.
Action: Make sure LDAP directory service is up and running.
ORA-28278 No domain policy registered for password based GLOBAL users
Cause: No policy about password authenticated GLOBAL users has been registered.
Action: Add attribute orclDBAuthTypes to the database server's Enterprise domain.
ORA-28279 Error reading rdbms_server_dn parameter in INIT.ORA
Cause: The initialization parameter RDBMS_SERVER_DN is not specified corrrectly (cannot be normalized).
Action: Make sure the RDBMS_SERVER_DN initialization parameter is set to a correct value.
ORA-28280 Multiple entries for ORACLE database password exist.
Cause: The ORACLE password attribute of a user entry has multiple entries of ORACLE database password.
Action: Make sure ORACLE password attribute has one entry for ORACLE Database password.
ORA-28500 connection from ORACLE to a non-Oracle system returned this message:
Cause: The cause is explained in the forwarded message.
Action: See the non-Oracle system's documentation of the forwarded message.
ORA-28501 communication error on heterogeneous database link
Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system.
Action: See the documentation for the non-Oracle system for an explanation of the second error message.
ORA-28502 internal communication error on heterogeneous database link
Cause: A communication error internal to Oracle's heterogeneous services has occurred.
Action: Contact Oracle Support Services.
ORA-28503 bind value cannot be translated into SQL text for non-Oracle system
Cause: A SQL statement used bind variables on a Heterogeneous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables.
Action: Change your SQL statement so that it does not use bind variables.
ORA-28504 ROWID not found in ROWID cache for heterogeneous database link
Cause: The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache.
Action: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the HS_ROWID_CACHE_SIZE Heterogenious Services initialization parameter.
ORA-28505 cannot get non-Oracle system capabilities from string
Cause: Oracle was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views.
Action: Contact the database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.
ORA-28506 parse error in data dictionary translation for string stored in string
Cause: A reference to an Oracle data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The Oracle data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation.
Action: Contact customer support of the agent vendor.
ORA-28507 error in data dictionary view string
Cause: The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect.
Action: Verify correct installation of the following Heterogeneous Services' initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. If these views are not available, make sure you ran the script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory.
ORA-28508 invalid value string for Heterogeneous Services initialization parameter string
Cause: The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system.
Action: Check the Heterogeneous Services and agent documentation to determine acceptable values.
ORA-28509 unable to establish a connection to non-Oracle system
Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system.
Action: Check the Net8 service name definition in the following places:
the USING clause of the CREATE DATABASE LINK statement
the TNSNAMES.ORA file
the Oracle Names Server
The following are possible reasons for name mismatches:
The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in the TNSNAMES.ORA file or in the Oracle Names Server.
The protocol-specific information in the service name definition must match the protocol-specific definition of the responding listener.
The SID=name in the service name definition (in the TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener.
ORA-28510 heterogeneous database link initialization failed
Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system.
Action: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly.
ORA-28511 lost RPC connection to heterogeneous remote agent using SID=string
Cause: A fatal error occurred in one of the following places:
the connection between the Oracle server and the agent
the heterogeneous services remote agent itself
the connection to the non-Oracle system
This error occurred after communication had been established successfully.
Action: Check for network problems and remote host crashes. The problem is probably in the agent software. If so, contact customer support of the agent vendor.
ORA-28512 cannot get data dictionary translations from string
Cause: Oracle was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views.
Action: Ask your database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.
ORA-28513 internal error in heterogeneous remote agent
Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link.
Action: Make a note of how the error was produced and contact customer support of the agent vendor.
ORA-28514 heterogeneous database link initialization could not convert system date
Cause: The system date was not retrievable.
Action: Verify that the Oracle server's host machine and operating system are operational. This error should not occur unless low level system functions are failing.
ORA-28515 cannot get external object definitions from string
Cause: Oracle was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed.
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory.
ORA-28518 data dictionary translation has illegal translation type
Cause: A data dictionary translation definition, either in the Oracle server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are 'T' or 't' for 'translate', 'M' or 'm' for 'mimic'. Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the Oracle instance and to the Oracle instance's alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an Oracle server on the first connection from the server to the agent.
Action: Contact the customer support of the agent vendor.
ORA-28519 no heterogeneous data dictionary translations available
Cause: The Oracle server's data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
Action: Ask a database administrator to resolve this problem. The easiest solution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor.
ORA-28520 error initializing heterogeneous data dictionary translations
Cause: Oracle was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor.
ORA-28521 no heterogeneous capability information available
Cause: The Oracle server's data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
Action: Ask a database administrator to resolve this problem. The easiest resolution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor.
ORA-28522 error initializing heterogeneous capabilities
Cause: Oracle was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor.
ORA-28523 ORACLE and heterogeneous agent are incompatible versions
Cause: An operation on a database link attempted to connect to a non-Oracle system, but the Oracle instance and the agent process for the non-Oracle system are incompatible.
Action: Ask your database administrator to confirm configuration of both the Oracle instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the Oracle instance and the agent, and in the Oracle instance's alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported.
ORA-28525 unable to create Heterogeneous Services error message text
Cause: Incorrect arguments were passed into the error message creation routine.
Action: Contact Oracle Support Services.
ORA-28526 invalid describe information returned to Heterogeneous Services
Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent.
Action: Contact customer support of the agent vendor.
ORA-28527 Heterogeneous Services datatype mapping error
Cause: Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the Oracle server's data dictionary.
Action: Verify that the Oracle server's data dictionary has been initialized with correct capability definitions for the connected FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, a database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. If the error persists contact customer support of the agent vendor.
ORA-28528 Heterogeneous Services datatype conversion error
Cause: Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for the conversion failure:
overflow problems (in the case of numbers)
length limitations (in the case of character strings)
invalid values passed into the conversion routines
Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it may not be possible to convert the value.
ORA-28529 invalid or missing parameter in Net8 service name definition
Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server.
Action: Ask your database administrator to make sure the information in the Net8 service definition is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent's documentation.
ORA-28530 Heterogeneous Services initialization error in NLS language ID
Cause: Heterogeneous Services was unable to initialize an NLS language ID. Both the Oracle server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs.
Action: Contact Oracle Support Services.
ORA-28533 Heterogeneous Services coercion handling error
Cause: The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions.
Action: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed.
ORA-28534 Heterogeneous Services preprocessing error
Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled.
Action: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed.
ORA-28535 invalid Heterogeneous Services context
Cause: A Heterogeneous Services agent's driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver.
Action: Contact customer support of the agent vendor.
ORA-28536 error in processing Heterogeneous Services initialization parameters
Cause: An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the Oracle server data dictionary.
Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and HS_ALL_INITS. Look for conditions which could produce the error identified in the error message immediately following this one.
ORA-28538 result set not found
Cause: The client program tried fetching from a result set that is no longer open. Many gateways will, on execution of a stored procedure, automatically close all result sets that were returned by any previously executed stored procedure.
Action: Check the documentation for the gateway that you are using and see if it will automatically close currently open result sets each time a stored procedure is executed. Then check if your client program is violating this rule. If it is, fix your program. If it is not, contact Oracle Support Services.
ORA-28539 gateway does not support result sets
Cause: The client program tried executing a stored procedure that returns one or more result sets through a gateway that does not have result set support.
Action: Check the documentation for the gateway that you are using and see if it supports result sets returned from stored procedures. If it does not, then the only way of accessing such stored procedures is to upgrade to a version of the gateway that does support result sets (if such a version exists). If the gateway does have result set support and you are still seeing this error, contact Oracle Support Services.
ORA-28541 Error in HS init file on line number.
Cause: A syntax error occurred in the gateway initialization file.
Action: Check the gateway init file to correct the syntax error. For further information, check the error message in the gateway trace file.
ORA-28542 Error in reading HS init file
Cause: Reading the gateway init file generated an error.
Action: Check the gateway initialization file name to see that the gateway initialization file acctually exists. Check the ifile parameter to see that it points to the correct location.
ORA-28543 Error initializing apply connection to non-Oracle system
Cause: Attempt to initialize connection to non-Oracle for heterogeneous replication failed.
Action: Check if the listener used to connect to the gateway is up and is correctly configured. Make sure that the database link used has been configured correctly and, if a tnsnames alias has been used in the database link definition, make sure that the configuration of the entry in tnsnames.ora has been done correctly.
ORA-28544 connect to agent failed, probable Net8 administration error
Cause: Net8 reported a failure to make a RSLV connection or a protocol mode error when the Oracle database server attempted to establish communication with a Heterogeneous Services agent or an external procedure agent. This usually is due to an administration error in setting up Net8 service definitions in TNSNAMES.ORA or LISTENER.ORA: A basic network connection is opened, but it connects to a program which does not use the appropriate protocol. This often is a sign that the connection goes to the wrong program.
Action: Check Net8 administration in the following ways:
When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID.
Check LISTENER.ORA on the agent's host machine to assure that the service name or SID refers to the correct agent executable in its (PROGRAM=...) clause.
Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
ORA-28545 error diagnosed by Net8 when connecting to an agent
Cause: An attempt to call an external procedure or to issue SQL to a non-Oracle system on a Heterogeneous Services database link failed at connection initialization. The error diagnosed by Net8 NCR software is reported separately.
Action: Refer to the Net8 NCRO error message. If this isn't clear, check connection administrative setup in tnsnames.ora and listener.ora for the service associated with the Heterogeneous Services database link being used, or with 'extproc_connection_data' for an external procedure call.
ORA-28546 connection initialization failed, probable Net8 admin error
Cause: A failure occurred during initialization of a network connection from the Oracle database server to a second process: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Net8 administrative setup for database links or external procedure calls. The most frequent specific causes are:
Database link setup for an Oracle-to-Oracle connection instead connects to a Heterogeneous Services agent or an external procedure agent.
Database link setup for a Heterogeneous Services connection instead connects directly to an Oracle database server.
The extproc_connection_data definition in tnsnames.ora connects to an Oracle instance instead of an external procedure agent.
Connect data for a Heterogeneous Services database link, usually defined in tnsnames.ora, does not specify (HS=).
Connect data for an Oracle-to-Oracle database link, usually defined in tnsnames.ora, specifies (HS=).
Action: Check Net8 administration in the following ways:
When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID.
Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID connects to the correct program.
Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
ORA-28550 pass-through SQL: cursor not found
Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor.
Action: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call.
ORA-28551 pass-through SQL: SQL parse error
Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement.
Action: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system.
ORA-28552 pass-through SQL: call flow error
Cause: A pass-through SQL function was called in an invalid order.
Action: Correct program flow by changing the order of API calls to match the flow described in the manual.
ORA-28553 pass-through SQL: invalid bind-variable position
Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.
Action: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system.
ORA-28554 pass-through SQL: out of cursors
Cause: The maximum number of open cursors has been exceeded.
Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function.
ORA-28555 pass-through SQL: required parameter missing or NULL
Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
Action: Use a non-NULL value for the parameter.
ORA-28556 authorization insufficient to access table
Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.
Action: Contact the database administrator for the non-Oracle system. The database administrator can grant permission to access the privileged table or columns.
ORA-28557 unknown string for database link to non-Oracle system
Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. Oracle requires these names to configure the heterogeneous database link.
Action: Contact the database administrator to check setup of the connection and the Heterogeneous Services agent.
ORA-28558 HS_FDS_CONNECT_STRING undefined for non-Oracle system
Cause: A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the Oracle server's data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed.
Action: Contact your database administrator to verify correct setup of an HS_FDS_CONNECT_STRING entry in the Oracle Heterogeneous Services data dictionary.
ORA-28559 FDS_CLASS_NAME is string, FDS_INST_NAME is string
Cause: An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the Oracle data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store.
Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values to check Oracle data dictionary contents when necessary to diagnose the cause of the associated error.
ORA-28560 error in configuration of agent process
Cause: An Oracle server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable.
Action: Check Net8 administration in the following ways:
When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the Oracle server uses the correct SID.
Check LISTENER.ORA on the agent's host machine to assure that this SID refers to the correct agent executable in its (PROGRAM=...) clause.
ORA-28561 unable to set date format on non-Oracle system
Cause: Initialization of a Heterogeneous Services connection to set the date format to be used on the connected non-Oracle system.
Action: If the Oracle data dictionary supplies a value for the HS_NLS_DATE_FORMAT parameter, confirm that this value is formatted correctly by the rules of the non-Oracle system. Also check for additional information in log and trace files generated by the Heterogeneous Services agent.
ORA-28575 unable to open RPC connection to external procedure agent
Cause: Initialization of a network connection to the external procedure agent did not succeed. This problem can be caused by network problems, incorrect listener configuration, or incorrect transfer code.
Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or check Oracle Names Server.
ORA-28576 lost RPC connection to external procedure agent
Cause: A fatal error occurred in either an RPC network connection, the external procedure agent, or the invoked 3GL after communication had been established successfully.
Action: First check the 3GL code you are invoking; the most likely cause of this error is abnormal termination of the invoked "C" routine. If this is not the case, check for network problems. Correct the problem if you find it. If all components appear to be normal but the problem persists, the problem could be an internal logic error in the RPC transfer code. Contact Oracle Support Services.
ORA-28577 argument string of external procedure string has unsupported datatype string
Cause: While transferring external procedure arguments to the agent, an unsupported datatype was detected.
Action: Check your documentation for the supported datatypes of external procedure arguments.
ORA-28578 protocol error during callback from an external procedure
Cause: An internal protocol error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
Action: Contact Oracle Support Services.
ORA-28579 network error during callback from external procedure agent
Cause: An internal network error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
Action: Contact Oracle Support Services.
ORA-28580 recursive external procedures are not supported
Cause: A callback from within a user's 3GL routine resulted in the invocation of another external procedure.
Action: Make sure that the SQL code executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, such as triggers calling external procedures, PL/SQL procedures calling external procedures, and so on.
ORA-28581 protocol error while executing recursive external procedure
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
Action: Contact Oracle Support Services.
ORA-28582 a direct connection to this agent is not allowed
Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed.
Action: When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent.
ORA-28583 remote references are not permitted during agent callbacks
Cause: A Heterogeneous Services agent issued a callback to the Oracle database server which attemted to access a remote system. This is not supported.
Action: Make sure that SQL code issued by Heterogeneous Services agents does not reference a database link.
ORA-28584 heterogeneous apply internal error
Cause: The apply slave process encountered an error while trying to apply changes through a gateway to a non-Oracle system.
Action: Make sure that the apply database link is correctly configured and that the gateway listener and the non-Oracle system are correctly set up and are up and running. If everything is configured correctly and the problem still occurs, then contact Oracle Support Services.
ORA-28590 agent control utility: illegal or badly formed command
Cause: The user has issued an unrecognized or syntactically incorrect command.
Action: Refer to documentation and correct the syntax of the command.
ORA-28591 agent control utility: unable to access parameter file
Cause: The agent control utility was unable to access its parameter file. This could be because it could not find its ADMIN directory or because permissions on directory were not correctly set.
Action: The agent control utility puts its parameter file in either the directory pointed to by the environment variable AGTCTL_ADMIN or in the directory pointed to by the environment variable TNS_ADMIN. Make sure that at least one of these environment variables is set and that it points to a directory that the agent has access to.
ORA-28592 agent control utility: agent SID not set
Cause: The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail.
Action: Issue the command SET AGENT_SID value and then retry the command that failed.
ORA-28593 agent control utility: command terminated with error
Cause: An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shut down an agent that is no longer running.
Action: If the user wishes to issue a SET or an UNSET command, he should make sure the agent is shut down first by issuing the SHUTDOWN command.
ORA-28594 agent control utility: invalid parameter name
Cause: The user tried to set or unset an invalid agent parameter.
Action: Refer to documentation and correct the parameter name.
ORA-28601 invalid [no]MINIMIZE option
Cause: User did not type this alter table table_name MINIMIZE RECORDS_PER_BLOCK or alter table table_name NOMINIMIZE RECORDS_PER_BLOCK.
Action: Re-enter correct SQL command.
ORA-28602 statement not permitted on tables containing bitmap indexes
Cause: Table has bitmap indexes and user is minimizing or nominalizing RECORDS_PER_BLOCK.
Action: Drop all bitmap indexes before changing RECORDS_PER_BLOCK.
ORA-28603 statement not permitted on empty tables
Cause: Table is empty and statement does not work on empty tables.
Action: Try statement after loading your data.
ORA-28604 table too fragmented to build bitmap index (string,string,string)
Cause: The table has one or more blocks that exceed the maximum number of rows expected when creating a bitmap index. This is probably due to deleted rows. The values in the message are: (data block address, slot number found, maximum slot allowed)
Action: Defragment the table or block(s). Use the values in the message to determine the FIRST block affected (there may be others).
ORA-28605 bitmap indexes cannot be reversed
Cause: An attempt was made to create reverse bitmap index. This is not supported.
Action: No action required.
ORA-28611 bitmap index is corrupted - see trace file for diagnostics
Cause: Validate Index detected bitmap corruption in its argument index.
Action: Drop this bitmap index and create a new one.
ORA-28650 Primary index on an IOT cannot be rebuilt
Cause: An attempt was made to issue alter index rebuild on IOT-TOP.
Action: Use Alter table MOVE to reorganize the table(IOT).
ORA-28651 Primary index on IOTs can not be marked unusable
Cause: An attempt was made to mark IOT-TOP unusable through ALTER INDEX.
Action: Remove the option UNUSABLE.
ORA-28652 overflow segment attributes cannot be specified
Cause: During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING.
Action: Remove the illegal option(s).
ORA-28653 tables must both be index-organized
Cause: An attempt was made to exchange a non-IOT table/partition with a partition/table respectively.
Action: Ensure that non-partitioned and partitioned tables are both index-organized.
ORA-28654 table and partition not overflow compatible
Cause: If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one does not.
Action: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does.
ORA-28655 Alter table add overflow syntax error
Cause: Syntax error.
Action: Check the syntax.
ORA-28656 incomplete attribute specification
Cause: The attribute specification is not done for all partitions.
Action: Specify the storage attributes either for ALL partitions or NONE.
ORA-28658 This operation is supported only for Index-Organized tables
Cause: Attempt to perform some IOT specific operation on a non-IOT. This is not supported.
Action: No action required.
ORA-28659 COMPRESS must be specified at object level first
Cause: An attempt was made to specify COMPRESS at the partition level without first specifying it at the table level.
Action: Specify COMPRESS at the table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ...
ORA-28660 Partitioned Index-Organized table may not be MOVEd as a whole
Cause: An attempt was made to MOVE a partitioned index-organized table as a whole. This is not supported.
Action: Do not try to MOVE a partitioned index-organized table as a whole.
ORA-28661 Object already has COMPRESS clause specified
Cause: An attempt was made to specify COMPRESS for an index-organized table/index which already has a compression clause. This attribute can only be specified at creation time.
Action: Do not specify COMPRESS for an index-organized table/index which already has a compression clause.
ORA-28662 IOT index and overflow segments must share the same LOGGING attribute
Cause: An attempt was made to specify LOGGING for one segment and NOLOGGING for the other segment.
Action: Use the same attribute value for both segments.
ORA-28663 Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
Cause: An attempt was made to specify LOGGING for an ALTER TABLE ADD OVERFLOW statement.
Action: Do not specify LOGGING in this context.
ORA-28664 a partitioned table may not be coalesced as a whole
Cause: User attempted to coalesce a partitioned IOT using ALTER TABLE COALESCE statement, which is illegal.
Action: Coalesce the table a partition at a time (using ALTER TABLE MODIFY PARTITION COALESCE).
ORA-28665 table and partition must have same compression attribute
Cause: User attempted to EXCHANGE a compression enabled partition with a compression disabled table or vice versa OR the # of columns compressed is different for table and partition.
Action: Make sure the compression attributes match. If they don't, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS.
ORA-28666 option not allowed for an index on UROWID column(s)
Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL partitioned index on UROWID column(s).
Action: Build the index without these options.
ORA-28667 USING INDEX option not allowed for the primary key of an IOT
Cause: User attempted to define storage attributes for the primary key index of an Index-Organized table with USING INDEX clause. All the storage attribute defined for the (IOT)table applies to the primary key index and a separate USING INDEX clause is not required.
Action: Remove the USING INDEX clause and specify all attributes directly for the table.
ORA-28668 cannot reference mapping table of an index-organized table
Cause: An attempt to directly access the mapping table of an index-organized table.
Action: Issue the statement against the parent index-organized table containing the specified mapping table.
ORA-28669 bitmap index can not be created on an IOT with no mapping table
Cause: User attempted to create a bitmap index on an index-organized table without a mapping table.
Action: Enable bitmap indexes on the Index-organized table by creating a mapping table using 'ALTER TABLE ... MOVE MAPPING TABLE'.
ORA-28670 mapping table cannot be dropped due to an existing bitmap index
Cause: User attempted to drop the mapping table with NOMAPPING option when the IOT has one or more bitmap indexes.
Action: Drop the bitmap index(es) before dropping the mapping table.
ORA-28671 UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is illegal.
Action: Issue a partition level operation with ALTER INDEX ... PARTITION ... UPDATE BLOCK REFERENCES.
ORA-28672 UPDATE BLOCK REFERENCES may not be used on a global index
Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned or non-partitioned index. This feature is not supported for non-partitioned or global partitioned indexes on a partitioned IOT and a global partitioned index on a non-partitioned IOT.
Action: Use online index [partition] rebuild to fix the block references.
ORA-28673 Merge operation not allowed on an index-organized table
Cause: User attempted merge operation on an index-organized table. Merge is not supported on an IOT .
Action: Use updates and inserts on the index-organized table.
Cause: User is changing password but password verification function is turned on, the original password is not specified, and the user does not have the alter user system privilege.
Action: Supply the original password.
ORA-28231 no data passed to obfuscation toolkit
Cause: A NULL value was passed to a function or procedure.
Action: Make sure that the data passed is not empty.
ORA-28232 invalid input length for obfuscation toolkit
Cause: Length of data submitted for encryption or decryption is not a multiple of 8 bytes.
Action: Make sure that the length of the data to be encrypted or decrypted is a multiple of 8 bytes.
ORA-28233 double encryption not supported
Cause: The obfuscation toolkit does not support the encryption of already-encrypted data.
Action: Do not attempt to encrypt already-encrypted data.
ORA-28234 key length too short
Cause: The key specified is too short for the algorithm. DES requires a key of at least 8 bytes. Triple DES requires a key of at least 16 bytes in two-key mode and 24 bytes in three-key mode.
Action: Specify a longer key.
ORA-28235 algorithm not available
Cause: The desired encryption algorithm is not available.
Action: Run the installer to install the needed algorithm in Oracle Advanced Security.
ORA-28236 invalid Triple DES mode
Cause: An unknown value was specified for the mode in which triple DES encryption is to run.
Action: Specify a valid value. See the package declaration for a list of valid values.
ORA-28237 seed length too short
Cause: The seed specified for the key generation routine must be at least 80 characters.
Action: Specify a longer seed.
ORA-28238 no seed provided
Cause: A NULL value was passed in as the seed to be used in generating a key.
Action: Provide a non-NULL value for the seed.
ORA-28239 no key provided
Cause: A NULL value was passed in as an encryption or decryption key.
Action: Provide a non-NULL value for the key.
ORA-28261 CURRENT_USER can not be used in PLSQL Definer's Right procedure.
Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL interface.
Action: Use a SQL statement to query CURRENT_USER inside a DR procedure.
ORA-28262 global_context_pool_size has invalid value.
Cause: Initialization parameter GLOBAL_CONTEXT_POOL_SIZE has a value less than the minimum required value (10K).
Action: Specify a value for the initialization parameter GLOBAL_CONTEXT_POOL_SIZE that is atleast 10k.
ORA-28263 Insufficient memory in global context pool
Cause: Allocations for the global context heap exceeded the value set in the initialization parameter file.
Action: Increase the value of the GLOBAL_CONTEXT_POOL_SIZE initialization parameter or clear unused global context.
ORA-28264 Client identifier is too long
Cause: The length of the client identifier is longer than 64.
Action: Set a client identifier whose length is less than 64.
ORA-28265 NameSpace beginning with 'sys_' is not allowed
Cause: Namespace beginning with 'sys_' is not allowed.
Action: Use a namespace that does not begin with 'sys_'.
ORA-28270 Malformed user nickname for password authenticated global user
Cause: An attempt to login as password-auuthenticated global user with a malformed user nickname.
Action: Make sure the nickname is valid and re-login.
ORA-28271 No permission to read user entry in LDAP directory service
Cause: ORACLE server does not have read permission on user nickname's X.500 user entry.
Action: Make sure ORACLE server is using the correct SSL credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are correct.
ORA-28272 Domain policy restricts password based GLOBAL user authentication
Cause: Domain policy does not allow password-authenticated GLOBAL users.
Action: Make sure ORACLE server is using the correct SSL credentials to connect to LDAP directory services. Make sure orclDBAuthTypes attributes within Oracle enterprise domain object is either set to PWD or ALL.
ORA-28273 No mapping for user nickname to LDAP distinguished name exists
Cause: ORACLE server cannot map the given user nickname to LDAP distinguished name.
Action: Make sure user entries in LDAP are correctly provisioned with correct user nickname attribute values.
ORA-28274 No ORACLE password attribute corresponding to user nickname exists
Cause: LDAP user entry corresponding to user nickname does not have a ORACLE password attribute or the attribute is not initialized.
Action: Make sure user entries in LDAP are correctly provisioned with correct ORACLE password attribute values.
ORA-28275 Multiple mappings for user nickname to LDAP distinguished name exist
Cause: The given user nickname maps to more than one LDAP distinguished name.
Action: Make sure user nickname is unique within the enterprise.
ORA-28276 Invalid ORACLE password attribute
Cause: The ORACLE password attribute of a user entry has an invalid format.
Action: Make sure ORACLE password attribute value is RFC-2307 compliant.
ORA-28277 LDAP search, while authenticating global user with passwords, failed
Cause: The LDAP search for finding the appropriate user entry and ORACLE password failed.
Action: Make sure LDAP directory service is up and running.
ORA-28278 No domain policy registered for password based GLOBAL users
Cause: No policy about password authenticated GLOBAL users has been registered.
Action: Add attribute orclDBAuthTypes to the database server's Enterprise domain.
ORA-28279 Error reading rdbms_server_dn parameter in INIT.ORA
Cause: The initialization parameter RDBMS_SERVER_DN is not specified corrrectly (cannot be normalized).
Action: Make sure the RDBMS_SERVER_DN initialization parameter is set to a correct value.
ORA-28280 Multiple entries for ORACLE database password exist.
Cause: The ORACLE password attribute of a user entry has multiple entries of ORACLE database password.
Action: Make sure ORACLE password attribute has one entry for ORACLE Database password.
ORA-28500 connection from ORACLE to a non-Oracle system returned this message:
Cause: The cause is explained in the forwarded message.
Action: See the non-Oracle system's documentation of the forwarded message.
ORA-28501 communication error on heterogeneous database link
Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system.
Action: See the documentation for the non-Oracle system for an explanation of the second error message.
ORA-28502 internal communication error on heterogeneous database link
Cause: A communication error internal to Oracle's heterogeneous services has occurred.
Action: Contact Oracle Support Services.
ORA-28503 bind value cannot be translated into SQL text for non-Oracle system
Cause: A SQL statement used bind variables on a Heterogeneous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables.
Action: Change your SQL statement so that it does not use bind variables.
ORA-28504 ROWID not found in ROWID cache for heterogeneous database link
Cause: The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache.
Action: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the HS_ROWID_CACHE_SIZE Heterogenious Services initialization parameter.
ORA-28505 cannot get non-Oracle system capabilities from string
Cause: Oracle was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views.
Action: Contact the database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.
ORA-28506 parse error in data dictionary translation for string stored in string
Cause: A reference to an Oracle data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The Oracle data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation.
Action: Contact customer support of the agent vendor.
ORA-28507 error in data dictionary view string
Cause: The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect.
Action: Verify correct installation of the following Heterogeneous Services' initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. If these views are not available, make sure you ran the script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory.
ORA-28508 invalid value string for Heterogeneous Services initialization parameter string
Cause: The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system.
Action: Check the Heterogeneous Services and agent documentation to determine acceptable values.
ORA-28509 unable to establish a connection to non-Oracle system
Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system.
Action: Check the Net8 service name definition in the following places:
the USING clause of the CREATE DATABASE LINK statement
the TNSNAMES.ORA file
the Oracle Names Server
The following are possible reasons for name mismatches:
The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in the TNSNAMES.ORA file or in the Oracle Names Server.
The protocol-specific information in the service name definition must match the protocol-specific definition of the responding listener.
The SID=name in the service name definition (in the TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener.
ORA-28510 heterogeneous database link initialization failed
Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system.
Action: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly.
ORA-28511 lost RPC connection to heterogeneous remote agent using SID=string
Cause: A fatal error occurred in one of the following places:
the connection between the Oracle server and the agent
the heterogeneous services remote agent itself
the connection to the non-Oracle system
This error occurred after communication had been established successfully.
Action: Check for network problems and remote host crashes. The problem is probably in the agent software. If so, contact customer support of the agent vendor.
ORA-28512 cannot get data dictionary translations from string
Cause: Oracle was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views.
Action: Ask your database administrator to check the server data dictionary table named in the error message. If table contents are incorrect, the database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server.
ORA-28513 internal error in heterogeneous remote agent
Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link.
Action: Make a note of how the error was produced and contact customer support of the agent vendor.
ORA-28514 heterogeneous database link initialization could not convert system date
Cause: The system date was not retrievable.
Action: Verify that the Oracle server's host machine and operating system are operational. This error should not occur unless low level system functions are failing.
ORA-28515 cannot get external object definitions from string
Cause: Oracle was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed.
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory.
ORA-28518 data dictionary translation has illegal translation type
Cause: A data dictionary translation definition, either in the Oracle server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are 'T' or 't' for 'translate', 'M' or 'm' for 'mimic'. Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the Oracle instance and to the Oracle instance's alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an Oracle server on the first connection from the server to the agent.
Action: Contact the customer support of the agent vendor.
ORA-28519 no heterogeneous data dictionary translations available
Cause: The Oracle server's data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
Action: Ask a database administrator to resolve this problem. The easiest solution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor.
ORA-28520 error initializing heterogeneous data dictionary translations
Cause: Oracle was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor.
ORA-28521 no heterogeneous capability information available
Cause: The Oracle server's data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled.
Action: Ask a database administrator to resolve this problem. The easiest resolution is to enable automatic self-registration by setting the Oracle server's HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact customer support of the agent vendor.
ORA-28522 error initializing heterogeneous capabilities
Cause: Oracle was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly.
Action: Verify that the Oracle server's Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the Oracle server, verify that the script has been run. If both scripts were executed and the error persists, contact customer support of the agent vendor.
ORA-28523 ORACLE and heterogeneous agent are incompatible versions
Cause: An operation on a database link attempted to connect to a non-Oracle system, but the Oracle instance and the agent process for the non-Oracle system are incompatible.
Action: Ask your database administrator to confirm configuration of both the Oracle instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the Oracle instance and the agent, and in the Oracle instance's alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported.
ORA-28525 unable to create Heterogeneous Services error message text
Cause: Incorrect arguments were passed into the error message creation routine.
Action: Contact Oracle Support Services.
ORA-28526 invalid describe information returned to Heterogeneous Services
Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent.
Action: Contact customer support of the agent vendor.
ORA-28527 Heterogeneous Services datatype mapping error
Cause: Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the Oracle server's data dictionary.
Action: Verify that the Oracle server's data dictionary has been initialized with correct capability definitions for the connected FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, a database administrator should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. If the error persists contact customer support of the agent vendor.
ORA-28528 Heterogeneous Services datatype conversion error
Cause: Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for the conversion failure:
overflow problems (in the case of numbers)
length limitations (in the case of character strings)
invalid values passed into the conversion routines
Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it may not be possible to convert the value.
ORA-28529 invalid or missing parameter in Net8 service name definition
Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server.
Action: Ask your database administrator to make sure the information in the Net8 service definition is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent's documentation.
ORA-28530 Heterogeneous Services initialization error in NLS language ID
Cause: Heterogeneous Services was unable to initialize an NLS language ID. Both the Oracle server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs.
Action: Contact Oracle Support Services.
ORA-28533 Heterogeneous Services coercion handling error
Cause: The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions.
Action: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed.
ORA-28534 Heterogeneous Services preprocessing error
Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled.
Action: The capability table settings are controlled by the agent vendor and can be modified by the database administrator. Contact your database administrator and agent vendor and get the correct set of capabilities installed.
ORA-28535 invalid Heterogeneous Services context
Cause: A Heterogeneous Services agent's driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver.
Action: Contact customer support of the agent vendor.
ORA-28536 error in processing Heterogeneous Services initialization parameters
Cause: An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the Oracle server data dictionary.
Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and HS_ALL_INITS. Look for conditions which could produce the error identified in the error message immediately following this one.
ORA-28538 result set not found
Cause: The client program tried fetching from a result set that is no longer open. Many gateways will, on execution of a stored procedure, automatically close all result sets that were returned by any previously executed stored procedure.
Action: Check the documentation for the gateway that you are using and see if it will automatically close currently open result sets each time a stored procedure is executed. Then check if your client program is violating this rule. If it is, fix your program. If it is not, contact Oracle Support Services.
ORA-28539 gateway does not support result sets
Cause: The client program tried executing a stored procedure that returns one or more result sets through a gateway that does not have result set support.
Action: Check the documentation for the gateway that you are using and see if it supports result sets returned from stored procedures. If it does not, then the only way of accessing such stored procedures is to upgrade to a version of the gateway that does support result sets (if such a version exists). If the gateway does have result set support and you are still seeing this error, contact Oracle Support Services.
ORA-28541 Error in HS init file on line number.
Cause: A syntax error occurred in the gateway initialization file.
Action: Check the gateway init file to correct the syntax error. For further information, check the error message in the gateway trace file.
ORA-28542 Error in reading HS init file
Cause: Reading the gateway init file generated an error.
Action: Check the gateway initialization file name to see that the gateway initialization file acctually exists. Check the ifile parameter to see that it points to the correct location.
ORA-28543 Error initializing apply connection to non-Oracle system
Cause: Attempt to initialize connection to non-Oracle for heterogeneous replication failed.
Action: Check if the listener used to connect to the gateway is up and is correctly configured. Make sure that the database link used has been configured correctly and, if a tnsnames alias has been used in the database link definition, make sure that the configuration of the entry in tnsnames.ora has been done correctly.
ORA-28544 connect to agent failed, probable Net8 administration error
Cause: Net8 reported a failure to make a RSLV connection or a protocol mode error when the Oracle database server attempted to establish communication with a Heterogeneous Services agent or an external procedure agent. This usually is due to an administration error in setting up Net8 service definitions in TNSNAMES.ORA or LISTENER.ORA: A basic network connection is opened, but it connects to a program which does not use the appropriate protocol. This often is a sign that the connection goes to the wrong program.
Action: Check Net8 administration in the following ways:
When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID.
Check LISTENER.ORA on the agent's host machine to assure that the service name or SID refers to the correct agent executable in its (PROGRAM=...) clause.
Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
ORA-28545 error diagnosed by Net8 when connecting to an agent
Cause: An attempt to call an external procedure or to issue SQL to a non-Oracle system on a Heterogeneous Services database link failed at connection initialization. The error diagnosed by Net8 NCR software is reported separately.
Action: Refer to the Net8 NCRO error message. If this isn't clear, check connection administrative setup in tnsnames.ora and listener.ora for the service associated with the Heterogeneous Services database link being used, or with 'extproc_connection_data' for an external procedure call.
ORA-28546 connection initialization failed, probable Net8 admin error
Cause: A failure occurred during initialization of a network connection from the Oracle database server to a second process: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Net8 administrative setup for database links or external procedure calls. The most frequent specific causes are:
Database link setup for an Oracle-to-Oracle connection instead connects to a Heterogeneous Services agent or an external procedure agent.
Database link setup for a Heterogeneous Services connection instead connects directly to an Oracle database server.
The extproc_connection_data definition in tnsnames.ora connects to an Oracle instance instead of an external procedure agent.
Connect data for a Heterogeneous Services database link, usually defined in tnsnames.ora, does not specify (HS=).
Connect data for an Oracle-to-Oracle database link, usually defined in tnsnames.ora, specifies (HS=).
Action: Check Net8 administration in the following ways:
When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID.
Check LISTENER.ORA on the connection end point's host machine to assure that this service name or SID connects to the correct program.
Confirm in TNSNAMES.ORA or the equivalent service definition that service 'extproc_connection_data' does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
ORA-28550 pass-through SQL: cursor not found
Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor.
Action: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call.
ORA-28551 pass-through SQL: SQL parse error
Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement.
Action: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system.
ORA-28552 pass-through SQL: call flow error
Cause: A pass-through SQL function was called in an invalid order.
Action: Correct program flow by changing the order of API calls to match the flow described in the manual.
ORA-28553 pass-through SQL: invalid bind-variable position
Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.
Action: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system.
ORA-28554 pass-through SQL: out of cursors
Cause: The maximum number of open cursors has been exceeded.
Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function.
ORA-28555 pass-through SQL: required parameter missing or NULL
Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
Action: Use a non-NULL value for the parameter.
ORA-28556 authorization insufficient to access table
Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.
Action: Contact the database administrator for the non-Oracle system. The database administrator can grant permission to access the privileged table or columns.
ORA-28557 unknown string for database link to non-Oracle system
Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. Oracle requires these names to configure the heterogeneous database link.
Action: Contact the database administrator to check setup of the connection and the Heterogeneous Services agent.
ORA-28558 HS_FDS_CONNECT_STRING undefined for non-Oracle system
Cause: A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the Oracle server's data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed.
Action: Contact your database administrator to verify correct setup of an HS_FDS_CONNECT_STRING entry in the Oracle Heterogeneous Services data dictionary.
ORA-28559 FDS_CLASS_NAME is string, FDS_INST_NAME is string
Cause: An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the Oracle data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store.
Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values to check Oracle data dictionary contents when necessary to diagnose the cause of the associated error.
ORA-28560 error in configuration of agent process
Cause: An Oracle server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable.
Action: Check Net8 administration in the following ways:
When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the Oracle server uses the correct SID.
Check LISTENER.ORA on the agent's host machine to assure that this SID refers to the correct agent executable in its (PROGRAM=...) clause.
ORA-28561 unable to set date format on non-Oracle system
Cause: Initialization of a Heterogeneous Services connection to set the date format to be used on the connected non-Oracle system.
Action: If the Oracle data dictionary supplies a value for the HS_NLS_DATE_FORMAT parameter, confirm that this value is formatted correctly by the rules of the non-Oracle system. Also check for additional information in log and trace files generated by the Heterogeneous Services agent.
ORA-28575 unable to open RPC connection to external procedure agent
Cause: Initialization of a network connection to the external procedure agent did not succeed. This problem can be caused by network problems, incorrect listener configuration, or incorrect transfer code.
Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or check Oracle Names Server.
ORA-28576 lost RPC connection to external procedure agent
Cause: A fatal error occurred in either an RPC network connection, the external procedure agent, or the invoked 3GL after communication had been established successfully.
Action: First check the 3GL code you are invoking; the most likely cause of this error is abnormal termination of the invoked "C" routine. If this is not the case, check for network problems. Correct the problem if you find it. If all components appear to be normal but the problem persists, the problem could be an internal logic error in the RPC transfer code. Contact Oracle Support Services.
ORA-28577 argument string of external procedure string has unsupported datatype string
Cause: While transferring external procedure arguments to the agent, an unsupported datatype was detected.
Action: Check your documentation for the supported datatypes of external procedure arguments.
ORA-28578 protocol error during callback from an external procedure
Cause: An internal protocol error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
Action: Contact Oracle Support Services.
ORA-28579 network error during callback from external procedure agent
Cause: An internal network error occurred while trying to execute a callback to the Oracle server from the user's 3GL routine.
Action: Contact Oracle Support Services.
ORA-28580 recursive external procedures are not supported
Cause: A callback from within a user's 3GL routine resulted in the invocation of another external procedure.
Action: Make sure that the SQL code executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, such as triggers calling external procedures, PL/SQL procedures calling external procedures, and so on.
ORA-28581 protocol error while executing recursive external procedure
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
Action: Contact Oracle Support Services.
ORA-28582 a direct connection to this agent is not allowed
Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed.
Action: When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent.
ORA-28583 remote references are not permitted during agent callbacks
Cause: A Heterogeneous Services agent issued a callback to the Oracle database server which attemted to access a remote system. This is not supported.
Action: Make sure that SQL code issued by Heterogeneous Services agents does not reference a database link.
ORA-28584 heterogeneous apply internal error
Cause: The apply slave process encountered an error while trying to apply changes through a gateway to a non-Oracle system.
Action: Make sure that the apply database link is correctly configured and that the gateway listener and the non-Oracle system are correctly set up and are up and running. If everything is configured correctly and the problem still occurs, then contact Oracle Support Services.
ORA-28590 agent control utility: illegal or badly formed command
Cause: The user has issued an unrecognized or syntactically incorrect command.
Action: Refer to documentation and correct the syntax of the command.
ORA-28591 agent control utility: unable to access parameter file
Cause: The agent control utility was unable to access its parameter file. This could be because it could not find its ADMIN directory or because permissions on directory were not correctly set.
Action: The agent control utility puts its parameter file in either the directory pointed to by the environment variable AGTCTL_ADMIN or in the directory pointed to by the environment variable TNS_ADMIN. Make sure that at least one of these environment variables is set and that it points to a directory that the agent has access to.
ORA-28592 agent control utility: agent SID not set
Cause: The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail.
Action: Issue the command SET AGENT_SID value and then retry the command that failed.
ORA-28593 agent control utility: command terminated with error
Cause: An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shut down an agent that is no longer running.
Action: If the user wishes to issue a SET or an UNSET command, he should make sure the agent is shut down first by issuing the SHUTDOWN command.
ORA-28594 agent control utility: invalid parameter name
Cause: The user tried to set or unset an invalid agent parameter.
Action: Refer to documentation and correct the parameter name.
ORA-28601 invalid [no]MINIMIZE option
Cause: User did not type this alter table table_name MINIMIZE RECORDS_PER_BLOCK or alter table table_name NOMINIMIZE RECORDS_PER_BLOCK.
Action: Re-enter correct SQL command.
ORA-28602 statement not permitted on tables containing bitmap indexes
Cause: Table has bitmap indexes and user is minimizing or nominalizing RECORDS_PER_BLOCK.
Action: Drop all bitmap indexes before changing RECORDS_PER_BLOCK.
ORA-28603 statement not permitted on empty tables
Cause: Table is empty and statement does not work on empty tables.
Action: Try statement after loading your data.
ORA-28604 table too fragmented to build bitmap index (string,string,string)
Cause: The table has one or more blocks that exceed the maximum number of rows expected when creating a bitmap index. This is probably due to deleted rows. The values in the message are: (data block address, slot number found, maximum slot allowed)
Action: Defragment the table or block(s). Use the values in the message to determine the FIRST block affected (there may be others).
ORA-28605 bitmap indexes cannot be reversed
Cause: An attempt was made to create reverse bitmap index. This is not supported.
Action: No action required.
ORA-28611 bitmap index is corrupted - see trace file for diagnostics
Cause: Validate Index detected bitmap corruption in its argument index.
Action: Drop this bitmap index and create a new one.
ORA-28650 Primary index on an IOT cannot be rebuilt
Cause: An attempt was made to issue alter index rebuild on IOT-TOP.
Action: Use Alter table MOVE to reorganize the table(IOT).
ORA-28651 Primary index on IOTs can not be marked unusable
Cause: An attempt was made to mark IOT-TOP unusable through ALTER INDEX.
Action: Remove the option UNUSABLE.
ORA-28652 overflow segment attributes cannot be specified
Cause: During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING.
Action: Remove the illegal option(s).
ORA-28653 tables must both be index-organized
Cause: An attempt was made to exchange a non-IOT table/partition with a partition/table respectively.
Action: Ensure that non-partitioned and partitioned tables are both index-organized.
ORA-28654 table and partition not overflow compatible
Cause: If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one does not.
Action: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does.
ORA-28655 Alter table add overflow syntax error
Cause: Syntax error.
Action: Check the syntax.
ORA-28656 incomplete attribute specification
Cause: The attribute specification is not done for all partitions.
Action: Specify the storage attributes either for ALL partitions or NONE.
ORA-28658 This operation is supported only for Index-Organized tables
Cause: Attempt to perform some IOT specific operation on a non-IOT. This is not supported.
Action: No action required.
ORA-28659 COMPRESS must be specified at object level first
Cause: An attempt was made to specify COMPRESS at the partition level without first specifying it at the table level.
Action: Specify COMPRESS at the table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ...
ORA-28660 Partitioned Index-Organized table may not be MOVEd as a whole
Cause: An attempt was made to MOVE a partitioned index-organized table as a whole. This is not supported.
Action: Do not try to MOVE a partitioned index-organized table as a whole.
ORA-28661 Object already has COMPRESS clause specified
Cause: An attempt was made to specify COMPRESS for an index-organized table/index which already has a compression clause. This attribute can only be specified at creation time.
Action: Do not specify COMPRESS for an index-organized table/index which already has a compression clause.
ORA-28662 IOT index and overflow segments must share the same LOGGING attribute
Cause: An attempt was made to specify LOGGING for one segment and NOLOGGING for the other segment.
Action: Use the same attribute value for both segments.
ORA-28663 Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
Cause: An attempt was made to specify LOGGING for an ALTER TABLE ADD OVERFLOW statement.
Action: Do not specify LOGGING in this context.
ORA-28664 a partitioned table may not be coalesced as a whole
Cause: User attempted to coalesce a partitioned IOT using ALTER TABLE COALESCE statement, which is illegal.
Action: Coalesce the table a partition at a time (using ALTER TABLE MODIFY PARTITION COALESCE).
ORA-28665 table and partition must have same compression attribute
Cause: User attempted to EXCHANGE a compression enabled partition with a compression disabled table or vice versa OR the # of columns compressed is different for table and partition.
Action: Make sure the compression attributes match. If they don't, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS.
ORA-28666 option not allowed for an index on UROWID column(s)
Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL partitioned index on UROWID column(s).
Action: Build the index without these options.
ORA-28667 USING INDEX option not allowed for the primary key of an IOT
Cause: User attempted to define storage attributes for the primary key index of an Index-Organized table with USING INDEX clause. All the storage attribute defined for the (IOT)table applies to the primary key index and a separate USING INDEX clause is not required.
Action: Remove the USING INDEX clause and specify all attributes directly for the table.
ORA-28668 cannot reference mapping table of an index-organized table
Cause: An attempt to directly access the mapping table of an index-organized table.
Action: Issue the statement against the parent index-organized table containing the specified mapping table.
ORA-28669 bitmap index can not be created on an IOT with no mapping table
Cause: User attempted to create a bitmap index on an index-organized table without a mapping table.
Action: Enable bitmap indexes on the Index-organized table by creating a mapping table using 'ALTER TABLE ... MOVE MAPPING TABLE'.
ORA-28670 mapping table cannot be dropped due to an existing bitmap index
Cause: User attempted to drop the mapping table with NOMAPPING option when the IOT has one or more bitmap indexes.
Action: Drop the bitmap index(es) before dropping the mapping table.
ORA-28671 UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is illegal.
Action: Issue a partition level operation with ALTER INDEX ... PARTITION ... UPDATE BLOCK REFERENCES.
ORA-28672 UPDATE BLOCK REFERENCES may not be used on a global index
Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned or non-partitioned index. This feature is not supported for non-partitioned or global partitioned indexes on a partitioned IOT and a global partitioned index on a non-partitioned IOT.
Action: Use online index [partition] rebuild to fix the block references.
ORA-28673 Merge operation not allowed on an index-organized table
Cause: User attempted merge operation on an index-organized table. Merge is not supported on an IOT .
Action: Use updates and inserts on the index-organized table.
No comments:
Post a Comment