SQL0727N An error occurred during implicit system action type
"<action-type>". Information returned for the error
includes SQLCODE "<sqlcode>", SQLSTATE "<sqlstate>"
and message tokens "<token-list>".
The processing of a statement or command has caused the database
manager to implicitly perform additional processing. During this
processing an error was encountered. The action attempted is
shown by the "<action-type>":
1 implicit rebind of a package
2 implicit prepare of a cached dynamic SQL statement
3 implicit regeneration of a view
4 This return code is reserved for use by DB2.
5 incremental bind of a static SQL statement, not bound during
package bind time
The sqlcode, sqlstate and message token list (each token is
separated by the vertical bar character) are provided. The
message tokens may be truncated. See the corresponding message
for the "<sqlcode>" for further explanation of the error.
The original SQL statement or command that caused the
"<action-type>" cannot be processed and the implicit system
action was not successful.
Federated system users: You may have received this message
because you dynamically prepared an SQL statement in a
pass-through session and then tried to execute the statement
after the session was closed.
Check the message associated with the SQLCODE of the SQL
statement that failed. Follow the action suggested by that
For an invalid package, the REBIND command can be used to
recreate the error or to explicitly validate the package once the
cause of the error has been resolved.
For a failure while regenerating a view, the name of the view
that failed is recorded in the administration notification log.
The failing view can be dropped or a change made to the statement
or command that caused the view regeneration.
Federated system users: If the statement that failed was
dynamically prepared in a pass-through session, open another
pass-through session, write and prepare the statement again, and
execute it while the session is still open.
sqlcode : -727
sqlstate : 56098
Visit the new-look IDUG Website , register to gain access to the excellent content.
Apart from creation of global temporary table, I want to improve the performance of my query. Currently the query is using UNION as:
insert into SESSION.TEST (SELECT distinct
NMS_SEC_NUM = :mc__402
NMS_NMBRNG_SCHM = :mc__400
:mc__400 = 0
NMH_SEC_NUM = :mc__402
NMH_NMBRNG_SCHM = :mc__400
:mc__400 = 0
TNS_SEC_NUM = :mc__402
TNS_NMBRNG_SCHM = :mc__400
:mc__400 = 0
I have broken the abobe query to 3 individual SQL query that will insert the data in SESSION.TEST table. My question is:
1. Will it improve performance or should i stick to UNION query?
2. For table NMS_NUM_SCHM, should I create index on NMS_NMBRNG_SCHM and NMS_SEC_NUM or on NMS_NMBRNG_SCHM, NMS_SEC_NUM and NMS_SEC_ID ?
The same is applicable ofr table NMH and TNS also.