Getting EID_DBAPP_INSERT_LOGINID(301200172) Error When Logging into Argus Safety Application (Doc ID 2190271.1)

Last updated on OCTOBER 05, 2016

Applies to:

Oracle Argus Safety - Version 7.0.0 to 8.0.1 [Release 7.0.0 to 8.0]
Information in this document applies to any platform.

Symptoms

Getting the error (EID_DBAPP_INSERT_LOGINID(301200172)) when logging into the Argus Safety application

The following errors are observed in different logs:

1. Observed the following error in the SQLTimes log: SQL_TIMES_04-Oct-2016-00_1436_100084.TXT

04-Oct-2016, 00:59:48 >> ARGUS_LOGIN 0.11 Comment P_ZULU_HOURS set to Invalid DateTime
04-Oct-2016, 00:59:49 >> ARGUS_LOGIN 0.06 UPDATE CMN_USER_LOGIN SET deleted = sysdate where USER_ID = :P_USER_ID and deleted is null and login_id <> 1
04-Oct-2016, 00:59:49 >> ARGUS_LOGIN 0.00 select * from dual
04-Oct-2016, 00:59:49 >> ARGUS_LOGIN 0.01 Comment P_ERROR_TEXT set to Oracle error -1 occurred.
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
SQL: INSERT INTO CMN_USER_LOGIN (LOGIN_ID, USER_ID, login_time) VALUES (:P_LOGIN_ID, :P_USER_ID, to_date(:P_ZULU_HOURS, 'YYYY/MM/DD HH24:MI:SS'))

2. Observed the following error in argus log:Argusvr2.Argusvr2.D[2016-10-04].T[00-59-42].P[01436].log

[EnterpiseID: 1] 04-Oct-2016, 00:59:49:182, [3], UserId: xxxxxx, Exception DetailsMessage
Error:-1; What: ORA-01841: (full) year must be between -4713 and +9999, and not be 0
Stack Trace


[EnterpiseID: 1] 04-Oct-2016, 00:59:49:417, [3], UserId: xxxxxxx, Exception DetailsMessage
Error:-1; Oracle error -1 occurred.
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
SQL: INSERT INTO CMN_USER_LOGIN (LOGIN_ID, USER_ID, login_time) VALUES (:P_LOGIN_ID, :P_USER_ID, to_date(:P_ZULU_HOURS, 'YYYY/MM/DD HH24:MI:SS'))
Stack Trace


3. Observed the following error in cmn_error_log starting 04th Oct 2016:

"Argus Safety.COM :- Oracle error -1 occurred.
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
SQL: INSERT INTO CMN_USER_LOGIN (LOGIN_ID, USER_ID, login_time) VALUES (:P_LOGIN_ID, :P_USER_ID, to_date(:P_ZULU_HOURS, 'YYYY/MM/DD HH24:MI:SS'))"

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