‘ORA-00022: invalid session ID; access denied’ error message when running AE

Some processes may end in “No Success” and encounter the following error message ‘ORA-00022: invalid session ID; access denied’.If one sets a trace on this processes one may notice that the error is caused by a call of the standard function GetNextNumberWithGapsCommit.
To avoid this situations from appearing in a PeopleSoft environment, a recommendation would be to set the following “DbFlags” value in the psprcs.cfg (Process Scheduler configuration file) an psappsrv.cfg (Application Serverconfiguration file) to 8:
;DbFlags Bitfield
;
; Bit Flag
; — —-
; 1 – Ignore metaSQL to update database statistics(shared with COBOL)
; 2 – not yet allocated
; 4 – Disable Second DB Connection
; 8 – Disable Persistent Secondary DB Connection
; 16 – not yet allocated
; 32 – not yet allocated
; 64 – not yet allocated
; 128 – not yet allocated
; 256 – not yet allocated
DbFlags=8

This way the second database connection which is opened automatically by the GetNextNumberWithGapsCommit function, will not be a persistent one.
According to the Peoplebooks – System and Server Administration (http://www.oracle.com/applications/peoplesoft/tools_tech/ent/ptools/peoplebook-system-and-server-administration.pdf) the difference between ‘0’ and ‘8’ is that in second situation, the second database connection will be immediately closed after the call of GetNextNumberWithGapsCommit function.