Oracle数据库数据恢复、性能优化

找回密码
注册
搜索
热搜: 活动 交友 discuz
Oracle数据库数据恢复、性能优化»论坛 › Oracle › Oracle数据库管理 › ORA-04063 错误问题（package body "SYS.DBMS_LOGSTDBY ...
发新帖
yehc@epsoft.com

75

积分

1

好友

8

主题

[升级] ORA-04063 错误问题（package body "SYS.DBMS_LOGSTDBY" has errors）

1#
发表于 2012-12-22 16:45:04 | 查看: 29287| 回复: 11
环境描述：
OS level  ：AIX 6100-06
GI：11.2.0.3
DB：11.2.0.3
ASM

数据库alert日志每隔几分钟出现同样错误信息：
  1. ……
  2. Sat Dec 22 16:36:17 2012
  3. Errors in file /home/oracle/diag/rdbms/jhcxjm/jhcxjm1/trace/jhcxjm1_cjq0_6881530.trc:
  4. ORA-00604: error occurred at recursive SQL level 1
  5. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
  6. Errors in file /home/oracle/diag/rdbms/jhcxjm/jhcxjm1/trace/jhcxjm1_cjq0_6881530.trc:
  7. ORA-00604: error occurred at recursive SQL level 1
  8. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
  9. Sat Dec 22 16:36:27 2012
  10. Errors in file /home/oracle/diag/rdbms/jhcxjm/jhcxjm1/trace/jhcxjm1_cjq0_6881530.trc:
  11. ORA-00604: error occurred at recursive SQL level 1
  12. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
  13. Errors in file /home/oracle/diag/rdbms/jhcxjm/jhcxjm1/trace/jhcxjm1_cjq0_6881530.trc:
  14. ORA-00604: error occurred at recursive SQL level 1
  15. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
  16. Sat Dec 22 16:36:37 2012
  17. Errors in file /home/oracle/diag/rdbms/jhcxjm/jhcxjm1/trace/jhcxjm1_cjq0_6881530.trc:
  18. ORA-00604: error occurred at recursive SQL level 1
  19. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
  20. ……
复制代码
trace文件显示内容如下：
  1. Trace file /home/oracle/diag/rdbms/jhcxjm/jhcxjm1/trace/jhcxjm1_cjq0_6881530.trc
  2. Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  3. With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
  4. Data Mining and Real Application Testing options
  5. ORACLE_HOME = /oracle/11.2
  6. System name:    AIX
  7. Node name:      jhcx01
  8. Release:        1
  9. Version:        6
  10. Machine:        0005A84BD600
  11. Instance name: jhcxjm1
  12. Redo thread mounted by this instance: 1
  13. Oracle process number: 42
  14. Unix process pid: 6881530, image: oracle@jhcx01 (CJQ0)


  17. *** 2012-12-22 06:00:00.036
  18. *** SESSION ID:(586.713) 2012-12-22 06:00:00.036
  19. *** CLIENT ID:() 2012-12-22 06:00:00.036
  20. *** SERVICE NAME:(SYS$BACKGROUND) 2012-12-22 06:00:00.036
  21. *** MODULE NAME:() 2012-12-22 06:00:00.036
  22. *** ACTION NAME:() 2012-12-22 06:00:00.036

  24. Setting Resource Manager plan SCHEDULER[0x318E]:DEFAULT_MAINTENANCE_PLAN via scheduler window
  25. Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter

  27. *** 2012-12-22 14:44:41.701

  29. *** 2012-12-22 14:44:42.455
  30. ORA-00604: error occurred at recursive SQL level 1
  31. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors

  33. *** 2012-12-22 14:44:47.509
  34. ORA-00604: error occurred at recursive SQL level 1
  35. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors

  37. *** 2012-12-22 14:44:52.512
  38. ORA-00604: error occurred at recursive SQL level 1
  39. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors

  41. *** 2012-12-22 14:44:57.515
  42. ORA-00604: error occurred at recursive SQL level 1
  43. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors

  45. *** 2012-12-22 14:45:02.518
  46. ORA-00604: error occurred at recursive SQL level 1
  47. ORA-04063: package body "SYS.DBMS_LOGSTDBY" has errors
  48. ……
复制代码
初步诊断是SYS.DBMS_LOGSTDBY包体失效，但是通过查看dba_objects视图，发现有大量失效对象：
  1. SQL> select object_name from dba_objects where status like '%INVALID%' and owner='SYS' and object_name like '%DBMS%';

  3. OBJECT_NAME
  4. --------------------------------------------------
  5. DBMS_XSTREAM_UTL_IVK
  6. DBMS_XSTREAM_ADM_UTL
  7. DBMS_STREAMS_SM
  8. DBMS_STREAMS_MC
  9. DBMS_STREAMS_AUTO_INT
  10. DBMS_STREAMS_ADM
  11. DBMS_RCVMAN
  12. DBMS_LOGSTDBY
  13. DBMS_LOGREP_UTIL
  14. DBMS_LOGMNR_SESSION
  15. DBMS_LOGMNR_LOGREP_DICT
  16. DBMS_LOGMNR_INTERNAL
  17. DBMS_LOGMNR_FFVTOLOGMNRT
  18. DBMS_LOGMNR
  19. DBMS_INTERNAL_LOGSTDBY
  20. DBMS_CAPTURE_SWITCH_INTERNAL
  21. DBMS_CAPTURE_SWITCH_ADM
  22. DBMS_CAPTURE_PROCESS
  23. DBMS_CAPTURE_ADM_INTERNAL
  24. DBMS_CAPTURE_ADM
  25. DBMS_APPLY_HANDLER_ADM
  26. DBMS_APPLY_ADM_INTERNAL
  27. DBMS_APPLY_ADM

  29. 23 rows selected.
复制代码
再次查看alert日志，发现在14:37分左右，有人执行过drop tablespace操作：
  1. /* OracleOEM */ CREATE SMALLFILE TABLESPACE "STREAM_TBS" LOGGING DATAFILE 'stream01.ora' SIZE 2048M EXTENT MANAGEMENT LOCAL SEGMENT
  2. SPACE MANAGEMENT  AUTO
  3. Sat Dec 22 14:41:05 2012
  4. Completed: /* OracleOEM */ CREATE SMALLFILE TABLESPACE "STREAM_TBS" LOGGING DATAFILE 'stream01.ora' SIZE 2048M EXTENT MANAGEMENT LOC
  5. AL SEGMENT SPACE MANAGEMENT  AUTO
  6. Sat Dec 22 14:44:31 2012
  7. /* OracleOEM */ DROP TABLESPACE "STREAM_TBS" INCLUDING CONTENTS  CASCADE CONSTRAINTS
复制代码
后确认是开发人员误操作所致。

我的问题：
是否可以重建这些包体？？？
2#
发表于 2012-12-22 20:06:06
FYI
  1. [oracle@vrh8 admin]$ grep -i "DBMS_LOGSTDBY" *
  2. a0902000.sql:execute dbms_logstdby.set_tablespace('SYSAUX');
  3. a1001000.sql:Rem    ajadams     06/22/04 - conditionally call dbms_logstdby.set_tablespace
  4. a1001000.sql:    dbms_logstdby.set_tablespace('SYSAUX');
  5. c1001000.sql:Rem    ajadams     05/09/05 - dbms_logstdby_public package depricated
  6. c1001000.sql:drop package DBMS_LOGSTDBY_PUBLIC;
  7. dbmslsby.sql:Rem      dbms_logstdby package definition.
  8. dbmslsby.sql:Rem    ajadams     05/02/05 - dbms_logstdby_public now deprecated
  9. dbmslsby.sql:Rem    sslim       06/06/04 - fast failover: dbms_logstdby.rebuild
  10. dbmslsby.sql:Rem    raguzman    06/20/03 - dbms_logstdby should be invokers rights
  11. dbmslsby.sql:Rem    jnesheiw    09/03/02 - create DBMS_LOGSTDBY_PUBLIC package
  12. dbmslsby.sql:CREATE OR REPLACE PACKAGE sys.dbms_logstdby AUTHID CURRENT_USER IS
  13. dbmslsby.sql:--      this proc is here not dbms_logstdby_internal because
  14. dbmslsby.sql:END dbms_logstdby;
  15. dbmslsby.sql:CREATE OR REPLACE PUBLIC SYNONYM dbms_logstdby FOR sys.dbms_logstdby;
  16. dbmslsby.sql:-- Revoke execute on DBMS_LOGSTDBY from public.  If it has already
  17. dbmslsby.sql:   execute immediate 'REVOKE EXECUTE ON dbms_logstdby FROM public';
  18. dbmslsby.sql:GRANT EXECUTE ON dbms_logstdby TO dba;
  19. dbmslsby.sql:GRANT EXECUTE ON dbms_logstdby TO logstdby_administrator;
  20. prvtlsby.plb:CREATE OR REPLACE LIBRARY sys.dbms_logstdby_lib wrapped
  21. prvtlsby.plb:CREATE OR REPLACE PACKAGE BODY sys.dbms_logstdby wrapped
  22. [oracle@vrh8 admin]$
  23. [oracle@vrh8 admin]$
  24. [oracle@vrh8 admin]$ pwd
  25. /s01/oracle/product/10.2.0.5/db_1/rdbms/admin




  30. @dbmslsby.sql
  31. @prvtlsby.plb
复制代码

回复 只看该作者 道具 举报

3#
发表于 2012-12-22 20:24:47
谢谢刘大恢复，之前我已尝试过：
  1. @?/rdbms/admin/dbmslm.sql
  2. @?/rdbms/admin/dbmslmd.sql
  3. @?/rdbms/admin/dbmslms.sql
  4. @?/rdbms/admin/prvtlm.plb
  5. @?/rdbms/admin/prvtlmd.plb
  6. @?/rdbms/admin/prvtlmrd.plb
  7. @?/rdbms/admin/prvtlms.plb
  8. @?/rdbms/admin/prvtlms2.plb
  9. @?/rdbms/admin/catpstr.sql

  11. @?/rdbms/admin/utlrp.sql
复制代码
按照你的方法，执行后问题依然存在：
  1. SQL> @?/rdbms/admin/dbmslsby.sql

  3. Package created.

  5. No errors.

  7. Synonym created.


  10. PL/SQL procedure successfully completed.


  13. Grant succeeded.

  15. CREATE ROLE logstdby_administrator
  16.             *
  17. ERROR at line 1:
  18. ORA-01921: role name 'LOGSTDBY_ADMINISTRATOR' conflicts with another user or
  19. role name



  23. Grant succeeded.


  26. Grant succeeded.


  29. Grant succeeded.


  32. Library created.


  35. SQL> @?/rdbms/admin/prvtlsby.plb

  37. Warning: Package Body created with compilation errors.

  39. Errors for PACKAGE BODY SYS.DBMS_LOGSTDBY:

  41. LINE/COL ERROR
  42. -------- -----------------------------------------------------------------
  43. 646/3    PL/SQL: SQL Statement ignored
  44. 647/10   PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors
  45. grant select on dba_logstdby_progress to select_catalog_role
  46.                 *
  47. ERROR at line 1:
  48. ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors


  51. grant select on dba_logstdby_log to select_catalog_role
  52.                 *
  53. ERROR at line 1:
  54. ORA-04063: view "SYS.DBA_LOGSTDBY_LOG" has errors



  58. 0 rows updated.


  61. Commit complete.

  63. SQL>


  66. SQL> @?/rdbms/admin/utlrp.sql

  68. TIMESTAMP
  69. --------------------------------------------------------------------------------
  70. COMP_TIMESTAMP UTLRP_BGN  2012-12-22 20:20:47

  72. DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
  73. DOC>   objects in the database. Recompilation time is proportional to the
  74. DOC>   number of invalid objects in the database, so this command may take
  75. DOC>   a long time to execute on a database with a large number of invalid
  76. DOC>   objects.
  77. DOC>
  78. DOC>   Use the following queries to track recompilation progress:
  79. DOC>
  80. DOC>   1. Query returning the number of invalid objects remaining. This
  81. DOC>      number should decrease with time.
  82. DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
  83. DOC>
  84. DOC>   2. Query returning the number of objects compiled so far. This number
  85. DOC>      should increase with time.
  86. DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
  87. DOC>
  88. DOC>   This script automatically chooses serial or parallel recompilation
  89. DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
  90. DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
  91. DOC>   On RAC, this number is added across all RAC nodes.
  92. DOC>
  93. DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
  94. DOC>   recompilation. Jobs are created without instance affinity so that they
  95. DOC>   can migrate across RAC nodes. Use the following queries to verify
  96. DOC>   whether UTL_RECOMP jobs are being created and run correctly:
  97. DOC>
  98. DOC>   1. Query showing jobs created by UTL_RECOMP
  99. DOC>         SELECT job_name FROM dba_scheduler_jobs
  100. DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
  101. DOC>
  102. DOC>   2. Query showing UTL_RECOMP jobs that are running
  103. DOC>         SELECT job_name FROM dba_scheduler_running_jobs
  104. DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
  105. DOC>#
  106. DECLARE
  107. *
  108. ERROR at line 1:
  109. ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
  110. ORA-06508: PL/SQL: could not find program unit being called:
  111. "SYS.DBMS_INTERNAL_LOGSTDBY"
  112. ORA-06512: at "SYS.UTL_RECOMP", line 827
  113. ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
  114. ORA-06508: PL/SQL: could not find program unit being called:
  115. "SYS.DBMS_INTERNAL_LOGSTDBY"
  116. ORA-06512: at line 4



  120. TIMESTAMP
  121. --------------------------------------------------------------------------------
  122. COMP_TIMESTAMP UTLRP_END  2012-12-22 20:20:48

  124. DOC> The following query reports the number of objects that have compiled
  125. DOC> with errors (objects that compile with errors have status set to 3 in
  126. DOC> obj$). If the number is higher than expected, please examine the error
  127. DOC> messages reported with each object (using SHOW ERRORS) to see if they
  128. DOC> point to system misconfiguration or resource constraints that must be
  129. DOC> fixed before attempting to recompile these objects.
  130. DOC>#

  132. OBJECTS WITH ERRORS
  133. -------------------
  134.                  59

  136. DOC> The following query reports the number of errors caught during
  137. DOC> recompilation. If this number is non-zero, please query the error
  138. DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
  139. DOC> are due to misconfiguration or resource constraints that must be
  140. DOC> fixed before objects can compile successfully.
  141. DOC>#

  143. ERRORS DURING RECOMPILATION
  144. ---------------------------
  145.                           0


  148. Function created.


  151. PL/SQL procedure successfully completed.


  154. Function dropped.

  156. Warning: XDB now invalid, could not find xdbconfig

  158. PL/SQL procedure successfully completed.

  160. SQL> select object_name,status from dba_objects where status like '%INVALID%' and owner='SYS' and object_name like '%DBMS%';

  162. OBJECT_NAME                              STATUS
  163. ---------------------------------------- -------
  164. DBMS_XSTREAM_UTL_IVK                     INVALID
  165. DBMS_XSTREAM_ADM_UTL                     INVALID
  166. DBMS_STREAMS_SM                          INVALID
  167. DBMS_STREAMS_MC                          INVALID
  168. DBMS_STREAMS_AUTO_INT                    INVALID
  169. DBMS_STREAMS_ADM                         INVALID
  170. DBMS_RCVMAN                              INVALID
  171. DBMS_LOGSTDBY                            INVALID
  172. DBMS_LOGREP_UTIL                         INVALID
  173. DBMS_LOGMNR_SESSION                      INVALID
  174. DBMS_LOGMNR_LOGREP_DICT                  INVALID
  175. DBMS_LOGMNR_INTERNAL                     INVALID
  176. DBMS_LOGMNR_FFVTOLOGMNRT                 INVALID
  177. DBMS_INTERNAL_LOGSTDBY                   INVALID
  178. DBMS_CAPTURE_SWITCH_INTERNAL             INVALID
  179. DBMS_CAPTURE_SWITCH_ADM                  INVALID
  180. DBMS_CAPTURE_PROCESS                     INVALID
  181. DBMS_CAPTURE_ADM_INTERNAL                INVALID
  182. DBMS_CAPTURE_ADM                         INVALID
  183. DBMS_APPLY_HANDLER_ADM                   INVALID
  184. DBMS_APPLY_ADM_INTERNAL                  INVALID
  185. DBMS_APPLY_ADM                           INVALID

  187. 22 rows selected.
复制代码

回复 只看该作者 道具 举报

4#
发表于 2012-12-22 20:26:58
@?/rdbms/admin/catproc   ==>注意在downtime做
@dbmslsby.sql
@prvtlsby.plb

回复 只看该作者 道具 举报

5#
发表于 2012-12-22 22:01:26
刘大，尝试跑了下catproc.sql  跑了半个多小时。
过程中任然出现之前的错误信息：
  1. SQL> @?/rdbms/admin/catproc.sql
  2. DOC>######################################################################
  3. DOC>######################################################################
  4. DOC>    The following PL/SQL block will cause an ORA-20000 error and
  5. DOC>    terminate the current SQLPLUS session if the user is not SYS.
  6. DOC>    Disconnect and reconnect with AS SYSDBA.
  7. DOC>######################################################################
  8. DOC>######################################################################
  9. DOC>#

  11. PL/SQL procedure successfully completed.
  12. ……
  13. Package body created.

  15. No errors.

  17. Warning: Package Body created with compilation errors.

  19. Errors for PACKAGE BODY SYS.DBMS_LOGSTDBY:

  21. LINE/COL ERROR
  22. -------- -----------------------------------------------------------------
  23. 646/3    PL/SQL: SQL Statement ignored
  24. 647/10   PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors
  25. grant select on dba_logstdby_progress to select_catalog_role
  26.                 *
  27. ERROR at line 1:
  28. ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors


  31. grant select on dba_logstdby_log to select_catalog_role
  32.                 *
  33. ERROR at line 1:
  34. ORA-04063: view "SYS.DBA_LOGSTDBY_LOG" has errors



  38. 0 rows updated.


  41. Commit complete.


  44. Warning: Package Body created with compilation errors.

  46. Errors for PACKAGE BODY SYS.DBMS_INTERNAL_LOGSTDBY:

  48. LINE/COL ERROR
  49. -------- -----------------------------------------------------------------
  50. 4305/5   PL/SQL: SQL Statement ignored
  51. 4305/50  PL/SQL: ORA-00942: table or view does not exist
  52. 6696/3   PL/SQL: SQL Statement ignored
  53. 6697/10  PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors
  54. 6705/5   PL/SQL: SQL Statement ignored
  55. 6706/12  PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_LOG" has errors
  56. 6720/5   PL/SQL: SQL Statement ignored
  57. 6721/12  PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_LOG" has errors

  59. Package body created.

  61. No errors.

  63. Package body created.

  65. No errors.
  66. ……
复制代码
@?/rdbms/admin/dbmslsby.sql
@?/rdbms/admin/prvtlsby.plb

@?/rdbms/admin/utlrp.sql
@?/rdbms/admin/utlrp.sql
@?/rdbms/admin/utlrp.sql

重新编译几次后，失效的包体还是原来那些。。怀疑是否SYSAUX表空间问了问题？

另外该库目前测试阶段，未正式上线，有备份数据，是否考虑重建实例来解决问题？

回复 只看该作者 道具 举报

6#
发表于 2012-12-22 22:15:30

SQL> alter view SYS.DBA_LOGSTDBY_PROGRESS compile;

View altered.

SQL> show errors;

回复 只看该作者 道具 举报

7#
发表于 2012-12-22 22:17:15
是不是做stream 把logminer相关的数据字典迁到了别的表空间，而又删除了这个表空间。
可以尝试以下方法：在plsql中查看无效对象涉及到的表是什么，然后在别的数据库中找到该表的create ddl，在问题库中recreate，然后重新编译。

回复 只看该作者 道具 举报

8#
发表于 2012-12-22 23:06:53
感谢大神回复。
我之前已做过类似操作：
参考文章：
https://forums.oracle.com/forums/thread.jspa?threadID=2165317
输出的结果跟我的情况一致
  1. SQL> alter package DBMS_LOGSTDBY compile body;

  3. Warning: Package Body altered with compilation errors.

  5. SQL> show errors
  6. Errors for PACKAGE BODY DBMS_LOGSTDBY:

  8. LINE/COL ERROR
  9. -----------------------------------------------------------------
  10. 646/3 PL/SQL: SQL Statement ignored
  11. 647/10 PL/SQL: ORA-04063: view "SYS.DBA_LOGSTDBY_PROGRESS" has errors
  12. SQL> alter package DBMS_LOGSTDBY compile;

  14. Warning: Package altered with compilation errors.

  16. SQL> show errors
  17. No errors.

  19. SQL> alter view SYS.DBA_LOGSTDBY_PROGRESS compile;

  21. Warning: View altered with compilation errors.

  23. SQL> show error;
  24. No errors.
  25. SQL> select text from dba_errors where name = 'DBA_LOGSTDBY_PROGRESS';

  27. TEXT
  28. ORA-00942: table or view does not exist
复制代码
之前也试过重新compile，重新编译成功，但有错误：

我甚至执行过如下脚本，问题任然存在。
@?/rdbms/admin/catalog.sql;
@@catblock.sql;
@@catproc.sql;
@@catoctk.sql;
@@owminst.plb;

@?/rdbms/admin/utlrp.sql
@?/rdbms/admin/utlrp.sql
@?/rdbms/admin/utlrp.sql

回复 只看该作者 道具 举报

9#
发表于 2012-12-22 23:11:50

1. 考虑提交SR

2. 需要debug这个compile过程 获得更多信息

3. 目前未找到MOS上类似案例

回复 只看该作者 道具 举报

10#
发表于 2012-12-22 23:12:40
sunnyihui 发表于 2012-12-22 22:17
是不是做stream 把logminer相关的数据字典迁到了别的表空间，而又删除了这个表空间。
可以尝试以下方法：在 ...

问题产生的原因是对的，但目前要定位那些表和视图比较困难，DBMS基本package boby基本是加密的。

回复 只看该作者 道具 举报

11#
发表于 2012-12-24 11:42:59
pssql developer很容易看的啊

回复 只看该作者 道具 举报

12#
发表于 2013-9-10 15:58:15
yehc@epsoft.com 发表于 2012-12-22 23:12
问题产生的原因是对的，但目前要定位那些表和视图比较困难，DBMS基本package boby基本是加密的。 ...

知道原因就好办了，找一个正常的库，把logminer相关的表重建，再把无效对象重新编译

回复 只看该作者 道具 举报

返回列表
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

QQ|手机版|Archiver|Oracle数据库数据恢复、性能优化

GMT+8, 2025-1-4 07:14 , Processed in 0.050641 second(s), 20 queries .

Powered by Discuz! X2.5

© 2001-2012 Comsenz Inc.

回顶部
TEL/電話+86 13764045638
Email service@parnassusdata.com
QQ 47079569