ORA-15030: diskgroup name "dg1" is in use by another diskgroup

dear all
i'm implementing rac on vmware
I've installed oracle instance on both nodes. i create a diskgroup on one node, it's ok but when I create a diskgroup in the second node it throws an error
ORA-15018: diskgroup cannot be created
ORA-15030: diskgroup name "DG1" is in use by another diskgroupwhat the error can be?
thanks
John

AlexeyDev wrote:
Even if you have 10 ASM instances in Your RAC environment all of them should shared the same disks and disk groups.
Try to use oracleasm scandisks and oracleasm listdisks on all nodes.i've already used scandisk and listdisks, they show the same
vol1
vol2
when i create an as instance, it creates the instances on both nodes, it's ok
then i create a disk, it creates and mounts it in the first node, and I got the following errors from the second node:
Could not mount the diskgroup no remote node rac2 using connection service rac2:1521:+ASM2 . ensure that the listener is running on this node and the ASM instance is registered to the listener. Received the following error:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DG1"Somehow my listeners status is blocked, may be that's the reason?

Similar Messages

ORA-15018: diskgroup cannot be created

Dear All,
I am trying to create ASM Disk group using SQL but geting blow error not able to create asm diskgroup.
SQL> CREATE DISKGROUP dg1 normal redundancy
2 failgroup dg1_fg01 disk
3 '/dev/sdf1' name raw_disk1,
4 '/dev/sdg1' name raw_disk2
5 failgroup dg_1fg02 disk
6 '/dev/sdh1' name raw_disk3,
7 '/dev/sdi1' name raw_disk4;
CREATE DISKGROUP dg1 normal redundancy
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/sdi1' matches no disks
ORA-15025: could not open disk '/dev/sdi1'
ORA-15056: additional error message
Linux Error: 13: Permission denied
Additional information: 42
Additional information: 3674204
Additional information: 3776832
ORA-15031: disk specification '/dev/sdh1' matches no disks
ORA-15025: could not open disk '/dev/sdh1'
ORA-15056: additional error message
Linux Error: 13: Permission denied
Additional information: 42
Additional information: 3674204
Additional information: 3776832
ORA-15031: disk specification '/dev/sdg1' matches no disks
ORA-15025: could not open disk '/dev/sdg1'
ORA-15056: additional error message
Linux Error: 13: Permission denied
Additional information: 42
Additional information: 3674204
Additional information: 3776832
ORA-15031: disk specification '/dev/sdf1' matches no disks
ORA-15025: could not open disk '/dev/sdf1'
ORA-15056: additional error message
Linux Error: 13: Permission denied
Additional informat
When i checked wheather the disk are recognized by asm or not by checking as
SQL> select disk_number,name,path,mount_status,header_status,mode_status,state,failgroup,repair_timer from v$asm_disk;
DISK_NUMBER NAME            PATH            MOUNT_S HEADER_STATU MODE_ST STATE    FAILGROUP       REPAIR_TIMER
          0 ASMDATA1        ORCL:ASMDATA1   CACHED MEMBER       ONLINE NORMAL   ASMDATA1                   0
          1 ASMDATA2        ORCL:ASMDATA2   CACHED MEMBER       ONLINE NORMAL   ASMDATA2                   0
          0 ASMDATA3        ORCL:ASMDATA3   CACHED MEMBER       ONLINE NORMAL   ASMDATA3                   0
          1 ASMDATA4        ORCL:ASMDATA4   CACHED MEMBER       ONLINE NORMAL   ASMDATA4                   0
          7                 ORCL:RAW_DISK4 CLOSED PROVISIONED ONLINE NORMAL                              0
          6                 ORCL:RAW_DISK3 CLOSED PROVISIONED ONLINE NORMAL                              0
          5                 ORCL:RAW_DISK2 CLOSED PROVISIONED ONLINE NORMAL                              0
          4                 ORCL:RAW_DISK1 CLOSED PROVISIONED ONLINE NORMAL                              0
8 rows selected.
So anyone from you genius kindly let me know where i am mistaking
Thanks in advance

Instead of '/dev/sd..' try to use 'ORCL:RAW_DISK..' (as in v$asm_disk.path column).

ORA-15041: diskgroup

Hi,
Db :11.2.0.1
Os :Aix 6
We refresh a db from production to development.
Production db name is PROD23,size is 3tb.we created pfile with instance name PROD23 in target machine(development machine) and db name also PROD23.
We started instance and restore completed.We got a error while recovery
channel t4: reading from backup piece q5nfe9jj_1_1
channel t3: ORA-19870: error while restoring backup piece q3nfe6f3_1_1
ORA-19504: failed to create file "+P0DEV_ARCHGROUP01/P0DEV/arch/arch_1_20113_774871139.arc"
ORA-17502: ksfdcre:4 Failed to create file +P0DEV_ARCHGROUP01/P0DEV/arch/arch_1_20113_774871139.arc
ORA-15041: diskgroup "P0DEV_ARCHGROUP01" space exhausted
failover to previous backup
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: '+P0DEV_DATAGROUP01/P0DEV/system01.dbf'
2GB free space available in archivegroup.I didn't understand why it's throwing a error?
I checked space in asmcmd which shows like
+P0DEV_ARCHGROUP01*
ASMCMD> ls -ltr
WARNING:option 'r' is deprecated for 'ls'
please use 'reverse'
Type Redund Striped Time Sys Name
Y PROD23/
N PP0DEV/
can i delete archive logs from PROD23.
Usually we complete recovery and changed db name to PP0DEV from PROD23.So i am asking above question.
Thanks & Regards,
VN

user3266490 wrote:
Hi,
Thanks for your reply.
NAME STATE TYPE TOTAL_MB FREE_MB
ASM_DISKGROUP01 MOUNTED EXTERN 102400 102341
PP0DEV_ARCHGROUP01 CONNECTED EXTERN 921600 144857
PP0DEV_DATAGROUP01 CONNECTED EXTERN 3686400 1000468
PP0DEV_REDOGROUP01 CONNECTED EXTERN 409600 409486
Redolog size is 8GB. the db has 8 redo group and 2 members each.
Interesting that your status for the PP0DEV groups is CONNECTED ... using NFS or iSCSI? I typically see MOUNTED.
What is your definition for DB_RECOVERY_DEST, DB_RECOVERY_DEST_SIZE. The error stated that you had exhausted space,but if I read this correctly, I see 144857M (144G) in your ARCHGROUP1, make sure your DEST_SIZE is 900G (TOTAL_MB for the ARCHIVE group)

ORA-15041: diskgroup "DATA" space exhausted

Hi,
We have created two node rac on linux and oracle version is 11.2.0.3. When i try to create tbs some got created and others getting below error.
ORA-15041: diskgroup "DATA" space exhausted
I see space in my disk and below are the asm disk details.
GROUP_NUMBER~NAME~TOTAL_MB~FREE_MB~USABLE_FILE_MB
*1~DATA~2017128~1701824~784344*
my FRA is inside DATA disk that have 4gb of space. currently FRA is 85% available.
Can you please help why its giving error even if we have space in asm disk..
thanks for your help and time.

Ora_DBA wrote:
SQL> connect sys@+ASM as sysdba
Enter password:
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specifiederror has NOTHING to do with RAC.
Basic SQL*Net issue
ORA-12154 ALWAYS only occurs on SQL Client & no SQL*Net packets ever leave client system
ORA-12154 occurs when client requests a connection to some DB server system using some connection string.
The lookup operation fails because the name provided can NOT be resolved to any remote DB.
The analogous operation would be when you wanted to call somebody, but could not find their name in any phonebook.
The most frequent cause for the ORA-12154 error is when the connection alias can not be found in tnsnames.ora.
The lookup operation of the alias can be impacted by the contents of the sqlnet.ora file; specifically DOMAIN entry.
TROUBLESHOOTING GUIDE: ORA-12154 & TNS-12154 TNS:could not resolve service name [ID 114085.1]
http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/

ORA-01403: no data found Problem when using AUTOMATIC ROW FETCH to populate

ORA-01403: no data found Problem when using AUTOMATIC ROW FETCH to populate a form.
1) Created a FORM on EMP using the wizards. This creates an AUTOMATIC ROW FETCH
TABLE NAME - EMP
Item Containing PRIMARY KEY - P2099_EMPNO
Primary key column - EMPNO
By default the automatic fetch has a ‘Process Error Message’ of ‘Unable to fetch row.’
2) Created a HTML region. Within this region add
text item P2099_FIND_EMPNO
Button GET_EMP to submit
Branch Modified the conditional branch created during button creation to set P2099_EMPNO with &P2099_FIND_EMPNO.
If I then run the page, enter an existing employee number into P2099_EMPNO and press the GET_EMP button the form is populated correctly. But if I enter an employee that does not exist then I get the oracle error ORA-01403: no data found and no form displayed but a message at the top of the page ‘Action Processed’.I was expecting a blank form to be displayed with the message ‘Unable to fetch row.’
I can work around this by making the automated fetch conditional so that it checks the row exists first. Modify the Fetch row from EMP automated fetch so that it is conditional
EXIST (SQL query returns at least one row)
select 'x'
from EMP
where EMPNO = :P2099_EMPNO
But this means that when the employee exists I must be fetching from the DB twice, once for the condition and then again for the actual row fetch.
Rather than the above work around is there something I can change so I don’t get the Oracle error? I’m now wondering if the automatic row fetch is only supposed to be used when linking a report to a form and that I should be writing the fetch process manually. The reason I haven’t at the moment is I’m trying to stick with the automatic wizard generation as much as I can.
Any ideas?
Thanks Pete

Hi Mike,
I've tried doing that but it doesn't seem to make any difference. If I turn debug on it shows below.
0.05: Computation point: AFTER_HEADER
0.05: Processing point: AFTER_HEADER
0.05: ...Process "Fetch Row from EMP": DML_FETCH_ROW (AFTER_HEADER) F|#OWNER#:EMP:P2099_EMPNO:EMPNO
0.05: Show ERROR page...
0.05: Performing rollback...
0.05: Processing point: AFTER_ERROR_HEADER
I don't really wan't the error page, either nothing with the form not being populated or a message at the top of the page.
Thanks Pete

ORA-15001: diskgroup "DATA" does not exist or is not mounted in 11gR2

Dear all,
the system is HP-UX 11.31
the new RAC infrastructure is 11gR2 11.2.0.2 (2nodes using ASM)
i am restoring the 10G 10.2.0.4 database to this infrastructure
copy binary files over to new oracle home,
relink all binaries with option rac_off
--startup nomount
--restore controlfile
--mount database
--catalog the restore files
then run restore
run {
restore database ;
recover database;
i always get this error, i did not see this error in 11gR1( restore few times to 11gR1)
verified the diskgroup DATA and i was mounted
ORA-19504: failed to create file "+DATA/OCP/data1.dbf"
ORA-17502: ksfdcre:3 Failed to create file +DATA/OCP/data1.dbf
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
Please give me an advice.
Thanks,

found this note in Metalink and it had solved my issue.
Unable To Create 10.1 or 10.2 or 11.1(< 11gR2) ASM RAC Databases (ORA-29702) Using Brand New 11gR2 Grid Infrastructure Installation . [ID 946332.1]

ORA-01161: database name ORA10G in file header does not match given name of

Database: Oracle 10g
os: windows 2000
I want to create a new database as same as of a TEST database.
i have followed the steps below however while create the controlfile i am getting the error ORA-01161
1.i took the full backup of test system(while databse is normal shutdown)
2.Prepare new initsid.ora file and change the parameter DN_NAME=newname
3.prepare new create controlfile script with new database name
4.startup pfile='initsid.ora' nomount
5.while executing the controlfile creation script, it gives the error ORA-01161
how can resolve the problem

i am already using the REUSE option
CREATE CONTROLFILE REUSE DATABASE "ora10g1" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 454
LOGFILE
GROUP 1 'C:\ORA10GDB\ORADATA\Backups1\REDO01.LOG' SIZE 10M,
GROUP 2 'C:\ORA10GDB\ORADATA\Backups1\REDO02.LOG' SIZE 10M,
GROUP 3 'C:\ORA10GDB\ORADATA\Backups1\REDO03.LOG' SIZE 10M
-- STANDBY LOGFILE
DATAFILE
'C:\ORA10GDB\ORADATA\BACKUPS1\SYSTEM01.DBF',
'C:\ORA10GDB\ORADATA\BACKUPS1\UNDOTBS01.DBF',
'C:\ORA10GDB\ORADATA\BACKUPS1\SYSAUX01.DBF',
'C:\ORA10GDB\ORADATA\BACKUPS1\USERS01.DBF',
'C:\ORA10GDB\ORADATA\BACKUPS1\EXAMPLE01.DBF',
'C:\ORA10GDB\ORADATA\BACKUPS1\PLAY01DF.DBF'
CHARACTER SET WE8MSWIN1252
Test Database name : ora10g
New database name :ora10g1
I am using the same machine to create the new database.

ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'

Hi, All -
This is my first time cloning a database. The recovery finished but gave me the following error message. All the parameters in the pfile are set to "DEV1". I believe that the parameter db_name 'PROD1' exists in the control file and causing this error. The control file is under ASM.
How can I change the parameter in the control file and bring the 'DEV1' cloned database up? Also, how can I avoid this issue next time I do a clone?
Thanks in advance!
Oracle 10g Release 2 on RHEL5
Database cloning using RMAN Duplicate > ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'
ASMCMD> ls
control01.ctl
current.275.729098001
archive log filename=/u001/dbsvr/dev1/1_131706_653848580.dbf recid=59 stamp=741953991
media recovery complete, elapsed time: 00:09:31
*Finished recover at 01-FEB-11*
contents of Memory Script:
   shutdown clone;
   startup clone nomount ;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area     725614592 bytes
Fixed Size                     2075592 bytes
Variable Size                448791608 bytes
Database Buffers             268435456 bytes
Redo Buffers                   6311936 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DEV1" RESETLOGS ARCHIVELOG
MAXLOGFILES     50
MAXLOGMEMBERS      5
MAXDATAFILES      100
MAXINSTANCES     1
MAXLOGHISTORY     5445
LOGFILE
GROUP 1 '+DATA3/dev1/datafile/redo01.log' SIZE 100 M ,
GROUP 2 '+DATA3/dev1/datafile/redo02.log' SIZE 100 M ,
GROUP 3 '+DATA3/dev1/datafile/redo03.log' SIZE 100 M
DATAFILE
'+DATA3/dev1/datafile/system01.dbf'
CHARACTER SET WE8ISO8859P1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/01/2011 10:30:17
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'
RMAN>
RMAN> **end-of-file**
RMAN>

Respected, Sybrand Bakker -
Thanks for constructive feedback!
Here are the command that I ran.
RMAN> connect target sys/<password>@PROD1
connected to target database: PROD1 (DBID=556212836)
RMAN> connect auxiliary sys/<password>
connected to auxiliary database: DEV1 (not mounted)
RMAN> @rman_dup.sql
rman_dup.sql contains
run {
    allocate auxiliary channel d1 type disk;
set newname for datafile 1 to '+DATA3/dev/datafile/system01.dbf';
set newname for datafile 2 to '+DATA3/dev/datafile/undotbs01.dbf';
set newname for datafile 3 to '+DATA3/dev/datafile/cwmlite01.dbf';
set newname for datafile 4 to '+DATA3/dev/datafile/drsys01.dbf';
set newname for datafile 5 to '+DATA3/dev/datafile/example01.dbf';
set newname for datafile 6 to '+DATA3/dev/datafile/indx01.dbf';
set newname for datafile 7 to '+DATA3/dev/datafile/odm01.dbf';
set newname for datafile 8 to '+DATA3/dev/datafile/tools01.dbf';
set newname for datafile 9 to '+DATA3/dev/datafile/users01.dbf';
set newname for datafile 10 to '+DATA3/dev/datafile/xdb01.dbf';
set newname for datafile 11 to '+DATA3/dev/datafile/cons01.dbf';
set newname for datafile 12 to '+DATA3/dev/datafile/survey01.dbf';
set newname for datafile 13 to '+DATA3/dev/datafile/mem201.dbf';
set newname for datafile 14 to '+DATA3/dev/datafile/cons02.dbf';
set newname for datafile 15 to '+DATA3/dev/datafile/mem202.dbf';
set newname for datafile 16 to '+DATA3/dev/datafile/cater01.dbf';
set newname for datafile 17 to '+DATA3/dev/datafile/users02.dbf';
set newname for datafile 18 to '+DATA3/dev/datafile/mar_data01.dbf';
set newname for datafile 19 to '+DATA3/dev/datafile/sysaux01.dbf';
set newname for datafile 20 to '+DATA3/dev/datafile/streams_tbs_01.dbf';
set newname for datafile 21 to '+DATA3/dev/datafile/users03.dbf';
set newname for tempfile 1 to '+DATA3/dev1/tempfile/temp01.dbf';
duplicate target database to dev1
until scn 48712532746
logfile
   '+DATA3/dev1/datafile/redo01.log' size 100M,
   '+DATA3/dev1/datafile/redo02.log' size 100M,
   '+DATA3/dev1/datafile/redo03.log' size 100M;
}Edited by: CipherDBA on Feb 3, 2011 10:50 AM

ORA-04091: table name is mutating, trigger/function may not see it

Hi,
I have a row level before update trigger written on a table A which calls a procedure to undergo some processing. Procedure has some select queries against table A and it inturn causes the following error.
ORA-04091: table name is mutating, trigger/function may not see it
To overcome this I have used a combination of PL/SQL collection types (nested tables based on the following definition TYPE t_table_a is table of A.colname%TYPE index by binary_integer;), a row level before update trigger and statement level after update trigger. The mutating problem is fixed, but to update one row of data it took around 3 min and I am wondering if its the problem with PL/SQL tables I have used.
In before update trigger I am storing the unique id's which needs to be updated into the PL/SQL table and in the after update trigger I am looping through the PL/SQL table and peforming the rest of the processing by calling in the procedure.
Can anyone help how to minimize the run time of this process or if any other better solution exists?
Thanks for the help

Triggers raise the mutating table issue, because else they could be used to create endless loops. If you work around the mutating table issue, then you should make sure not to create an endless loop yourself. This would be possible.
You description also seems to imply something like this.
Without code it is impossible to say something specific.
- Do you initialize your collection in a before statement trigger?
- Is your looping mechanism somehow broken?
- Do you update the same table again and again and again?

Help for: ORA-01103: database name PRIMARY in control file is not STANDBY

Hello all, this will be my first post to the support forum. I'm an associate dba with just 6 months on the job, so if I've forgotten something or not given some infromation that is needed please let me know.
I've also combed the forums/internet, and some of the answers haven't helped. The Oracle Document ORA-1103 While Mounting the Database Using PFILE [ID 237073.1] says my init.ora file is corrupted, but creating a new init.ora file from the spfile does not help. Neither does just starting from the spfile. I have older copies of the init.ora file and the spfiles that the database was running on previously, so I believe they are good.
This standby NIRNASD1 has existed previously, I had to refresh the primary NIKNASD2, and then re-instantiate NIRNASD1 after the refresh is complete.
My env is set correctly, and my ORACLE_SID has been exported to NIRNASD1
NIKNASD2 = Primary Database
NIRNASD1 = Secondary/Standby Database
Goal: Creation of Logical Standby NIRNASD1 after creating Physical Standby from NIKNASD2
My database versions are 10.2.0.4.0, and the databases are on a Unix server. Both databases are located on separate servers.
Steps that I have taken:
I used RMAN to backup our primary database to the staging area:
$ rman target /
run {
backup database
format '/datatransa/dg_stage/%U'
include current controlfile for standby;
sql "alter system archive log current";
backup archivelog all format '/datatransa/dg_stage/%U';
I used RMAN to Create Secondary Database utilizing RMAN DUPLICATE command.
RMAN> run {
2> allocate auxiliary channel auxdisk device type disk;
3> duplicate target database for standby NOFILENAMECHECK;
4> }
On Secondary database I started Managed Recovery mode
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
(I used pfile here, thinking that I needed to mount the database to the pfile so that the database would see the change in the dataguard parameters in the init.ora file, the change from logical to physical- I commeneted out the logical and uncommented the physical line)
# Dataguard Parameters
For logical standby, change db_name to name of standby database.
db_name=NIKNASD2 ### for physical, db_name is same as primary
#db_name=NIRNASD1 ### for logical, db_name is same as unique_name
SQL> STARTUP MOUNT PFILE = /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/initNIRNASD1.ora;
ORACLE instance started.
Total System Global Area 1577058304 bytes
Fixed Size 2084368 bytes
Variable Size 385876464 bytes
Database Buffers 1174405120 bytes
Redo Buffers 14692352 bytes
Database mounted.
SQL> ALTER DATABASE recover managed standby database using current logfile disconnect;
I then verified the Data Guard Configuration by using “alter system archive log current;” on the primary database and watching the sequence number change in the secondary database.
I made sure that:
•     The primary database was in MAXIMUM PERFORMANCE MODE
•     Stopped managed recover on the standby database: alter database recover managed standby database cancel;
•     Built a logical standby data dictionary on the primary database
•     The db_name in init.ora was changed (this is in our document at my job)
•     I changed my database name (from physical to logical) in my init.ora pfile (reverse of what I did above)
# Dataguard Parameters
For logical standby, change db_name to name of standby database.
#db_name=NIKNASD2 ### for physical, db_name is same as primary
db_name=NIRNASD1 ### for logical, db_name is same as unique_name
I then went to shutdown my standby database and re-start it in a mount exclusive state, which is where I get the ORA-01103 Error (Again I used the pfile, thinking that I needed to tell the database it is now a logical standby):
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP EXCLUSIVE MOUNT PFILE = /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/initNIRNASD1.ora;
ORACLE instance started.
Total System Global Area 1577058304 bytes
Fixed Size 2084368 bytes
Variable Size 385876464 bytes
Database Buffers 1174405120 bytes
Redo Buffers 14692352 bytes
ORA-01103: database name 'NIKNASD2' in control file is not 'NIRNASD1'
From what I understand of the process, the name in the control file is correct, I want it to be NIRNASD1. But the database for some reason thinks it should be NIKNASD2. The following are the parts of my init.ora file that include the dataguard parameters:
# Database Identification
db_domain=""
#db_name=NIRNASD1
#db_unique_name=NIRNASD1
# File Configuration
control_files=("/oradba2/oradata/NIRNASD1/control01.ctl", "/oradba3/oradata/NIRNASD1/control02.ctl", "/oradba4/oradata/NIRNASD1/control03.ctl")
# Instance Identification
instance_name=NIRNASD1
# Dataguard Parameters
#db_name=NIKNASD2 ### for physical, db_name is same as prmary
db_name=NIRNASD1 ### for logical, db_name is same as unique_name
db_unique_name=NIRNASD1
dg_broker_start=TRUE
db_file_name_convert='NIKNASD2','NIRNASD1'
log_file_name_convert='NIKNASD2','NIRNASD1'
log_archive_config='dg_config=(NIRNASD1,NIKNASD2)'
log_archive_dest_1='LOCATION="/oraarcha/NIRNASD1/" valid_for=(ONLINE_LOGFILES,all_roles) db_unique_name=NIRNASD1'
#log_archive_dest_2='LOCATION="/oraarcha/NIKNASD2/" valid_for=(standby_logfiles,standby_roles) db_unique_name=NIRNASD1'
log_archive_dest_2='LOCATION="/oraarcha/NIKNASD2/" valid_for=(standby_logfile,standby_role) db_unique_name=NIRNASD1'
STANDBY_ARCHIVE_DEST='LOCATION=/oraarcha/NIKNASD2/'
# Parameters are not needed since this server will NOT become primary
#log_archive_dest_2='service=NIKNASD2
# valid_for=(online_logfiles,primary_role)
# db_unique_name=NIKNASD2'
fal_server='NIKNASD2'
fal_client='NIRNASD1'
I would appreciate any help, or pointing me in the right direction. I'm just missing something. I am reviewing the documents for building a physical and logical standby from oracle. Just not sure where to go from here.
Thank you
Edited by: 977917 on Dec 19, 2012 5:49 PM

First of all, thank you both for answering my post. I've pulled up Mr. Hesse's page and will make it a go-to staple.
We're in the process of upgrading our databases, but we have 130+ databases and only six Oracle dba's, and I'm one of them. It's a large corporation, and things move at a "slow and tested" pace.
The pfile parameters listed above are from my secondary/standby database. And I do want to create a logical standby.
I forgot to mention that we do use DataGuard Broker, but I did not think that would be the cause of why the database was starting up incorrectly, so I did not mention it. My apologies there.
As far as the db_name, here's my question on that. It's my understanding the the db_name should be the name of the primary database when you are working with a physical standby, but as soon as you convert it to logical, you should change the db_name to the secondary/standby database? Am I correct on that?
Leading from that, during the process of creating the physical standby and converting the physical standby to the logical standby, should I change the db_name in the secondary/standby database in the spfile and never use the pfile at all? For instance, when I create the physical standby I have to change the db_name in the standby to the PRIMARY database, so that makes me think I should change db_name in the spfile? (If you see above, I changed db_name in the pfile and did a startup pfile)
This morning I was able to reach out to a fellow DBA (they are were asleep when I posted this last night), and they tried a few things. We had a redirect in the standby directory /oraa/app/oracle/product/1020/dbs folder that looked like this: spfileNIRNASD1.ora -> /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/spfileNIRNASD1.ora
She removed the redirect and the startup mount exclusive then worked without the error.
Thank you again for your help Mr.Quluzade and Mr. Hesse, I appreciate you all taking the time to teach someone new to the craft. I will definitely read up on the link that you sent me.
Chris Cranford

ORA-07202 sltln: invalid parameter to sltln.using dbca to create 11g

OS:Red Hat Linux 5
DB :11.2.0.2
i am getting this error while creating 11g DB using DBCA ORA-07202 sltln: invalid parameter to sltln.using dbca to create

user13549752 wrote:
OS:Red Hat Linux 5
DB :11.2.0.2
i am getting this error while creating 11g DB using DBCA ORA-07202 sltln: invalid parameter to sltln.using dbca to create
07202, 00000, "sltln: invalid parameter to sltln."
// *Cause: The sltln name translation routine was called with invalid
// arguments. The input, or output stings were either NULL or 0 length.
// *Action: Probable internal oracle error. Contact customer support.I suspect you failed to Read The Fine Manual, Installation Guide

ORA-20100: Column name undefined invalid Error - Table splitting

Hi
While tablesplitting in our upgraded ECC6.0 (EHP4) system, we are facing the below error
BEGIN table_splitter.ranges('SOFFCONT1','undefined',5,'/tmp/sapinst_instdir/ERPEhP4/LM/COPY/ORA/EXP/CENTRAL/AS-ABAP/PRETABSPLIT/Split/DATA'); END;
ERROR at line 1:
ORA-20100: Column name undefined invalid
ORA-06512: at "SAPR3.TABLE_SPLITTER", line 775
ORA-06512: at line 1
In our R3hint file we have the below entry, but still we face the issue.
(kdecc01)#cat R3ta_hints.txt | grep SOFF
SOFFCONT1 PHIO_ID
Has anyone faced this issue before?
Senthil

see SAP note 1043380
Ensure the directory being reference does actually exist and ensure
privilege are provided for access. Also, a Directory Alias should be
used instead of the database parameter UTL_FILE_DIR which has been
deprecated.
Grant the READ or WRITE privileges to the username accessing the
DIRECTORY.
Ensure that the file being read does exist and actually contains
information to be read.
regards,
Vincent

ORA-02084: datbase name is missing a component

Hello,
I am attemtping to configure OMS using EMCA on Windows XP. I get the following errors:
ORA-02084: datbase name is missing a component
Creating local database with SID "OEMREP"...
C:\oracle\ora92\bin\launch.exe C:\oracle\ora92\assistants\dbca dbca.cl -progress_only -emca_internal -createDatabase -templateName Transaction_Processing.dbc -gdbName OEMREP.hsd1.va.comcast.net. -sid OEMREP
Failed to create local database.Processing failed.
Question is what component is the database missing and how do I resolve it?
Thanks.

Try this one:
CREATE DATABASE LINK "SYNO.DELTEMIPPM.HUTCH.IN" connect to
STRMADMIN identified by STRMADMIN using 'SYNO.DELTEMIPPM.HUTCH.IN';
and then check whether the delink is working by the below mentioned command:
select * from tab@"SYNO.DELTEMIPPM.HUTCH.IN";
Regards,
Abhirup.
Kolkata, India.

ORA-15041: diskgroup space exhausted

Hi,
I've an Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
Some days ago I was receiving the error:
unable to extend segment in tablespace system
I looked at the tablespace table and this was the situation:
+DATA/evodb/datafile/system.270.720825887                SYSTEM               0,68359375 (GB)
+DATA/evodb/datafile/system.267.717679031                SYSTEM               1,953125 (GB)
+DATA/evodb/datafile/system.256.662113891                SYSTEM               14,775390625 (GB)
All files are autoextensible.
This was the situation of ASM diskgroup/file:
.PATH DN GROUP_NAME HEADER_STA FREE_MB OS_MB TOTAL_MB NAME FAILGROUP
/dev/asm0 0 ONLINELOG MEMBER 3434 6138 6138 ONLINELOG_0000 ONLINELOG_0000
/dev/asm1 0 ARCHIVELOG MEMBER 47529 48127 48127 ARCHIVELOG_0000 ARCHIVELOG_0000
/dev/asm10 8 DATA MEMBER 11412 48127 48127 DATA_0008 DATA_0008
/dev/asm11 9 DATA MEMBER 10995 51199 51199 DATA_0009 DATA_0009
/dev/asm12 0 DATA MEMBER 0 5115 5115 DATA_0010 DATA_0010
/dev/asm2 0 DATA MEMBER 11404 48127 48127 DATA_0000 DATA_0000
/dev/asm210 0 STORE MEMBER 152914 208500 208500 STORE_0000 STORE_0000
/dev/asm211 11 DATA MEMBER 49178 208500 208500 DATA_0011 DATA_0011
/dev/asm212 16 CANDIDATE 0 208500 0
/dev/asm213 12 DATA MEMBER 52546 228352 228352 DATA_0012 DATA_0012
/dev/asm3 1 DATA MEMBER 11390 48127 48127 DATA_0001 DATA_0001
/dev/asm4 2 DATA MEMBER 11398 48127 48127 DATA_0002 DATA_0002
/dev/asm5 3 DATA MEMBER 11403 48127 48127 DATA_0003 DATA_0003
/dev/asm6 4 DATA MEMBER 11401 48127 48127 DATA_0004 DATA_0004
/dev/asm7 5 DATA MEMBER 11403 48127 48127 DATA_0005 DATA_0005
/dev/asm8 6 DATA MEMBER 11402 48127 48127 DATA_0006 DATA_0006
/dev/asm9 7 DATA MEMBER 11389 48127 48127 DATA_0007 DATA_0007
My first doubt is:
why it was not able to extend itself as it had 3 files and 2 very small size?
Anyway I tried an alter tablespace add datafile, but:
SQL> alter tablespace system add datafile;
alter tablespace system add datafile
*+
ERROR at line 1:
ORA-01119: error in creating database file 'DATA'+
ORA-17502: ksfdcre:4 Failed to create file DATA+
ORA-15041: diskgroup space exhausted
Why I got this error? Every memeber had enough space and 1 even 52gb...
I had to had the disk asm212 at the DATA diskgroup. Then I was able to add the datafile.
Thanks in advance,
Samuel

hi,
i got this result from yr query
ASMDB_GROUP1     0     ASMDB_GROUP1_0000     20480     0     /dev/rhdisk4     UNKNOWN
ASMDB_GROUP1     1     ASMDB_GROUP1_0001     20480     0     /dev/rhdisk5     UNKNOWN
ASMDB_GROUP3     0     ASMDB_GROUP3_0000     20480     0     /dev/rhdisk8     UNKNOWN
ASMDB_GROUP3     1     ASMDB_GROUP3_0001     20480     0     /dev/rhdisk9     UNKNOWN
ASMDB_GROUP4     0     ASMDB_GROUP4_0000     20480     0     /dev/rhdisk10     UNKNOWN
ASMDB_GROUP4     1     ASMDB_GROUP4_0001     20480     0     /dev/rhdisk11     UNKNOWN
it means i dont have any free space, so can i add space in group1 ?
can i add space from another diskgroup to diskgroup1 ?
DO I NEED TO shudown my databsae ?
THXS

Rman transportable tablespace ORA-39087: directory name is invalid

Hello all,
We are trying to restore a backup of a tablepace using RMAN's TRANSPORTABLE TABLESPACE command. I created the director in oracle (and it exists on the server), granted privs yet it fails with ORA-39087: directory name is invalid. It seems to fail at the end. Here's my steps, does anyone know how to fix? Thanks in advance for your time!
Dave
CREATE DIRECTORY ARCH_DIR as '/opt/oracle/arch';
GRANT IMP_FULL_DB, EXP_FULL_DB TO SYS, RMAN, SYSTEM;
GRANT READ, WRITE ON DIRECTORY ARCH_DIR TO SYS, RMAN, SYSTEM;
export ORACLE_SID=ADMIN_P1
rman target / catalog rman/rmanpassword@mydb
TRANSPORT TABLESPACE REPORTER
TABLESPACE DESTINATION '/opt/oracle/arch'
AUXILIARY DESTINATION '/opt/oracle/arch'
UNTIL SCN 2144439724
DATAPUMP DIRECTORY ARCH_DIR
DUMP FILE 'reporter.dmp'
IMPORT SCRIPT 'reporter.imp'
EXPORT LOG 'reporter.log';

Creating a directory object inside the database does not create anything in the operating system. My guess is that the physical directory, with appropriate permissions, does not exist.

ORA-15030: diskgroup name "dg1" is in use by another diskgroup

Similar Messages

Maybe you are looking for