<< Click to Display Table of Contents >>   Oracle Databases

This is a list of all possible errors that may occur when testing a connection to this type of Database.

 

Error = ORA-01017: invalid username/password; logon denied

 

Possible cause

Message generated on application log when password or user name is wrong.

 

Solution

Check if this user exists and if password is correct.

 

Error = ORA-12154: TNS: could not resolve the connect identifier specified

 

Possible cause

This client connection was not found.

 

Solution

Check if this connection exists on the computer and if it is working using one of the network utilities provided by Oracle.

 

Error = ORA-02264: name already used by an existing constraint

 

Possible cause

There is already a Database object with this name.

 

Solution

To prevent this error, create and configure different index or primary key names in Elipse E3.

 

Error = ORA-01403: no data found

 

Possible cause

This message is generated when an internal Elipse E3 Query searches for Database objects and does not find them. For example, a Historic table does not exist, thus it must be created.

 

Solution

This is considered an error only if it persists on application logs.

 

Error = ORA-00001: unique constraint (SYSTEM.E3INDEX) violated

 

Possible cause

Whenever there is an attempt to write a record where a field defined as the primary key has a duplicated value, this writing is refused and this message is displayed. Note that a key name is displayed, in this case, SYSTEM.E3INDEX key, as User.KeyName. Depending on the project, this error is expected, but most of the time it is important to check if this key is adequate. These two cases illustrate that situation:

•Power Measurement Systems: Aiming to store all data from a single day, routines used for collecting admit upper and lower tolerances in their timestamps for the collecting process. Thus, some records must be written more than once. In this case, this error is expected

•Alarm maintenance: For this case, there may have been more than one error per second on an application. If the E3TimeStamp field is used as a primary key, there may have been losses of some alarm occurrences, which may lead to a misinterpretation of events. In this case, rethinking a primary key can be the adequate solution

 

Solution

There are two ways to solve this issue:

1.Users must create a unique index for these key fields.

2.Users must check that application, so that it does not send repeated key values for recording.