We successfully capture snapshots across all our environments when the data being collected is average size. However, when we capture snapshots for User Entitlements or Account Details where the data collected is quite large, the task fails trying to write the completion status on the imreport6 table. This happens on all environments as well. We have attached a screenshot of the error. If we go into SQL Developer and change the status from In Progress to Completed we can request the report successfully.
Release : 14.3, 14.4
Component : IdentityMinder(Identity Manager)
I have received an update from the customer that this issue has been resolved in the customer's environment.
The customer had to increase the idle timeout to the object store to 30 minutes.
In an OOTB environment this is unlimited, but usually tightened in production environments for security
We found the following Oracle Error
17:46:43,976 ERROR [ims.jdbc.JDBCSchema] (Thread-334) Unable to run test statement: java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again
17:47:39,713 ERROR [com.netegrity.ims.imrexport.object.RDBCollector] (Thread-334) ["User Entitlements Report Snapshot","Prt01"] Error inserting values into table "imrgroup6"
Also we found a network layer connection issue, connection to runtime database, repetitively until the bottom of the log (until 20:32:11,886 as far as I get in the log file). This issue is separate from the above report snapshot issue.
Caused by: java.net.ConnectException: Connection timed out
at sun.nio.ch.Net.connect0(Native Method) [rt.jar:1.8.0_201]
at sun.nio.ch.Net.connect(Net.java:454) [rt.jar:1.8.0_201]
at sun.nio.ch.Net.connect(Net.java:446) [rt.jar:1.8.0_201]
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648) [rt.jar:1.8.0_201]
at java.nio.channels.SocketChannel.open(SocketChannel.java:189) [rt.jar:1.8.0_201]
at oracle.net.nt.TimeoutSocketChannel.(TimeoutSocketChannel.java:81) [ojdbc8.jar:]
at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:169) [ojdbc8.jar:]
... 32 more
This is environmental issue and not product defect. The following suggestion given to resolve Oracle error.
Please refer https://community.oracle.com/thread/547168
Customer needs to check which profile the Oracle user (eup_imstore) is using.
select username,PROFILE from dba_users where username='USER ID IN DATASOURCE';
Then customer needs to check what the limits for that profile are.
select RESOURCE_NAME,LIMIT from dba_profiles where profile='DEFAULT' and resource_name='IDLE_TIME';
This should be tuned. Please work with your DBA and reference the above oracle community thread.