ORA-29254: Invalid lower_bound argument passed to procedure dbms_sql.define_ array

ORA-29254: Invalid lower_bound argument passed to procedure dbms_sql.define_ array

Cause: The lower_bound argument specified in the call to procedure define_array had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal.

Action: Correct your PL or SQL program so that only valid arguments are passed to define_array and try again.

ORA-29253: Invalid count argument passed to procedure dbms_sql.define_array

ORA-29253: Invalid count argument passed to procedure dbms_sql.define_array

Cause: The count argument specified in the call to procedure define_array of package dbms_sql had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer.

Action: Correct your PL or SQL program so that only valid arguments are passed to define_array and try again.

ORA-29252: collection does not contain elements at index locations in call to dbms_ sql.bind_array

ORA-29252: collection does not contain elements at index locations in call to dbms_ sql.bind_array

Cause: The bound table does not contain elements at both index locations in call to bind_array of dbms_sql. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true.

Action: Either modify the two indexes or the contents of the table and try the call again.

ORA-29251: Index1 is greater than Index2 in call to dbms_sql.bind_array

ORA-29251: Index1 is greater than Index2 in call to dbms_sql.bind_array

Cause: The value of index1 was greater than the value for index2 in the call to bind_array. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2.

Action: Correct the value of the two indexes and try the call to again bind_array.

ORA-29250: Invalid index specifed in call to dbms_sql.bind_array

ORA-29250: Invalid index specifed in call to dbms_sql.bind_array

Cause: An invalid index was specified in a call to bind_array of dbms_sql. The index may have been null or of an improper value.

Action: Correct the index value by modifying your PL or SQL program and try the bind_array call again.

ORA-28674: cannot reference transient index-organized table

ORA-28674: cannot reference transient index-organized table

Cause: An attempt was made to directly access a transient table created created on behalf of a index-organized table partition maintenance operation.

Action: Issue the statement against the associated permanent index-organized table.

ORA-28673: Merge operation not allowed on an index-organized table

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 a IOT .

Action: Use updates and inserts on index-organized table .

ORA-28672: UPDATE BLOCK REFERENCES may not be used on a global index

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 index 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-28671: UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole

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-28670: mapping table cannot be dropped due to an existing bitmap index

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 indexed.

Action: Drop the bitmap index(es) before dropping the mapping table.

ORA-28669: bitmap index can not be created on an IOT with no 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-28668: cannot reference mapping table of an index-organized 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-28667: USING INDEX option not allowed for the primary key of an IOT

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-28666: option not allowed for an index on UROWID column(s)

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-28665: table and partition must have same compression attribute

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-28664: a partitioned table may not be coalesced as a whole

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-28663: Logging or Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW

ORA-28663: Logging or Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW

Cause: Attempt to specify LOGGING for a Alter Table Add Overflow.

Action: don t do that

ORA-28662: IOT index and overflow segments must share the same LOGGING attribute

ORA-28662: IOT index and overflow segments must share the same LOGGING attribute

Cause: Attempt to specify LOGGING for one segment and NOLOGGING for the other segment.

Action: don t do that

ORA-28661: Object already has COMPRESS clause specified

ORA-28661: Object already has COMPRESS clause specified

Cause: Attempt to specify compress for iot or index which already has a compression clause.

Action: This is a create time only attribute

ORA-28660: Partitioned Index-Organized table may not be MOVEd as a whole

ORA-28660: Partitioned Index-Organized table may not be MOVEd as a whole

Cause: Attempt to MOVE partitioned IOT as a whole

Action: don t do this. This is not supported

ORA-28659: COMPRESS must be specified at object level first

ORA-28659: COMPRESS must be specified at object level first

Cause: Attempt to specify COMPRESS at partition level without first specifying at the table level

Action: Specify COMPRESS at table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ...

ORA-28658: This operation is supported only for Index-Organized tables

ORA-28658: This operation is supported only for Index-Organized tables

Cause: Attempt to perform some IOT specific operation on a non-IOT

Action: don t do this. This is not supported

ORA-28656: incomplete attribute specification

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 NLS_ DO_NOT_TRANSLATE (28657,28657(

ORA-28655: Alter table add overflow syntax error

ORA-28655: Alter table add overflow syntax error

Cause: Syntax error

Action: Check the syntax.

ORA-28654: table and partition not overflow compatible

ORA-28654: table and partition not overflow compatible

Cause: If one of the tables (partitioned or non-partitioned) has overflow data segment and the other one doesn t.

Action: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does.

ORA-28653: tables must both be index-organized

ORA-28653: tables must both be index-organized

Cause: Attempt to exchange a non IOT table or partition with a partition or table respectively

Action: Ensure that non-partitioned and partitioned tables are both index-organized.

ORA-28652: overflow segment attributes cannot be specified

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-28651: Primary index on IOTs can not be marked unusable

ORA-28651: Primary index on IOTs can not be marked unusable

Cause: An attempt is made to mark IOT-TOP unusable thru ALTER INDEX

Action: Remove the option UNUSABLE

ORA-28650: Primary index on an IOT cannot be rebuilt

ORA-28650: Primary index on an IOT cannot be rebuilt

Cause: An attempt is made to issue alter index rebuild on IOT-TOP

Action: Use Alter table MOVE to reorganize the table(IOT)

ORA-28611: bitmap index is corrupted - see trace file for diagnostics

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-28606: block too fragmented to build bitmap index (string,string)

ORA-28606: block too fragmented to build bitmap index (string,string)

Cause: The block(s) exceed the maximum number of rows expected when creating a bitmap index. This is probably due to maximum slot allowed set too low. The values in the message are: (slot number found, maximum slot allowed)

Action: alter system flush shared_pool; update tab$ set spare1 = 8192 where obj# = (select obj# from obj$ where NAME=lamp;lt;lamp;nbsp;table_namelamp;gt; AND owner# = lamp;lt;lamp;nbsp;table_ ownerlamp;gt;; commit;

ORA-28605: bitmap indexes cannot be reversed

ORA-28605: bitmap indexes cannot be reversed

Cause: user tried to create reverse bitmap index

Action: don t do this; it is not supported

ORA-28604: table too fragmented to build bitmap index (string,string,string)

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-28603: statement not permitted on empty tables

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-28602: statement not permitted on tables containing bitmap indexes

ORA-28602: statement not permitted on tables containing bitmap indexes

Cause: table has bitmap indexes and user is minimizing or nominimizing records_per_block

Action: drop all bitmap indexes before changing records_per_block

ORA-28601: invalid (no(MINIMIZE option

ORA-28601: invalid (no(MINIMIZE option

Cause: user didn t type this alter table lamp;lt;lamp;nbsp;table_namelamp;gt; MINIMIZE RECORDS_ PER_BLOCK or alter table lamp;lt;lamp;nbsp;table_namelamp;gt; NOMINIMIZE RECORDS_PER_BLOCK

Action: reenter correct sql command

ORA-28595: Extproc agent : Invalid DLL Path

ORA-28595: Extproc agent : Invalid DLL Path

Cause: The path of DLL supplied for the extproc execution is invalid.

Action: Check if the DLL path is set properly using the EXTPROC_DLLS environment variable. errors 28600 - 28620 are reserved for bitmap indexes

ORA-28594: agent control utility: invalid parameter name

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-28593: agent control utility: command terminated with error

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 shutdown 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 shutdown first by issuing the SHUTDOWN command.

ORA-28592: agent control utility: agent SID not set

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 lamp;lt;lamp;nbsp;valuelamp;gt; and then retry the command that failed.

ORA-28591: agent control utility: unable to access parameter file

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-28590: agent control utility: illegal or badly formed command

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-28584: heterogeneous apply internal error

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, contact Oracle customer support. errors 28590 - 28599 are reserved for the HS agent control utility

ORA-28583: remote references are not permitted during agent callbacks

ORA-28583: remote references are not permitted during agent callbacks

Cause: A Heterogeous Services agent issued a callback to the Oracle server which attemted to 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-28582: a direct connection to this agent is not allowed

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: SVRMGRlamp;gt; CONNECT SCOTT or TIGERNETWORK_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-28581: protocol error while executing recursive external procedure

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 customer support.

ORA-28580: recursive external procedures are not supported

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 or SQL procedures calling external procedures, etc.

ORA-28579: network error during callback from external procedure agent

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 customer support.

ORA-28578: protocol error during callback from an external procedure

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 customer support.

ORA-28577: argument string of external procedure string has unsupported datatype string

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-28576: lost RPC connection to external procedure agent

ORA-28576: lost RPC connection to external procedure agent

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 your customer support representative.

Action: First check the 3GL code you are invoking; the most likely

ORA-28575: unable to open RPC connection to external procedure agent

ORA-28575: unable to open RPC connection to external procedure agent

Cause: Initialization of a network connection to the extproc 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-28561: unable to set date format on non-Oracle system

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-28560: error in configuration of agent process

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-28559: FDS_CLASS_NAME is string, FDS_INST_NAME is string

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-28558: HS_FDS_CONNECT_STRING undefined for non-Oracle system

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 DBA to verify correct setup of an HS_FDS_CONNECT_ STRING entry in the ORACLE Heterogeneous Services data dictionary.

ORA-28557: unknown string for database link to non-Oracle system

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 or FDS_INST_NAME. ORACLE requires these names to configure the heterogeneous database link.

Action: Contact the DBA to check setup of the connection and the Heterogeneous Services agent.

ORA-28556: authorization insufficient to access table

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 DBA for the non-Oracle system. The DBA can grant permission to access the privileged table or columns.

ORA-28555: pass-through SQL: required parameter missing or NULL

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-28554: pass-through SQL: out of cursors

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.