E1: UPGTC: Table Conversions Failing In Creating FnnnTCTEMP Tables - AS400 iSeries platform (Doc ID 1592323.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

Issues creating FnnnTCTEMP tables, as well as failing to find or describe tables.  Issue is temporarily resolved after rebuilding the SQL cross reference tables. TC Job Log from iSeries:

CPF327E    Diagnostic              40   10/10/13  16:06:48.665507  QDBCRTFI     QSYS        *STMT    QSQCRTT     QSYS        *STMT

                                     From user . . . . . . . . . :   JDE

                                     From module . . . . . . . . :   QDBCRTFI

                                     From procedure  . . . . . . :   SEND_PMSG

                                     Statement . . . . . . . . . :   41408

                                     To module . . . . . . . . . :   QSQCRTT

                                     To procedure  . . . . . . . :   QSQCRTT

                                     Statement . . . . . . . . . :   11558

                                     Message . . . . :   Alternative name for file Fnnnn0001 not allowed.

                                     Cause . . . . . :   An attempt was made to create, move, or change database file Fnnnn0001 with alternative name FnnnnTCTEMP into library PRODDTA. However, the operation was not done for reason code 3.  The reason codes are: 1 - The alternative name is not a valid database alternative name. 2 - The alternative name is a duplicate of the alternative name for database file *N that already exists in library PRODDTA. 3 - The alternative name could not be verified as a duplicate of other file's alternative names in library PRODDTA because of problems with the system cross reference files. 4 - Only one alternative name is allowed. 5 - Alternative name  was not found. 

                                     Recovery  . . . :   Do the following for the specified reason code: 1 - Change the alternative name to a valid database alternative name. 2 - Change the alternative name or the library name on the command so that the alternative name will not be a duplicate of another file's alternative name. 3 - Try the operation again.  If the operation fails again with this message and reason code, run reclaim storage (RCLSTG SELECT(*DBXREF)) to update the system cross reference files. 4 - Report this problem using the Analyze Problem (ANZPRB) command. 5 - Report this problem using the Analyze Problem (ANZPRB) command.

 

Changes

New LPAR set up for Production Upgrade.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms