Action
If the user has no open cursors, the current SQL statement accesses more than the maximum allowed remote databases. Otherwise, the user may free remote database connections by closing all cursors that access the databases.
If this occurs often, consider increasing the value of the initialization parameter OPEN_LINKS, which controls the maximum number of concurrent open
connections to remote databases per user process.
ORA–02021
DDL operations are not allowed on a remote database
Cause
An attempt was made to use a DDL operation on a remote database. For example, “CREATE TABLE tablename@remotedbname...”.
Action
To alter the remote database structure, you must connect to the remote database with the appropriate privileges.
ORA–02022
remote statement has unoptimized view with remote object
Cause
The local view is unoptimized and contains references to objects at the remote database, and the statement must be executed at the remote database.
Action
Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote.
ORA–02023
START WITH or CONNECT BY predicate cannot be evaluated by remote database
Cause
The statement contains a tree query on a remote database, and the tree query’s START WITH or CONNECT BY predicate contains a term that cannot be
evaluated at the remote database. Such terms include calls to user functions, calls to USERENV, and references to ROWID.
Action
Remove the disallowed term, directly connect, or log on to the
remote database.
ORA–02024
database link not found
Cause
The database link to be dropped is not found in the dictionary.
Action
Correct the database link name.
Oracle7 Server Messages
2 – 199
01900–02039: SQL Parsing
ORA–02025
all tables in the SQL statement must be at the remote database
Cause
A SQL statement referenced tables from multiple databases, and one or more of the remote databases are not Oracle7 Servers.
Action
Remote updates can be performed only if all databases in the SQL statement are Oracle7 Servers. Update the earlier version databases in a
separate statement.
ORA–02026
missing LINK keyword
Cause
The keyword LINK is required in this context.
Action
Check syntax, insert keyword LINK as required, and try again.
ORA–02027
multi–row UPDATE of LONG column is not supported
Cause
A bind variable whose length is greater than 2000 bytes is being used to update a column, and the UPDATE statement affects more than one row.
Action
Check that each such bind variable updates only a single row.
ORA–02028
fetching an exact number of rows is not supported by the server Cause
The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.
Action
Connect to a valid server or do not use an exact fetch.
ORA–02029
missing FILE keyword
Cause
The keyword FILE is required in this context.
Action
Check syntax, insert keyword FILE as required, and try again.
ORA–02030
can only select from fixed tables/views
Cause
An operation other than SELECT on a fixed dynamic performance table or view was attempted. It is only possible to select from fixed tables or views.
Action
Remove the fixed table or view name from the SELECT statement.
ORA–02031
no ROWID for fixed tables
Cause
An attempt was made to select the ROWID from a fixed table.
Action
Do not select ROWID from a fixed table.
2 – 200
Oracle7 Server Messages
01900–02039: SQL Parsing
ORA–02032
clustered tables cannot be used before the cluster index is built Cause
An attempt was made to perform a DML operation on a clustered table for which no cluster index has yet been created.
Action
Create a cluster index before referencing clustered tables in a SQL statement.
ORA–02033
a cluster index for this cluster already exists
Cause
A cluster index already exists for the cluster.
Action
No action required.
ORA–02034
speed bind not permitted
Cause
Speed bind not allowed with supplied bind variables.
Action
No action required.
ORA–02035
illegal bundled operation combination
Cause