Thursday, June 26, 2014

Oracle Application forms in Firefox

Mozilla Firefox ESR is certified as a Windows-based client browser for Oracle E-Business Suite 11i, 12.0, 12.1, and 12.2. 

Not all the versions of Firefox will be able to open the Oracle Applications forms. Only the ESR version could be used to open forms in Oracle Applications.

Download the software from the following link and install on your windows machine.

https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/24.1.0esr/win32/en-US/

Try launching Oracle Application forms now in Firefox.


To view the version of Firefox goto Help-->Options-->About Firefox.


Host key verification failed.

I was trying to scp files from one server to another server.

when I hit scp it scolded me that "Host key verification failed."

[appprd@host01 PRD]$ scp -pr xxlpr apptst@host02.domain.com:/u02/app/apptst/
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE host01 IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA Host key has just been changed.
The fingerprint for the RSA key sent by the remote host01 is
80:f3:c5:26:16:d1:9a:23:8d:c9:00:44:84:75:1a:7f.
Please contact your system administrator.
Add correct host01 key in /u01/app/appprd/.ssh/known_hosts to get rid of this message.

Offending key in /u01/app/appprd/.ssh/known_hosts:5
RSA host01 key for host02.domain.com has changed and you have requested strict checking.

Host key verification failed.

lost connection

Cuase: The same Host was registered with different key in $HOME/.ssh/known_hosts file


Solution:

Temporary: mv /u01/app/appprd/.ssh/known_hosts /u01/app/appprd/.ssh/known_hosts_old. Once the job is done replace again.

Permanent(in fact correct): remove the host01 key entry from $HOME/.ssh/known_hosts.

When you try scp again it will prompt you to add the new key, say yes. The new key will be added in known_hosts file. 

Now it will not give your the error.

[appprd@host01 PRD]$ mv /u01/app/appprd/.ssh/known_hosts /u01/app/appprd/.ssh/known_hosts_old
[appprd@host01 PRD]$ scp -pr xxlpr apptst@host02.domain.com:/u02/app/apptst/

The authenticity of Host 'host02.domain.com (192.168.1.102)' can't be established.
RSA key fingerprint is 80:f3:c5:26:16:d1:9a:23:8d:c9:00:44:84:75:1a:7f.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'host02.domain.com,192.168.1.102' (RSA) to the list of known hosts.
apptst@host02.domain.com's password:

RMAN-06026: some targets not found - aborting restore during clone

I got this error when I was trying to clone TEST from PROD using duplicate method.

released channel: c1

released channel: c2

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 06/25/2014 00:00:49

RMAN-03015: error occurred in stored script Memory Script

RMAN-06026: some targets not found - aborting restore

RMAN-06023: no backup or copy of datafile 584 found to restore

RMAN-06023: no backup or copy of datafile 583 found to restore

RMAN-06023: no backup or copy of datafile 582 found to restore

RMAN-06023: no backup or copy of datafile 581 found to restore

RMAN-06023: no backup or copy of datafile 580 found to restore

RMAN-06023: no backup or copy of datafile 579 found to restore

RMAN-06023: no backup or copy of datafile 578 found to restore

RMAN-06023: no backup or copy of datafile 577 found to restore

RMAN-06023: no backup or copy of datafile 576 found to restore

RMAN-06023: no backup or copy of datafile 575 found to restore

RMAN-06023: no backup or copy of datafile 574 found to restore

RMAN-06023: no backup or copy of datafile 573 found to restore

RMAN-06023: no backup or copy of datafile 572 found to restore

RMAN-06023: no backup or copy of datafile 571 found to restore

RMAN-06023: no backup or copy of datafile 570 found to restore

RMAN-06023: no backup or copy of datafile 569 found to restore

RMAN-06023: no backup or copy of datafile 568 found to restore

RMAN-06023: no backup or copy of datafile 567 found to restore

RMAN-06023: no backup or copy of datafile 566 found to restore

RMAN-06023: no backup or copy of datafile 565 found to restore

RMAN-06023: no backup or copy of datafile 564 found to restore

RMAN-06023: no backup or copy of datafile 563 found to restore

RMAN-06023: no backup or copy of datafile 562 found to restore

RMAN-06023: no backup or copy of datafile 561 found to restore

RMAN-06023: no backup or copy of datafile 560 found to restore

RMAN-06023: no backup or copy of datafile 559 found to restore

RMAN-06023: no backup or copy of datafile 558 found to restore

RMAN-06023: no backup or copy of datafile 557 found to restore

RMAN-06023: no backup or copy of datafile 556 found to restore

RMAN-06023: no backup or copy of datafile 555 found to restore

RMAN-06023: no backup or copy of datafile 554 found to restore

RMAN-06023: no backup or copy of datafile 553 found to restore

RMAN-06023: no backup or copy of datafile 552 found to restore

RMAN-06023: no backup or copy of datafile 551 found to restore

RMAN-06023: no backup or copy of datafile 550 found to restore

RMAN-06023: no backup or copy of datafile 549 found to restore

RMAN-06023: no backup or copy of datafile 548 found to restore

RMAN-06023: no backup or copy of datafile 547 found to restore

RMAN-06023: no backup or copy of datafile 546 found to restore

RMAN-06023: no backup or copy of datafile 545 found to restore

RMAN-06023: no backup or copy of datafile 544 found to restore

RMAN-06023: no backup or copy of datafile 543 found to restore

RMAN-06023: no backup or copy of datafile 542 found to restore

RMAN-06023: no backup or copy of datafile 541 found to restore

RMAN-06023: no backup or copy of datafile 540 found to restore

RMAN-06023: no backup or copy of datafile 539 found to restore

RMAN-06023: no backup or copy of datafile 538 found to restore

RMAN-06023: no backup or copy of datafile 537 found to restore

RMAN-06023: no backup or copy of datafile 536 found to restore

RMAN-06023: no backup or copy of datafile 535 found to restore

RMAN-06023: no backup or copy of datafile 534 found to restore

RMAN-06023: no backup or copy of datafile 533 found to restore

RMAN-06023: no backup or copy of datafile 532 found to restore

RMAN-06023: no backup or copy of datafile 531 found to restore

RMAN-06023: no backup or copy of datafile 530 found to restore

RMAN-06023: no backup or copy of datafile 529 found to restore

RMAN-06023: no backup or copy of datafile 528 found to restore

RMAN-06023: no backup or copy of datafile 527 found to restore

RMAN-06023: no backup or copy of datafile 526 found to restore

RMAN-06023: no backup or copy of datafile 525 found to restore

RMAN-06023: no backup or copy of datafile 524 found to restore

RMAN-06023: no backup or copy of datafile 523 found to restore

RMAN-06023: no backup or copy of datafile 522 found to restore

RMAN-06023: no backup or copy of datafile 521 found to restore

RMAN-06023: no backup or copy of datafile 520 found to restore

RMAN-06023: no backup or copy of datafile 519 found to restore

RMAN-06023: no backup or copy of datafile 518 found to restore

RMAN-06023: no backup or copy of datafile 517 found to restore

RMAN-06023: no backup or copy of datafile 516 found to restore

RMAN-06023: no backup or copy of datafile 515 found to restore

RMAN-06023: no backup or copy of datafile 514 found to restore

RMAN-06023: no backup or copy of datafile 513 found to restore

RMAN-06023: no backup or copy of datafile 512 found to restore

MAN-

RMAN>



Recovery Manager complete.



The backup is mounted on TEST with the same directory structure. I am surprised how the backup does not have the specified datafiles as I have already verfied the backup log before starting the activity.

I checked the whether any access privilige issue with the backup. It is not, the backups are accessible without issues.

The backups available in

-bash-3.00$ cd /u03/backup/PRD

-bash-3.00$ ls -ltr

total 40

drwxrwxrwx  2 21000 21000 8192 Jun 23 07:32 day1

-rw-r--r--  1 21000 21000    0 Jun 24 23:50 day3.last

drwxrwxrwx  2 21000 21000 8192 Jun 25 00:11 day2

drwxr-xr-x  2 21000 21000 4096 Jun 25 02:11 day3


When a backup starts it removes the oldest one and creates new directory. My backup was in day3 now its renamed to day2.

I fired the restore script just before the new backup starts. Hence the rman could not identify the backup pieces.

Cuase: Backup directory structure changed at OS level and not in sync with RMAN repository.


Solution:
---------
crosscheck backup;
reinitiate the restore script;




NLS boot file not found or invalid opmnctl ping – EBS 12.2 ADCFGCLONE FAIL

Error: adcfgclone.pl failed while performing clone of EBS 12.2 instance. This occurred while ohsT2PApply is in progress. INST_TOP/adm...