ORA-02026 when dropping database.

Is the Drop Database functionality available in 9i? This is what I get when I try to execute the statement under sys. I also went through the DBCA to drop the database but for some reason none of my databases are showing up in it. Looked under the help file, and it said my SID is not in its "Shell"... whatever that means...
SQL> DROP DATABASE;
DROP DATABASE
ERROR at line 1:
ORA-02026: missing LINK keyword
So. my question is, is there a way to get my databases to show up in the DBCA? If not, how do I drop a database in 9i manually? Thanks for all the help so far :)

Thats cute guys, but you fail to notice 98% of the questions that are asked on this forum can be answered directly from some kind of documentation written either in the past or close to present. If what your asking is for people to check documentation before posting, what your really asking for is a INACTIVE FORUM.
So tell me, who's being lazy? The developer thats found a faster way to get their questions answered (which coincidentally is getting more work done at light speed) or the plethora of "trying-to-be-oracle-aces" who continually ask for less work on the very forum they're supposed to help people on?
I imagine that this forum is supposed to help oracle lessen the work load of meta-link. So do you job guys, and help some people. Flaming people will just make you look like an *ss.

Similar Messages

ORA-02303 when creating database on Exadata using template with BP12

I get ORA-02303 when creating a RAC database on Exadata. Logs indicate that error happened when applying bundle patch BP12 and probably when running following script: /u01/app/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/catsnap.sql
CREATE OR REPLACE TYPE SYS.RewriteMessage AS OBJECT(
Check the following file for errors:
/u01/app/oracle/product/11.2.0.4/dbhome_1/cfgtoollogs/catbundle/catbundle_EXA_ACSES01_GENERATE_2014Dec17_13_07_45.log
Apply script: /u01/app/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/catbundle_EXA_ACSES01_APPLY.sql
Rollback script: /u01/app/oracle/product/11.2.0.4/dbhome_1/rdbms/admin/catbundle_EXA_ACSES01_ROLLBACK.sql
Executing script file...
Processing Oracle Database Packages and Types...
CREATE OR REPLACE TYPE SYS.RewriteMessage AS OBJECT(
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
CREATE OR REPLACE TYPE SYS.ExplainMVMessage AS OBJECT (
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
Anyone experienced the same issue??

Metalink search points to few bugs. May be opening a SR is a good idea.

ORA-12154 when using Database Link

We're running 11r2 on our servers. I have a primary db and a standby db, using Data Guard. The standby is open for read-only querying. We are not using ASM.
The primary (and thus the standby) have a PUBLIC database link to a third db server.
When I run a query against the database link on the primary: select * from test@MyDBlink; Everything works fine.
When I run the same query against the database link on the standby: select * from test@MyDBlink; I get ORA-12154: TNS:could not resolve the connect identifier.
I check that the db link exists on the standby. It does.
I go to command prompt on the standby and run "tnsping MyDBlink". It executes fine. It says "Used TNSNAMES adapater to resolve the alias" and sure enough, MyDBlink is referenced in the TNSNAMES.ORA.
I also run "tnsping IP-of-MyDBlink" to doublecheck. No issues.
What is going on that is blocking the db link on the standby? Many reports utilize that standby and I'd hate to deny them the functionality of a db link.
Thanks

893968 wrote:
We're running 11r2 on our servers. I have a primary db and a standby db, using Data Guard. The standby is open for read-only querying. We are not using ASM.
The primary (and thus the standby) have a PUBLIC database link to a third db server.
When I run a query against the database link on the primary: select * from test@MyDBlink; Everything works fine.
When I run the same query against the database link on the standby: select * from test@MyDBlink; I get ORA-12154: TNS:could not resolve the connect identifier.
I check that the db link exists on the standby. It does.
I go to command prompt on the standby and run "tnsping MyDBlink". It executes fine. It says "Used TNSNAMES adapater to resolve the alias" and sure enough, MyDBlink is referenced in the TNSNAMES.ORA.
I also run "tnsping IP-of-MyDBlink" to doublecheck. No issues.
What is going on that is blocking the db link on the standby? Many reports utilize that standby and I'd hate to deny them the functionality of a db link.
ThanksMost people with this problem don't understand that the dblink is just another client, no different than sqplus running on the same machine - and therefore the link uses the tnsames in the ORACLE_HOME of the database containing the link. But it seems from the steps you've described that you've grasped that. The only thing I can think of off the top of my head is when you try sqlplus from the standby server you are hitting a different tnsnames than the one the database is using.

RMAN 11gr2 ORA-00308 when dulplicate database from active

Hi,
I'm trying to clone a production database (Oracle 11.2.0.3) from HP-UX IA64 to Solaris 10 (Sparc 64) (source on Filesystem, target on ASM)
the previous steps was done (same oracle software installation, same patches, sqlnet comunication, etc.)
but the RMAN fails at end of the process:
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Aug 22 09:44:34 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SIN (DBID=634625013)
connected to recovery catalog database
connected to auxiliary database: SIN (not mounted)
RMAN> run
+2> {+
+3> allocate channel c1 type disk;+
+4> allocate channel c2 type disk;+
+5> allocate channel c3 type disk;+
+6> allocate channel c4 type disk;+
+7> allocate auxiliary channel a1 type disk;+
+8> allocate auxiliary channel a2 type disk;+
+9> set newname for datafile 1 to '+DG_DATA';+
+10> set newname for datafile 2 to '+DG_DATA';+
+11> set newname for datafile 3 to '+DG_DATA';+
+12> set newname for datafile 4 to '+DG_DATA';+
+13> set newname for datafile 5 to '+DG_DATA';+
+14> set newname for datafile 6 to '+DG_DATA';+
+15> set newname for datafile 7 to '+DG_DATA';+
+16> set newname for datafile 8 to '+DG_DATA';+
+17> set newname for datafile 9 to '+DG_DATA';+
+18> set newname for datafile 10 to '+DG_DATA';+
+... to...+
+398> set newname for datafile 390 to '+DG_DATA';+
+399> set newname for datafile 391 to '+DG_DATA';+
+400> duplicate target database to "sin" from active database nofilenamecheck+
+401> DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','+DG_DATA/',+
+402> '/u11/oradata/sin/','+DG_DATA/',+
+403> '/u07/oradata/sin/','+DG_DATA/',+
+404> '/u08/oradata/sin/','+DG_DATA/',+
+405> '/u09/oradata/sin/','+DG_DATA/');+
+406> }+
+407>+
starting full resync of recovery catalog
full resync complete
allocated channel: c1
channel c1: SID=1787 device type=DISK
allocated channel: c2
channel c2: SID=2406 device type=DISK
allocated channel: c3
channel c3: SID=850 device type=DISK
allocated channel: c4
channel c4: SID=1146 device type=DISK
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=1514 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
+...+
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 22-AUG-12
contents of Memory Script:
+{+
sql clone "create spfile from memory";
+}+
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
+{+
shutdown clone immediate;
startup clone nomount;
+}+
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    7317790720 bytes
Fixed Size                     2173456 bytes
Variable Size               3808433648 bytes
Database Buffers            3489660928 bytes
Redo Buffers                  17522688 bytes
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=758 device type=DISK
contents of Memory Script:
+{+
sql clone "alter system set control_files =
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
sql clone "alter system set db_name =
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+sql clone "alter system set db_unique_name =+
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+shutdown clone immediate;+
+startup clone force nomount+
+backup as copy current controlfile auxiliary format '+DG_DATA/sin/controlfile/current.512.791978153';+
+restore clone controlfile to '+DG_DATA/sin/controlfile/current.625.791978153' from+
+'+DG_DATA/sin/controlfile/current.512.791978153';+
+sql clone "alter system set control_files =+
+''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/current.625.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+shutdown clone immediate;+
+startup clone nomount;+
+alter clone database mount;+
+}+
+executing Memory Script+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.562.791978153'' comment= ''Set by RMAN'' scope=spfile+
+sql statement: alter system set db_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+sql statement: alter system set db_unique_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+Oracle instance shut down+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+Starting backup at 22-AUG-12+
+channel c1: starting datafile copy+
+copying current control file+
+output file name=/u06/tmpapp/rmanbkps/snapcf_sin.f tag=TAG20120822T094657 RECID=49 STAMP=791977621+
+channel c1: datafile copy complete, elapsed time: 00:00:01+
+Finished backup at 22-AUG-12+
+Starting restore at 22-AUG-12+
+channel a2: skipped, AUTOBACKUP already found+
+channel a1: copied control file copy+
+Finished restore at 22-AUG-12+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.625.791978153'' comment= ''Set by RMAN'' scope=spfile+
+Oracle instance shut down+
+connected to auxiliary database (not started)+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+database mounted+
+Using previous duplicated file +DG_DATA/sin/datafile/system.666.791914845 for datafile 1 with checkpoint SCN of 46164275052+
+Using previous duplicated file +DG_DATA/sin/datafile/undotbs1.678.791913821 for datafile 2 with checkpoint SCN of 46164227408+
+...+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.498.791939115 for datafile 389 with checkpoint SCN of 46165353395+
+Using previous duplicated file +DG_DATA/sin/datafile/mytablespace.674.791914359 for datafile 390 with checkpoint SCN of 46164253329+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.499.791939115 for datafile 391 with checkpoint SCN of 46165353396+
+contents of Memory Script:+
+{+
+sql 'alter system archive log current';+
+}+
+executing Memory Script+
+sql statement: alter system archive log current+
+contents of Memory Script:+
+{+
+backup as copy reuse+
+archivelog like "/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065832.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065833.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065834.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065835.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065836.ARC" auxiliary format+
+"+DG_DATA" ;+
+catalog clone start with "+DG_DATA";+
+catalog clone datafilecopy "+DG_DATA/sin/datafile/system.666.791914845",+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.679.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.689.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.690.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.677.791914357",+
+"+DG_DATA/sin/datafile/drsys.621.791939555",+
+"+DG_DATA/sin/datafile/high_idx.663.791914889",+
+"+DG_DATA/sin/datafile/tools.507.791939555",+
+...+
+"+DG_DATA/sin/datafile/bkptemp.497.791939113",+
+"+DG_DATA/sin/datafile/med_dat.498.791939115",+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359",+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+switch clone datafile 1 to datafilecopy+
+"+DG_DATA/sin/datafile/system.666.791914845";+
+switch clone datafile 2 to datafilecopy+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821";+
+switch clone datafile 3 to datafilecopy+
+...+
+"+DG_DATA/sin/datafile/med_dat.498.791939115";+
+switch clone datafile 390 to datafilecopy+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359";+
+switch clone datafile 391 to datafilecopy+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+}+
+executing Memory Script+
+Starting backup at 22-AUG-12+
+channel c1: starting archived log copy+
+input archived log thread=1 sequence=65832 RECID=48339 STAMP=791913640+
+channel c2: starting archived log copy+
+input archived log thread=1 sequence=65833 RECID=48340 STAMP=791933223+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65834 RECID=48341 STAMP=791939052+
+channel c4: starting archived log copy+
+input archived log thread=1 sequence=65835 RECID=48342 STAMP=791962351+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.791978259 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:00:35+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65836 RECID=48343 STAMP=791977692+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 RECID=0 STAMP=0+
+channel c1: archived log copy complete, elapsed time: 00:00:51+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.791978259 RECID=0 STAMP=0+
+channel c2: archived log copy complete, elapsed time: 00:01:41+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.791978295 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:01:06+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.791978259 RECID=0 STAMP=0+
+channel c4: archived log copy complete, elapsed time: 00:01:41+
+Finished backup at 22-AUG-12+
+searching for all files that match the pattern +DG_DATA+
+List of Files Unknown to the Database+
+=====================================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+cataloging files...+
+cataloging done+
+List of Cataloged Files+
+=======================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65835.516.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+List of Files Which Where Not Cataloged+
+=======================================+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+RMAN-07518: Reason: Foreign database file DBID: 0 Database Name:+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/system.666.791914845 RECID=442 STAMP=791978374+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.678.791913821 RECID=443 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.679.791913821 RECID=444 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.689.791913821 RECID=445 STAMP=791978375+
+cataloged datafile copy+
+...+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.498.791939115 RECID=830 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/mytablespace.674.791914359 RECID=831 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.499.791939115 RECID=832 STAMP=791978408+
+datafile 1 switched to datafile copy+
+input datafile copy RECID=442 STAMP=791978374 file name=+DG_DATA/sin/datafile/system.666.791914845+
+datafile 2 switched to datafile copy+
+input datafile copy RECID=443 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.678.791913821+
+datafile 3 switched to datafile copy+
+input datafile copy RECID=444 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.679.791913821+
+datafile 4 switched to datafile copy+
+input datafile copy RECID=445 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.689.791913821+
+...+
+datafile 389 switched to datafile copy+
+input datafile copy RECID=830 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.498.791939115+
+datafile 390 switched to datafile copy+
+input datafile copy RECID=831 STAMP=791978408 file name=+DG_DATA/sin/datafile/mytablespace.674.791914359+
+datafile 391 switched to datafile copy+
+input datafile copy RECID=832 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.499.791939115+
+contents of Memory Script:+
+{+
+set until scn 46167049411;+
+recover+
+clone database+
+delete archivelog+
+;+
+}+
+executing Memory Script+
+executing command: SET until clause+
+Starting recover at 22-AUG-12+
+starting media recovery+
+archived log for thread 1 with sequence 65832 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.7+
+91978259+
+archived log for thread 1 with sequence 65833 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.7+
+91978259+
+archived log for thread 1 with sequence 65834 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.7+
+91978259+
+archived log for thread 1 with sequence 65835 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.7+
+91978259+
+archived log for thread 1 with sequence 65836 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.7+
+91978295+
+archived log file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 thread=1 sequence=65832+
+released channel: c1+
+released channel: c2+
+released channel: c3+
+released channel: c4+
+Oracle Error:+
+ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below+
+ORA-01194: file 1 needs more recovery to be consistent+
+ORA-01110: data file 1: '+DG_DATA/sin/datafile/system.666.791914845'+
*+released channel: a1+*
*+released channel: a2+*
*+RMAN-00571: ===========================================================+*
*+RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============+*
*+RMAN-00571: ===========================================================+*
*+RMAN-03002: failure of Duplicate Db command at 08/22/2012 09:52:27+*
*+RMAN-05501: aborting duplication of target database+*
*+RMAN-03015: error occurred in stored script Memory Script+*
*+RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DG_DATA/sin/archivelog/2012_08_22/thre+*
*+ad_1_seq_65832.513.791978259'+*
*+ORA-00308: cannot open archived log '+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259'+*
+Recovery Manager complete.+
the error is always the same, a previous backup with RMAN was taken on tape on the source database (production).
Please help me to find what is wrong here!!

Hi mseberg
that's exactly i'm doing:
1. Create an Oracle Password File for the Auxiliary Database
a. done, passwd file created*
2. Create the Directory Structure on the remote server
a. done, all the admin structure wa created.*
3. Oracle Net Setup ( you need an entry for the CLONE in your TNSNAMES.ORA on both servers ) ( I use SID_LIST_LISTENER entry for static )
a. done, i have the entries working on my tnsnames.ora (source and target with static listeners)*
4. Create an Initialization Parameter File for the Auxiliary Instance ( I use Parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change locations)
a. done, this is my initialization file:*
*.audit_file_dest='/u01/app/oracle/admin/sin/adump'*
*.audit_trail='db'*
*.compatible='11.2.0.0.0'*
*.db_block_size=8192*
*.db_create_file_dest='DG_DATA'+*
*.db_domain=''*
*.db_files=2048*
*.db_name='sin'*
*.db_recovery_file_dest='DG_DATA'+*
*.db_recovery_file_dest_size=20G*
*.diagnostic_dest='/u01/app/oracle'*
*.dispatchers='(PROTOCOL=TCP) (SERVICE=sinXDB)'*
*.log_archive_format='%t_%s_%r.dbf'*
*.memory_target=7340032000*
*.open_cursors=300*
*.processes=2000*
*.remote_login_passwordfile='EXCLUSIVE'*
*.sessions=2205*
*.undo_tablespace='UNDOTBS1'*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/')+
LOG_FILE_NAME_CONVERT=('/u04/oradata/sin/','DG_DATA/',+*
+'/u05/oradata/sin/','+DG_DATA/',+
+'/u03/oradata/sin/','+DG_DATA/',+
+'/u02/oradata/sin/','+DG_DATA/')+
and this is my command from RMAN:
run*
*+{+*
allocate channel c1 type disk;*
allocate channel c2 type disk;*
allocate channel c3 type disk;*
allocate channel c4 type disk;*
allocate auxiliary channel a1 type disk;*
allocate auxiliary channel a2 type disk;*
set newname for datafile 1 to 'DG_DATA';+*
set newname for datafile 2 to 'DG_DATA';+*
set newname for datafile 3 to 'DG_DATA';+*
set newname for datafile 4 to 'DG_DATA';+*
set newname for datafile 5 to 'DG_DATA';+*
set newname for datafile 6 to 'DG_DATA';+*
set newname for datafile 7 to 'DG_DATA';+*
set newname for datafile 8 to 'DG_DATA';+*
set newname for datafile 9 to 'DG_DATA';+*
set newname for datafile 10 to 'DG_DATA';+*
+...+
set newname for datafile 390 to 'DG_DATA';+*
set newname for datafile 391 to 'DG_DATA';+*
duplicate target database to "sin" from active database nofilenamecheck*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/');+
+}+
do you think the problem may be in the name of the database?, I am using the same name in the auxiliary
and when I get the error, I have the same dbid in both databases (source and destination)
Thanks
MM

ORA-12547 when upgrade database (from 10.1.0.4 to 10.2.0.4) using dbua

Hi,
I got error when doing the database upgrade using dbua from 10.2.0.4 home.
It is in 15% progress of "Upgrading Oracle Server". It shows ORA-12547: TNS: lost contact.
You can either ignore or abort.
Any suggestion?
Thanks in advance.
milic

You can almost never ignore an error message ... unless you want a failure.
Did you read the upgrade instructions with respect to the database, listener, and oem dbconsole?

ORA 1426 when dropping a datafile.

Hello,
While dropping a datafile, I got the following error message:
ORA-00604: une erreur s'est produite au niveau SQL récursif 1
ORA-01426: dépassement numérique
The command I used is the following:
alter tablespace m4prod drop datafile 'd:\oradata\paie\m4prod02.dbf';
Most of the posts I got from the net regarding that error were in reference to calling a procedure. I am not invoking any PL/SQL block so I don't understand why that error and how do I fix it.
Thanks in advance.

My database version is:
select from v$version;*
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
I did not configure any trigger either on the database nor on an object.

Oracle 9.0.1.0 and Ora-00604 when dropping a table.

Hi. I'm running Oracle 9i (9.0.1.0.0) on Redhat linux 7.3
I am trying to drop a table and I get this error.
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (SYS.I_COL_USAGE$) violated
Any idea, what I should do?
Thanks in advance.

On Metalink about your problem you can see :
Obtain a fix for [BUG:2144889] by upgrading to RDBMS version 9.2 or applying the 9.0.1.4 patchset release. There are also one-off fixes available for version 9.0.1.3 on some platforms.

ORA 3113 error when dropping user

I have an instance of oracle 9.2 that when I drop a user I get the ORA-3113 error.
I have no other problems with this database, It can be started and stopped with out error, users can connect...etc.
I tried the following oracle solution without success
Subject: ORA-03113 While Dropping a User
 Doc ID: Note:291186.1 Type: PROBLEM
 Last Revision Date: 21-JUL-2005 Status: MODERATED
The information in this document applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.5
This problem can occur on any platform.
Errors
ORA-03113 "end-of-file on communication channel"
Symptoms
ORA-03113 is thrown, while dropping a User
SQL> drop user test9 cascade;
ORA-03113 end-of-file on communication channel
Cause
Corrupted password file
Check whether REMOTE_LOGIN_PASSWORDFILE is set to { SHARED | EXCLUSIVE}
Fix
-- Recreate the password file.
++ $ orapwd file=orapw<sid> password=<sys's password> entries=<max # user's>
NOTE:
-- Set the REMOTE_LOGIN_PASSWORDFILE=NONE
-- Drop the user
-- If it is successful, You are hitting this problem.

Are u getting this error sometimes while connecting to DB.
If not check the trace file generated on the server at failure time.
Regards
Raman

Drop database link & ORA-02082 Error

Hello,
I have created db link. Now, I would like to DROP it but I got "ORA-02082 a loopback database link must have a connection qualifier".
I have tried every possible combination but without success.
Thanks for help
sasa

Hello Barbara,
I agree with you that if db link exist I should be able to drop it. If you look into my first reply there is complete select from user_db_links. Select from dba_db_links are the same because I haven't any others db links. I try to drop the db link as owner or as sys. I do not need to think about drop with name "qwer.cscargo.cz" because is wrong (our inner domain is "in.cscargo.cz"). The only difference among others db links is that qwer have "current_user".
DB_LINK USERNAME HOST
CARGODB.IN.CSCARGO.CZ CARGO_ADM cargodb
LMDB.IN.CSCARGO.CZ CARGO_ADM lmdb
QWER.IN.CSCARGO.CZ CURRENT_USER speisdb
SPEISDB.IN.CSCARGO.CZ CARGO_ADM speisdb_rac
There could be one problem. I created the db link when my db have name "speisdb". I rename my db (using rman - duplicate db) to "speisdev". Could be this source of problems?
Here is output of your drop script:
drop database link qwer
ERROR at line 1:
ORA-02082: a loopback database link must have a connection qualifier
drop database link qwer.cscargo.cz
ERROR at line 1:
ORA-02024: database link not found
drop database link qwer.in.cscargo.cz
ERROR at line 1:
ORA-02084: database name is missing a component
drop database link qwer@loopback
ERROR at line 1:
ORA-02024: database link not found
drop database link qwer.cscargo.cz@loopback
ERROR at line 1:
ORA-02024: database link not found
drop database link qwer.in.cscargo.cz@loopback
ERROR at line 1:
ORA-02084: database name is missing a component
drop public database link qwer
ERROR at line 1:
ORA-02082: a loopback database link must have a connection qualifier
drop public database link qwer.cscargo.cz
ERROR at line 1:
ORA-02024: database link not found
drop public database link qwer.in.cscargo.cz
ERROR at line 1:
ORA-02084: database name is missing a component
drop public database link qwer@loopback
ERROR at line 1:
ORA-02024: database link not found
drop public database link qwer.cscargo.cz@loopback
ERROR at line 1:
ORA-02024: database link not found
drop public database link qwer.in.cscargo.cz@loopback
ERROR at line 1:
ORA-02084: database name is missing a component
Thanks SASA

ORA-28150 when accessing data from a remote database

Portal Version: Portal 3.0.9.8.0
RDBMS Version: 8.1.6.3.0
OS/Vers. Where Portal is Installed:: Solaris 2.6
Error Number(s):: ORA-28150
I have a problem with using a database link to access a table in
a remote database. So long as the dblink uses explicit logins
then everything works correctly. When the dblink does not have a
username then I get the ORA-28150 message. The database link is
always public. A synonym is created locally that points to a
synonym in the remote database. I am using the same Oracle user
in both databases. The Oracle portal lightweight user has this
same Oracle user as its default schema. The contents of the
remote table are always visible to sqlplus, both when the link
has a username and when it doesn't have a username.
All the databases involved are on the same version of Oracle.
I'm not sure which Oracle login is being used to access the
remote database, if my lightweight user has a database schema
of 'xyz' then does portal use 'xyz' to access the remote
database? I would be very grateful for any help or pointers that
might help to solve this problem.
James
To further clarify this, both my local and remote databases
schemas are owned by the same login.
The remote table has a public synonym.
The link is public but uses default rather than explicit logins.
The local table has a public synonym that points to the remote
synonym via the database link.
If I change the link to have an explicit login then everything
works correctly.
I can view the data in the remote database with TOAD and with
sqlplus even when the database link has default login rather
than explicit login.
This seems to point to Portal as being the culprit. Can anyone
tell me whether default logins can be used across database links
with portal?
TIA
James

832019 wrote:
One way to do this is by creating a database link and joining the two tables directly. But this option is ruled out. So please suggest me some way of doing this.Thus you MUST use two connection strings.
Thus you are going to be either constructing some intricate SQL dynamically or you are going to be dragging a lot of data over the wire and doing an in memory search.
Although realistically that is what the database link table would have done as well.
Might be better to look at moving the table data from one database to the other. Depends on size of course.

Why I got error ORA-02429 when I tried to drop a tablespace?

I use the following command to drop the tablespace:
drop tablespace users including contents and datafiles;The error message is below:
Error report:
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-02429: cannot drop index used for enforcement of unique/primary key
00604. 00000 - "error occurred at recursive SQL level %s"
*Cause: An error occurred while processing a recursive SQL statement
 (a statement applying to internal dictionary tables).
*Action: If the situation described in the next error on the stack
 can be corrected, do so; otherwise contact Oracle Support.However, I have removed all the tables and indexes in this tablespace.
Nothing found when I issued the following enquiries.
select index_name from user_indexes where TABLESPACE_NAME = 'USERS';
select table_name from user_tables where TABLESPACE_NAME = 'USERS';Is there anything I missed?
Thanks in advance.

999274 wrote:
Could you please let me know how to purge recyclebin ?It's bad form to hijack someone else's thread for your own questions.
As for your question
=================================================
Learning how to look things up in the documentation is time well spent investing in your career. To that end, you should drop everything else you are doing and do the following:
Go to [url tahiti.oracle.com]tahiti.oracle.com.
Locate the link for your Oracle product and version, and click on it.
You are now at the entire documentation set for your selected Oracle product and version.
BOOKMARK THAT LOCATION
Spend a few minutes just getting familiar with what is available here. Take special note of the "books" and "search" tabs. Under the "books" tab (for 10.x) or the "Master Book List" link (for 11.x) you will find the complete documentation library.
Spend a few minutes just getting familiar with what kind of documentation is available there by simply browsing the titles under the "Books" tab.
Open the Reference Manual and spend a few minutes looking through the table of contents to get familiar with what kind of information is available there.
Do the same with the SQL Reference Manual.
Do the same with the Utilities manual.
You don't have to read the above in depth. They are reference manuals. Just get familiar with what is there to be referenced. Ninety percent of the questions asked on this forum can be answered in less than 5 minutes by simply searching one of the above manuals.
Then set yourself a plan to dig deeper.
- Read a chapter a day from the Concepts Manual.
- Take a look in your alert log. One of the first things listed at startup is the initialization parms with non-default values. Read up on each one of them (listed in your alert log) in the Reference Manual.
- Take a look at your listener.ora, tnsnames.ora, and sqlnet.ora files. Go to the Network Administrators manual and read up on everything you see in those files.
- When you have finished reading the Concepts Manual, do it again.
Give a man a fish and he eats for a day. Teach a man to fish and he eats for a lifetime.
=================================

ORA-01017 error in Database Configuration Assistant when installing Oracle

I am installing Oracle 9i, 9.0.1.1, on an NT Workstation.
When I get to the Database Configuration Assistant step, after the software has been installed, I get an error when the database is being created:
ORA-01017 Invalid Username/Password; Login denied
I have tried several times with different database creations. The first time I got the error was when I did a custom database creation, the other time was when I created a general purpose database, which clones an existing database onto the NT workstation.
The NT system that I am using had an earlier version of Oracle installed on it, which I completely uninstalled.
Any ideas what might be wrong?

Deepak_DBA wrote:
hi,
you might have deleted the instance manually..
oradim -delete -sidHence,
ebrian wrote:
Did you already remove the Windows service associated with the database?

Ora-12154 when trying to connect to database from fortran application

I am trying to connect to database and run an simple select query to a table(without any where clause) using pro*fortran code.
the connect strng is like
exec sql connect :uidpwd
where uidpwd = username/password@SID
SID and tnsnames connect string are the same.
The fortran (profortran) code is placed in the database server and there are no errors when make is run.
Tnsping is working fine, also i am able to conect using sql*plus and run the same query.
Please help
Thanks and Regards
Nitin

Hi Nitin
Thanks for the helpful! With your point I'm now Pro! Great thanks.
By the way have your seen that?
Files such as LISTENER.ORA, TNSNAMES.ORA, SQLNET.ORA, if configured manually, or copied and edited from earlier releases of Oracle Database may have record attributes that are incompatible with Oracle Database 10g release 2. The software cannot read such files. The required record format is stream_lf and the record attributes are carriage_control and carriage_return.
This may result in:
Inability to start the listener
Services not registered with the listener
Inability to connect to other databases
ORA-12154: TNS:could not resolve service name
Run the following command on each file affected:
$ DIR/FULL filename
An output similar to the following may be displayed:
Record format: Variable length, maximum 255 bytes
Record attributes: Carriage return carriage control
If the output includes the preceding entries, then run the following command:
$ CONVERT/FDL=SYS$INPUT filename filename
RECORD
CARRIAGE_CONTROL CARRIAGE_RETURN
FORMAT STREAM_LF
^Z
Otherwise herewith an interesting metalink note. Doc ID: Note:437597.1
Subject: Ora-12154 When Executing Pro*Fortran Code Compiled With Oracle 10g.
Hope this will also help you...
Cheers
Hubert

ORA-01031 WHEN CONNECTING TO AUXILIARY DATABASE

Hi
i am currently trying to to create a standby database using RMAN using the ORACLE RMAN Backup and recovery book.
I get the ORA-01031 when i connect to the auxiliary database.
i do the following:
RMAN> connect target sys/password@primary
connected to target
RMAN > connect auxiliary sys/password@aux1
ORA-01031.............insufficient privileges
obviously the database aux1 hasnt been created yet but i have configured the tns and listener and both work fine, also created a password file and created a pfile from the spfile in the primary database as instructed by the book. I also started the aux1 database in nomount mode as well.
does any one have any ideas where i maybe going wrong?
thanks

conn sys/pwd@aux1 as sysdba ,what happens to this
in sqlplus
add an entry to your TNSNAMES.ora
SQLNET.AUTHENTICATION_SERVICES = (NTS)
We dont need this entry this is for OS authenicarion sorry
then try again
Version and OS?
Message was edited by:
Maran Viswarayar
Message was edited by:
Maran Viswarayar

ORA-03113 when trying to connect to database

RDBMS Version:: 9.2.0.6
Operating System and Version:: Win2003 Small Business Server
Error Number (if applicable):: ORA-03113
Server Net Version:: 9.2.0.6
Client Operating System and Version:: Solaris10
Client Net Version:: 2.1.3
ORA-03113 when trying to connect to database
I've currently a 7.1.3 client on SUN Solaris (5.10 Generic_118844-26 i86pc i386 i86pc) where I want to connect to the 9.2.0.6 database on a Win2003 Server hardware.
When i try to connect via SQL*Plus (Release 3.1.3.4.1), I get ORA-03113. Looking into the listener resp. alertfile on the server, I can see that the connectiorequest is recognized, but immediately answered by an ORA-0600, producing also trc-files.
listener: 25-MAI-2007 09:37:23 * (CONNECT_DATA=(SID=HTASQL)(CID=(PROGRAM=)(HOST=eklvpa)(USER=sat250))) * (ADDRESS=(PROTOCOL=tcp)(HOST=172.17.233.3)(PORT=32790)) * establish * HTASQL * 0
alert: ORA-00600: internal error code, arguments: [12333], [26], [0], [115], [], [], [], []
Activating traces on the client-side showed the following errors:
-<ERROR>- ntus2err: sd=8, op=1, resnt[0]=511, resnt[1]=2, resnt[2]=0
-<ERROR>- nserror: nsres: id=0, op=65, ns=12541, ns2=12560; nt[0]=511, nt[1]=2, nt[2]=0
-<ERROR>- nsopen: unable to open transport
-<ERROR>- nsprecv: transport read error
-<ERROR>- nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0
-<ERROR>- osnqrc: wanted 1 got 0, type 0
-<ERROR>- osnqper: error from osnqrc
-<ERROR>- osnqper: nr err code: 0
-<ERROR>- osnqper: ns main err code: 12537
-<ERROR>- osnqper: ns (2) err code: 12560
-<ERROR>- osnqper: nt main err code: 507
-<ERROR>- osnqper: nt (2) err code: 0
-<ERROR>- osnqper: nt OS err code: 0
-<ERROR>- osnqsm: send-break: failed to send OOB break...
-<ERROR>- osnqper: error from send-marker
-<ERROR>- osnqper: nr err code: 0
-<ERROR>- osnqper: ns main err code: 12583
-<ERROR>- osnqper: ns (2) err code: 0
-<ERROR>- osnqper: nt main err code: 0
-<ERROR>- osnqper: nt (2) err code: 0
-<ERROR>- osnqper: nt OS err code: 0
-<ERROR>- osnqbr: returning 3113
Can anybody help me in determining the problem ? Is there a systemtic incompatibility in connecting a 7.1.3 client to a 9.2 (or even higher) database ?

Thanks for your reply.
But the funny thing on this compatibility issues is, that this configuration worked before. The only thing we did, was to setup the client-PC on a new hardware with also a new operating system (upgrading from Solaris 5.8 to 5.10). And from that time we encountered this problem.
Are there any OS-related problems known or better to say: is (was) ORACLE 7.1.3 supported on Solaris 5.10 ? Should we look for any patches which might help us ?

ORA-02026 when dropping database.

Similar Messages

Maybe you are looking for