oracle 12CR2打补丁报错处理一例

2019-7-10:昨天团队会议，当leader开讲时，让我百感交集。3个月零17天前，当时来到现场出现三个有意思的现象，一是客户对交付极度不满意；二是现场项目经理自嗨感爆棚；三是团队每天都像木偶一样拴在项目经理身上，跳大绳一样的在办公室里东窜西跳。现象有了，问题出在哪里？根源在哪里？如果是你怎么解决这个问题？这些需要了解的可以私信我，这里就不占用过多时间。今天早上我想表达是这件事情的结果：一、办公室里不是一个人在跳大绳了，而是整个团队自觉有序，激情洋溢的群体跳大绳；二、整个团队积极向上，那些90后的孩子们因为找到了方法，得到了认可，脸上洋溢的那种自信和从容，真的让人看到感觉很温暖，更让人感到幸福；三、因为团队找到了自己节奏，客户对交付质量“群众性满意”（群众性满意是指所有客户干系人都满意）。客户满意认可，团队则效率越高，效率越高，客户满意认可，以此形成良好的正向循环。下面这张图就是我们团队遇到问题，处理问题的思维模型：

2019-07-09 :早上睁开眼，圈里看到这个图： 

自己奔四了，在刚毕业的那几年，每个月都是月初工资没几天，就和兄弟夜宵没了，回头想想，那些最终成为能谈心，能沟通的兄弟，反而是那些很少胡吃海喝的，胡吃海喝的除了胡吃海喝，好像就没有别的了。所以，要尽早养成不乱花钱，攒钱的习惯，这就和我们说的阳光灿烂的日子修屋顶一个道理，因为意外和美好哪个先来，只有老天知道，但老天从来不泄漏哪个先来。管理其实也是一样的，当棘手的事情逐渐解决，慢慢向好之后，我们要做是如何保持，如何未雨绸缪，黑天鹅，灰犀牛，不是我们不愿意，不喜欢，他就不来找咱，凡人的我们决定不了明天的阴晴圆缺，但我们可以为明天的阴晴圆缺储备对应的措施。生于忧患 死于安乐。

今天给12R2打db补丁，以阅女无数的心态三下五去二开始，结果直接干骨头上了，报错结果如下：

[oracle@xxxx:/oracle/product/12.2.0/OPatch]$  ./datapatch -verbose

SQL Patching tool version 12.2.0.1.0Production on Fri Apr 19 16:56:58 2019

Copyright (c) 2012, 2019, Oracle.  All rights reserved.

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

Connecting to database...OK

Bootstrapping registry and package tocurrent versions...done

Determining current state...done

Current state of SQL patches:

Patch 29249637 (OJVM RELEASE UPDATE:12.2.0.1.190416 (29249637)):

 Installed in the binary registry only

Bundle series DBRU:

  ID190416 in the binary registry and ID 190416 with errors in the SQL registry

Adding patches to installation queue andperforming prereq checks...

Installation queue:

 Nothing to roll back

  Thefollowing patches will be applied:

   29249637 (OJVM RELEASE UPDATE: 12.2.0.1.190416 (29249637))

   29314339 (DATABASE APR 2019 RELEASE UPDATE 12.2.0.1.190416)

Installing patches...

Patch installation complete.  Total patches installed: 2

Validating logfiles...

Patch 29249637 apply: SUCCESS

 logfile:/oracle/app/cfgtoollogs/sqlpatch/29249637/22825875/29249637_apply_BSSJFDB_2019Apr19_16_58_47.log(no errors)

Patch 29314339 apply: WITH ERRORS

 logfile:/oracle/app/cfgtoollogs/sqlpatch/29314339/22848642/29314339_apply_BSSJFDB_2019Apr19_17_00_14.log(errors)

   Error at line 3727: Warning: Package Body created with compilationerrors.

   Error at line 32342: Warning: Package Body created with compilationerrors.

   Error at line 32349: 4675/4  PL/SQL: Statement ignored

   Error at line 32350: 4675/23 PLS-00302: component ISNONORACLECLOUD must be declared

   Error at line 32372: 4675/4  PL/SQL: Statement ignored

   Error at line 32373: 4675/23 PLS-00302: component ISNONORACLECLOUD must be declared

   Error at line 33026: Warning: Trigger created with compilation errors.

   Error at line 33033: 0/0     PLS-00905: object GSMADMIN_INTERNAL.DBMS_GSM_POOLADMIN is invalid

   Error at line 33050: Warning: Trigger created with compilation errors.

   Error at line 33057: 0/0     PLS-00905: object GSMADMIN_INTERNAL.DBMS_GSM_POOLADMIN is invalid

   Error at line 33064: Warning: Trigger created with compilation errors.

   Error at line 33071: 0/0     PLS-00905: object GSMADMIN_INTERNAL.DBMS_GSM_POOLADMIN is invalid

Please refer to MOS Note 1609718.1 and/orthe invocation log

/oracle/app/cfgtoollogs/sqlpatch/sqlpatch_35782718_2019_04_19_16_56_58/sqlpatch_invocation.log

for information on how to resolve the aboveerrors.

SQL Patching tool complete on Fri Apr 1917:00:53 2019

撸了撸MOS，结合MOS相关提示，处理过程如下：

1、查询无效对象：

select owner,object_type,object_name,status from dba_objects where status = INVALID order by owner;

2、重编译下对象

Sqlplus / as sysdba

?$ORACLE_HOME/rdbms/admin/catproc

?$ORACLE_HOME/rdbms/admin/utlrp

3、重新运行更新数据字典脚本

su - oracle

cd /oracle/product/12.2.0/OPatch

./datapatch -verbose

执行成功无报错。