$HOME/.odbc.ini
theODBC.INIfile located in the user’s home directory
the file pointed to by theSYSODBCINIenvironment variable, if set
/var/TimesTen/instance/sys.odbc.ini
See "ODBCINI environment variable" in the for more information.
TT12003Cannot open user/ system odbc.ini fileUNIX only. TimesTen could not open either the user or systemODBC.INIfile.TT12004Syntax error in odbc.ini fileUNIX only. TimesTen en countered a syntax error while parsing the user or systemODBC.INIfile.TT12005Environment variable specified in the attribute is not setUNIX only. In either the user or systemODBC.INIfile, you have specified an attribute of the DSN with an environment variable that has not been set.TT12006Invalid attribute nameThe specified DSN attribute name isNULL, an empty string or not a valid attribute for a TimesTen data manager DSN. This error is also returned if the user or systemODBC.INIfile contains an inv alid attribute_name=value pair.TT12007The value of the attribute in the ini file is empty. It should not be emptyUNIX only. TimesTen DSN attributes are defined in the user or systemODBC.INIfile using a=pair. The value specified is either an empty string or white space.TT12008The length of the value-string in the ini file is too long for this attributeUNIX only. TimesTen DSN attributes are defined in the user or systemODBC.INIfile using a=pair. The length of the value specified exceeds the maxim um length allowed for the attribute.TT12009Specified DSN is not found in user and system odbc.ini files (or registry)On Windows, the DSN has not been defined as a user or system DSN using the ODBC Data Source Administrator. On UNIX, the DSN is not defined as a user or system DSN in aODBC.INIfile.TT12010Specified buffer is NULL or of 0-lengthThe buffer specified for returning a valu e is eitherNULLor the length of the buffer is 0.TT12011Specified buffer length is not big enough to hold the value for this attribute. Value truncated. The specified buffer length is less than the length of the requested DSN attribute value. TimesTen returns a truncated value.TT12012malloc() failedUnable to allocate memory for TimesTen internal data structures.TT12013Specified data store name is NULL or of zero length, or a client DSN was usedThe specified database name is eitherNULLor an empty string. You must specify a valid database name.TT12014Internal error in Ti mesTen utility library. Could not get current contextInternal error. Contact TimesTen Technical Support.TT12015Internal error in TimesTen utility libra ry. Could not set current contextInternal error. Contact TimesTen Technical Support.TT12016The number of seconds must be > 0The number of seconds for the RAM Grace Period must be greater than 0 seconds.TT12017Failed to allocate environment handleA call to the ODBCSQLAllocEnvfunction failed.TT12018Failed to allocate connection handleA call to the ODBCSQLAllocConnectfunction failed.TT12019Failed to locate data store filesTimesTen cannot determine the path and names of the database files for the s pecified database.TT12020Failed to connect to data storeA call to the ODBCSQLDriverConnectfunction failed to connect to the database using the specified connection string.TT12021Failed to disconnect from data storeA call to the ODBCSQLDisconnectfunction failed.TT12022Failed to free connection handleA call to the ODBCSQLFreeConnectfunction failed.TT 12023Failed to free environment handleA call to the ODBCSQLFreeEnvfunction failed.TT12024Data store already loaded into RAM and being managedA request to load a database into RAM failed because the database has already been loaded into RAM.TT12025Data store already manually unloaded from RAMA request to unload a database from RAM failed because the database has already been unloaded from RAM.TT12026The agent is already running for the data storeThe specified agent has already been started by th e TimesTen daemon.TT12027The agent is already stopped for the data storeThe specified agent has already been stopped by the TimesTen daemon.TT12028No r ecord of a data store in the location specified by the DataStore attribute of the DSN. Specified DSN may be a temporary data storeThe database does not exist in the location specified by theDataStoreattribute of the DSN.TT12030Data store is in useThe TimesTen daemon cannot perform. the requested operation because another application is connected t o the database.TT12032Invalid RamPolicy specifiedThe valid RAM Policy values are:TT_RAMPOL_MANUAL
TT_RAMPOL_ALWAYS
TT_RAMPOL_INUSE
TT12034RamPolicy cannot be set for temporary data storesRAM Policy can only be set for permanent databases.TT12035Could not initialize winsockWindows o nly. A call to WSAStartup failed.TT12036No winsock.dll (that supports version 1.1.) foundWindows only. A call toWSAStartupcould not locate awinsock.dllthat supports version 1.1.TT12037Could not terminate winsockWindows only. A call toW SACleanupfailed.TT12038Could not connect to TimesTen daemon on remote host Make sure that the TimesTen daemon is running on the remote host.TT12039Coul d not get port number of TimesTen replication agent on remote host. The replication agent may have either not been started or may have just been started and have not had time to communicate its port number to the TimesTen daemonMake sure that the TimesTen replication agent for the specified database is running on the remote host.TT12040Could not connect to TimesTen replication agent on remote hostInternal error. Contact TimesTen Technical Support.TT12041Host not foundTimesTen failed to determin e the IP addresses associated with the specified host name in the system’s/etc/hostsfile. Verify that you have correctly identified the host name, as described in "Configuring host IP addresses" in the .TT12042Cannot start transaction to perform. this operationInternal error. Contact TimesTen Technical Support.TT12043Unable to create temporary file nameInternal error. Contact TimesTen Technical Support.TT12044Transmission failure sendingTimesTen failed to transmit data to the remote TimesTen replication agent.TT12045Cannot create temporary fileInternal error. Contact TimesTen Technical Support.TT12046Transmission failure receivingTimesTen failed to receive data from the remote TimesTen replication agent.TT12047Data transmitted corruptThe type of response received from the remote TimesTen replication agent does not match the expected r esponse type.TT12048Error performing backup at sourceThis error can occur during a ttRepDuplicateEx operation when the backup operation on the source d atabase fails. See the verbose user error log on the source database for additional diagnostic information.TT12049Cannot write to temporary fileInternal error. Contact TimesTen Technical Support.TT12050Transaction commit for the swap operation failedInternal error. Contact TimesTen Technical Support.TT12052Replication scheme name too longMaximum length is 30 characters.TT12053Replication scheme owner too longMaximum length is 30 characters.TT12054Internal Error: Cannot determine useridInternal error. Contact TimesTen Technical Support.TT12055No changes needed to upgrade the replication schemaDuring upgrade, if the replication schema version of the old database is same as the current installation, no upgrade is required.TT12056Size values of local store must match that of the remote storeThePermSize,TempSizeandLogBuffSizeattributes of the local database do not match those of the remote database.TT12057Error creating temporary data storeFailed to cr eate a local database.TT12058Failed to read replication backup CTNFailed to read replication backup Commit Ticket Number.TT12059Deadlock/ TimeoutEither the operation caused a deadlock or the operation timed out.TT12060Invalid remote host specifiedA call to gethostbyname with the specified remote host name failed.TT12061Invalid local host specifiedA call to gethostbyname with the specified local host name failed.TT12062Failed to upgrade from unsupported versionUpgrade from this previous replication schema version is not supported.TT12063Cannot read from temporary fileInternal error. Contact TimesTen Technical Support.TT12064Failed to execute SQL command during updateInternal error. Contact TimesTen Technical Support.TT12065Multiple records of replication schema versionInternal error. Contact TimesTen Technical Support.TT12066Failed to compile commandInternal error. Contact TimesTen Technical Support.TT12067Failed to open cursorInternal error. Contact TimesTen Technical Support.TT12068Fai led to get next rowInternal error. Contact TimesTen Technical Support.TT12069Failed to get format handle of the SQL commandInternal error. Contact Time sTen Technical Support.TT12070Failed to get column informationInternal error. Contact TimesTen Technical Support.TT12071Failed to get column valueInternal error. Contact TimesTen Technical Support.TT12072Multiple definitions of replication store id for the specified data storeInternal error. Contact TimesTen Technical Support.TT12073Cannot determi ne my own store nameInternal error. Contact TimesTen Technical Support.TT12074Cannot determine my own hostnameInternal error. Contact TimesTen Technica l Support.TT12075Replication tables are from an earlier version. Consider using ‘ttRepAdmin -self -upgrade’ to upgradeThe specified operation is not allowed on replication schemes for older versions of TimesTen.TT12076Replication schema is later than TimesTen utility libraryThe specified operation is not allowed on replication schemes for new versi ons of TimesTen.TT12077Hostname is not set on this machineInternal error. Contact TimesTen Technical Support.TT12078Failed to rest is_local_storeIntern al error. Contact TimesTen Technical Support.TT12079Failed to set is_local_storeInternal error. Contact TimesTen Technical Support.TT12080No receiver found to swap withInternal error. Contact TimesTen Technical Support.TT12081Unsupported column type in upgradeInternal error. Contact TimesTen Technical Support.TT12082Failed to reset receiver CTNTi mesTen failed to reset receiver Commit Ticket Number.TT12083Found no source store ID in TTREP.REPLICATIONSInternal error. Contact TimesTen Technical Support.TT12084Call to gethostname() failedInternal error. Contact TimesTen Technical Support.TT12085No table found for table idInternal error. Contact TimesTen Technical Support.TT12086Ca nnot get information on tableInternal error. Contact TimesTen Technical Support.TT12087Cannot get format of tableInternal error. Contact TimesTen Techn ical Support.TT12088Multiple definitions of source store idInternal error. Contact TimesTen Technical Support.TT12089Cannot get column information of tableInternal error. Contact TimesTen Technical Support.TT12090Cannot get type mapping for columnInternal error. Contact TimesTen Technical Support.TT12091Cannot determine if version 2 replication ta bles existInternal error. Contact TimesTen Technical Support.TT12092Replication schema is not empty; cannot upgradeReplication schema must be empty for the upgrade operation.TT12093No count information returned from upgrade’s scan of TTREP.TABLESIntern al error. Contact TimesTen Technical Support.TT12094Cannot get count information from TTREP.TABLESInternal error. Contact TimesTen Technical Support.TT 12095Cannot update object idInternal error. Contact TimesTen Technical Support.TT12096Cannot set object idInternal error. Contact TimesTen Technical Support.TT12097Cannot get column values from TTREP.PEERInternal error. Contact TimesTen Technical Support.TT12098Failed to determine correct write LSN for TTREP.REPPEERS.SENDLSNInternal error. Contac t TimesTen Technical Support.TT12099Multiple schemes found. Must specify -scheme to identify which replication scheme to useMultiple replication scheme s found.TT12100Cannot create replication table definitionInternal error. Contact TimesTen Technical Support.TT12101Cannot start transaction to check replication schema versionInternal error. Contact TimesTen Technical Support.TT12102Failed to commit transaction for checking replication schema versionInternal error. Contact TimesTen Technical Suppor t.TT12103Cannot get column value from TTREP.REPELEMENTS tableInternal error. Contact TimesTen Technical Support.TT12104Cannot find write LSNInternal er ror. Contact TimesTen Technical Support.TT12105Failed to update LSNInternal error. Contact TimesTen Technical Support.TT12106Cannot set new replication hold LSNInternal error. Contact TimesTen Technical Support.TT12107Deleting table definition info failedInternal error. Contact TimesTen Technical Support.TT12108Invalid policy ” specified. Must b e The policy value supplied to the built-in procedure must be of the values in the valid_policy_list. Refer to the documentation on each specific built -in procedure for a description of its valid policy values. See "Built-In Procedures" in .TT12109Syntax error in connection stringThere is a syntax error in the specified connection string. Correct the connection string and try connectin g again.TT12110Neither DSN= nor DRIVER= attributes are present in the connection stringThe connection string must contain either aDSNorDRIVERattribute. TT12111Signal receivedThe application received a signal and terminated.TT12114Version mismatch between the backup files and restore. Backed-up files are version ; ttRestore is version The restore operation failed because the backup files were created by a different version of TimesTen than the ttRestore utility u sed.TT12116Cannot create database for restoreInternal error. Contact TimesTen Technical Support.TT12117Disconnect from newly created database failedInt ernal error. Contact TimesTen Technical Support.TT12119Cannot open destination fileFailed to open database file while restoring from stream input.TT12120Insufficient bytes read from input streamInternal error. Contact TimesTen Technical Support.TT12125Bad data store file header read from input streamVerify that the stream input is valid.TT12132Er ror forming basename of data storeFailed to create a file name from theDataStoreattribute of the DSN.TT12133Data store file already existsA database fi le with the same name as indicated by theDataStoreattribute of the DSN already exists.TT12134Log file(s) already existLog file(s) with the same name as indicated by theDataStoreattribute of the DSN already exists.TT12135Failed to delete data store files; OS-detected error: Internal error. Contact TimesTen Technical Support.TT12136Error while deleting log filesInternal error. Contact TimesTen Technical S upport.TT12148Specified connection string is NULL or of 0-lengthThe connection string argument passed is eitherNULLor an empty string. You must specify a valid connection string argument.TT12150Cannot start transaction to update receiver CTN in TTREP.REPPEERSInternal error. Contact TimesTen Technical Support.TT12151Failed to commit TimesTen transaction for updating receiver CTNInternal error. Contact TimesTen Technical Support.TT12152Cannot set timestamp column for tableInternal error. Contact TimesTen Technical Support.TT12153Cannot get DS_OBJ_ID value from TTREP.REPELEMENTSInternal error. Contact TimesTen Technical Support.TT12154Cannot get TBLID value from SYS.TABLESInternal error. Contact TimesTen Technical Support.TT12155Cannot get row id for row in TTREP.REPELEMENTSInternal error. Contact TimesTen Technical Support.TT12156Too many tables found on second passInternal error. Contact TimesTen Technical Support.TT12157Failed to update the table IDs from the mapping we’ve createdInter nal error. Contact TimesTen Technical Support.TT12158Cannot set replication fields in SYS.TABLESInternal error. Contact TimesTen Technical Support.TT12 159NULL passed for a pointer argumentThe pointer argument must be a non-NULLvalue.TT12160Timeout – the agent is still startingUnder some conditions, you may receive this error when trying to stop the cache agent for a database while the agent is starting up. Retry the operation.TT12161Cannot backup temporary data storesBackup is not allowed for temporary databases.TT12164RamGrace cannot be set for temporary data storesttAdmin-ramGracecan only be s et on a permanent database.TT12166Failed to start BackupThe replication agent ran into an error while running thettBackuputility on the subscriber database or when runningttRepAdmin-duplicateconcurrently on more than one database. Run thettBackuputility on the subscriber with replication disabled, or avoid running two duplicate operations concurrently.TT12184Could not initialize connection to TimesTen daemonInternal error. Contact TimesTen Techn ical Support.TT12185No definitions of replication store id for the specified data storeInternal error. Contact TimesTen Technical Support.TT12186fstat() system call failed for user/system odbc.ini fleInternal error. Contact TimesTen Technical Support.TT12187read() system call failed for user/ system odbc.ini fileInternal error. Contact TimesTen Technical Support.TT12188close() system call failed for user/system odbc.ini fileInternal error. Contact TimesTen Technical Support.TT12189Scan stopped for user/ system odbc.ini fileInternal error. Contact TimesTen Technical Support.TT12190Attribute name is too longMaximum length of attribute names is 30 charact ers.TT12191Invalid length for connection stringThe value specified for the length of the connection string to theSQLDriverConnectODBC call is less than 0 and not equal toSQL_NTS.TT12192Invalid backup typeAn invalid value was passed as the type parameter of thettBackuputility library function. See "ttBackup" in the TT12193No backup directory specifiedA null pointer or em pty string was passed as thebackupDirparameter of thettBackuputility library function. See "ttBackup" in the .TT12194Failed to retrieve data store informationInternal error. Contact TimesTen Technical Support.TT12195Basename contains invalid charactersA n invalid value was passed as thebaseNameparameter of thettBackuputility library function. See "ttBackup" in the TT12196Backup status file not foundNo backup status file was found for the given backup directory and/or base name. See "ttBackup" in the .TT12197Existing backup files do not match data storeThe backup files indicated by the given backup directory and/ or base name are not from the database that is being backed up.Causes for the mismatch include:These backup files can be overwritten by specifying a no n-atomic backup. See "ttBackup" in the .The database that is stored in the backup files has a different database path name than the database that is being backed up.
The database being backed up has the same database path name as the database that is stored in the backup files, but the two databases do not have the same creation time. This can happen if the backed up database was destroyed and a new database was created with the same database path name.
TT12198One or more files missing from backup directoryOne or more backup files are missing from the backup indicated by the given backup directory and/ or base name. See "ttBackup" in the .TT12199Cannot read directory contents; OS-detected error: The contents of the backup directory could not be read due to an operating system error. See "ttBackup" in the .TT12200Failed to open backup status file: OS-detected error: The backup status file for the backup indicated by the backup directory and/ or base name could not be opened due to an operating system error. See "ttBackup" in the .TT12201Failed to read backup status file: OS-detected error: The backup status file for the backup indicated by the backup directory and/or base name could not be read due to an operating system error. See "ttBackup" in the .TT12202Failed to write backup status file: OS-detected error: The backup status file for the backup indicated by the backup directory and/ or base name could not be written due to an operating system error. See "ttBackup" in the .TT12203Failed to close backup status file: OS-detected error : The backup status file for the backup indicated by the backup directory and/or base name could not be closed due to an operating system error. See "ttBackup" in the .TT12204Invalid or corrupted backup status fileThe backup status file for the backup indicated by the backup directory and/ or base name is invalid or corrupt. See "ttBackup" in the .TT12205Backup is incompleteThe backup status file for the backup indicated by the backup dir ectory and/or base name is incomplete. See "ttBackup" in the .TT12206Backup control information corrupted or incomplete (may indicate TimesTen version mismatch)The backup status information for the backup indicated by the backup directory and/or base name is corrupted or incomplete. See "ttBackup" in the .TT12207Failed to write backup status record; OS-detected error: Backup status information for the backup indicated by the given backup directory and/ or base name could not be written due to an operating system error. See "ttBackup" in the .TT12208Failed to retrieve file information; OS-detected error: An attempt to retrieve information about one or more of the backup files indicated by the backup directory and/ or base name failed due to an operating system error. See "ttBackup" in the .TT12209Failed to open file ; OS-detected error: One or more of the backup files indicated by the backup directory and/ or base name could not be opened due to an operating system error. See "ttBackup" in the .TT12210Failed to read backup file; OS-detected error: One or more of the backup files indicated by the backup directory and/ or base name could not be read due to an operating system error. See "ttBackup" in the .TT12211Backup file is shorter than expectedOne or more of the b ackup files indicated by the given backup directory and/or base name have been truncated. See "ttBackup" in the .TT12212Failed to write backup file; OS-detected error: One or more of the backup files indicated by the backup directory and/ or base name could not be written due to an operating system error. See "ttBackup" in the .TT12213Failed to close backup file; OS-detected error: One or more of the backup files indicated by the backup directory and/ or base name could not be closed due to an operating system error. See "ttBackup" in the .TT12214Failed to rename backup file; OS-detected error: One or more of the backup files indicated by the backup directory and/ or base name could not be renamed due to an operating system error. See "ttBackup" in the .TT12215Backkup terminated because data store connection inva lidatedThe requested backup operation was terminated because the database connection was terminated. See "ttBackup" in the .TT12216Invalid restore type An invalid value was passed as the type parameter of thettRestoreutility library function. See "ttRestore" in the .TT12217Cannot restore into a temporary data storeA temporary database cannot be the target of a database restore operation. See "ttRestore" in the .TT12218Could not get port number of TimesTen Server. Make sure that it is runningGenerally, the TimesTen Server is automatically started by the TimesTen daemon. Upon start up, the TimesTen Server lets the daemon know the port number that the Server is listening on. This error indicates that there was a problem starting the TimesTen Server. Hence, the daemon does not know the port number of the TimesTen Server. Refer to the daemon/ server log for further details.TT12219Failed to connect to TimesTen Server. Refer to user error log for further detailsA socket connection to the Times Ten Server failed. Refer to the daemon/server log for further details.TT12220Failed to send request to TimesTen ServerA socketsendcall failed. Normally, this is accompanied with a description of the OS error.TT12221Platform. mismatch between backed-up files and ttRestore. Backed-up files are ; ttRestore is Files can only be restored on the same platform. type where they were backed up.TT12222Backed-up files appear to be from a TimesTen releas e prior to TimesTen 5.0Files that were backed up using a TimesTen release prior to 5.0 cannot be restored using this TimesTen release’s utilities.TT122 31Failed to truncate tablesA problem occurred during the execution of the ttRepAdmin-duplicateutility with the-truncateoption.TT12232Failed to drop objectsA problem occurred during the execution of ttRepAdmin-duplicateutility with the-dropoptionTT12233Failed to truncate tableSpecifies the table that had the problem referred to in error 12231.TT122 34Failed to drop tableSpecifies a table that was referred to in error 12232.TT12235There are identifiers supplied for the drop option which are also qu oted for the truncate optionThe ttRepAdmin-duplicateutility tries to drop and truncate the same table or tables with the-dropand-truncateoptions.TT12236There are duplicate identifiers specified in the drop optionThe same table is listed twice for the-dropoption ofttRepAdmin -duplicate.TT12237There are duplicate identifiers specified in the trunca te option.The same table is listed twice for the-truncateoption ofttRepAdmin -duplicate.TT12238For -truncate or -drop you can specify "ALL" or a list o f tables, not both.For the-truncateor-dropoptions of thettRepAdmin -duplicateutility, you can specify "ALL" or a list of tables, but you cannot specify both in the same statement.TT12245No definitions of replication store id for the data store on Arguments passed during database duplication are not consistent with store definitions on the source database.TT12246DSN exceeds the maximum length of A database name cannot exceed 3 2 characters.TT12247A sequence cannot be truncatedOccurs when the name of a sequence is supplied to the-truncateoption ofttRepAdmin-duplicateor tottRepDuplicateEx.TT12248RamGrace cannot be specified with always or manual RAM policyWhen setting the RAM residence policy for a database, a grace period can be used only with theinUsepolicy.TT12249The remoteDaemonPort can only be 0 or between 1024 and 65535Reset the value of thettRepAdmi n -duplicate -remoteDaemonPortoption to a value specified in the error message.TT12250The duplicate verbosity level must be 0, 1, or 2Acceptable values for thettRepAdmin -duplicate -verbosityoption are 0, 1 or 2.TT12251The duplicate verbosity level must be 0, 1, or 2Acceptable values for thettRepAdmin -duplicate -verbosityoption are 0, 1 or 2.TT12252Could not check Oracle DBAn additional error message from the cache layer accompanies this message. Review that message to determine the problem and fix.TT12253The Active Standby Oracle Database is the same as the DR Oracle databaseWhen thettRepAdmin -duplicate -initCacheDRoption is used the DR Oracle database cannot be the same database as the active standby Oracle subscribing database. The check has identified att_03_reppeersentry which is from one of the Active Standby master stores to the DR Oracle Database. Reconfigure the data recovery to resolve this conflict.TT12254Remote peer does not support parallel replication.There is a mismatch in the parallel replication configuration between two stores involved in a replication scheme, where one store is enabled for parallel replication and the other is not.TT12255A/ S pairs cannot be created when parallel mode replication configured.Active Standby Pair replication schemes are not configured while the database has been created with parallel replication attributes, with theReplicationApplyOrderingattribute configured greater than 0.TT12257Error creating bookmarks for the parallel tracks.Internal error. Tried to cr eate entries inTTREP.REPPEERSfor parallel replication tracks. When parallel replication is enabled, there are more than one TTREP.REPPEERS entry for master->subscriber. The number of entries is dependent upon theReplicationParallelismparameter.TT12258 Return Receipt or Return TwoSafe cannot be used when parallel mode replication is configured.Return Receipt and Return Twosafe cannot be used for a ret urn service when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0.TT12259A store cannot be defined as a PROPAGATOR when parallel mode replication is configu red.Propagator stores are not supported when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0.TT12260Create cache group is not permitted when parallel mode replication is configured.Ca che groups are not supported when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0.TT12261ALTER TABLE is not permitted on a replicated table when parallel mode replication i s configured.ALTER TABLEis not allowed when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0. This error is raised at application time.TT12262Error setting track for connection.Intern al Error. The replication agent cannot use a specific track for its database connection.TT12263Aging is not permitted on a replicated table when parall el mode replication is configured.In 11.2.1.6.0, aging on tables was allowed whenReplicationApplyOrderingwas set to 1. Currently, we disable aging whenReplicationApplyOrderingis set to 1. When a database withReplicationApplyOrderingset to 1 is upgraded from 11.2.1.6.0, aging will be disabledTT12264ALTER TABLE cannot be replicated to a store with parallel mode replication enabled.This error occurs if the replication ag ent detectsALTER TABLEwhen parallel mode replication is enabled.TT12274Failed to read track entries for peer.This is an internal error that is returned if the transmitter could not read metadata fromttrep.reppeers. Contact TimesTen Technical Support.TT12275Failed to convert replicated XLA bookmarks to non-replicated for read only subscriberThis error is returned after ttRepAdmin -duplicate processing. When a read-only subscriber is created with the -duplicate qualifier, TimesTen modifies replicated bookmarks to non-replicated.
This error is returned if there is a problem modifying the bookmarks.TT12700NLSRTL environment could not be initializedThe NLS data files could not be located. The installation directory may have been corrupted or become unreadable.TT12701DatabaseCharacterSet attribute required for data store creation . Refer to the TimesTen documention for information on selecting a character set.You must specify a value for theDatabaseCharacterSetattribute when creating a database. The database character set cannot be changed after database creation. For more details on selecting a database character set, see "Choosing a database character set" in the .TT12702Unable to load NLS data from A particular NLS data file could not be located. The installation directory may have been corrupted or become unreadable. could be a character set name or a sort name.TT12705Invalid session parameterThe session para meter is unknown or unsupported by TimesTen. For example:ALTER SESSION SET NLS_BOGUS=’french’;
returns
12705: Invalid NLS session parameter
TT12706Invalid session parameter value.The value supplied for the session parameter is unknown or unsupported by TimesTen. or example: ALTER SESSION SET NLS_SORT=’bogus’; returns
12706: Invalid NLS session parameter valueTT12707Linguistic index maximum key value length limit exceededThe value computed for the linguistic index ke y exceeds the maximum length allowed for that index. There is a 64k upper limit for linguistic index key values.TT12708Conversion of TIMESTEN8 characte r set data is not allowedAn operation either explicitly or implicitly tried to convertTIMESTEN8data to another character set. Conversion ofTIMESTEN8character data is undefined and therefore not allowed.TT12713Character data loss in NCHAR/ CHAR conversionNLS_NCHAR_CONV_EXCPwas set toTRUEand a conversion was attempted for anNCHARcharacter having no corresponding mapping in the database cha racter set.TT12714NLSSORT computation failed due to invalid characters in stringThe string passed to theNLSSORTfunction contained invalid characters fo r the given character set. A meaningfulNLSSORTresult value could not be computed. Character data containing invalid characters is of dubious usefulness and should be eliminated from the database.TT12715NLS_SORT value must be BINARY when database character set is TIMESTEN8When the database character set isTIM ESTEN8, the only setting allowed forNLS_SORTisBINARY. Non-binary comparison rules forTIMESTEN8data are undefined.TT12716” must be followed by four hexadecima l characters or another ”TheUNISTRfunction argument allows the back-slash character only as an escape for a hexadecimal Unicode character or itself. For example: UNISTR(‘0041’) UNISTR(‘abc
op’)TT12717Character data loss in character set conversionThis is a warning. During character set conversion of data, a character was encountered for which no valid conversion exists. TimesTen substituted a replacement character in its place. You should change your con nection character set to one that is compatible with the database character set in use.TT12718Error setting default date/ timestamp format Contact TimesTen Technical Support.TT12719Error in conversion of NCHAR to ASCIIIf you attempt to convert the NCHAR type to either the DATE type or numeric type, TimesTen first converts the NCHAR type to ASCII. There was an error when TimesTen attempted to convert NCHAR TO ASCII. Check the data for your NCHAR ty pe.TT13000License file file_name does not exist.TimesTen cannot locate the evaluation license file.TT13001License file file_name unreadable.TimesTen ca nnot read the evaluation license file.TT13002License key in file_name is invalid.Invalid evaluation license.