saup007

133 积分	0 好友	17 主题

发消息

[SQL调优] SYS_AUTO_SQL_TUNING_TASK的job跑失败，连接2天失效了。<结贴>

1^#

发表于 2012-12-6 15:35:55 | 查看: 10814| 回复: 6

本帖最后由 saup007 于 2012-12-29 09:13 编辑

更新：

今天晚上22点，又跑失败了，肿么回事？

在MOS没找到对应的文章。

同样的错误ORA-01461: can bind a LONG value only for insert into a LONG column，也可以做实验再现，只是不知道scheduler job怎么也报这个，难道是bug？

linux 5.6 x86_64
oracle 11.2.0.2.0

alter 日志：

Wed Dec 05 22:17:32 2012
SYS_AUTO_SQL_TUNING_TASK exiting with error "1461" for execution "EXEC_61608". See DBA_ADVISOR_EXECUTIONS for more details.
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Errors in file /u01/app/oracle/diag/rdbms/yongbing/YONGBING/trace/YONGBING_j004_18678.trc:
ORA-12012: error on auto execute of job "SYS"."ORA$AT_SQ_SQL_SW_14823"
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-06512: at "SYS.PRVT_ADVISOR", line 2735
ORA-06512: at "SYS.DBMS_ADVISOR", line 241
ORA-06512: at "SYS.DBMS_SQLTUNE", line 821
ORA-06512: at line 4

复制代码

scheduler也有报错：

SQL> select * from Dba_Scheduler_Job_Run_Details WHERE status <> 'SUCCEEDED';
LOG_ID LOG_DATE OWNER JOB_NAME STATUS RUN_DURATION ADDITIONAL_INFO
---------- --------------------------------------- ------ ---------------------- ------- ------------- -------------------------------------------------------------------
211333 05-12月-12 10.17.32.347700 下午 +08:00 SYS ORA$AT_SQ_SQL_SW_14823 FAILED +000 00:17:30 ORA-01461: can bind a LONG value only for insert into a LONG column

复制代码

alter日志建议查看DBA_ADVISOR_EXECUTIONS

SQL> select * from DBA_ADVISOR_EXECUTIONS t where task_name='SYS_AUTO_SQL_TUNING_TASK';
OWNER TASK_ID TASK_NAME EXECUTION_ID EXECUTION_TYPE EXECUTION_TYPE# EXECUTION_START ADVISOR_NAME ADVISOR_ID STATUS STATUS# ERROR_MESSAGE
------ ---------- ------------------------------------------ --------------- --------------- --------------- ------------------ ---------- ----------- ---------- --------------------------------------------
SYS 1 SYS_AUTO_SQL_TUNING_TASK 61608 TUNE SQL 1 2012/12/5 22:00：02 SQL Tuning Advisor 4 FATAL ERROR 6 ORA-01461: 仅能绑定要插入 LONG 列的 LONG 值
30 rows selected

复制代码

trace 文件：

$ cat /u01/app/oracle/diag/rdbms/yongbing/YONGBING/trace/YONGBING_j004_18678.trc
Trace file /u01/app/oracle/diag/rdbms/yongbing/YONGBING/trace/YONGBING_j004_18678.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: dbserver2
Release: 2.6.18-238.19.1.el5xen
Version: #1 SMP Fri Jul 15 08:16:59 EDT 2011
Machine: x86_64
VM name: Xen Version: 3.1 (PVM)
Instance name: YONGBING
Redo thread mounted by this instance: 1
Oracle process number: 95
Unix process pid: 18678, image: oracle@dbserver2 (J004)
*** 2012-12-05 22:00:31.151
*** SESSION ID:(1397.63227) 2012-12-05 22:00:31.151
*** CLIENT ID:() 2012-12-05 22:00:31.151
*** SERVICE NAME:(SYS$USERS) 2012-12-05 22:00:31.151
*** MODULE NAME:(DBMS_SCHEDULER) 2012-12-05 22:00:31.151
*** ACTION NAME:(ORA$AT_SQ_SQL_SW_14823) 2012-12-05 22:00:31.151
status=(pst=ERROR)
error: pos=0, message follows:
kestsDumpMsg(): dump message
msg=(@=0x2ad7126cc3d8, fac=ORA, cod=16960, p1=ORA-16960: SQL Analyze could not reproduce the desired plan.)
*** 2012-12-05 22:14:23.599
status=(pst=SUCCESS)
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 477607
CU gets: 0
Disk Reads: 409893
Disk Writes: 0
IO Read Requests: 35590
IO Write Requests: 0
Bytes Read: 3357843456
Bytes Written: 0
Bytes Exchanged with Storage: 3357843456
Bytes Exchanged with Disk: 3357843456
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 13 (s)
CPU Time: 3236 (ms)
User I/O Time: 9327 (ms)
status=(pst=ERROR)
status=(pst=SUCCESS)
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 393109
CU gets: 0
Disk Reads: 8368
Disk Writes: 0
IO Read Requests: 8351
IO Write Requests: 0
Bytes Read: 68550656
Bytes Written: 0
Bytes Exchanged with Storage: 68550656
Bytes Exchanged with Disk: 68550656
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 7245 (ms)
CPU Time: 2116 (ms)
User I/O Time: 4847 (ms)
*** 2012-12-05 22:14:43.598
status=(pst=SUCCESS)
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 2305
CU gets: 0
Disk Reads: 0
Disk Writes: 0
IO Read Requests: 0
IO Write Requests: 0
Bytes Read: 0
Bytes Written: 0
Bytes Exchanged with Storage: 0
Bytes Exchanged with Disk: 0
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 8831 (us)
CPU Time: 6800 (us)
User I/O Time: 0 (us)
status=(pst=SUCCESS)
*** 2012-12-05 22:16:08.786
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 76936
CU gets: 2
Disk Reads: 587
Disk Writes: 0
IO Read Requests: 587
IO Write Requests: 0
Bytes Read: 4808704
Bytes Written: 0
Bytes Exchanged with Storage: 4808704
Bytes Exchanged with Disk: 4808704
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 3047 (ms)
CPU Time: 224 (ms)
User I/O Time: 2678 (ms)
status=(pst=ERROR)
status=(pst=SUCCESS)
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 10984
CU gets: 2
Disk Reads: 509
Disk Writes: 0
IO Read Requests: 504
IO Write Requests: 0
Bytes Read: 4169728
Bytes Written: 0
Bytes Exchanged with Storage: 4169728
Bytes Exchanged with Disk: 4169728
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 154 (ms)
CPU Time: 139 (ms)
User I/O Time: 14 (ms)
*** 2012-12-05 22:17:24.011
status=(pst=SUCCESS)
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 100734
CU gets: 0
Disk Reads: 90330
Disk Writes: 0
IO Read Requests: 1838
IO Write Requests: 0
Bytes Read: 739983360
Bytes Written: 0
Bytes Exchanged with Storage: 739983360
Bytes Exchanged with Disk: 739983360
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 6862 (ms)
CPU Time: 1068 (ms)
User I/O Time: 5197 (ms)
*** 2012-12-05 22:17:32.235
ORA-12012: error on auto execute of job "SYS"."ORA$AT_SQ_SQL_SW_14823"
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-06512: at "SYS.PRVT_ADVISOR", line 2735
ORA-06512: at "SYS.DBMS_ADVISOR", line 241
ORA-06512: at "SYS.DBMS_SQLTUNE", line 821
ORA-06512: at line 4

复制代码

分享0

收藏0 回复只看该作者道具举报

saup007

7^#

发表于 2012-12-29 09:09:53

本帖最后由 saup007 于 2012-12-29 09:12 编辑

Liu Maclean(刘相兵发表于 2012-12-7 21:01
SQL 过长确实可能是引起该问题的一种原因，还是建议禁止该自动tuning job

SQL> select object_id from dba_advisor_objects where execution_name='EXEC_61608'
2 minus
3 select object_id FROM dba_advisor_findings where execution_name='EXEC_61608'
4 ;
OBJECT_ID
----------
62611
62724
查找这两个对象对应的SQL:
SQL> col ATTR1 for a30
SQL> col ATTR3 for a30
SQL>
SQL>
SQL>
SQL> select object_id,type,task_name,ATTR1,ATTR3 from dba_advisor_objects where object_id in (62611,62724);
OBJECT_ID TYPE TASK_NAME ATTR1 ATTR3
---------- ------------------------------ ------------------------------ ------------------------------ ------------------------------
62611 AUTOMATIC SQL WORKLOAD SYS_AUTO_SQL_TUNING_TASK 124
62724 SQL SYS_AUTO_SQL_TUNING_TASK ct94ypw24bjtn zhongyl
SQL> select sql_id,to_char(sql_text) from dba_hist_sqltext where sql_id='ct94ypw24bjtn';
select sql_id,to_char(sql_text) from dba_hist_sqltext where sql_id='ct94ypw24bjtn'
ORA-22835: 缓冲区对于 CLOB 到 CHAR 转换或 BLOB 到 RAW 转换而言太小 (实际: 12044, 最大: 4000)

复制代码

手工对这个SQL调用 DBMS_SQLTUNE:

SQL> DECLARE
2 l_sql_tune_task_id VARCHAR2(100);
3 v_sql clob:='select *
4 from username.table_name t
5 where t.user_id in
6 (
7 1847,
...............
1003 1856
1004 )';
1005 BEGIN
1006 l_sql_tune_task_id := DBMS_SQLTUNE.create_tuning_task (
1007 sql_text => v_sql,
1008 scope => DBMS_SQLTUNE.scope_comprehensive,
1009 time_limit => 60,
1010 task_name => 'ct94ypw24bjtn_tuning_task',
1011 description => 'Tuning task for statement ct94ypw24bjtn.');
1012 DBMS_OUTPUT.put_line('l_sql_tune_task_id: ' || l_sql_tune_task_id);
1013 END;
1014 /
DECLARE
l_sql_tune_task_id VARCHAR2(100);
v_sql clob:='select *
from username.表 t
where t.user_id in
(
..........
ORA-13607: 指定的任务或对象 ct94ypw24bjtn_tuning_task 已存在
ORA-06512: 在 "SYS.DBMS_SQLTUNE_INTERNAL", line 7625
ORA-06512: 在 "SYS.PRVT_SQLADV_INFRA", line 40
ORA-06512: 在 "SYS.DBMS_SQLTUNE", line 629
ORA-06512: 在 line 1006
SQL>
这里报错是因为我之前已经执行过了。
SQL> begin
2 DBMS_SQLTUNE.execute_tuning_task(task_name => 'ct94ypw24bjtn_tuning_task');
3 end;
4 /
begin
DBMS_SQLTUNE.execute_tuning_task(task_name => 'ct94ypw24bjtn_tuning_task');
end;
ORA-01461: 仅能绑定要插入 LONG 列的 LONG 值
ORA-06512: 在 "SYS.PRVT_ADVISOR", line 2735
ORA-06512: 在 "SYS.DBMS_ADVISOR", line 241
ORA-06512: 在 "SYS.DBMS_SQLTUNE", line 837
ORA-06512: 在 line 2

复制代码

鉴于这是一个偶然调用的SQL，所以我删除其对应的SNAPSHOT，这样在SYS_AUTO_SQL_TUNING_TASK执行的时候，就不会对其进行分析了。
SQL> select to_char(timestamp,'yyyymmdd hh24:mi:ss') from dba_hist_sql_plan where sql_id='ct94ypw24bjtn';
TO_CHAR(TIMESTAMP,'YYYYMMDDHH2
------------------------------
20121205 10:13:27
20121205 10:13:27
通过以下SQL找到对应的 SNAPSHOT
select */*to_char(begin_interval_time,'yyyymmdd hh24:mi:ss'),to_char(end_interval_time,'yyyymmdd hh24:mi:ss')*/ from dba_hist_snapshot where begin_interval_time >= to_date('20121205 09:50:00','yyyymmdd hh24:mi:ss') and end_interval_time <= to_date('20121205 10:40:00','yyyymmdd hh24:mi:ss')
删除SNAPSHOT：
SQL> exec dbms_workload_repository.drop_snapshot_range(23418,23418,2205571097);
PL/SQL procedure successfully completed
以后正常了。
select * FROM DBA_AUTOTASK_TASK
这个视图记录了 sql tuning advisor 是否ENABLED.
其实这个job enable、disable意义并不大，因为默认不接受自动生成的SQL PROFILE，需要更改配置
BEGIN
DBMS_SQLTUNE.SET_TUNING_TASK_PARAMETER(
task_name => 'SYS_AUTO_SQL_TUNING_TASK',
parameter => 'ACCEPT_SQL_PROFILES',
value => 'TRUE');
END;
/

复制代码

回复只看该作者道具举报

Liu Maclean(刘相兵

6^#

发表于 2012-12-7 21:01:36

SQL 过长确实可能是引起该问题的一种原因，还是建议禁止该自动tuning job

回复只看该作者道具举报

saup007

5^#

发表于 2012-12-7 15:23:32

本帖最后由 saup007 于 2012-12-7 15:28 编辑

Liu Maclean(刘相兵发表于 2012-12-6 22:50
在MOS没找到对应的文章。=> 为啥我一下就找到了呢？考虑禁用该自动tuning job 来绕过该问题吧，运行以下 ...

2012-12-05 job_name='ORA$AT_SQ_SQL_SW_14823'

select * from dba_hist_active_sess_history where action='ORA$AT_SQ_SQL_SW_14823'
order by to_char(sample_time,'yyyymmdd hh24:mi:ss') desc ;
--最后一个运行sql_id='2x7umvydhanuq'
select length(sql_text) from dba_hist_sqltext where sql_id='2x7umvydhanuq'
--长度为89026

复制代码

2012-12-06 job_name='ORA$AT_SQ_SQL_SW_14843'
select * from dba_hist_active_sess_history where action='ORA$AT_SQ_SQL_SW_14843'
order by to_char(sample_time,'yyyymmdd hh24:mi:ss') desc ;
--最后一个运行sql_id='2x7umvydhanuq'
select length(sql_text) from dba_hist_sqltext where sql_id='2x7umvydhanuq'
--长度为89026

复制代码

sql_id的文本在2x7umvydhanuq.sql里

select sql_id,max(length(sql_text)) from dba_hist_sqltext
group by sql_id order by max(length(sql_text)) desc
SQL_ID MAX(LENGTH(SQL_TEXT))
1 2x7umvydhanuq 89026
2 byz2v1s7n7bsk 44643
3 5xxxrg5ckv1k3 15477
4 1m9jgx6ftdx76 13986
5 6qjjq18g2f7ur 12843
6 93fhja4nptvy6 12842

复制代码

2x7umvydhanuq.txt (86.94 KB, 下载次数: 1388)

Desktop.rar (40.91 KB, 下载次数: 1665)

回复只看该作者道具举报

saup007

4^#

发表于 2012-12-7 00:44:37

Liu Maclean(刘相兵发表于 2012-12-6 22:50
在MOS没找到对应的文章。=> 为啥我一下就找到了呢？考虑禁用该自动tuning job 来绕过该问题吧，运行以下 ...

HI，Maclean：
不是没有搜MOS等现成的，我的确搜了好久，挨个看也没找到，除了打不开的《Write Formula Form, Errors: ORA-01461: Can bind a LONG value only for insert into a LONG column(806895.1)》

我记得bug都在知识库有文章记录？

在“搜索源”，为“搜索知识库”，加上bug db或所有源就可以搜到了。真心是杯具。MOS还是用的不熟。谢谢Maclean。

回复只看该作者道具举报

Liu Maclean(刘相兵

3^#

发表于 2012-12-6 22:50:48

saup007 发表于 2012-12-6 16:25
我猜是不是这种可能？

SYS.PRVT_ADVISOR.SET_TASK_PARAMETER因为L_DATA VARCHAR2( 32767) := DATA; 当VAR ...

在MOS没找到对应的文章。=> 为啥我一下就找到了呢？

dr: 12957646 11.2.0.2 RDBMS 11.2.0.2 SVRMAN SQLTN PRODID-5 PORTID-226 ORA-1461
Abstract: ORA-1461 DURING AUTOTASK RUN
BUG TYPE CHOSEN
===============
Code
SubComponent: Dictionary
========================
DETAILED PROBLEM DESCRIPTION
============================
unable to use Automatic tuning task due to :
ORA-1461: Ein LONG-Wert kann nur zur Einfügung in eine LONG-Spalte gebunden
werden
----- Current SQL Statement for this session (sql_id=3m8smr0v7v1m6) -----
INSERT INTO sys.wri$_adv_message_groups
(task_id,id,seq,message#,fac,hdr,lm,nl,p1,p2,p3,p4,p5)
VALUES (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13)
DIAGNOSTIC ANALYSIS
===================
failing request via DBMS_SCHEDULER
same request fails via SQLPLUS
WORKAROUND?
===========
No
TECHNICAL IMPACT
================
Automatic tuning task can not be used
RELATED ISSUES (bugs, forums, RFAs)
===================================
[ORA-1461 wri$_adv_message_groups]
BUG: 5877381
RDBMS 11.1.0.0 SVRMAN SQLTN PRODID-5 PORTID-46 5696361
Abstract: LNX070207 - SYS_AUTO_SQL_TUNING_TASK EXITING WITH ERROR "1461"
--> Status: 36,Duplicate Bug.
.
BUG: 5696361
RDBMS 11.0.1.3 SVRMAN SQLTN PRODID-5 PORTID-46 ORA-1461
Abstract: SYS_AUTO_SQL_TUNING_TASK FAILS WITH ORA-1461
-->Status: 31,Could Not Reproduce
.
[kgeselv <- ksesecl0 <- opiobv]
BUG: 12876003
RDBMS 11.2.0.2 DICTIONARY PRODID-5 PORTID-226
Abstract: INTERMITTENT ORA-1461 SIGNALLED ON JOBS AFTER UPGRADE FROM
11.2.0.1
Status :11
HOW OFTEN DOES THE ISSUE REPRODUCE AT CUSTOMER SITE?
====================================================
Always
DOES THE ISSUE REPRODUCE INTERNALLY?
====================================
Not attempted
EXPLAIN WHY THE ISSUE WAS NOT TESTED INTERNALLY.
================================================
not having all values for bind variables

复制代码

考虑禁用该自动tuning job 来绕过该问题吧，运行以下脚本禁用 SYS_AUTO_SQL_TUNING_TASK

BEGIN
dbms_auto_task_admin.disable(
client_name => 'sql tuning advisor',
operation => NULL,
window_name => NULL);
END;
/
select client_name,status from DBA_AUTOTASK_CLIENT where client_name='sql tuning advisor';

复制代码

回复只看该作者道具举报

saup007

2^#

发表于 2012-12-6 16:25:54

本帖最后由 saup007 于 2012-12-6 16:29 编辑

我猜是不是这种可能？

SYS.PRVT_ADVISOR.SET_TASK_PARAMETER

PROCEDURE SET_TASK_PARAMETER(TASK_NAME IN VARCHAR2,
PARAMETER IN VARCHAR2,
DATA IN VARCHAR2,
PROP IN BINARY_INTEGER := 0 ,
SCOPE IN BINARY_INTEGER := FUTURE_EXECUTIONS,
TASK_OWNER_ID IN BINARY_INTEGER := -1 ) IS
TASK_ID_NUM BINARY_INTEGER := 0 ;
TP SYS.WRI$_ADV_ABSTRACT_T;
L_DATA VARCHAR2( 32767) := DATA;
L_NAME VARCHAR2( 32767) := PARAMETER;
ADV_PROP BINARY_INTEGER;
TASK_PROP BINARY_INTEGER;
L_NEW_FLAGS BINARY_INTEGER := 0 ;
TASK_STATUS BINARY_INTEGER;
TASK_STORED_PROP NUMBER;
L_DEFAULTED BOOLEAN := FALSE;
ENAME VARCHAR2( 30);
BEGIN
IF PROP IS NULL OR PROP = 0 THEN
TASK_PROP := TASK_PROP_TASK;
ELSE
TASK_PROP := PROP;
END IF;
TASK_ID_NUM := VALIDATE_TASK(TASK_NAME, TASK_PROP, TASK_OWNER_ID);
HANDLE_LOCK(TASK_ID_NUM, TASK_LOCK_X);
CHECK_MODIFY(TASK_NAME, TASK_ID_NUM);
TP := FETCH_ADVISOR(TASK_ID_NUM);
SELECT PROPERTY
INTO ADV_PROP
FROM SYS.WRI$_ADV_DEFINITIONS
WHERE ID = TP.ADVISOR_ID;
SELECT NVL(E.STATUS, A.STATUS) STATUS#, A.PROPERTY
INTO TASK_STATUS, TASK_STORED_PROP
FROM WRI$_ADV_TASKS A, WRI$_ADV_EXECUTIONS E
WHERE A.ID = E.TASK_ID(+)
AND A.ADVISOR_ID = E.ADVISOR_ID(+)
AND A.LAST_EXEC_NAME = E.NAME(+)
AND A.ID = TASK_ID_NUM;
VALIDATE_TASK_PARAMETER(TP,
ADV_PROP,
TASK_NAME,
TASK_ID_NUM,
TASK_STATUS,
TASK_STORED_PROP,
SCOPE,
L_NAME,
L_DATA,
L_NEW_FLAGS);
IF (SCOPE = FUTURE_EXECUTIONS) THEN
IF (BITAND(ADV_PROP, ADV_PROP_MULTI_EXEC) <> 0) THEN
PROPAGATE_TASK_PARAMETER(TASK_ID_NUM, L_NAME);
END IF;
UPDATE SYS.WRI$_ADV_PARAMETERS A
SET A.VALUE = L_DATA, A.FLAGS = L_NEW_FLAGS
WHERE A.TASK_ID = TASK_ID_NUM
AND A.NAME = L_NAME
AND A.VALUE <> L_DATA;
ELSE
ENAME := GET_LAST_EXECUTION(TASK_ID_NUM);
MERGE INTO WRI$_ADV_EXEC_PARAMETERS P
USING ( SELECT TASK_ID_NUM TASK_ID,
ENAME EXEC_NAME,
L_NAME NAME,
L_DATA VALUE
FROM DUAL) I
ON (P.TASK_ID = I.TASK_ID AND P.EXEC_NAME = I.EXEC_NAME AND P.NAME = I.NAME)
WHEN MATCHED THEN
UPDATE SET P.VALUE = I.VALUE
WHEN NOT MATCHED THEN
INSERT
(TASK_ID, EXEC_NAME, NAME, VALUE)
VALUES -----2735行
(I.TASK_ID, I.EXEC_NAME, I.NAME, I.VALUE);
END IF;
UPDATE_TASK(TASK_ID_NUM);
COMMIT;
HANDLE_LOCK(TASK_ID_NUM, TASK_LOCK_R);
RETURN;
EXCEPTION
WHEN OTHERS THEN
ROLLBACK;
HANDLE_LOCK(TASK_ID_NUM, TASK_LOCK_R);
RAISE;
END SET_TASK_PARAMETER;

复制代码

因为L_DATA VARCHAR2( 32767) := DATA; 当VARCHAR2超过4000，估计就被Oracle认为是LONG类型了，在merge时报错。

16:24:41 sys@PRI11G> desc WRI$_ADV_EXEC_PARAMETERS
Name Null? Type
------------------------------------------------ --------
TASK_ID NOT NULL NUMBER
EXEC_NAME NOT NULL VARCHAR2(30)
NAME NOT NULL VARCHAR2(30)
VALUE NOT NULL VARCHAR2(4000)

回复只看该作者道具举报

返回列表

		自动登录	找回密码
密码			注册