당신은 주제를 찾고 있습니까 “ora-01274 cannot add data file that was originally created as – ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified“? 다음 카테고리의 웹사이트 https://ppa.charoenmotorcycles.com 에서 귀하의 모든 질문에 답변해 드립니다: ppa.charoenmotorcycles.com/blog. 바로 아래에서 답을 찾을 수 있습니다. 작성자 muhammad hussain 이(가) 작성한 기사에는 조회수 8,372회 및 좋아요 52개 개의 좋아요가 있습니다.
ora-01274 cannot add data file that was originally created as 주제에 대한 동영상 보기
여기에서 이 주제에 대한 비디오를 시청하십시오. 주의 깊게 살펴보고 읽고 있는 내용에 대한 피드백을 제공하세요!
d여기에서 ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified – ora-01274 cannot add data file that was originally created as 주제에 대한 세부정보를 참조하세요
ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified
STATUS : FAILURE TEST FAILED ORA-00604 ERROR OCCURRED AT RECURSIVE sql LEVEL 1ORA-12705
ora-01274 cannot add data file that was originally created as 주제에 대한 자세한 내용은 여기를 참조하세요.
ORA-01274: cannot add data file that was originally created as
ORA-01274: cannot add data file that was originally created as · 1. Check the standby_file_management parameter in the standby database. · 2. Cancel the recovery:
Source: dbaclass.com
Date Published: 4/30/2022
View: 5576
MRP0: Background Media Recovery terminated with error 1274
ORA-01274: cannot add data file … The ORA-01274 error is related with the new added datafile to the Production and standby_file_management …
Source: ittutorial.org
Date Published: 3/21/2022
View: 6687
MRP Fails with ORA-1274 while Creating PDB on Standby
ORA-01274: cannot add data file that was originally created as ‘
Source: support.oracle.com
Date Published: 7/21/2022
View: 2603
ORA-01274: cannot add datafile – file could not be created
Now, how to fix and restart MRP? 1:- Check where was left this file#: SQL> select name, bytes from v$datafile where file#=106; NAME BYTES — …
Source: www.alex-sanz.com
Date Published: 4/21/2021
View: 3054
ORA-01274: cannot add datafile on standby database
The file should be manually created to continue. … Recovery interrupted! … Recovery stopped due to failure in applying recovery marker (opcode …
Source: ctdba.blogspot.com
Date Published: 9/1/2022
View: 3389
Fix : ORA-01274: cannot add datafile – Gouranga’s Tech Blog
— When Standby database not in synch due to adding of new tablespace or datafile to primary se. … The file should be manually created to …
Source: facedba.blogspot.com
Date Published: 10/10/2021
View: 5691
cannot add data file that was originally created as ‘string’
Either use the ALTER DATABASE CREATE DATAFILE statement to create the file, … ORA-01274：cannot add data file that was originally created as ‘string’.
Source: www.modb.pro
Date Published: 2/16/2021
View: 544
ORA-01274 Adding file in DATAGUARD having …
On Physical Standby · Identifying unnamed file · Adding file in Standby. · Primary Database File system and Physical Standby ASM. · Change the …
Source: ora9212.wordpress.com
Date Published: 11/10/2022
View: 6675
Oracle 11gR2 ORA-01274 cannot add datafile ‘string’
Oracle Database Error Code ORA-01274 Description … Cause: Automated standby file management was disabled, so an added file could not automatically be created on …
Source: www.oraexcel.com
Date Published: 6/18/2022
View: 1032
Physical Reserve ORA 01274 Problem Handling
1. standby_of the repositoryFile_Management is to be set to MANUAL state. · 2. Find the name of the file that cannot be created in the repository.
Source: programming.vip
Date Published: 5/17/2021
View: 561
주제와 관련된 이미지 ora-01274 cannot add data file that was originally created as
주제와 관련된 더 많은 사진을 참조하십시오 ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified. 댓글에서 더 많은 관련 이미지를 보거나 필요한 경우 더 많은 관련 기사를 볼 수 있습니다.
주제에 대한 기사 평가 ora-01274 cannot add data file that was originally created as
- Author: muhammad hussain
- Views: 조회수 8,372회
- Likes: 좋아요 52개
- Date Published: 2019. 9. 6.
- Video Url link: https://www.youtube.com/watch?v=1NjL8yJwCC8
ORA-01274: cannot add data file that was originally created
PROBLEM:
After adding a datafile in primary database, recovery process in standby stopped with below error.
— Primary database:
SQL> alter tablespace prim add datafile size 1g;
Tablespace altered.
— Error in alert log of standby database
File #5 added to control file as ‘UNNAMED00005’ because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
MRP0: Background Media Recovery terminated with error 1274
Fri Feb 10 12:19:57 2017
Errors in file /oracle/app/oracle/diag/rdbms/noncdb1/STDBY/trace/STDBY_pr00_24003.trc:
ORA-01274: cannot add data file that was originally created as ‘/archive/NONPLUG/NONCDB/NONCDB/datafile/o1_mf_prim_d9v1fq7k_.dbf’
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Recovered data files to a consistent state at change 13111955
Fri Feb 10 12:19:57 2017
Errors in file /oracle/app/oracle/diag/rdbms/noncdb1/STDBY/trace/STDBY_pr00_24003.trc:
ORA-01274: cannot add data file that was originally created as ‘/archive/NONPLUG/NONCDB/NONCDB/datafile/o1_mf_prim_d9v1fq7k_.dbf’
Fri Feb 10 12:19:57 2017
Checker run found 1 new persistent data failures
Fri Feb 10 12:19:57 2017
MRP0: Background Media Recovery process shutdown (STDBY)
SOLUTION:
This issue happens, when the standby_file_management parameter is set to MANUAL in standby database. So when a datafile is added in primary database, standby database is unable to process it. To fix it follow the below process
1. Check the standby_file_management parameter in the standby database.
SQL> show parameter standby NAME TYPE VALUE ———————————— ———– —————————— standby_archive_dest string ?/dbs/arch standby_file_management string MANUAL
2. Cancel the recovery:
SQL> recover managed standby database disconnect from session; Media recovery complete.
3. Check the file, which caused the issue:[ STANDBY]
SQL> select file#, error, name from v$datafile_header where ERROR=’FILE MISSING’; FILE# ERROR ———- —————————————————————– NAME ——————————————————————————– 5 FILE MISSING SQL> select name from v$datafile where file#=5; NAME ——————————————————————————– /oracle/app/oracle/product/12.1.0.2/dbhome_1/dbs/UNNAMED00005
3. Recreate the datafile as below [ STANDBY ]
SQL> alter database create datafile ‘/oracle/app/oracle/product/12.1.0.2/dbhome_1/dbs/UNNAMED00005’ as new; database altered.
If you dont have OMF files, then get the exact datafile name from primary and recreate.
— Primary SQL> select name from v$datafile where file#=5; NAME ——————————————————————————– /archive/NONPLUG/NONCDB/NONCDB/datafile/o1_mf_prim_d9v1fq7k_.dbf — Recreate datafile in standby SQL> alter database create datafile ‘/oracle/app/oracle/product/12.1.0.2/dbhome_1/dbs/UNNAMED00005’ as ‘/archive/NONPLUG/NONCDB/NONCDB/datafile/o1_mf_prim_d9v1fq7k_.dbf’;
4. Set standby_file_management to AUTO, to avoid similar issue in future
alter system set standby_file_management=AUTO scope=both;
5. Start recovery in standby database
alter database recover managed standby database disconnect from session;
MRP0: Background Media Recovery terminated with error 1274
I got ” MRP0: Background Media Recovery terminated with error 1274 after adding a Datafile ” error in Oracle dataguard ( Standby Site ).
MRP0: Background Media Recovery terminated with error 1274
Details of error are as follows.
File #692 added to control file as ‘UNNAMED00692’ because the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL The file should be manually created to continue. Errors with log +ARCH_MSDB/MSDBDR/ARCHIVELOG/2020_12_02/thread_4_seq_336447.1795.1058125471 PR00 (PID:94177): MRP0: Background Media Recovery terminated with error 1274 2020-12-06T09:57:00.113322+03:00 Errors in file /u01/app/oracle/diag/rdbms/MSDBdr/MSDBDR1/trace/MSDBDR1_pr00_94177.trc: ORA-01274: cannot add data file that was originally created as ‘+DATA/MSDB/DATAFILE/bigdatatbs.184399.1058113529’ 2020-12-06T09:57:01.755485+03:00 Recovery interrupted! 2020-12-06T09:58:53.698469+03:00 rfs (PID:322307): Archived Log entry 4725 added for B-977575671.T-8.S-359459 ID 0x7a7af737 LAD:2
ORA-01274: cannot add data file
The ORA-01274 error is related with the new added datafile to the Production and standby_file_management parameter is set to MANUAL in standby database.
This Error occurs if we add a Datafile OR Tablespace in PRIMARY Database and that could not be translated to the Standby Database due to these Reasons:
Standby_file_management is set to MANUAL
Primary & Physical Standby are having different file structures and DB_FILE_NAME_CONVERT is not set according to the Directory Structures in Primary and Standby
Insufficient Space or wrong Permissions on the Standby Database to create the Datafile
If standby_file_management is set to Auto ,but directory path of Primary and standby are different , db_file_name_convert is not set ,but db_create_file_dest has been set to wrong value on standby.
The Redo Log generated from Primary will have Information about the Tablespace / Datafile added however it could not be created successfully in Physical Standby Database due to the standby_file_management = MANUAL
or is not able to find the specified Folder due to a missing / incorrect Filename Conversion.
The File Entry is added to Standby Controlfile as “UNNAMED0000n” in /dbs or /database
folder depends on the Operating System and eventually the MRP terminates.
SQL> show parameter standby_file NAME TYPE VALUE ———————————— ———– —————————— standby_file_management string MANUAL SQL>
To solve this error, Find the unnamed file in Standby. You can find out This unnamed filename both in alertlog and with the following script.
SQL> select file#,name from v$datafile where name like ‘%UNNAMED%’; /u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/UNNAMED00692
Now create it again as follows, it will solve this error.
SQL> alter database create datafile ‘/u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/UNNAMED00692’ as ‘+DATAC1’; Database altered. SQL>
And set the standby_file_management to the auto as follows.
SQL>alter database set standby_file_management = ‘auto’ scope=both sid=’*’;
Now Start the MRP Process and start dataguard again as follows.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; Database altered. SQL>
You can read the following post to see dataguard related errors.
If you want to learn how to install Dataguard ( Standby ), read the following post.
Oracle Database Tutorials for Beginners ( Junior Oracle DBA )
1,824 views last month, 1 views today
MRP Fails with ORA-1274 while Creating PDB on Standby
MRP Fails with ORA-1274 while Creating PDB on Standby (Doc ID 2423108.1)
Last updated on OCTOBER 06, 2021
Applies to:
Symptoms
MRP fails with below errors on standby while creating PDB when hot cloning of PDB is performed on primary :
Recovery created pluggable database
TEST23(5):Recovery scanning directory
/DATAFILE for any matching files MRP0: Background Media Recovery terminated with error 1274
2018-06-14T23:53:17.426215+00:00
Errors in file
/ _pr00_12190030.trc: ORA-01274: cannot add data file that was originally created as ‘
/DATAFILE/system.268.111111′ ORA-01565: error in identifying file ‘
‘ ORA-17503: ksfdopn:2 Failed to open file
ORA-15045: ASM file name ‘
‘ is not in reference form Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Changes
Cause
Sign In To view full details, sign in with your My Oracle Support account. Register Don’t have a My Oracle Support account? Click to get started!
ORA-01274: cannot add datafile – file could not be created – Database Blog
Sometimes you might see this error in a Standby DB and MRP fails:
Fri Feb 05 20:30:04 2016 Media Recovery Log +FRA/dbname/archivelog/2016_02_05/thread_1_seq_60424.32931.903038469 Media Recovery Log +FRA/dbname/archivelog/2016_02_05/thread_2_seq_57484.19935.903038469 Media Recovery Log +FRA/dbname/archivelog/2016_02_05/thread_3_seq_57737.6129.903038467 File #106 added to control file as ‘UNNAMED00106’ because the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL The file should be manually created to continue. Errors with log +FRA/dbname/archivelog/2016_02_05/thread_3_seq_57737.6129.903038467 MRP0: Background Media Recovery terminated with error 1274 Errors in file /u03/app/oracle/diag/rdbms/dbname/dbname1/trace/dbname1_pr00_14002.trc: ORA-01274: cannot add datafile ‘+DATA/dbname/datafile/tbsinstalaciones_dat.569.903038575’ – file could not be created Recovery interrupted! Fri Feb 05 20:30:17 2016 Recovered data files to a consistent state at change 203534746089 Fri Feb 05 20:30:17 2016 MRP0: Background Media Recovery process shutdown (dbname1)
Now, how to fix and restart MRP?
ORA-01274: cannot add datafile on standby database
File #17 added to control file as ‘UNNAMED00017’ because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
MRP0: Background Media Recovery terminated with error 1274
Errors in file /u01/app/oracle/diag/rdbms/test/test2/trace/test2_pr00_261555.trc:
ORA-01274: cannot add datafile ‘+DATA01/test02/datafile/fct_ir_ic_rated_201710_data.15961.957834065’ – file could not be created
Fri Oct 20 01:01:57 2017
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Fri Oct 20 01:04:54 2017
Recovery stopped due to failure in applying recovery marker (opcode 17.30).
Datafiles are recovered to a consistent state at change 8889714250266 but controlfile could be ahead of datafiles.
SQL> show parameter standby_file_management
NAME TYPE VALUE
———————————— ———– ——————————
standby_file_management string MANUAL
SQL> select file#, name from v$datafile where file#=17;
FILE# NAME
——————————————————————————–
17 /u01/app/oracle/product/11.2.0.4/dbhome_2/dbs/UNNAMED00017
SQL> alter database create datafile ‘/u01/app/oracle/product/11.2.0.4/dbhome_2/dbs/UNNAMED00017’ as ‘+DATA01/test02/datafile/fct_ir_ic_rated_201710_data.15961.957834065’;
alter database create datafile ‘/u01/app/oracle/product/11.2.0.4/dbhome_2/dbs/UNNAMED00017’ as ‘+DATA01/test02/datafile/fct_ir_ic_rated_201710_data.15961.957834065’
*
ERROR at line 1:
ORA-01276: Cannot add file
+DATA01/test02/datafile/fct_ir_ic_rated_201710_data.15961.957834065. File has
an Oracle Managed Files file name.
SQL> alter database create datafile ‘/u01/app/oracle/product/11.2.0.4/dbhome_2/dbs/UNNAMED00017’ as ‘+DATA01′;
Database altered.
SQL> select file#, name from v$datafile where file#=17;
FILE# NAME
——————————————————————————–
17 +DATA01/test/datafile/fct_ir_ic_rated_201710_data.7440.958128309
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO scope=both sid=’*’;
System altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
SQL> select process, status , sequence# from v$managed_standby;
MOS: Doc ID 739618.1
ORA-01274：cannot add data file that was originally created as ‘string’
错误描述：cannot add data file that was originally created as ‘string’
错误原因：The recovery failed to add the specified data file either because the recovery tried to create the specified data file but automated standby file management was disabled, or the recovery tried to look for the specified data file but the data file did not exist. In the former case, the recovery added a control file entry as ‘UNNAMEDnnnnn’.
解决方法：Either use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO, or restore the data file to the location specified by the corresponding control file entry, and restart standby recovery.
ORA-01274 Adding file in DATAGUARD having heterogeneous file system
Error Message in Alert log
File #911 added to control file as ‘UNNAMED00911’ because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
Errors with log /ora_arch01/arch01/archive/arch_2_7406_768211041.arch
MRP0: Background Media Recovery terminated with error 1274
Errors in file /orcl11g/11.2.0.4/diag/rdbms/db11gpr/db11gpr/trace/db11gpr_pr00_3777.trc:
ORA-01274: cannot add datafile ‘+DATA/db11g_rb1/datafile/large_index.869.922820761’ – file could not be created
Sat Sep 17 19:17:16 2014
Recovery interrupted!
Solution:
On Physical Standby
SQL>Alter system set STANDBY_FILE_MANAGEMENT=MANUAL scope=both
Identifying unnamed file
Media recovery (MRP) interrupt after creating a UNNAMED file get the information of unnamed file.
SQL> select file#,name from v$datafile where name like ‘UNNAME%’;
FILE# NAME
——– ————————————————————–
911 /orcl11g/11.2.0.4/dbhome_1/dbs/UNNAMED00911
Adding file in Standby.
Scenarios:
Primary Database ASM and Physical Standby file system based. Primary Database File system and Physical Standby ASM.
Primary Database ASM and Physical Standby file system based.
If the standby is in ASM + OMF then use the below command,
SQL> alter database create datafile ‘/orcl11g/11.2.0.4/dbhome_1/dbs/UNNAMED00911’ as ‘+DATA’ 20G;
You need to mention the size of datafile when you add in ASM based standby.
Primary Database File system and Physical Standby ASM
SQL> alter database create datafile ‘/orcl11g/11.2.0.4/dbhome_1/dbs/UNNAMED00911’ as ‘/oradata/db11g/sales01.dbf’;
No need to mention the size.
Change the STANDBY_FILE_MANAGMENT to AUTO
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO scope=both;
Start the MRP (this is using Real Time Apply)
SQL> alter database recover managed standby database using current logfile disconnect;
Verify the MRP is running as expected
SQL> select process, status , sequence# from v$managed_standby;
Oracle 11gR2 ORA-01274 cannot add datafile ‘string’
Database: 11g Release 2
Error code: ORA-01274
Description: cannot add datafile ‘string’ – file could not be created
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is ‘UNNAMEDnnnnn’.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
Database: 10g Release 1
Error code: ORA-01274
Description: cannot add datafile ‘string’ – file could not be created
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The controlfile file entry for the file is ‘UNNAMEDnnnnn’.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
Database: 10g Release 2
Error code: ORA-01274
Description: cannot add datafile “string” – file could not be created
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is “UNNAMEDnnnnn”.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
Database: 11g Release 1
Error code: ORA-01274
Description: cannot add datafile ‘string’ – file could not be created
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is ‘UNNAMEDnnnnn’.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
Database: 12c Release 1
Error code: ORA-01274
Description: cannot add datafile ‘string’ – file could not be created
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is ‘UNNAMEDnnnnn’.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
Database: 12c Release 2
Error code: ORA-01274
Description: cannot add data file that was originally created as ‘ string ‘
Cause: The recovery failed to add the specified data file either because the recovery tried to create the specified data file but automated standby file management was disabled, or the recovery tried to look for the specified data file but the data file did not exist. In the former case, the recovery added a control file entry as ‘UNNAMEDnnnnn’.
Action: Either use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO, or restore the data file to the location specified by the corresponding control file entry, and restart standby recovery.
Database: 18c Release 1
Error code: ORA-01274
Description: cannot add data file that was originally created as ‘string’
Cause: The recovery failed to add the specified data file either because the recovery tried to create the specified data file but automated standby file management was disabled, or the recovery tried to look for the specified data file but the data file did not exist. In the former case, the recovery added a control file entry as ‘UNNAMEDnnnnn’.
Action: Either use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO, or restore the data file to the location specified by the corresponding control file entry, and restart standby recovery.
Physical Reserve ORA 01274 Problem Handling
My physical standby failed to start and terminate MRP due to ora 01274 problem.This problem is very simple to handle, but Baidu almost took me to the pit after searching an article, so I wrote down the standard steps of MOS for your friends to refer to.
This DG environment was built two weeks ago and needs to be officially switched today.Before switching, it is customary to check the status of the primary backup.This check found that the repository has not been logged for more than a week.Since the DG setup has a checklist, it is not forgotten to turn on MRP, but there must be a problem in the middle that caused the log application to fail.Looking at the repository alert, the following errors were found:
Fri Nov 24 16:39:15 2017 File #9 added to control file as ‘UNNAMED00009’ because the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL The file should be manually created to continue. MRP0: Background Media Recovery terminated with error 1274 Errors in file /u01/app/oracle/diag/rdbms/dbnamestby/dbname/trace/dbname_pr00_46964.trc: ORA-01274: cannot add datafile ‘+DATA/dbnameprmy/datafile/datafile.491.960914347’ – file could not be created Managed Standby Recovery not using Real Time Apply Recovery interrupted! Recovery stopped due to failure in applying recovery marker (opcode 17.30). Datafiles are recovered to a consistent state at change 12687535588875 but controlfile could be ahead of datafiles. Fri Nov 24 16:39:17 2017 MRP0: Background Media Recovery process shutdown (dbname)
View the error code:
01274, 0000, “cannot add datafile ‘%s’ – file could not be created” // *Cause: Automated standby file management was disabled, so an added file // could not automatically be created on the standby. // The error from the creation attempt is displayed in another message. // The control file file entry for the file is ‘UNNAMEDnnnnn’. // *Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the // file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart // standby recovery.
The solution is also simple: (Note: For versions below 12c.My version is 11.2.For PDB, there are additional steps on MOS)
1. standby_of the repositoryFile_Management is to be set to MANUAL state.
2. Find the name of the file that cannot be created in the repository
SQL> select name from v$datafile; NAME ——————————————————————————– D:\ORADATA\MYSTD\SYSTEM.DBF D:\ORADATA\MYSTD\UNDO.DBF D:\ORADATA\MYSTD\SYSAUX.DBF D:\ORADATA\MYSTD\SERVICE01.DBF C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UNNAMED00005
3. Rebuild the data file
SQL> alter database create datafile ‘C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\UNNAMED00005’ as ‘D:\oradata\mystd\sales01.dbf’;
SQL> alter database create datafile ‘/oracle/product/GSIPRDGB/dbs/UNNAMED00210’ as <'+ASMDISKGROUPNAME'> size
; or SQL>alter database create datafile ‘/oracle/product/GSIPRDGB/dbs/UNNAMED00210’ as new; If the backup library uses ASM+OMF, the following commands can also be used:4. Look at the new data file names and they should be consistent
SQL> select name from v$datafile; NAME ——————————————————————————– D:\ORADATA\MYSTD\SYSTEM.DBF D:\ORADATA\MYSTD\UNDO.DBF D:\ORADATA\MYSTD\SYSAUX.DBF D:\ORADATA\MYSTD\SERVICE01.DBF D:\ORADATA\MYSTD\SALES01.DBF
5. STANDBY_FILE_The MANAGEMENT parameter is modified to AUTO in case this happens in the future.
6. Turn on MRP.
You can see redo in the log.
키워드에 대한 정보 ora-01274 cannot add data file that was originally created as
다음은 Bing에서 ora-01274 cannot add data file that was originally created as 주제에 대한 검색 결과입니다. 필요한 경우 더 읽을 수 있습니다.
이 기사는 인터넷의 다양한 출처에서 편집되었습니다. 이 기사가 유용했기를 바랍니다. 이 기사가 유용하다고 생각되면 공유하십시오. 매우 감사합니다!
사람들이 주제에 대해 자주 검색하는 키워드 ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified
- ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified
- NLS Data Files Or Invalid Environment Specified
- ORA-12705
- Cannot Access NLS Data Files Or Invalid Environment Specified
- ORACLE-12705
- STATUS : FAILURE TEST FAILED ORA-00604 ERROR OCCURRED AT RECURSIVE sql LEVEL 1ORA-12705
- EST FAILED ORA-00604 ERROR OCCURRED AT RECURSIVE sql LEVEL
- 1ORA-12705
- ORA-00604
- STATUS : FAILURE TEST FAILED ORA-00604
ORA-12705: #Cannot #Access #NLS #Data #Files #Or #Invalid #Environment #Specified
YouTube에서 ora-01274 cannot add data file that was originally created as 주제의 다른 동영상 보기
주제에 대한 기사를 시청해 주셔서 감사합니다 ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified | ora-01274 cannot add data file that was originally created as, 이 기사가 유용하다고 생각되면 공유하십시오, 매우 감사합니다.
