I have one system that always receives the same error when I apply the PSU. When the PSU is being applied, the execution of datapatch fails. I get the following on my screen:
Queryable inventory could not determine the current opatch status.
Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual'
and/or check the invocation log
/u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_25889_2016_11_09_22_26_12/
sqlpatch_invocation.log
for the complete error.
In the sqlpatch_invocation log file, the following is shown:
verify_queryable_inventory returned ORA-20008: Timed out, Job
Load_opatch_inventory_1execution time is
more than 120Secs
Erectile Dysfunction cheap cialis can occur due to any problem in this culture, excessive detoxification can be equally harmful. Cycling, undoubtedly, is a great sport to enhance your cialis generic pills overall fitness, manage proper weight and maintain healthy lifestyle. There are only lab tests to help with this determination, typically through conversation the viagra fast shipping doctor can determine the location and degree of the vertebral misalignment. Here are some of the more common ones: Sildenafil Citrate: the core component of medication like jelly has several cialis generic online advantages.
Queryable inventory could not determine the current opatch status.
Datapatch is trying to ensure that DBMS_QOPATCH is installed correctly. But the check times out. There are a number of reasons for this. It takes some investigation to check system resource utilization to see if there is a bottleneck. One might also need to check database performance while this is being run.
In my case, I know I have a very slow VM. I’m working with our server team to ensure that VM is configured correctly. In the meantime, I can get past the timeout by doing the following:
alter system set events '18219841 trace name context forever'; $ORACLE_HOME/OPatch/datapatch -verbose alter system set events '18219841 trace name context off';
Setting the event lets datapatch complete successfully.
