Shulou(Shulou.com)05/31 Report--

This article mainly introduces the oracle ora00372 and ora01110 data files can not write error report how to do, the article is very detailed, has a certain reference value, interested friends must read it!

Resolve:

1. Query data file status status and its tablespace ts#:

SQL > select TS#,FILE#,STATUS,BYTES/1024/1024 size_m,NAME from v$datafile where file#=35

TS# FILE# STATUS SIZE_M NAME

32 35 ONLINE 4003.99219 / oracle10g/oradata/xzdata_4g_012

Or query the dba_data_files view, online_status,file_id,tablespace_name

SQL > select FILE_ID,FILE_NAME,TABLESPACE_NAME,BYTES/1024/1024 size_m,STATUS,ONLINE_STATUS from dba_data_files where file_id='35'

FILE_ID FILE_NAME TABLESPACE_NAME SIZE_M STATUS ONLINE_

35 / oracle10g/oradata/xzdata_4g_012 COMM_TBS 4003.99219 AVAILABLE ONLINE

-- query the name of the table space corresponding to the table space:

SQL > select TS#,NAME from v$tablespace where ts#=32

TS# NAME

32 COMM_TBS

Second, query the corresponding tablespace status:

SQL > select TABLESPACE_NAME,STATUS,CONTENTS from dba_tablespaces where TABLESPACE_NAME='COMM_TBS'

TABLESPACE_NAME STATUS CONTENTS

COMM_TBS READ ONLY PERMANENT

It is found that the original tablespace state is readonly, so data cannot be written.

The above is all the contents of this article "what to do if you can't write an error report in ora00372 and ora01110 data files in oracle". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.