Queryable inventory could not determine the current opatch status.

By -
[oracle@Testing02 OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Fri May 15 15:54:19 2020
Copyright (c) 2012, 2019, Oracle.  All rights reserved.

Log file for this invocation: /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log

Connecting to database...OK
Bootstrapping registry and package to current versions...done

Queryable inventory could not determine the current opatch status.
Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual'
and/or check the invocation log
/testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log
for the complete error.
Prereq check failed, exiting without installing any patches.

Please refer to MOS Note 1609718.1 and/or the invocation log
/testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_29313_2020_05_15_15_54_19/sqlpatch_invocation.log
for information on how to resolve the above errors.

SQL Patching tool complete on Fri May 15 15:54:25 2020



After checking we found:

[oracle@Testing02 OPatch]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Fri May 15 15:56:10 2020

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> select dbms_sqlpatch.verify_queryable_inventory from dual;

 VERIFY_QUERYABLE_INVENTORY
--------------------------------------------------------------------------------
ORA-20001: Latest xml inventory is not loaded into table

 SQL> select * from OPATCH_XML_INV ;
ERROR:
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-25153: Temporary Tablespace is Empty



no rows selected



Solution:

SQL> select file_name,bytes/1024/1024/1024 from dba_temp_files;

 no rows selected
SQL> alter tablespace TEMP add tempfile '/Testprod_data/oradata/Testprod/tempfile/temp01.dbf' size 20G;

 Tablespace altered.

SQL> exit


[oracle@Testing02 tempfile]$ cd $ORACLE_HOME/bin
[oracle@Testing02 bin]$ cd ../OPatch
[oracle@Testing02 OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Fri May 15 15:59:31 2020
Copyright (c) 2012, 2019, Oracle.  All rights reserved.

Log file for this invocation: /testing/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_31032_2020_05_15_15_59_31/sqlpatch_invocation.log

Connecting to database...OK
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of SQL patches:
Bundle series DBRU:
  ID 200114 in the binary registry and not installed in the SQL registry

Adding patches to installation queue and performing prereq checks...
Installation queue:
  Nothing to roll back
  The following patches will be applied:
    30593149 (DATABASE JAN 2020 RELEASE UPDATE 12.2.0.1.200114)

Installing patches...
Patch installation complete.  Total patches installed: 1

Validating logfiles...
Patch 30593149 apply: SUCCESS
  logfile: /testing/app/oracle/cfgtoollogs/sqlpatch/30593149/23299902/30593149_apply_TestPROD_2020May15_15_59_39.log (no errors)
SQL Patching tool complete on Fri May 15 16:01:21 2020

Comments

Post a Comment

Popular posts from this blog

How to set the root password after creating instance on oracle cloud

By -
How to set the root password after creating instance on oracle cloud? since you have created instance on oracle cloud, it requires you private .ppk key file to login from putty you can login on your instance by directly providing that private key. and on Linux/Unix defult user is "opc". since during creation of instance it  will not ask you for  root password. You dont need any password to connect to root. to connect to root type below command as opc user. [opc@sts ~]$ sudo su [root@sts opc]# by this you will login as root. Now change your password [root@sts opc]# passwd Changing password for user root. New password: Retype new password: passwd: all authentication tokens updated successfully. [root@sts opc]# All done. Thanks & Regards Nikhil Kumar.
Read more

TNS-12541 TNS-12560 TNS-00511 TNS:protocol adapter error No listener

By -
Oracle Listener does not start with errors:  TNS-12541: TNS:no listener TNS-12560, TNS-00511, Linux Error: 2: No such file or directory, The listener supports no services euls25002.sgp.st.com:oraSID 51> ps -ef | grep -i tns root       330     2  0 Jul19 ?        00:00:00 [netns] oraSID   17512     1  0 Jul20 ?        00:01:25 /oracleSID/SID/121/bin/tnslsnr LISTENER_SID -inherit oraSID   56223 56131  0 08:02 pts/1    00:00:00 grep --color=auto -i tns euls25002.sgp.st.com:oraSID 52> lsnrctl status LISTENER_SID LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 25-SEP-2017 08:02:19 Copyright (c) 1991, 2014, Oracle.  All rights reserved. Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SID.WORLD)) TNS-12541: TNS:no listener  TNS-12560: TNS:protocol adapter error   TNS-00511: No listener    Linux Error: 2: No such file or directory ...
Read more