Error From Auxiliary Database Ora-12154
Contents |
NEWNAME FOR DATAFILE and SET NEWNAME FOR TEMPFILE 2.SET NEWNAME FOR TABLESPACE 3.SET NEWNAME FOR DATABASE The following variables are
Database Link Ora 12154
introduced for SET NEWNAME from 11gR2 :- %b The file name remains ora 12154 error in oracle 11g same as the original. For example, if a datafile is named D:\oracle\oradata\matrix\test.dbf, then %b results in test.dbf.
Ora 12154 Error Solution
%f Specifies the absolute file number of the datafile for which the new name is generated. %I Specifies the DBID. %N Specifies the tablespace name. %U Specifies the ora 12154 error in toad following format: data-D-%d_id-%I_TS-%N_FNO-%f. Time to testрџ™‚ In my test, i am creating a duplicate database ORCL, from the rman backup of MATRIX database. As i am doing it on Windows box, i do hit ORA-600 [KSMFPG5], [0xAEC0000], which is a bug, and also mentioned in one of my previous blog. 1. taking backup of matrix database - RMAN> ora 12154 error informatica run{ 2> backup database format 'D:\oracle\backup\matrix\%d_%s_%p'; 3> backup archivelog all format 'D:\oracle\backup\matrix\arc_%d_%s_%p'; 4> } Starting backup at 11-JAN-12 using channel ORA_DISK_1 channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00001 name=D:\ORACLE\ORADATA\MATRIX\SYSTEM01.DBF .............. channel ORA_DISK_1: finished piece 1 at 11-JAN-12 piece handle=D:\ORACLE\BACKUP\MATRIX\ARC_MATRIX_10_1 tag=TAG20120111T133016 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07 Finished backup at 11-JAN-12 The database as well as the archivelog backupset exist in D:\ORACLE\BACKUP\MATRIX\ 2. Duplicating db MATRIX to ORCL. Before executing the command, created ORCL pfile , passwordfile and windows service using oradim utility. D:\scripts>set oracle_sid=ORCL D:\scripts>sqlplus / as sysdba SQL*Plus: Release 11.2.0.2.0 Production on Wed Jan 11 13:32:14 2012 Copyright (c) 1982, 2010, Oracle. All rights reserved. Connected to an idle instance. SQL> startup nomount ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance ORACLE instance started. Total System Global Area 150667264 bytes Fixed Size 1382112 bytes Variable Size 92277024 bytes Database Buffers 50331648 bytes Redo Buffers 6676480 bytes SQL> exit Disconnected from Oracle Database 11g E
2 вперед Ctrl→ все ORA-12154: TNS:could not resolve the connect identifier specified [new] bambaleio Guest Выходит ошибка: RMAN>
Ora 12514 Error
connect auxiliary sys/oracle@db01stan RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK ora 12560 error FOLLOWS =============== RMAN-00571: =========================================================== RMAN-04006: error from auxiliary database: ORA-12154: TNS:could not resolve the connect
Ora 12541 Error
identifier specified tnsnames на первой базе: DB01= (DESCRIPTION= (ADDRESS=(protocol = TCP) (host = 192.168.56.14) (port = 1521)) (CONNECT_DATA= (SERVICE_NAME=db01prod) ) ) DB01STAN= (DESCRIPTION= (ADDRESS=(protocol = https://aprakash.wordpress.com/tag/duplicate-database/ TCP) (host = 192.168.56.15) (port = 1521)) (CONNECT_DATA= (SID=db01) ) ) tnsnames на второй базе: DB01= (DESCRIPTION= (ADDRESS=(protocol = TCP) (host = 192.168.56.15) (port = 1521)) (CONNECT_DATA= (SERVICE_NAME=db01stan) ) ) DB01PROD= (DESCRIPTION= (ADDRESS=(protocol = TCP) (host = 192.168.56.14) (port = 1521)) (CONNECT_DATA= (SID=db01) ) ) 2 ноя 15, 12:37 [18358364] Ответить http://www.sql.ru/forum/1182899/ora-12154-tns-could-not-resolve-the-connect-identifier-specified | Цитировать Сообщить модератору Re: ORA-12154: TNS:could not resolve the connect identifier specified [new] Vadim Lejnin Member Откуда: Сообщений: 4743 bambaleio,Найди два отличия (SID=db01) ... (SERVICE_NAME=db01prod) ... Для клонирования лучше использовать статическую регистрацию + orapwd тогда можно будет соединяться даже с offline instanceДля статической регистрации пропиши нужный SID в listener.ora(не путать с tnsalias) 2 ноя 15, 13:51 [18358947] Ответить | Цитировать Сообщить модератору Re: ORA-12154: TNS:could not resolve the connect identifier specified [new] bambaleio Guest Vadim Lejninbambaleio,Найди два отличия (SID=db01) ... (SERVICE_NAME=db01prod) ... Для клонирования лучше использовать статическую регистрацию + orapwd тогда можно будет соединяться даже с offline instanceДля статической регистрации пропиши нужный SID в listener.ora(не путать с tnsalias)Отличий четыре) Только не понял, что нужно... Сначала прописываем для основной базы, потом для второй, так? 2 ноя 15, 13:59 [18359002] Ответить | Цитировать Сообщить модератору Re: ORA-12154: TNS:could not resolve the connect identifier specified [new] Vadim Lejnin Member Откуда: Сообщений: 4743 Попро
Links Sunday, 28 July 2013 ORA-12154: TNS:could not resolve the connect identifier specified RMAN DUPLICATE FAILED WITH BELOW ERROR ===================================== Recovery Manager: Release 11.2.0.3.0 http://abduulwasiq.blogspot.com/2013/07/ora-12154-tnscould-not-resolve-connect.html - Production on Tue Jul 16 02:57:58 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. RMAN> RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== ORA-12154: TNS:could not resolve the connect identifier specified RMAN> connected to recovery catalog database RMAN> connected to auxiliary database (not started) Note: Comment ebstest_LOCAL ora 12154 paramater in tnsnames.ora file and try it again. Solution: oratest@ctsst $ diff tnsnames.ora tnsnames.ora_bkp 24c24 < #ebstest_LOCAL = --- > ebstest_LOCAL = 46,57d45 < ebsoltp = < (DESCRIPTION= < (ADDRESS=(PROTOCOL=tcp)(HOST=ebsoltp.user.com)(PORT=1535)) < (CONNECT_DATA= < (SID=ebsoltp) < ) < ) < catalog= < (DESCRIPTION = < (ADDRESS_LIST = < (ADDRESS = (COMMUNITY = TCP) (PROTOCOL=TCP) (Host ora 12154 error =catalog.user.com) (Port = 1525))) < (CONNECT_DATA = (SID = catalog))) 59d46 < oratest@ctsst $ oratest@ctsst $ rman Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jul 16 03:03:57 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. RMAN> connect target sys/tim3Pa55@ebsoltp connected to target database: EBSOLTP (DBID=2581404741) RMAN> connect catalog catalog/catalog007@catalog connected to recovery catalog database RMAN> connect auxiliary / connected to auxiliary database: EBSTEST (not mounted) After doing above steps issue got resolved.Happy learning !!!!!!!!!!!!!!! Posted by Abdul Wasiq at 19:36 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Total Pageviews Followers Page Statistics Follow by Email Blog Archive ► 2016 (13) ► May (5) ► March (3) ► January (5) ► 2015 (43) ► August (4) ► May (2) ► April (24) ► March (9) ► February (1) ► January (3) ► 2014 (110) ► July (6) ► June (5) ► A