探索_disable_logging的损坏作用_结论2

最新推荐文章于 2021-04-03 04:56:04 发布
最新推荐文章于 2021-04-03 04:56:04 发布
阅读量3k 收藏
点赞数
分类专栏： oracle 文章标签： logging oracle database thread archive transformation
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lunar2000/article/details/607917
版权

SQL> alter system set "_disable_logging"=true scope=spfile;

System altered.

Elapsed: 00:00:00.00
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area  403772836 bytes
Fixed Size                   452004 bytes
Variable Size             369098752 bytes
Database Buffers           33554432 bytes
Redo Buffers                 667648 bytes
Database mounted.
ORA-03113: end-of-file on communication channel


SQL>

///
检查日志：
///
Thu Dec  1 09:31:26 2005
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.6.0.
System parameters with non-default values:
  processes                = 150
  timed_statistics         = TRUE
  shared_pool_size         = 167772160
  sga_max_size             = 403772836
  large_pool_size          = 16777216
  java_pool_size           = 167772160
  control_files            = /oracle/oradata/TSMISC02/control01.ctl, /oracle/oradata/TSMISC02/control02.ctl, /oracle/oradata/TSMISC02/control03.ctl
  db_block_size            = 8192
  db_cache_size            = 33554432
  compatible               = 9.2.0.0.0
  log_archive_start        = TRUE
  log_archive_dest_1       = LOCATION=/oracle/oradata/TSMISC02/archive
  log_archive_format       = %t_%s.dbf
  _disable_logging         = TRUE
  db_file_multiblock_read_count= 16
  fast_start_mttr_target   = 300
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS2
  undo_retention           = 10800
  O7_DICTIONARY_ACCESSIBILITY= FALSE
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  instance_name            = TSMISC02
  dispatchers              = (PROTOCOL=TCP) (SERVICE=TSMISC02XDB)
  job_queue_processes      = 10
  hash_join_enabled        = TRUE
  background_dump_dest     = /oracle/admin/TSMISC02/bdump
  user_dump_dest           = /oracle/admin/TSMISC02/udump
  core_dump_dest           = /oracle/admin/TSMISC02/cdump
  sort_area_size           = 524288
  db_name                  = TSMISC02
  open_cursors             = 300
  star_transformation_enabled= FALSE
  query_rewrite_enabled    = FALSE
  pga_aggregate_target     = 25165824
  aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Thu Dec  1 09:31:27 2005
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
Thu Dec  1 09:31:28 2005
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Dec  1 09:31:28 2005
ARC1: Archival started
ARC1: Thread not mounted
Thu Dec  1 09:31:28 2005
ARC0: Thread not mounted
Thu Dec  1 09:31:28 2005
ALTER DATABASE   MOUNT
Thu Dec  1 09:31:32 2005
Successful mount of redo thread 1, with mount id 1740736752
Thu Dec  1 09:31:32 2005
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE   MOUNT
Thu Dec  1 09:31:32 2005
ALTER DATABASE OPEN
Thu Dec  1 09:31:32 2005
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 opened at log sequence 280
  Current log# 1 seq# 280 mem# 0: /oracle/oradata/TSMISC02/redo01.log
Successful open of redo thread 1
Thu Dec  1 09:31:32 2005
Errors in file /oracle/admin/TSMISC02/bdump/tsmisc02_lgwr_3103.trc:
ORA-07445: exception encountered: core dump [kcrfwcint()+1625] [SIGFPE] [Integer divide by zero] [0x828739D] [] []
Thu Dec  1 09:31:34 2005
Errors in file /oracle/admin/TSMISC02/bdump/tsmisc02_pmon_3099.trc:
ORA-00470: LGWR process terminated with error
Thu Dec  1 09:31:34 2005
PMON: terminating instance due to error 470
Instance terminated by PMON, pid = 3099
///
[oracle@ts01 bdump]$ ll tsmisc02_lgwr_3103.trc
-rw-r-----    1 oracle   oinstall   716212 Dec  1 09:31 tsmisc02_lgwr_3103.trc
[oracle@ts01 bdump]$ ll tsmisc02_pmon_3099.trc
-rw-r-----    1 oracle   oinstall      625 Dec  1 09:31 tsmisc02_pmon_3099.trc
[oracle@ts01 bdump]$

[oracle@ts01 bdump]$ cat tsmisc02_pmon_3099.trc
/oracle/admin/TSMISC02/bdump/tsmisc02_pmon_3099.trc
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
ORACLE_HOME = /oracle/product/920
System name:    Linux
Node name:      ts01
Release:        2.4.21-4.EL
Version:        #1 Fri Oct 3 18:13:58 EDT 2003
Machine:        i686
Instance name: TSMISC02
Redo thread mounted by this instance: 1
Oracle process number: 2
Unix process pid: 3099, image: oracle@ts01 (PMON)

*** SESSION ID:(1.1) 2005-12-01 09:31:34.198
error 470 detected in background process
ORA-00470: LGWR process terminated with error
[oracle@ts01 bdump]$
///

 

 

 


SQL> shutdown immediate;
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> exit             
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
[oracle@ts01 oracle]$ ipcs

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status     

------ Semaphore Arrays --------
key        semid      owner      perms      nsems    

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages   

[oracle@ts01 oracle]$ ps -ef | grep oracle
root      2620  2482  0 08:10 pts/0    00:00:00 su - oracle
oracle    2621  2620  0 08:10 pts/0    00:00:00 -bash
root      2666  2528  0 08:25 pts/1    00:00:00 su - oracle
oracle    2667  2666  0 08:25 pts/1    00:00:05 -bash
oracle    3095  2667  0 08:56 pts/1    00:00:00 tail -f alert_TSMISC02.log
root      3172  3126  0 09:33 pts/2    00:00:00 su - oracle
oracle    3173  3172  0 09:33 pts/2    00:00:00 -bash
oracle    3233  2621  0 09:57 pts/0    00:00:00 ps -ef
oracle    3234  2621  0 09:57 pts/0    00:00:00 grep oracle
[oracle@ts01 oracle]$

///
察看metalink:
///

Bookmark Go to End

Doc ID:  Note:342195.1
Subject:  ORA-7445 (kcrfwcint)
Type:  REFERENCE
Status:  PUBLISHED
 Content Type:  TEXT/X-HTML
Creation Date:  23-NOV-2005
Last Revision Date:  25-NOV-2005
 


Note: For additional ORA-7445 related information please read Note 211909.1

PURPOSE:

  This article provides information on one or more bugs that are
  known to result in the given ORA-7445 error.

SUGGESTIONS:

  If the Known Issues section below does not help in terms of identifying
  a solution, please submit the trace files and alert.log to Oracle
  Support Services for further analysis.

  Known Issues:
  Bug# 3868748   See Note 3868748.8
      Instance crashes when trying to use "_disable_logging"=true
      Fixed: 10.2.0.1
///

 

///
修正方法：
不要使用 _disable_logging=TRUE

修改pfile，将 _disable_logging 改为fase：
*._disable_logging=false

///
[oracle@ts01 oracle]$ cat a.ora| grep _disable_logging
*._disable_logging=false
#*._disable_logging=TRUE
[oracle@ts01 oracle]$
[oracle@ts01 oracle]$ sqlplus '/ as sysdba'

SQL*Plus: Release 9.2.0.6.0 - Production on Mon Dec 12 13:01:03 2005

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Connected to an idle instance.

SQL> startup pfile=a.ora
ORACLE instance started.

Total System Global Area  403772836 bytes
Fixed Size                   452004 bytes
Variable Size             369098752 bytes
Database Buffers           33554432 bytes
Redo Buffers                 667648 bytes
Database mounted.
Database opened.
SQL>
///
 


///
相关点alert：
///
Mon Dec 12 13:01:09 2005
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.6.0.
System parameters with non-default values:
  processes                = 150
  timed_statistics         = TRUE
  shared_pool_size         = 167772160
  sga_max_size             = 403772836
  large_pool_size          = 16777216
  java_pool_size           = 167772160
  control_files            = /oracle/oradata/TSMISC02/control01.ctl, /oracle/oradata/TSMISC02/control02.ctl, /oracle/oradata/TSMISC02/control03.ctl
  db_block_size            = 8192
  db_cache_size            = 33554432
  compatible               = 9.2.0.0.0
  log_archive_start        = TRUE
  log_archive_dest_1       = LOCATION=/oracle/oradata/TSMISC02/archive
  log_archive_format       = %t_%s.dbf
  _disable_logging         = FALSE
  db_file_multiblock_read_count= 16
  fast_start_mttr_target   = 300
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS2
  undo_retention           = 10800
  O7_DICTIONARY_ACCESSIBILITY= FALSE
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  instance_name            = TSMISC02
  dispatchers              = (PROTOCOL=TCP) (SERVICE=TSMISC02XDB)
  job_queue_processes      = 10
  hash_join_enabled        = TRUE
  background_dump_dest     = /oracle/admin/TSMISC02/bdump
  user_dump_dest           = /oracle/admin/TSMISC02/udump
  core_dump_dest           = /oracle/admin/TSMISC02/cdump
  sort_area_size           = 524288
  db_name                  = TSMISC02
  open_cursors             = 300
  star_transformation_enabled= FALSE
  query_rewrite_enabled    = FALSE
  pga_aggregate_target     = 25165824
  aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
Mon Dec 12 13:01:10 2005
starting up 1 shared server(s) ...
QMN0 started with pid=9
Mon Dec 12 13:01:10 2005
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
Mon Dec 12 13:01:11 2005
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Dec 12 13:01:11 2005
ALTER DATABASE   MOUNT
ARC1 started with pid=13
ARC1: Archival started
ARC1: Thread not mounted
Mon Dec 12 13:01:11 2005
ARC0: Thread not mounted
Mon Dec 12 13:01:15 2005
Successful mount of redo thread 1, with mount id 1741682071
Mon Dec 12 13:01:15 2005
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE   MOUNT
Mon Dec 12 13:01:15 2005
ALTER DATABASE OPEN
Mon Dec 12 13:01:15 2005
Beginning crash recovery of 1 threads
Mon Dec 12 13:01:15 2005
Started redo scan
Mon Dec 12 13:01:15 2005
Completed redo scan
 0 redo blocks read, 0 data blocks need recovery
Mon Dec 12 13:01:15 2005
Started recovery at
 Thread 1: logseq 282, block 2, scn 0.917167
Mon Dec 12 13:01:15 2005
Recovery of Online Redo Log: Thread 1 Group 3 Seq 282 Reading mem 0
  Mem# 0 errs 0: /oracle/oradata/TSMISC02/redo03.log
Mon Dec 12 13:01:15 2005
Completed redo application
Mon Dec 12 13:01:15 2005
Ended recovery at
 Thread 1: logseq 282, block 2, scn 0.937168
 0 data blocks read, 0 data blocks written, 0 redo blocks read
Crash recovery completed successfully
Mon Dec 12 13:01:15 2005
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 advanced to log sequence 283
Thread 1 opened at log sequence 283
  Current log# 1 seq# 283 mem# 0: /oracle/oradata/TSMISC02/redo01.log
Successful open of redo thread 1
Mon Dec 12 13:01:15 2005
SMON: enabling cache recovery
Mon Dec 12 13:01:15 2005
ARC0: Evaluating archive   log 3 thread 1 sequence 282
ARC0: Beginning to archive log 3 thread 1 sequence 282
Creating archive destination LOG_ARCHIVE_DEST_1: '/oracle/oradata/TSMISC02/archive/1_282.dbf'
ARC0: Completed archiving  log 3 thread 1 sequence 282
Mon Dec 12 13:01:15 2005
Successfully onlined Undo Tablespace 11.
Mon Dec 12 13:01:15 2005
SMON: enabling tx recovery
Mon Dec 12 13:01:15 2005
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: ALTER DATABASE OPEN
///

 


///
总结：
///
如果设置了 _disable_logging=true，那么数据库会因为下面的错误而crash：
Thu Dec  1 09:31:32 2005
Errors in file /oracle/admin/TSMISC02/bdump/tsmisc02_lgwr_3103.trc:
ORA-07445: exception encountered: core dump [kcrfwcint()+1625] [SIGFPE] [Integer divide by zero] [0x828739D] [] []
Thu Dec  1 09:31:34 2005
Errors in file /oracle/admin/TSMISC02/bdump/tsmisc02_pmon_3099.trc:
ORA-00470: LGWR process terminated with error
Thu Dec  1 09:31:34 2005
PMON: terminating instance due to error 470
Instance terminated by PMON, pid = 3099

修复的办法是 将 _disable_logging 的值改为 false。

 

 

 

lunar2000
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
_disable_logging参数研究系列（一）
lunar的小铺
02-24 2444
ORACLE 的隐含参数_disable_logging主要用于禁用日志生成（一般建议在oracle support的指导下用于非生产环境下），不难想象，如果禁止日志生成，那么必然导致事务的不可恢复性。对于这个参数的一些破坏作用做了一些测试：SQL> select * from v$instance;INSTANCE_NUMBER INSTANCE_NAME    HOST_NAME 
详解Oracle中的隐含参数_disable_logging
09-09
之前看到过一篇文章是介绍Oracle的一个内部隐含参数_disable_logging，最近又看到有朋友论述这个参数,所以下面这篇文章就来给大家介绍下关于Oracle中隐含参数_disable_logging的相关资料，需要的朋友可以参考下。
_disable_logging调整
cuicheng2535的博客
06-27 193
提示：Oracle的隐含参数只应该在测试环境或者在Oracle Support的支持下使用。从Oracle的系统表中，我们知道Oracle存在一个隐含参数_disable_logging可以用于禁用日志生成，这个参数显然只能用于...
_disable_logging
lb517290079的专栏
07-07 202
提示：Oracle的隐含参数只应该在测试环境或者在Oracle Support的支持下使用。 从Oracle的系统表中，我们知道Oracle存在一个隐含参数_disable_logging可以用于禁用日志生成，这个参数显然只能用于测试目的（可以极大提高Benchmark测试的性能），禁止日志生成必然导致事务的不可恢复性。 SQL> select ksppinm,ksppdesc f...
使用隐含参数_disable_logging分析oracle写redo logfile的性能
姚远OracleACE的博客
08-31 287
oracle有一个隐含参数_disable_logging可以禁止日志的生成，这个参数当然不能在生产库使用，但我们可以将其因为与测试，例如，如果我们怀疑数据库写redo logfile存在性能问题，我们可以将这个参数设置为true，禁止写日志，看看oracle的性能提高了多少。 SQL> alter system set "_disable_logging"=true ; alter system set "_disable_logging"=true * ERROR
蚁剑的能绕过disable_functions的插件
06-21
蚁剑的能绕过disable_functions的插件,插件无法下载问题
ulps_enable_disable.zip
10-18
标题 "ulps_enable_disable.zip" 暗示了这是一个与启用或禁用ULPS相关的软件配置包。...使用这些文件前，用户应确保了解ULPS的作用，并根据自身需求谨慎操作，因为错误地修改注册表设置可能导致系统不稳定甚至损坏。
disableditemscombobox_src.zip_ combobox disable_COMBOBOX_checkbo
07-15
部分选项可以处于非激活(disable)状态的复选框
oracle alter table logging,详解Oracle中的隐含参数_disable_logging
weixin_27015733的博客
04-03 571
注意：Oracle的隐含参数只应该在测试环境或者在Oracle Support的支持下使用。从Oracle的系统表中，我们知道Oracle存在一个隐含参数_disable_logging可以用于禁用日志生成，这个参数显然只能用于测试目的(可以极大提高Benchmark测试的性能)，禁止日志生成必然导致事务的不可恢复性,而且会导致日志文件损坏。SQL> select ksppinm,ksppd...
隐含参数_DISABLE_LOGGING导致数据库的损坏在重启数据库时报ORA-19821
08-09 268
由于修改了隐含参数_DISABLE_LOGGING为TRUE：_disable_logging = TRUE 那么启动数据库后进行任何的操作，在关闭数据库后，就会发现数据库出现了损坏：SQL> startup ...
_disable_logging 对于归档数据库的影响
weixin_34162695的博客
06-23 85
_disable_logging 对于归档数据库的影响 2008-6-23 事件：为了测试硬盘IO是否是影响数据库性能的瓶颈，将数据库关闭redo log记录。设置_disable_logging＝true。测试结束后，直接alter system set "_disable_logging"=false; alter system switch logfile; 后一直做不完，DB H...
参数 _disable_logging 和 _allow_resetlogs_corruption 使用
cuchou5321的博客
07-29 182
今天主要给大家介绍一下oracle的两个隐含参数_disable_logging与_allow_resetlogs_corruption。 通过下面的试验，给大家介绍这个两个参数的作用。以下的试验仅作学习测试用，实际情况需慎重...
_disable_logging如何禁止日志的生成
weixin_30814319的博客
03-31 463
在我们的实际的工作中,非归档模式下(注:归档模式会导致日志损坏)使用_disable_logging可以禁止日志的生成,在此条件下可以很大的提高某些特殊操作(例如批量加载或者Benchmark测试等)的性能. 禁止完成的参考示例: 首先我们需要启动两个Session,一个用来管理,一个用来测试。 1.Session 1 ,使用SYS用户连接数据库,当前_disable_logg...
隐含参数_disable_logging对数据库的负作用（1）
lunar的小铺
04-18 3144
不管是归档数据库，还是非归档数据库，只要设置了_disable_logging=true参数，那么在数据库的启动过程中都会因为ORA-07445 core dump [kcrfwcint()+1625]而异常终止的。隐含参数_disable_logging对数据库的负作用 本文作者: Lunar (lunar.zhang@gmail.com ) 摘要：“有oracle dba的地方
Golang(14)Error Handle Debugging Logging
快马扬鞭须努力！
05-22 108
Golang(14)Error Handle Debugging Logging1. Error Handlefunc Open(name string) (file *File, err error)It will return the err if we open file fail.f, err := os.Open(“filename.ext”)if err != nil {     lo...
_disable_logging对于归档数据库的影响
lunar的小铺
04-18 2914
_disable_logging对于归档数据库的影响在归档数据库下，如果设置了 _disable_logging＝true，那么数据库就会将所有的online redo logfile标记为corrput，从而在归档数据库下不能够正常的归档了，因此，每次需要当数据库中所有的日志组归档状态都为“NO”，且STATUS列的值出现n-1个“INACTIVE”和一个“CURRENT”时，即，除了当前日
_disable_logging是否会使数据库的数据加载操作速度惊人的增加？
lunar的小铺
04-18 2427
   _disable_logging是否会使数据库的数据加载操作速度惊人的增加？首先，检查一下当前的_disable_logging参数的设置：lunar@TSMISC01> show parameter disable_loggingNAME                                 TYPE        VALUE---------------
测试隐含参数_disable_logging带来的后果（二）
老A的自留地，欢迎加微信交流，微信号zhoul777
01-07 442
前面一篇文章，数据库处于归档模式。当设置隐含参数_disable_logging带来的后果是将redolog头损坏，当数据库处于非归档模式时，数据库会怎么样呢？用测试说明问题。由于时间关系，说明暂时省略。 SQL> archive log list Database log mode No Archive Mode Automatic archival ...
探索_disable_logging的损坏作用--结论1
lunar的小铺
02-24 2550
SQL> alter database clear logfile group 1;alter database clear logfile group 1*ERROR at line 1:ORA-00350: log 1 of thread 1 needs to be archivedORA-00312: online log 1 thread 1: /oracle/oradata/TSMIS
local_irq_disable irq_disable
最新发布
07-27
local_irq_disable是一个宏定义，用于禁用中断。它的实现代码如下： ```c #define local_irq_disable() do { raw_local_irq_disable(); } while (0) #define raw_local_irq_disable() arch_local_irq_disable() #define arch_local_irq_disable() 与CPU架构有关 ``` 其中，raw_local_irq_disable()是一个函数，用于具体执行禁用中断的操作。而arch_local_irq_disable()是与CPU架构相关的函数，用于在特定的CPU架构上执行禁用中断的操作。具体的实现代码会根据不同的CPU架构而有所不同。 local_irq_disable的实现代码中，先调用raw_local_irq_disable()函数，然后再调用arch_local_irq_disable()函数。这样的设计是为了将具体的中断禁用操作与CPU架构相关的实现分离开来，提高代码的可移植性。 总结起来，local_irq_disable的实现代码是通过调用raw_local_irq_disable()和arch_local_irq_disable()函数来实现中断的禁用操作。具体的实现代码会根据不同的CPU架构而有所不同。\[1\]\[2\] #### 引用[.reference_title] - *1* [local_irq_enable 与 local_irq_disable 不支持嵌套](https://blog.csdn.net/u012385733/article/details/90483495)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^control_2,239^v3^insert_chatgpt"}} ] [.reference_item] - *2* *3* [Linux Kernel中local_irq_enable()和local_irq_disable()的实现](https://blog.csdn.net/weixin_42135087/article/details/123174867)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^control_2,239^v3^insert_chatgpt"}} ] [.reference_item] [ .reference_list ]

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值