Forum Replies Created
ORA-600/ORA-7445 are oracle internal error. I would recommend using “My oracle support” (support.oracle.com) for debugging this issue
>>RMAN-05001: auxiliary file name /oracle/app/oradata/oas/redo01.log conflicts with a file used by the target database
Above error indicates that you are using cloning on same host or target host already has same files present. Most likely oas db is in open mode while you are trying to clone it again
Above data indicates that you should be using timestamp datatype
SQL> select to_date( ‘2012-09-28 02:00:00.000’, ‘YYYY-MM-DD HH24:MI:SS’) from dual;
select to_date( ‘2012-09-28 02:00:00.000’, ‘YYYY-MM-DD HH24:MI:SS’) from dual
ERROR at line 1:
ORA-01830: date format picture ends before converting entire input string
If I change this to timestamp it would work fine
select to_timestamp( ‘2012-09-28 02:00:00.000’, ‘YYYY-MM-DD HH24:MI:SS.FF’) from dual;
28-SEP-12 02.00.00.000000000 AM
I think you can do it using CTAS.
Suppose table emp has two columns empid,hiredate(varchar2)
create table emp_new as select empid,to_date(hiredate,'DD-MON-YYYY') hiredate from emp;
I believe above thing would work
As error states, you need to specify ‘as sysdba’. So it should be
sqlldr userid=sys/orcl as sysdba control=Spl_Master.ctl log=spl.log
Is this a normal redundancy diskgroup?
Stop crs and start using following command
crsctl start crs -excl -nocrs
Then try ocrconfig restore . It should work
Actually when you take backup on disk (assuming you have linked rman library with tape and set sbt_type) and are using catalog. Oracle will know which backup to restore. Check in Myoracle support for ‘rman tape’ and you will find many articles related to it.
I think you should check regarding licensing terms with Oracle sales representative. I believe if you restore on new server and use it for some number of days, you have to pay license cost. Not sure on this.
I have done ASM restore operation in past but don’t have documented steps. You will have to create the ASM Diskgroup disk’s prior to running the restore operation. Also if you are having any aliases like ‘+DG/orabcn (where orabcn is not oracle_sid), you will have to pre-create before starting restore.
I think what you require is disaster recover solution which is provided by using Oracle dataguard. So you can create a bcp for your existing RAC database which will help in case your primary RAC servers are gone. Also note that restoring from tape can take time, so you should have 1 backup copy on disk’s.30 June, 2011 at 5:46 am in reply to: CRS and ORACLE_HOME wiped out accidentally on node1 #2141
I think you can just copy the two oracle homes from other node and then run root102.sh/root.sh from CRS_HOME. No such thing is required for db home.
Transaction will keep running and it will generate redo and also write to datafiles. it is just that records will be marked uncommitted. RMAN will not wait for transaction to complete.
Suppose you took this rman backup and restored it. Once you apply redo which consists of “commit” point of this transaction, you can see the data. If you open the database before applying this redo, the changes will be rolled back
Apologies, didnt read the question properly. I have not seen any configuration using different catalog for primary and standby (there could be but I havent seen it). Moreover purpose of using rman at standby site is to reduce workload on primary so that in case of failure you can restore the backup. In case of failure, you would need to connect to this very catalog. Anyways I think you can register first primary database at catalog and then take standy backups.
Checked docs (http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmcatdb.htm#CIHECCEF) and they mention that registration can only be done at primary database.
You are not required to register standby database in recovery catalog. Oracle will understand that this is standby database (even though they share same dbid)
Hope this helps
When you don’t define failgroup while creating normal redundancy diskgroup, oracle would automatically create diskgroup for you. Run following query to identify this
select name,path,failgroup,header_status from V$ASM_DISKGROUP;