amHistory table produces errors

  • KM03107431
  • 01-Mar-2018
  • 01-Mar-2018

This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.

Summary

DBA ran statistics of the Oracle schema and increased Logging space, and the database ran much more efficiently.

Question

amHistory table records cannot be read from AM screens - Oracle error 03113 
When performing a Production conversion to AM9.60. After performing the Migration and Conversion utilities, clicking on the History tab of any record produces a hung client. Closing the window creates a Windows dialogue asking to Restore, Close, or wait for Windows to respond. Selecting “Close” produces a pop-up window showing the Oracle errors associated with accessing the amHistory table.
Error Messages:
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Oracle error: ORA-03113: end-of-file on communication channel
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Oracle error: Process ID: 40567202
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Oracle error: Session ID: 128 Serial number: 891
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) SQL statement 'SELECT H1.lHistoryId, H1.Field, H1.dtLastModif, H1.PreviousVal, H1.memPreviousCmt FROM amHistory H1 WHERE H1.lHistObjId = :1 AND H1.HistObjTable = :2 AND DECODE(Nvl(:3,:4), ' ', Nvl(H1.Field,:5), '') = Nvl(H1.Field,:6) AND DECODE(0, 0, H1.lAuthorId, 0) = H1.lAuthorId AND DECODE(Nvl(:7,:8), to_date('19000101','YYYYMMDD'), (H1.dtLastModif+:9), to_date(NULL)) <= H1.dtLastModif AND DECODE(Nvl(:10,:11), to_date('19000101','YYYYMMDD'), (H1.dtLastModif+:12), to_date(NULL)) >= H1.dtLastModif ORDER BY H1.lHistoryId' could not be executed
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 0='337869'
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 1='amComputer'
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 2=''
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 3=' '
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 4=' '
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 5=' '
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 6=''
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 7='1/1/1900'
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 8='-1'
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 9=''
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 10='1/1/1900'
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Parameter 11='1'
2018/02/03 20:13:50.000 0 1 [Thrd#:4392](0) Unable to access table 'History (amHistory)'.

Answer

Customer reported an issue with amHistory table records, it cannot be read from AM screens - Oracle error 03113 - Informed that DBA ran statistics of the Oracle schema and increased Logging space, and the database ran much more efficiently.
Customer is running Asset Manager 9.60 on a Windows 2012 R2 server and an Oracle 12c database.