We are currently seeking help on the autosys issue described below, so that we can resume running our autosys batch jobs without manual intervention.
On April 2018, an AIX 5.2 WPAR was installed on AIX 7.1.
Since the hardware virtualization application batch jobs scheduled in autosys are hanging when a new container is invoked to run. The problem is intermittent and jobs resume running when resubmitted manually.
AIX 5.2 Versioned WPAR Runtime 126.96.36.199
AIX 7.1 TL4 SP4 on the AIX host.
In log file SSAIX02:/autosysprd01/autotree/autouser/out/event_demon.*** the following Oracle error was found:
May 24th (Autsys Log)
[03:53:48.0979]  -- ORACLE error --
[03:53:48.0979]  ORA-01115: IO error reading block from file 5 (block # 2466) ORA-01110: data file 5: '/oradataprd03/PRD02/data01.dbf' ORA-27091: skgfqio: unable to queue I/O IBM AIX RISC System/6000 Error: 5: I/O error
[03:53:48.0980]  Processing OCI function not used (4)
Steps taken to resolve the issue.......
No errors in the Oracle alert log. Database review shows no issues with the database.
DB verify was clean.
DBVERIFY: Release 188.8.131.52.0 - Production on Thu May 24 11:58:54 2018
(c) Copyright 2000 Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE = /oradataprd03/PRD02/data01.dbf
DBVERIFY - Verification complete
Total Pages Examined : 38400
Total Pages Processed (Data) : 20980
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 0
Total Pages Failing (Index): 0
Total Pages Processed (Other): 38
Total Pages Empty : 17382
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Disk controller not reporting any errors,
Referenced Oracle Knowledge Article ( Doc ID 559697.1 ) : ORA-01115 ORA-01110 ORA-27091 ORA-27072 Error: 5: I/O error
Increased maxreqs to a value greater than or equal to 8192. (NOTE: Values that fixed the errors: 8192, 16384 or 32768.)
The "MAXREQS" value currently set at 4096 was changed to 16384 and the server rebooted to take effect.
The Oracle database and the autosys software was restarted as part of the normal reboot procedure.
Moved the datafile to a different filesystem.
Despite the aforementioned troubleshooting the problem still exists (same error message).
All recommendations with regards to this issue are greatly appreciated