Amazon books

Friday, June 26, 2015

Errors RMAN-03002 and RMAN-06571 While running SWITCH DATABASE TO COPY on Standby Database

If you are doing a rollforward of a standby database and in the middle of the process got errors like below:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch to copy command at 06/26/2015 23:08:53
RMAN-06571: datafile 301 does not have recoverable copy


Don't worry, you just need to catalog the datafile in question using this command below:

catalog datafilecopy '+DG_EBS_DATA/bwebspr_glt_p7/datafile/apps_ts_tx_idx.584';


You can also use this query below to build the command to you quickly:

select 'catalog datafilecopy '''||name||''';' from v$datafile where file#=301;



After doing that for all problematic datafiles you can finish your rollforward process.


Best Regards,
Paulo Portugal

Wednesday, May 20, 2015

RMAN-03002 ORA-19504 ORA-17502 ORA-15001 ORA-15040

I was trying to restore a standby control file to create a new standby database and got this error:

RMAN> run {
allocate channel c1 device type disk;
restore standby controlfile from '/home/orab2b/copia_ctl_stby.ctl';
release channel c1;
}
2> 3> 4> 5>
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=36 instance=BWB2BPR1 device type=DISK

Starting restore at 20-MAY-15

released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/20/2015 22:49:50
ORA-19504: failed to create file "+FRA/bwb2bpr/controlfile/control01.ctl"
ORA-17502: ksfdcre:3 Failed to create file +FRA/bwb2bpr/controlfile/control01.ctl
ORA-15001: diskgroup "FRA" does not exist or is not mounted
ORA-15040: diskgroup is incomplete
ORA-15040: diskgroup is incomplete
ORA-19600: input file is control file  (/home/orab2b/copia_ctl_stby.ctl)
ORA-19601: output file is control file  (+FRA/bwb2bpr/controlfile/control01.ctl)



To fox that, run this command below as GRID_HOME owner:

[bwdp0248-+ASM1]/u01/app/11.2.0.4/grid/bin>  ./setasmgidwrap o=/u01/app/oracle/product/11.2.0.4/dbb2b/bin/oracle  --HERE USE YOUR ORACLE RDBMS HOME



This fix my problem.

Best Regards,
Paulo Portugal

Monday, May 4, 2015

CellCLI> list cell CELL-01519: Cannot talk to the Management Server (MS). Error: ; nested exception is: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found CellCLI> exit

Hi guys,

I already got problems when I set my cell virtual machine with memory less than 1GB and also when I commented out the "127.x.x.x"  ip address in /etc/hosts file. But this error below was new for me.

To fix that in your TEST virtual machine of Exadata Cell, just do these following steps:

1-Stop the MS service



2-Redeploy the MS oc4j:


3-Start the MS processes:



Best Regards,
Paulo Portugal


Thursday, March 26, 2015

Great White Paper for 12c In-Memory Advisor

In this link below you can find a great white paper for In Memory Advisor:

http://www.oracle.com/technetwork/database/manageability/info/twp-in-memory-advisor-bp-2430474.pdf


Best Regards,
Paulo Portugal

Tuesday, March 10, 2015

Using DBMS_PASSTHROUGH to run command in SQL Server from Oracle

This simple example below update a table in SQL Server from Oracle:

declare
   l_num_rows number;
begin
  l_num_rows := dbms_hs_passthrough.execute_immediate@TMMASTER ('USE ORAIntegration_V2_test');
  commit;
  execute immediate 'alter session close database link TMMASTER';
  commit;
 
  l_num_rows := dbms_hs_passthrough.execute_immediate@TMMASTER ('UPDATE trans SET    a=333 WHERE  a=222 ');
  commit;
 
--  l_num_rows := dbms_hs_passthrough.execute_immediate@TMMASTER ('COMMIT TRANSACTION');
  commit;


  execute immediate 'alter session close database link TMMASTER';
  commit;
end;



select * from trans@TMMASTER;


Best Regards,
Paulo Portugal

Friday, March 6, 2015

The new Oracle Exadata Deployment Assistant - Fev 2015 - Elastic Rack, OVM, COD

Already including X5, Zero Data Loss and Super Cluster configuration options:

http://www.oracle.com/technetwork/database/exadata/oeda-download-2076737.html



The new OEDA have options to install Exadata, Zero Data Loss and Super Cluster


With Elastic option you can customize your Exadata (19 DB Nodes and 3 Cells for example) The maximum number os cell+db nodes is 23.


  The Hardware Options now have the Elastic Rack with Flash Disks (HP disks does not exists anymore) or HC Disks.
  You can choose to have a Virtualized Exadata or all physical db nodes. Also you can choose COD to save money on your software licenses.
 
Here you see one RAC with 19 nodes and 3 cells.  This is only one from many possibilities:
 
At the end, your template shows something like that:


Best Regards,
Paulo Portugal

DBMS_SCHEDULER CREDENTIAL ORA-27486 privilegios insuficientes

If you create an external job and is using a credential that already exists in another schema you will face this error below if not provide the necessary privilege for the using running the job :

SQL> conn / as sysdba
SQL> exec dbms_scheduler.run_job('MY_JOB');
BEGIN dbms_scheduler.run_job('MY_JOB'); END;

*
ERROR at line 1:
ORA-27486: privilegios insuficientes
ORA-06512: em "SYS.DBMS_ISCHED", line 196
ORA-06512: em "SYS.DBMS_SCHEDULER", line 486
ORA-06512: em line 1


Fix:

You should connect with the credential owner and grant the execute on that credential to the other user:

--Connect with the credential owner:
SQL> conn edi/edi
SQL> grant execute on edi.edi_credential to sys;
--Connect back to SYS
SQL> conn / as sysdba
Connected.
SQL> exec dbms_scheduler.run_job('MY_JOB');

PL/SQL procedure successfully completed.

SQL>



Best Regards,
Paulo Portugal