3 Responses to “RMAN-06023 and ORA-19909 ？”

1. roger Says:
   
   12月 25, 2011 at 上午 4:16

   PgSQL

   ### Grid Infrastructure 1. check 环境变量owner ，必须保持跟pre-version 一致 $ unset ORACLE_BASE $ unset ORACLE_HOME $ unset ORACLE_SID Relax permissions for GRID_HOME #chmod -R 755 /oracle/product/grid #chown -R oracle /oracle/product/grid #chown oracle /oracle/product 2. ORACLE_BASE或os user'home 避免设置为 /opt/oracle ，为了避免bug 10362257 3. Unset Oracle related environment variables especially ORA_CRS_HOME before starting OUI or before executing any root script for both root and grid user 4. The IP addresses for the public and private networks should not be in a link local subnet (169.254.*.*) and should be in unrelated, separate subnets to avoid the issue in Document 1062682.1 5. The output of "ifconfig" for the private network adapter and the cluster_interconnect part of the "oifcfg getif" command output should be consistent in regards to the network adapter name and the subnet. 6. Public/VIP network information should be consistent 7. The length of GI owner uid should be less than 7 digits 8. Os patch： IZ64508 （The issue is caused by AIX incorrectly reporting OS level; in above case 6.1.4.0 should be 6.1.0.0. ） 9. The CSS parameter "diagwait" ("crsctl get css diagwait") should either be unset(output shows "Configuration parameter diagwait is not defined") or set to a small value (13 or less) ----crsctl get css diagwait ----crsctl set css diagwait 13 -force 10. Output of "ocrcheck" should be clean 11. On AIX, rootpre.sh should finish successfully with no "Text file busy" messages before starting OUI to avoid the issue in Document 1053055.1 12. ASM init.ora/pfile/spfile should not have parameters like SGA_TARGET, SGA_MAX_SIZE, SHARED_POOL_SIZE, and LARGE_POOL_SIZE to avoid "ORA-00600 ksxpmprp1" error. ---之前需要apply的patch 9706490 --must 9413827 --must 9329767 10229886 9941757 If rootupgrade.sh fails, refer to Document 1050908.1 and Document 1053970.1 for troubleshooting steps.

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51

   ### Grid Infrastructure   1.  check 环境变量owner ，必须保持跟pre-version 一致   $ unset ORACLE_BASE $ unset ORACLE_HOME $ unset ORACLE_SID Relax permissions for GRID_HOME #chmod -R 755 /oracle/product/grid #chown -R oracle /oracle/product/grid #chown oracle /oracle/product   2.  ORACLE_BASE或os user'home 避免设置为 /opt/oracle ，为了避免bug 10362257   3.  Unset Oracle related environment variables especially ORA_CRS_HOME before starting OUI or before executing any root script for both root and grid user   4.  The IP addresses for the public and private networks should not be in a link local subnet (169.254.*.*) and should be in unrelated, separate subnets to avoid the issue in Document 1062682.1   5.  The output of "ifconfig" for the private network adapter and the cluster_interconnect part of the "oifcfg getif" command output  should be consistent in regards to the network adapter name and the subnet.   6.  Public/VIP network information should be consistent   7.  The length of GI owner uid should be less than 7 digits   8.  Os patch： IZ64508  （The issue is caused by AIX incorrectly reporting OS level; in above case 6.1.4.0 should be 6.1.0.0. ）     9.  The CSS parameter "diagwait" ("crsctl get css diagwait") should either be unset(output shows "Configuration parameter diagwait is not defined") or set to a small value (13 or less)      ----crsctl get css diagwait    ----crsctl set css diagwait 13 -force   10. Output of "ocrcheck" should be clean     11. On AIX, rootpre.sh should finish successfully with no "Text file busy" messages before starting OUI to avoid the issue in Document 1053055.1     12. ASM init.ora/pfile/spfile should not have parameters like SGA_TARGET, SGA_MAX_SIZE, SHARED_POOL_SIZE, and LARGE_POOL_SIZE to avoid "ORA-00600 ksxpmprp1" error.   ---之前需要apply的patch 9706490  --must 9413827  --must 9329767 10229886 9941757   If rootupgrade.sh fails, refer to Document 1050908.1 and Document 1053970.1 for troubleshooting steps.

2. hctech Says:
   
   1月 13, 2012 at 上午 2:24

   博主您好，请问一下：
   重建了controlfile，然后手工catalog backupipece 注册所需要的
   archivelog 备份片

   这个操作具体是怎么做的啊，谢谢~

3. roger Says:
   
   1月 15, 2012 at 上午 8:36

   to hcteck:

   1.重建controlfile如下：
   startup mount;
   alter database backup controlfile to trace;
   提取trace文件中的script；然后执行即可。

   2. 手工注册

   进入rman：
   RMAN> catalog archivelog ‘/xx/xxx/xxx.dbf’;

Leave a Reply

You must be logged in to post a comment.